API documentation

Shadow Reports

Shadow Reports aggregate observe-only Decionis decisions before enforcement is activated. They show would-block, would-escalate, policy drift, near misses, and candidate enforcement paths from protocol evaluation records.

Purpose

Use shadow evidence to decide whether a workflow is ready for controlled enforcement.

Observe first

Run mode=SHADOW to collect governed outcomes while the downstream application still follows its existing execution path.

Find boundaries

Near misses and policy drift show where Decionis would have stopped, escalated, or requested review.

Promote deliberately

Candidate enforcement paths identify workflows with enough traffic and low enough non-allow rates to consider enforcement.

Shadow is not a no-write environment

SHADOW evaluates the proposed action, produces the real verdict, records the evidence, and alters nothing downstream. No execution token, no grant. Shadow observation runs outside the production commit path; an adapter MUST NOT interpret a Shadow response as an instruction either to execute or to block that path. The downstream application still follows its existing execution path, so the writes it makes are real; a test environment with no real writes is a separate thing, and shadow mode is not it.

Routes

Read reports for workspace display or export them as hashable evidence.

GET/v1/protocol/shadow-reports?org_id=<org_uuid>&days=30&limit=50API key

Aggregate shadow decisions into summary cards, candidate paths, near misses, and recent evaluations.

curl "https://api.decionis.com/v1/protocol/shadow-reports?org_id=11111111-1111-4111-8111-111111111111&days=30&limit=50" \
  -H "Authorization: Bearer dcy_org_xxx"
POST/v1/protocol/shadow-reports/exportAPI key

Return a JSON export artifact with artifact_sha256 for enforcement-readiness review.

Cards

Cards are compact proof units suitable for workspace dashboards and review meetings.

CardMeaning
would_blockCount of shadow decisions that would have stopped execution.
would_escalateCount of shadow decisions that would have handed off for review.
policy_driftCount of cases where shadow posture diverged from expected policy.
near_missesApproved decisions near the policy boundary or confidence boundary.
candidate_enforcement_pathsWorkflow paths with enough clean traffic to consider enforcement.

Export

Exports keep the report body and hash together for audit trails and rollout signoff.

{
  "service": "decionis",
  "generated_at": "2026-05-05T10:00:00.000Z",
  "artifact_sha256": "94fb...",
  "artifact": {
    "artifact_type": "decionis.protocol.shadow_report.export",
    "version": "1.0",
    "window_days": 30,
    "report": {
      "summary": {
        "shadow_evaluations": 120,
        "would_block": 4,
        "would_escalate": 12,
        "candidate_enforcement_path_count": 2
      }
    }
  }
}

Rollout use

Shadow reports should inform enforcement readiness, not replace policy review.

Promotion requires operator acceptance

Use https://docs.decionis.com/policy-snapshot and https://docs.decionis.com/reason-codes to review what Decionis was evaluating, then use https://docs.decionis.com/execution-map to understand how enforcement artifacts will appear after promotion.