Playbook administration

Clauses

The Clause Library holds the drafted prose that backs your standards. Preferred, fallback and walk-away, each tagged with scope.

Preference levels

Preference	Meaning
`preferred`	The clause you would propose first. Drafting flows reach for this.
`fallback`	An acceptable secondary position when the preferred is pushed back.
`walk_away`	The floor. Marks a position you should not cross; drafting and counter-position flows surface a warning.

Scope

Clauses use the same scope model as standards. A liability clause keyed to agreement_type = MSA, jurisdiction = US-NY wins over a wildcard liability clause when drafting for a US-NY MSA. See Scope dimensions.

Derive from templates

Click Derive from templates to seed the library from the clauses actually appearing in your bound Templates folder. The platform extracts candidate clauses, you choose which to adopt and at what preference level.

Clauses vs standards

A standard is a one-line position (“Cap at 12× annual fees, mutual”). A clause is the full prose that implements it. Most obligation types only need a standard; sensitive areas (Liability, IP, DataProtection) usually want the prose too.

API access

Approved integrations can list clauses, create them, derive candidates from your bound Templates folder, and remove a clause by obligation type and label. See the Clauses API reference for the full request and response shapes.

Standards

Market practice toggle