ATTESTED
Evidence-backed, with a named source span, source hash, entering actor, confidence, and—when a locker is wired—a resolvable evidence object. Missing evidence downgrades the claim.
RECProvenance machineryintegrity ≠ correctness
Fields are not reality.
Project Shadow makes the epistemic status of every load-bearing field visible. A fluent system may still be wrong; it should no longer be able to hide where the decisive claim came from.
LONG-FORM COMPANION
Read the full chapter →Open the system reference at this layer.
Follow the mechanism through numbered execution, a worked trace, artifact-bound evidence, adverse results, and validation still required.
DECLARED
The operator names a judgment or default and takes responsibility for it. Declaration identifies the asserter; it does not become independently earned evidence.
ASSERTED
A load-bearing value appears without a ledger entry. In strict mode, an unproven steering field is a refusal floor rather than a silent assumption.
01Canonical action
02Field provenance
03Evidence locker
04Gate + SIL
05Maybe / Therefore
06Receipt seal
Artifact identity
Exact hashes can show that the runtime, codec, evidence file, or receipt has not been silently substituted.
Structural conformance
A deterministic validator can show that required fields, order, enums, floors, and chain structure conform to the specified contract.
Truth or judgment quality
A signed statement can still be false. A complete receipt can still document a bad decision. Provenance makes the claim attributable and reopenable.
Safety or authorization
Integrity, test completion, and standards alignment do not certify a deployment or authorize consequential action.
WRITE-AHEAD LAW
The receipt is written before the act. A rationale generated after the outcome is known is a different artifact.