Last updated: 2026-04-28 UTC

Stored DBaD trace detail

Recent traces Evaluator demo Trace API DBaD Explained

trc_20260428193300_pf67c1e2

Pressure-test case with clean evidence, no blind spots, declared completeness, and an incident outcome that was also expected.

This stored trace shows the minimal DBaD vertical-slice object returned by the evaluator pipeline. It is intentionally compact: action summary, state layers, trust posture, verification posture, constraint flags, and reasoning summary.

Back to recent traces Open API response

Version: 13 · Created: 16d ago 2026-04-28T19:33:00Z · Updated: 16d ago 2026-04-28T19:33:49Z · Review status: reviewed · Expected: incident · Outcome: incident · Blind spots: 0 · Completeness: declared_complete

Action Summary

Scenario: Pressure-test case with clean evidence, no blind spots, declared completeness, and an incident outcome that was also expected.

Preset: Perfect-Looking Incident Trace

Domain context: agent governance

Governance profile: General Governance Profile

State Layers

  • Local: allow · Allow
  • Systemic: none_reported · None reported
  • Effective: allow · Allow

The trace stays procedurally clean even though the substantive outcome is incident.

Trust and Verification

Trust inheritance: Structurally allowed despite the incident outcome.

Verification posture: Verification recorded: approved.

Outcome Status

Expected outcome: incident

auditor_pressure · 16d ago 2026-04-28T19:33:10Z

Expectation is aligned with the later incident outcome to keep the trace procedurally clean.

Current outcome: incident

Outcome status records the observed outcome, not proof of correctness.

Recorded before outcome. Not evaluated by the system.

Expectation vs Outcome
  • Expected = incident
  • Observed = incident

Declared Blind Spots

Total declared: 0

Declared blind spots record known limits of the trace. They do not prove that all omissions were disclosed.

No blind spots have been declared for this trace yet.

Completeness Attestation

Current status: declared_complete

auditor_v22 · 16d ago 2026-04-28T18:12:41Z

Scope: single trace audit path from expectation through reviewed transition and observed outcome

Coverage window: 2026-04-28 audit session

Completeness attestation records what this trace claims to cover. It does not prove nothing was omitted.

Included trace refs:
  • trc_20260428193300_pf67c1e2
Excluded known items:
  • No cross-trace completeness claim.

Per-trace completeness claim only.

Escalation Closure

No escalation closure is currently recorded for this trace.

Escalation closure records how a flagged trace was resolved. It does not prove the original decision was correct.

Constraint Flags

  • Continuity: No explicit continuity concern surfaced.
  • Verifier independence: No explicit verifier-independence concern surfaced.
  • Trajectory: No explicit trajectory concern surfaced.

Reasoning Summary

Governing summary: This case is meant to look procedurally perfect while still surfacing an incident outcome, exposing the boundary between structure and judgment.

Next step: Use to show that structurally clean traces can still describe bad substantive outcomes.

  • Purpose: perfect-looking pressure test.
  • Evidence is present for the supported transition.
  • No blind spots are declared.
  • Completeness is declared complete.
  • Outcome is incident and was also expected.

Next Actions

Allowed actions:

  • Verify: Allowed while the trace remains open.
  • Transition: Allowed under the current stored verification and state posture.

Blocked actions:

No blocked action is currently recorded by this minimal guidance layer.

Why actions are blocked:

  • No active core constraint is currently blocking the listed operator actions.

Additional concerns:

  • Expected outcome was recorded before later observation. DBaD does not evaluate whether that expectation was wise.
  • Completeness attestation declared complete coverage for the stated scope, but DBaD does not verify that claim.
  • Evidence reference recorded for the latest transition.

Next step: Use to show that structurally clean traces can still describe bad substantive outcomes.

Trace Validation

Deterministic validation checks the current core rule set only: verification independence, actor continuity, trust trajectory, propagation integrity, expected-outcome ordering, completeness-attestation shape, state-transition-evidence shape, and escalation-closure resume rules when applicable. Declared blind spots and incomplete completeness statuses are surfaced as metadata or advisories, not automatic failures.

/api/v1/dbad/validate Validation docs

No validation run yet.

  • No validation result yet.

Add Verification

Minimal vertical-slice action only. This appends one verification event to the trace and updates the visible verification posture.

Verification API: /api/v1/dbad/traces/trc_20260428193300_pf67c1e2/verification

Add Transition

Minimal vertical-slice transition only. This appends one transition event and updates the stored effective/review state where appropriate.

Transition API: /api/v1/dbad/traces/trc_20260428193300_pf67c1e2/transition

Evidence references are not verified by DBaD.

Update Outcome

Manual only. This records what was later observed without treating it as proof of safety or correctness.

Outcome API: /api/v1/dbad/traces/trc_20260428193300_pf67c1e2/outcome

Record Expected Outcome

Expected outcome has already been recorded for this trace and is now fixed.

Add Blind Spot

Use this to record known non-coverage or scope limits without claiming DBaD can detect every omission.

Blind spot API: /api/v1/dbad/traces/trc_20260428193300_pf67c1e2/blind-spots

Update Completeness Attestation

Record what this trace claims to cover without implying DBaD can prove that claim is true or exhaustive.

Completeness API: /api/v1/dbad/traces/trc_20260428193300_pf67c1e2/completeness-attestation

Verification History

  • approved by validator_clean
    18d ago 2026-04-27T14:38:06Z
    Low-risk continuation remains within the prior trusted context.

Transition History

Evidence references are not verified by DBaD.

  • mark_reviewed by auditor_pressure
    16d ago 2026-04-28T19:33:49Z
    Reviewed with full evidence for the pressure-test comparison.
    State transition evidence
    Before: state:perfect-v1
    After: state:perfect-v2
    Evidence: artifact:perfect-log-1
    Hash: sha256:db519f006c11441c77bb6a552f99f08364eb3e52ef10f643d4d5be8b2c7fff33

Outcome History

  • incident after unknown
    16d ago 2026-04-28T19:33:45Z
    reviewer: auditor_pressure
    Observed incident outcome matches the expected outcome exactly.

Completeness Attestation History

  • declared_complete by auditor_v22
    16d ago 2026-04-28T18:12:41Z
    Scope: single trace audit path from expectation through reviewed transition and observed outcome
    Coverage window: 2026-04-28 audit session
    Included refs: trc_20260428193300_pf67c1e2
    Excluded known items: No cross-trace completeness claim.
    Per-trace completeness claim only.

Escalation Closure History

No escalation closure events have been recorded for this trace yet.

State History

  • initial_evaluation allow
    16d ago 2026-04-28T19:33:00Z
    review: unreviewed · trace: open
  • manual_transition allow
    16d ago 2026-04-28T19:33:49Z
    review: reviewed · trace: open