References to draft-das-consequence-path-completeness

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document	Title	Status	Type	Downref
draft-das-actuation-bound-execution-finality	Command Accepted Is Not Actuation Authorized: Execution Finality for Cyber-Physical and Industrial Control Systems References Referenced by		informatively references
draft-das-composite-execution-finality	Partial Commit Is Not Finality: Composite Candidate Acts Across Multiple Finality Sinks References Referenced by		informatively references
draft-das-drip-uas-act-finality	Cleared to Fly or Drive Is Not Cleared to Act: Actuator-Level Execution Finality and Compact Act Evidence for UAS and Autonomous Vehicles References Referenced by		informatively references
draft-das-ef-registries	Illustrative Codes Are Not a Namespace: Registries for Execution-Finality Consequence Classes, Sink Types, Act Types, Failure Codes, Profiles, and Media Types References Referenced by		informatively references
draft-das-execution-handle	Possession Is Not Authority: Execution Handle, Sink Verification, Atomic Consumption, and Finality Receipt References Referenced by		informatively references
draft-das-jurisdiction-bound-execution-finality	Authorized Here, Not Authorized There: Jurisdiction-Bound Execution Finality for Cross-Border and Sovereign Systems References Referenced by		informatively references
draft-das-third-party-decision-binding	Trust Me, I Checked: Verifiable Third-Party Decision Binding at the Execution-Finality Boundary References Referenced by		informatively references