DLX: Decision–Ledger–eXecution — A Validation Architecture for State Transitions

DLX (Decision–Ledger–eXecution) is a validation architecture that separatesdecision execution from transition validation through evidence-bound statechanges. The architecture focuses on refutation of false process claims rather thanverification of correctness or outcomes. DLX does not guarantee correctness,safety, compliance, or optimal decisions. Instead, it constrains how decisionsalter system state and how those changes can be validated through reproducibleartifacts. DLX adopts a refutation-first epistemology: agreement between systems carriesno positive epistemic weight, while divergence under identical contractidentity and canonical input refutes a conformance claim. This overview document describes the architecture and links the main artifactsthat constitute the DLX validation framework. DLX Architecture Layers Principle Layer — Contract Reproducibilityhttps://doi.org/10.5281/zenodo.18402934 Standard Layer — ROVS-SD (Refutation-Only Validation Standard)https://doi.org/10.5281/zenodo.18412469 Implementation Layer — FSM Governance Enginehttps://doi.org/10.5281/zenodo.18394741 Framework Layer — ROVS-XL within DLXhttps://doi.org/10.5281/zenodo.18454313 These artifacts together form a validation-only architecture for governance,auditability, and integrity-critical decision systems. DLX constrains how claims, evidence artifacts, and state transitions interactwithout asserting correctness of the underlying systems.