Solutions · Contracts
Every agreement checked, chased, and filed. Every signature and every dollar behind a person.
Contract administration is four questions asked of every document, every day: is it complete, is it signed, is it expiring, and is it worth more than someone's authority. Those are rules. Razoo runs them at zero tokens, learns the routing and the drafting from your administrators, and never lets a rule request a signature or accept a value on its own.
The four checks
Rules first. Zero tokens, fully replayable.
Each check is a rule in the agent folder with a closed condition: field, eq, gte, lte, exists, all, any. Doctor validates it. Replay certifies it. An auditor can read it.
Completeness
Signature status
Expiry within 30 days
Value above threshold
The queue
Incoming, signature, expiry. One click each.
Incoming contract, signature request, and expiry review. The queue packs the document fields, walks the ladder, and shows the administrator only what the rules and patterns could not settle.
- A document that passes every check is filed by a rule and the Decision says which rule and version.
- A missing counterparty signature stages request_signature. The row waits for a confirm.
- A value above threshold stages escalate_review to the named person. The value is never accepted by a rule.
- An unfamiliar clause goes to a model on a token contract, which may draft a note. It stages. It does not send.
- Harbour Build · subcontractRule
signature: ours missing
rule missing-signature v1 · staged request_signature
- Northgate Pty Ltd · servicesLearned
expires in 21 days
renewal note drafted · learned · certified
- Meridian Group · master agreementHuman
value 240,000
above threshold · money_legal · to the reviewer
- Unknown party · NDAModel
completeness: 2 missing
new counterparty · capable tier · 980 tokens
- Pellam Logistics · leaseRule
complete · fully signed
filed · rule complete-and-signed v2
Staged · Harbour Build
via docusign-envelope · envelope: action · confirm required
Checked this week
61
Needed the model
9
Signatures sent unconfirmed
0
DocuSign, PandaDoc, your CLM
A confirmed action becomes an HTTPS call. No handler code.
Connector YAML maps a declared action to an external API with templated fields from the staged payload and secrets by key name. Doctor checks that the action exists, the template fields are declared, the URL is HTTPS, and no credential is inline.
- The call runs in the outbox handler, after the person confirms and after the dependency-binding and envelope checks. At most once.
- The response is appended as a fact against the work item. It does not become business truth until accepted.
- HTTPS only, private-address guard, bounded body, same-host redirects. A non-2xx throws so retry and dead-letter apply.
- PandaDoc, or any signature or CLM API, is the same file with a different URL and body.
id: docusign-envelope label: DocuSign kind: webhook fields: - { key: DOCUSIGN_TOKEN, label: Access token, secret: true, required: true } verify: kind: present keys: [DOCUSIGN_TOKEN] actions: request_signature: method: POST url: https://na1.docusign.net/restapi/v2.1/accounts/${payload.acct}/envelopes headers: Authorization: Bearer secret:DOCUSIGN_TOKEN # by reference content-type: application/json body: templateId: ${payload.template_id} status: sent expected_status: 201 # runs in the outbox handler after confirm and the authority checks
illustrative · the connector contract and this DocuSign example file are both shipped
Learned versus always human
The routing and the drafting are learned. The signature and the value are not.
Learnable fields are declared in fields.yaml. contract_value is money_legal and counterparty identity is an identity key, so neither can appear in a learned WHEN clause. Doctor refuses the file otherwise.
- Which reviewer a document type and business unit goes to.
- Which renewal template to draft for which agreement type and counterparty category.
- Which completeness misses are worth an escalation and which a nudge.
- Which expiring agreements are let lapse, once replay against your administrators' own history certifies it.
certified by replay · a person promotes · revoked on counterexample
- Sending a signature request. It stages; a person confirms.
- Accepting or changing a contract value. money_legal; the execution rule is machine-checked.
- Anything about a counterparty the business has not dealt with before. Identity keys are never learnable.
- Anything outside the envelope the pattern was promoted with. An action outside the envelope does not stage.
pinned by tests that fail if a guard is removed
The reference contracts agent ships in the repository.
Everything above is what the kernel does with any agent folder that declares these fields, rules, and actions — and domains/reference-contracts is the packaged one: work types for incoming contract, signature request, and expiry review, the four rules, learnable fields, email routes, request_signature and escalate_review actions, and twenty synthetic fixture events. DocuSign and Xero example connectors ship beside it.
Bring a quarter of agreements. We will run the four checks on them.
Design partners in legal and operations run the reference contracts agent on their own infrastructure, with every signature and value behind a named person.