Trust propagation

Trust should not travel farther than the trace supports.

DBaD governs how trust moves across a trace, not just how one action is scored.

This visual shows the normal path from action to downstream trust use, the points where DBaD constrains trust, and the governance states when continuity, verification, lineage, or trajectory break.

View diagram Open examples Cross-trace review
Actor continuity Verifier independence Trajectory constraints Lineage blocking

What changes trust flow

Clean lineage Trust can continue only when the recorded chain supports it.
Broken boundary Actor, verifier, trajectory, or lineage gaps constrain or halt inheritance.
Current runtime checks Trace validation now includes same-trace, declared-parent, and same-resource guardrails.

Last updated: 2026-05-30 UTC

Public visual explanation of DBaD trust propagation

Examples Peer review Try to break DBaD DBaD Explained What DBaD solves White paper v3 Known limits DecencyMeter demo

Start here

Use the diagram with live traces and known limits, not as a standalone proof claim.

Plain-language overview Read the core idea before interpreting the diagram. Runtime proof case Compare the diagram against a stored trace and live validation result. Known limits Check where DBaD does not infer identity, intent, or truth.

Trust Flow Diagram

DBaD trust propagation diagram A visual explanation showing action, verification, propagation, and downstream trust use, with interruption points for actor continuity, verifier independence, trajectory divergence, and orphan lineage. Action proposed step enters review Verification review, evidence, clearance posture Propagation trust tries to move forward Downstream Trust Use later action depends on prior trust Broken Actor Continuity undeclared handoff blocks normal continuation Failed Verification independence breaks or reuse becomes structural conflict Trajectory Divergence downstream behavior materially degrades from lineage Orphan / Reset Lineage fresh root or broken origin blocks inherited trust Trust Continues normal inherited trust remains available Trust Constrained continuation limited, state remains gated Trust Halted unsafe inheritance path is stopped Verification Required additional review or evidence before trust moves

How to Read It

The top row shows the normal path: an action is reviewed, verified, propagated, and then relied on later. The middle row shows the main interruption points where DBaD can constrain trust instead of letting it move forward silently.

DBaD is not trying to prove everything. It is trying to make trust movement legible, constrain unsafe inheritance, and keep the reasons visible in the trace.

Legend

  • Trust continues: no structural break prevents normal inherited trust.
  • Trust constrained: trust can still matter, but only under tighter governing conditions.
  • Trust halted: inherited trust is stopped because the path is structurally unsafe.
  • Verification required: additional evidence or review is needed before trust can move forward.

Why This Matters

Most systems evaluate the endpoint. DBaD focuses on the path that produced the endpoint. That is where continuity breaks, borrowed trust, verifier capture, and lineage resets become visible.

Continue with proof-backed examples, the peer-review findings, Try to Break DBaD, what DBaD solves, the white paper v3, the known limits, or the research demo.