Skip to main content
The evidence pack is the bundle of data behind a decision. It composes automatically from whichever vendor / AI / rule outputs the workflow run produced.

​
Evidence pack structure

{
  "decision_id": "dec_...",
  "workflow_run_id": "run_...",
  "vendor_payloads": {
    "identity_suite": { ... },
    "aml_screening":  { ... },
    "blockchain_analytics": { ... },
    "identity_enrichment": { ... },
    "registry_validation": { ... },
    "banking_rail_counterpart": { ... }
  },
  "ai_outputs": {
    "address_rewrite":   { ... },
    "fp_synthesis":      { ... },
    "risk_synthesis":    { ... }
  },
  "rule_outputs": {
    "region_check": "pass",
    "address_needs_rewrite": "false",
    "identity_path": "proceed"
  },
  "manual_review": [
    {
      "reviewer": "user_alice",
      "started_at": "...", "completed_at": "...",
      "response": { "decision": "approve", "reason": "..." }
    }
  ],
  "notes": [
    { "by": "user_bob", "ts": "...", "body": "Cross-checked with prior case from 2026-03." }
  ]
}

​
What’s NOT in the pack

  • Image binaries (selfies, document scans) — live with the identity vendor. Pack carries a vendor_request_id so the binary can be retrieved on-demand.
  • The model prompts verbatim — versioned with the workflow definition, not duplicated per decision.
  • The credential values — only opaque references.

​
Notes

Analyst-written notes are first-class evidence. They appear in:
  • The Decision Console (always).
  • The audit log (with author + timestamp).
  • The regulator export bundle (when relevant).
Notes are tenant-private — they never travel with vendor calls or with relationship-client RFIs.