August 30, 2026
Two weeks ago, the Decision Contract named a standard.
It said: a record of an automated decision must be deterministic, replayable, tamper-evident, framework-mapped, and rationale-bearing. Five conditions. No exceptions.
Today, the specification exists.
What the Specification Defines
The Decision Contract Specification v1.0.0 defines what a compliant record must contain.
The five conditions. Determinism. Replayability. Tamper-evidence. Framework mapping. Rationale. Each condition is defined precisely enough to be tested against.
Required record contents. Every compliant record must include a unique identifier, an engine version, a timestamp, the complete input, the complete output, a cryptographic hash, evidence that each condition is satisfied, a link to the previous record, and a signature from the issuing authority.
Hash chaining. The record is cryptographically chained to the one before it. Any alteration to any prior record invalidates everything after it. Append-only. Insertion or deletion breaks the chain.
Replay verification. An independent party extracts the input and engine version from the record, submits it again, and compares the output. If it matches, the record is verified. The procedure demonstrates only that the same input produces the same output.
Framework mapping. The record must list which frameworks applied, which specific controls or principles are satisfied, and why each mapping is valid.
Versioning. Semantic versioning. Major for incompatible changes. Minor for new frameworks. Patch for clarifications.
External anchoring. Optional third-party timestamps, blockchain anchors, or notary services for additional evidentiary weight.
Why This Matters
A specification turns a name into a standard. It gives auditors something to cite. It gives regulators something to reference. It gives engineers something to build against. It gives courts something to measure.
The Decision Contract article said what must be true. The specification says what a compliant record must contain.
Three layers. One standard. No ambiguity.
The Standard Is Now Complete
The Decision Contract has a name. It has a specification. It has an implementation.
The algorithm age needed a measuring stick. Now it has one.
The specification is live. The standard is defined.
Founder & CEO, Decision Security Layer
https://seais-decision-core.onrender.com
Contact: decseclayer@gmail.com
Top comments (0)