DBaD White Paper v3
A tested governance protocol for decision integrity across time.
The current DBaD white paper documents the structured decision-trace model, lifecycle governance, dependency reasoning, three confirmed protocol flaws found through red-team testing, and the first runtime enforcement layer designed to close unsafe trust-inheritance paths.
This matters because most systems evaluate decisions in isolation. DBaD is built to govern how trust, obligations, and verification behave across chains, handoffs, and later audit.
- White paper v3
- Structured decision trace
- Runtime enforcement v1
Key Highlights
- Structured decision trace with local, systemic, and effective state.
- Lifecycle governance across evaluation, verification, restoration, and audit.
- Dependency and provenance reasoning instead of isolated point-in-time scoring.
- Three confirmed protocol flaws from red-team discovery.
- Runtime Enforcement Layer v1 with narrow trust-inheritance controls.
- Known limits documented instead of hidden behind confidence theater.
Why It Matters
Most evaluation systems produce a score or recommendation for a single action and stop there. DBaD is aimed at the harder problem: how decisions should remain governable when lineage, handoffs, verification, and audit all matter.
The white paper focuses on trust inheritance failures. It shows how apparently clean continuations can still fail when verifier independence breaks, actor continuity breaks, or lineage risk rises materially over time.
Downloads
Supporting links: methodology · API docs · demo
Confirmed Flaws
- Verifier Independence: multi-party clearance can fail if reciprocal or cartel-like approval relationships are treated as independent.
- Actor Continuity: silent handoff can look like ordinary continuation unless continuity is checked at runtime.
- Trust Trajectory: a high-risk action can borrow credibility from a clean-looking lineage path unless trajectory degradation is checked.
Runtime Enforcement Layer v1
The first runtime layer is intentionally narrow. It adds three checks at the points where trust inheritance can fail: verifier independence, actor continuity, and lineage risk trajectory.
Good history can reduce the severity of the first response, but it does not remove re-validation friction. The goal is minimal enforcement that blocks the known failure classes without forcing a full schema redesign.
Public Summary
Website intro: DBaD White Paper v3 presents a tested governance protocol for decision integrity across time. It combines structured decision traces, lifecycle governance, dependency reasoning, and a narrow runtime enforcement layer shaped by adversarial testing and confirmed protocol flaws.
Homepage teaser: A governance protocol for decision integrity across time. DBaD goes beyond point-in-time scoring by combining structured decision traces, lifecycle governance, dependency reasoning, and runtime enforcement shaped by adversarial testing.
Launch blurb: We published the latest DBaD white paper: a tested governance protocol for human, AI, and hybrid decision systems. It documents the core model, three confirmed protocol flaws discovered through red-team testing, and the first runtime enforcement layer designed to prevent unsafe trust inheritance.