Policy evidence
Policy Snapshot and Reason Codes identify the policy artifact and explain the governed outcome without exposing client-side policy logic.
Loading…
API documentation
Execution Map
The Execution Map is the compact proof view for how a Decionis-governed action travels from intent capture to outcome, evidence, and handoff. It is derived from protocol artifacts, so native surfaces, SDKs, web, and public API all resolve through the same evidence model.
Map
Use this sequence when explaining Decionis to reviewers who need the whole control path in one screen.
| Stage | What it proves |
|---|---|
| 1. Intent | Application, SDK, API route, or native surface captures execution intent. |
| 2. Evaluation | Decionis resolves the governed outcome through /v1/protocol/evaluate-decision. |
| 3. Policy Snapshot | Response records policy version, bundle ID, and immutable digests. |
| 4. Reason Codes | Stable explanation vocabulary travels with the response and dossier. |
| 5. Decision Dossier | Per-decision audit artifact records outcome, evidence, and verification links. |
| 6. Decision Chain | Related evaluations are linked into workflow lineage when supplied. |
| 7. Ledger | Hash-linked audit ledger records protocol artifact integrity. |
| 8. Dispatch or handoff | Execution continues, stops, escalates, or hands off through the surface. |
Artifact roles
Each artifact owns one part of the proof story.
Decision evidence
Decision Dossier and public verification show what Decionis decided, which evidence was recorded, and how reviewers can verify it.
Workflow evidence
Decision Chain and Override Trail connect related decisions, appeals, and reviewer outcomes to the original dossier.
Rollout evidence
Shadow Reports and Execution Dispatch records show how observe-only paths mature into controlled enforcement.
Routes
The map is assembled from protocol routes rather than a separate reporting API.
| Artifact | Route |
|---|---|
| Decision Evaluation | POST /v1/protocol/evaluate-decision |
| Policy Snapshot | policy_snapshot on evaluate-decision and Decision Dossier payloads |
| Reason Codes | GET /v1/protocol/reason-codes and reason_codes on responses |
| Decision Dossier | GET /v1/protocol/dossiers/:dossierId |
| Public verification | GET /v1/public/decision-dossiers/:dossierId/verify |
| Decision Chain | GET /v1/protocol/decision-chains/:chainId |
| Override Trail | GET /v1/protocol/dossiers/:dossierId/overrides |
| Shadow Reports | GET /v1/protocol/shadow-reports |
| Ledger | GET /v1/protocol/audit/ledger and /v1/protocol/audit/ledger/verify |
| Execution Dispatch | POST /v1/protocol/executions/dispatches |
Workspace use
The workspace can render the map as a timeline: active proof in the center, supporting cards on either side.
{
"execution_map": {
"intent": "OPEN_POSITION",
"outcome": "ESCALATE",
"policy_snapshot": "/docs/policy-snapshot",
"reason_codes": ["PROTOCOL_OUTCOME_ESCALATE", "POLICY_MATCHED"],
"dossier_id": "22222222-2222-4222-8222-222222222222",
"decision_chain": {
"chain_id": "77777777-7777-4777-8777-777777777777",
"integrity_verified": true
},
"handoff": "REVIEW"
}
}Homepage boundary
Keep artifact detail in docs and evidence pages so the homepage remains proof-led and compact.
Evidence index is the packaging layer
Use /docs/decision-evaluation for the canonical call, /docs/decision-dossier for per-decision proof, and /evidence for the one-screen shipped artifact map.