Original stays intact
The original Decision Dossier remains the record of what Decionis decided at execution time.
Loading…
API documentation
Overrides
Overrides attach appeal, reviewer, and exception evidence to the original Decision Dossier. They preserve accountability for the human decision without changing the original governed outcome, and repeated override patterns become Policy Drift signals for governed policy evolution.
Model
The override record links back to the dossier, optional decision chain, actor identity, reason code, and reviewer outcome.
Appeal is linked
The override carries original_dossier_id, decision_evaluation_id, and decision_chain_id when available.
Reviewer outcome is separate
Review status, reviewer identity, notes, and evidence references live on the override trail.
Routes
Use generic override routes for dossiers.
POST
/v1/protocol/overridesAPI keySubmit an override request for an existing Decision Dossier.
curl -X POST https://api.decionis.com/v1/protocol/overrides \
-H "Authorization: Bearer dcy_org_xxx" \
-H "Content-Type: application/json" \
-d '{
"org_id": "11111111-1111-4111-8111-111111111111",
"original_dossier_id": "22222222-2222-4222-8222-222222222222",
"reason_code": "CUSTOMER_APPEAL",
"override_note": "Reviewer asked to inspect new evidence.",
"evidence_refs": ["ticket:INC-4812"]
}'GET
/v1/protocol/dossiers/:dossierId/overrides?org_id=<org_uuid>API keyList override records attached to a specific Decision Dossier.
GET
/v1/orgs/:orgId/protocol/overrides?status=PENDINGAPI keyList override records for an organization, optionally filtered by status.
POST
/v1/protocol/overrides/:overrideId/reviewAPI keyRecord an admin reviewer decision for a pending override.
Statuses
Statuses are deliberately explicit so review queues and public summaries do not need to infer posture from notes.
| Status | Meaning |
|---|---|
| PENDING | Submitted and awaiting review. |
| APPROVED | Reviewer accepted the override request. |
| REJECTED | Reviewer rejected the override request. |
| ESCALATED | Reviewer moved the override to a higher authority path. |
| EXPIRED | The override request expired before completion. |
| CANCELLED | The override request was withdrawn or cancelled. |
Public verification
The public dossier verification route includes share-safe override summary fields when an override trail exists.
{
"verified": true,
"dossier": {
"dossier_id": "22222222-2222-4222-8222-222222222222",
"outcome": "ESCALATE"
},
"overrides": {
"count": 1,
"active_count": 1,
"latest_status": "PENDING",
"latest_reason_code": "CUSTOMER_APPEAL"
}
}Share-safe by default
Public verification can show override status and reason codes, while private reviewer notes stay inside org-scoped routes. See /docs/decision-dossier for public verification semantics.
Finance routes
Finance-specific override routes remain available for execution governance workflows that need finance vocabulary and downstream dispatches.
| Route | Use |
|---|---|
| GET /v1/protocol/finance/override-reason-codes | List finance-specific override reason codes. |
| POST /v1/protocol/finance/overrides/submit | Submit a finance override request. |
| POST /v1/protocol/finance/overrides/:overrideId/review | Review a finance override and dispatch status updates. |