The Two-Note Proof
Current state, candidate state, and the rule that no PASS exists without evidence
The two-note pattern presents:
CURRENT
accepted state and evidence
CANDIDATE
proposed state and expected consequences
A change review asks:
- what is added;
- what is removed;
- which source or authority changed;
- what becomes stale;
- what uncertainty increased;
- what evidence is required;
- how to roll back.
The pattern applies to:
- LCSM notes;
- Plan revisions;
- artifact promotion;
- code changes;
- policy;
- actor state;
- public claims.
Proof receipt
After execution, a receipt records:
request
prior state
result state
actor
authority
checks
artifacts
limitations
rollback
acceptance
A UI may display a PASS badge only when the named checks and artifacts exist.
Laws
You cannot draw trust; you can only prove it.
A gate that cannot fail is not a gate.
Acceptance is human-only where the contract requires it.
The two-note form makes change inspectable before it becomes history. The receipt makes the accepted transition replayable afterward.
Source register
- N16-S01 — LCSM Workbench E2E Specification.
LCSM-WORKBENCH-E2E-SPEC.v0.md - N16-S02 — Haygent Specification.
HAYGENT-SPEC-v1.0.md - N16-S03 — Glyphd proof receipt visual/source corpus.
Futuristic proof receipt dashboard interface.png