Runtime proof case

DBaD v2.2 Runtime Demo

Inspect the upstream proof-case trace behind the public DBaD to DecencyMeter story.

One runtime-audited trace shows expectation, evidence, observed outcome, escalation closure, blind spots, completeness attestation, and current deterministic validation in the same path.

DBaD v2.2 records structured integrity signals. It does not prove truth, correctness, safety, or global completeness.

Open full trace Validate trace Bridge to scoring Challenge the logic

Runtime trace Deterministic validation Advisory limits visible Not certification

v2.2 public runtime · Validation and interpretation stay separate

Current trace state

Trace trc_20260428181140_42396240

Runtime validation

NOT AUTHORIZATION - structural validation evidence: structural-evidence-code-v2-449e56952f0fa85ea1525509 - not permission

Boundary Use this page to inspect how the trace is structured before reading any downstream score.

Start here

Use this path before treating any downstream interpretation as meaningful.

Read the trace first Start with the runtime summary and current validation result. Then compare the bridge See what a downstream advisory layer may interpret without replacing DBaD validation. Challenge the boundary Review where the trace can still mislead, fail, or invite false confidence.

Audited Trace Summary

trace reference evidence: NOT AUTHORIZATION - trace reference evidence e6db27f3acd0 - not permission

trace_version: v2

validation status evidence: NOT AUTHORIZATION - validation evidence: structural-evidence-code-v2-37a279564397f28ba9e516ac - not permission

expected_outcome: not recorded

outcome_status: unknown

declared_blind_spot count: 0

escalation_closure status evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-625861655829a922adca2a71 - not permission

escalation_closure disposition evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-cf6cfc8746d52c50fd9e0c74 - not permission

completeness_attestation status evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-4105bc65f053157f41027cc6 - not permission

state_transition_evidence presence: not recorded

current advisory notes: missing_state_transition_evidence, missing_boundary_trust_state, trust_positive_resume_missing_boundary_trust_state, resource_continuity_first_use_attested

current pending requirements: none

Downstream Handoff Snapshot

These are the exact upstream runtime signals that a downstream advisory layer can read from this audited trace without changing DBaD validation.

Expectation vs observed outcome

Expected: not recorded

Observed: unknown

This preserves pre-commitment versus later outcome without asking DBaD to judge whether the result was ethically correct.

Escalation and completeness

Closure evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-cf6cfc8746d52c50fd9e0c74 - not permission

Completeness evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-4105bc65f053157f41027cc6 - not permission

These are governance and declared-scope signals, not proof that the closure was wise or that the trace is globally complete.

Blind spots and evidence

Blind spots declared: 0

Evidence presence: not recorded

This trace records structural validation evidence while still surfacing advisory caution around evidence completeness and explicit non-coverage. That evidence is not authorization.

Integrity Stack Walkthrough

Expected outcome

What it records: a pre-committed expectation before later outcome is observed.

What it does NOT prove: that the expectation was correct, wise, or morally justified.

Audited trace value: not recorded

State transition evidence

What it records: before/after references plus an evidence reference, with optional hashing.

What it does NOT prove: that the referenced artifact is true, complete, or independently verified by DBaD.

Audited trace value: not recorded

Outcome status

What it records: what was later observed after the trace was already live.

What it does NOT prove: that the original decision was correct or safe.

Audited trace value evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-37100cab57cf8179299f5157 - not permission

Escalation closure

What it records: how an escalation-oriented trace was resolved before trust-positive continuation resumed.

What it does NOT prove: that the closure decision was substantively correct.

Audited trace value evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-cf6cfc8746d52c50fd9e0c74 - not permission

Declared blind spots

What it records: scope limits and known non-coverage that the trace explicitly declares.

What it does NOT prove: that every omission has been disclosed.

Audited trace value: 0

Completeness attestation

What it records: what the trace claims to cover within its declared scope.

What it does NOT prove: that nothing was omitted or that cross-trace completeness is solved.

Audited trace value evidence: NOT AUTHORIZATION - status evidence: structural-evidence-code-v2-4105bc65f053157f41027cc6 - not permission · canonical broken trace proof case

Validation Result

validation boolean evidence: NOT AUTHORIZATION - structural validation evidence: structural-evidence-code-v2-449e56952f0fa85ea1525509 - not permission

validation summary: Trace failed 4 deterministic validation check(s).

Violations

actor_continuity
trust_trajectory
propagation_integrity
missing_boundary_trust_state_on_trust_positive_resume

Advisory notes

missing_state_transition_evidence
missing_boundary_trust_state
trust_positive_resume_missing_boundary_trust_state
resource_continuity_first_use_attested

Pending requirements

none

Checked rules summary

verification_independence = NOT AUTHORIZATION - pass - structural evidence only
actor_continuity = fail - not authorization
trust_trajectory = fail - not authorization
propagation_integrity = fail - not authorization
expected_outcome_order = NOT AUTHORIZATION - pass - structural evidence only
completeness_attestation = NOT AUTHORIZATION - pass - structural evidence only
state_transition_evidence_presence = fail - not authorization
boundary_trust_state_presence = fail - not authorization
trust_positive_boundary_state = fail - not authorization
escalation_closure = NOT AUTHORIZATION - pass - structural evidence only
historical_contamination_visibility = NOT AUTHORIZATION - pass - structural evidence only
cross_trace_lineage_integrity = NOT AUTHORIZATION - pass - structural evidence only
resource_lineage_integrity = NOT AUTHORIZATION - pass - structural evidence only
coverage_trace_exposure = NOT AUTHORIZATION - pass - structural evidence only
governing_intent_coverage_alignment = NOT AUTHORIZATION - pass - structural evidence only
trace_reliance_integrity = NOT AUTHORIZATION - pass - structural evidence only
reliance_declaration_completeness = NOT AUTHORIZATION - pass - structural evidence only
lineage_depth_limit = NOT AUTHORIZATION - pass - structural evidence only
zero_trust_reset_integrity = NOT AUTHORIZATION - pass - structural evidence only
zero_trust_reset_evidence_availability = NOT AUTHORIZATION - pass - structural evidence only
reset_boundary_continuity = NOT AUTHORIZATION - pass - structural evidence only

What this page shows

the v2.2 field stack exists in a real stored trace on the live runtime
the runtime exposes deterministic validation, advisory notes, and checked-rule results separately
the audited proof-case trace can be read downstream without collapsing DBaD validation into DecencyMeter scoring
expectation ordering and escalation-closure logic are part of the checked runtime rule set
blind spots and completeness remain explicit declarations rather than implied certainty

What this page does NOT show

it does not prove the underlying real-world facts are true
it does not prove the decision was correct
it does not prove the evidence artifact is authentic
it does not prove global or cross-trace completeness
it does not replace human review

Try to break this logic

Use this audited trace as a starting example, then challenge the logic, validation boundaries, and trust implications through the public review path.

Try to break DBaD Draft a finding Top issues

Links

Open full trace · Validate trace · DecencyMeter bridge · DecencyMeter demo · API docs · Current state · Try to break DBaD · Peer review findings