templates / library
Pre-delegated work templates

The mandate, ready before the work.

A template is a signed, parameterized mandate: the actions an agent may take, the evidence each one must carry, the limits that apply, and who must sign. Bind one at session start and its hash is committed into the chain root; at seal, the work is evaluated against it; at verify, anyone re-checks conformance from the copy embedded in the package.

Seed library
Finance operations

invoice_approval

v2.0.0 · sha256:37c1…50c8

Agent review and approval of vendor invoices under a bound spending limit, with PO-match evidence required on every decision.

  • params: max_amount, currency, vendor_allowlist
  • actions: invoice_reviewed → payment_approved
  • signers: reviewer + vendor countersign
✓ available
Healthcare administration

prior_auth_submission

v0.1 · sha256:84cf…0d6c

Agent submission of prior authorizations. Evidence is reference-shaped: opaque patient and document references, with additional fields closed off so no payload rides along (supplying ids/hashes rather than PHI is the integrator's contract).

  • params: payer_allowlist
  • actions: task_created → submit_prior_auth
  • signers: clinician attestation (optional)
✓ available
Finance operations

expense_reimbursement

v0.1 · sha256:e360…8bbb

Agent-processed expense review and reimbursement authorization against a bound per-item ceiling and policy reference.

  • params: max_amount, currency
  • actions: expense_reviewed → reimbursement_authorized
  • signers: agent (authorized_by is a recorded reference, not a countersignature)
✓ available
Agent payments

bounded_spend_mandate

draft · AP2 / Verifiable Intent aligned

A spending mandate for autonomous purchase agents: scope, ceiling, merchant constraints, and settlement evidence, closing the loop between authorized intent and what actually happened.

  • params: ceiling, merchant_allowlist, window
  • actions: quote_accepted → payment_executed
in design · design partners welcome
Legal & professional

document_execution

draft

Delegated document work: drafting, filing, and docketing actions with document-hash evidence, so the receipt points at the work product without containing it.

  • params: matter_ref, filing_window
  • actions: document_prepared → filing_submitted
in design · design partners welcome
Yours

your_workflow

authored by you, signed by you

Templates are plain, signed JSON. If your agent takes an action that would matter in an audit or a dispute, it can be mandated, and we'll help design-partner pilots write their first one.

  • authoring guide: docs (coming with the pilot program)
start a pilot →
Anatomy of a template

Signed. Parameterized. Content-addressed.

Parameters make one mandate serve many delegationsThe template declares its variables; you bind the values ($5,000, this vendor list) at session start. Both the template hash and the bound-parameter hash are committed into the chain genesis.
Evidence schemas make actions provableEvery allowed action declares the evidence it must carry. Schemas resolve against your bound parameters and are re-checked, deterministically, by any verifier from the embedded copy.
Transitions make sequence a ruleAllowed transitions define the order work may take, a full state machine, not just a checklist, so skipping a required step is a recorded violation, not a mystery.
Signatures make authorship attributableTemplates are author-signed. Offline, that proves consistent authorship; anchor a registered key and it proves an author you trust.
{
  "template_id": "invoice_approval",
  "version": "2.0.0",
  "parameters": {
    "max_amount": { "type": "number", "required": true },
    "currency":   { "type": "string", "default": "USD" }
  },
  "actions": [
    {
      "actionType": "invoice_reviewed",
      "required": true,
      "evidence_schema": {
        "required": ["vendor","invoiceId","amount","decision"],
        "properties": {
          "amount": { "maximum": { "$param": "max_amount" } },
          "vendor": { "$allowlist": "vendor_allowlist" }
        }
      }
    },
    { "actionType": "payment_approved", "required": true }
  ],
  "allowed_transitions": {
    "invoice_reviewed": ["payment_approved"]
  },
  "attestations": { "counterparty": { "required": false } },
  "author": { "id": "sequesign", "signature": "<COSE>" }
}
// content-addressed: sessions pin this document's hash, never "latest"
Lifecycle of a mandate

Bound at genesis. Evaluated at seal. Re-checked by anyone.

BIND

Session start

Template resolved, parameters bound, both hashes committed into the chain root. From this moment the terms cannot be swapped, weakened, or "clarified" after the fact.

CONFORM

Seal time

Recorded work is evaluated against the mandate. Violations don't block sealing; they seal in, as signed evidence, and verification reports them to everyone.

RE-CHECK

Any verifier, forever

The package embeds the template and parameters. Anyone re-resolves and re-evaluates conformance offline, no registry, no account, no trust in us.

Design partner pilots · now open

Your workflow has a template waiting to be written.

Start a pilot Read the quickstart