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.

Runtime trace Deterministic validation Advisory limits visible Not certification

Current trace state

Trace trc_20260428181140_42396240
Runtime validation invalid means deterministic structure only, not moral approval.
Boundary Use this page to inspect how the trace is structured before reading any downstream score.

Last updated: 2026-05-30 UTC

Public walkthrough of the runtime-audited v2.2 integrity stack

DecencyMeter bridge DecencyMeter demo Try to break DBaD Open full trace

Start here

Use this path before treating any downstream interpretation as meaningful.

Audited Trace Summary

trace_id: trc_20260428181140_42396240

trace_version: v11

validation status: invalid

expected_outcome: upheld

outcome_status: upheld

declared_blind_spot count: 1

escalation_closure status: recorded

escalation_closure disposition: approved_to_continue

completeness_attestation status: declared_complete

state_transition_evidence presence: recorded

current advisory notes: missing_state_transition_evidence, missing_boundary_trust_state, trust_positive_resume_missing_boundary_trust_state

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: upheld

Observed: upheld

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

Escalation and completeness

Closure: approved_to_continue

Completeness: declared_complete

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: 1

Evidence presence: recorded

This trace is structurally valid while still surfacing advisory caution around evidence completeness and explicit non-coverage.

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: upheld at 2026-04-28T18:12:41Z

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:

  • before_ref = state:v1
  • after_ref = state:v2
  • evidence_ref = artifact:audit-log-1
  • evidence_hash = sha256:8ed01a76871a42864d139a3430086ead48a36317c112dd6c0c6682f95fce5739

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: upheld

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: approved_to_continue

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: 1 · scope_limit

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: declared_complete · single trace audit path from expectation through reviewed transition and observed outcome

Validation Result

is_valid: false

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

Violations

  • 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

Pending requirements

none

Checked rules summary

  • verification_independence = true
  • actor_continuity = true
  • trust_trajectory = true
  • propagation_integrity = true
  • expected_outcome_order = true
  • completeness_attestation = true
  • state_transition_evidence_presence = false
  • boundary_trust_state_presence = false
  • trust_positive_boundary_state = false
  • escalation_closure = true
  • historical_contamination_visibility = true
  • cross_trace_lineage_integrity = true
  • resource_lineage_integrity = true
  • coverage_trace_exposure = true
  • governing_intent_coverage_alignment = true
  • trace_reliance_integrity = true
  • reliance_declaration_completeness = true
  • lineage_depth_limit = true
  • zero_trust_reset_integrity = true
  • zero_trust_reset_evidence_availability = true
  • reset_boundary_continuity = true

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.

Links

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