Undeclared Actor Handoff
Scenario: A valid-looking action is continued by a different actor without an explicit handoff or declared delegation.
Result: escalate
Trust inheritance: blocked
Verification posture: additional review required
Trace excerpt:
- step_n.actor = actor_a
- step_n+1.actor = actor_b
- continuation declared = false
- effective_state = escalate
Key constraints:
- Actor continuity
- Propagation integrity
Explanation: The immediate action may be locally plausible, but DBaD does not allow prior trust to continue across an undeclared actor break.
Try the demo · View trust flow
Chain Reset / Orphan Visibility
Scenario: Work resumes on an existing resource through a fresh root trace with no valid origin anchor.
Result: allow_conditional
Trust inheritance: blocked
Verification posture: verification required before ordinary continuation
Trace excerpt:
- resource_id = existing_target
- origin_anchor = null
- root_initialization = true
- zero_trust_birth = active
Key constraints:
- Propagation integrity
- Zero-Trust Birth handling
Explanation: DBaD does not treat a fresh lineage-free trace as a trusted continuation. It keeps trust constrained and makes the reset visible.
What DBaD solves · View trust flow
Repeated Verifier Reuse
Scenario: The same verifier repeatedly clears risky work on the same target across one lineage.
Result: escalate
Trust inheritance: blocked
Verification posture: independent verification required
Trace excerpt:
- verifier_id = verifier_x
- target_resource = target_17
- reuse_in_lineage = repeated
- effective_state = escalate
Key constraints:
- Verification independence
- Propagation integrity
Explanation: Structural verifier reuse on the same target weakens independence. DBaD treats that as a trust-inheritance problem, not as ordinary clean clearance.
Try the demo · What DBaD solves
Recovery Deadlock / Dampened Escalation
Scenario: Repeated blocked remediation attempts keep hitting the same enforcement result without changing state.
Result: escalate
Trust inheritance: not allowed to continue normally
Verification posture: higher-scrutiny review path remains required
Trace excerpt:
- correction_payload_hash = repeated
- enforcement_result = unchanged
- state_change = none
- escalation_events = dampened
Key constraints:
- Recovery deadlock visibility
- Propagation integrity
Explanation: DBaD does not treat repetitive blocked correction as fresh clean progress. It preserves the deadlock signal while avoiding endless escalation noise.
View trust flow · Try the demo
Clean Low-Risk Continuation
Scenario: A low-risk continuation stays within the same actor context, uses clean verification, and does not materially diverge from prior lineage.
Result: allow
Trust inheritance: allowed
Verification posture: no extraordinary review pressure
Trace excerpt:
- actor continuity = preserved
- verification independence = clean
- trajectory drift = low
- effective_state = allow
Key constraints:
- No continuity break
- No verifier-independence concern
- No trajectory concern
Explanation: When the trace remains structurally coherent, DBaD allows trust to continue. The system is not built to block everything; it is built to keep trust honest over time.
Try the demo · What DBaD solves