Choose a first-party boundary
Pricing exceptions, refund review, agent tool actions, and CRM write-back are the maintained reference patterns.
Developer Hub
Choose the boundary. Follow the proof.
Start with the software action you need to govern. Run a working shape, create one Decision Record, verify it, then request production access for that boundary.
The shortest complete path
Each step has a public artifact. Production access comes after the request shape and proof model are clear.
1. BoundaryName one state-changing action.
2. ExampleStart from a working request shape.
3. SDK or HTTPSCall the server-side Decision API.
4. RecordStore verdict, evidence, and hashes.
5. VerifyCheck integrity and authenticity.
6. LaunchKey and meter the live boundary.
Enter by objective
The catalog routes to the existing deep references. It does not create pretend provider pages or duplicate the full documentation.
Bind the decision to execution
Use CRM, billing, automation, queue, or agent guidance to preserve idempotency and record context through the state change.
Install the shipped JavaScript client
The public npm package includes the client, types, verifiers, Rulebook v1 conformance runner, examples, and fixtures.
Select the correct trust surface
Policy Notaries is public and read-only. Decision Runtime MCP handles customer-owned records in a separate private preview.
Check a record before relying on it
Use the hosted verifier, API, SDK, Ed25519 registry, or pinned trust material to verify Decision Records and packets.
Inspect operational evidence
Read the security boundary, live proof artifact, status packet, and changelog before production rollout.
The same catalog is machine-readable
The public catalog names only implemented protocols, maintained reference patterns, public integrations, shipped SDK commands, and the current MCP visibility boundary.
Public catalog
curl https://www.decide.fyi/api/public/catalogWell-known entry
curl https://www.decide.fyi/.well-known/decide.json