Last updated: 2026-05-01 UTC

Public summary of submitted DBaD logic-review findings

Try to break DBaD Submit finding

Public review signals

What reviewers are finding so far.

This page summarizes what people have reported while trying to break DBaD’s logic, trace model, validation assumptions, and governance boundaries.

These counts are descriptive only. They are not a score, not a system-health grade, and not a risk verdict.

Submit a finding Review the challenge path Inspect the v2.2 demo
  • 0 reports
  • No score
  • No risk grade
Reviewer-submitted signals · Deterministic aggregates stay descriptive · Challenge path stays separate

Quick orientation

Total reports 0 public logic-review reports submitted so far.
Most common issue type None yet
Most common severity label None yet

Start Here

Choose whether you want to inspect runtime proof, review current findings, or submit a new issue.

Inspect the runtime proof Open the v2.2 demo before deciding whether an issue is logic, boundary, or interpretation drift. See the reviewer path Understand what kinds of issues the public challenge surface is asking people to find. Submit a new finding Add a logic, documentation, UX, or research issue without turning this page into a scorecard.
Boundary First

All counts on this page are descriptive only. They do not rank DBaD, grade its risk, or convert the review backlog into a score.

Reviewer Snapshot

These are the simplest public counts, kept separate from deeper runtime aggregates.

Total Reports

0

Most Common Issue Type

None yet

Most Common Severity

None yet

Runtime Trace Aggregates

These counts come from stored DBaD traces. They are structured aggregates only, not a score, inference, risk grade, or system-health claim.

See bridge context

Observed Outcomes So Far

unknown

Most common recorded outcome across 43 stored traces.

  • unknown: 34
  • upheld: 3
  • reversed: 1
  • escalated: 0
  • incident: 5
  • no_observed_issue: 0

Expectation vs Observed Outcome

  • Expected outcome recorded: 9
  • Matches: 4
  • Mismatches: 3
  • Pending observation: 2

Mismatch pairs:

  • no_observed_issue -> incident: 2
  • upheld -> incident: 1

Outcome vs Blind Spots

  • unknown: 34 traces, 3 with blind spots, 3 with open blind spots
  • upheld: 3 traces, 1 with blind spots, 0 with open blind spots
  • reversed: 1 trace, 0 with blind spots, 0 with open blind spots
  • escalated: 0 traces, 0 with blind spots, 0 with open blind spots
  • incident: 5 traces, 1 with blind spots, 1 with open blind spots
  • no_observed_issue: 0 traces, 0 with blind spots, 0 with open blind spots

State-Transition Evidence Coverage

  • Traces with supported transitions: 14
  • Traces missing evidence on at least one supported transition: 11
  • Traces with all supported transitions evidenced: 3
  • Supported transitions total: 22
  • Supported transitions with evidence: 8
  • Supported transitions missing evidence: 14

Completeness Attestation Status

unknown

  • unknown: 33
  • declared_complete: 5
  • partial: 4
  • not_attested: 1
No public logic-review reports have been submitted yet.

The challenge is open. Submit a finding if you see a logic gap, unclear validation result, or misleading trace.

This page is intentionally simple.

It shows recurring logic-review signals, not a full issue tracker or a claim that DBaD is complete.

The v2.2 runtime demo shows the current integrity stack reviewers can challenge.

v2.2 demo · DecencyMeter bridge · Scoring anomalies · Pressure tests · Try to break DBaD · Submit a logic-review finding · Peer review · Examples