A crafted claim keeps two things apart: what it asserts (intent) and what backs the assertion (evidence). Evidence carries a recomputable anchor; an assertion carries only itself. Keep them in separate columns and a bare assertion can never masquerade as proof — because it has nothing to recompute. Break it with your own hands: smuggle an intent into the evidence column and watch the partition refuse it.
ACI · a CORE property made hands-on · separation enforced by TYPE, not by columns
The verdict
VALID
INTENT · what is asserted
EVIDENCE · what backs it
◈ seal a payload — recompute an anchor by hand, confirm the page is not lying (matches dlw.py / node)
anchor = sha256(payload) =
Verdict is three-state on purpose: VALID (every evidence intact, every intent backed) · INCOMPLETE (some intent has no verifiable backing — honest, but not proven) · INVALID (some evidence was altered after it was sealed). An unbacked claim is not a tampered one; the partition keeps them distinct.
Two layers, honestly
Real
The separation is enforced by type, not by two pretty columns. Only a row that carries kind:'hash', a string payload, and a 64-hex anchor can back a claim, and it backs it only if sha256(payload) === anchor (a genuine SHA-256, the same one dlw.py uses — recompute any anchor in the seal box to check). An assertion has no payload to hash and no slot to hold an anchor, so it is structurally rejected before any backing is counted. Node-verified: 18/18 (smuggle → UNVERIFIABLE → dependent intent UNBACKED; tamper payload or anchor → BROKEN; determinism digest stable).
Figure
The “two ledgers.” The columns are the picture; the type discipline is the mechanism. And a sharper caveat: VERIFIED means “unaltered since it was sealed,” not “true.” A false or irrelevant statement can be a perfectly VERIFIED payload — this checks integrity + presence + non-masquerade, never the truth of the content, and it cannot judge whether the evidence actually supports the intent’s meaning. As in THE ANCHOR, the anchor here is a local commitment recomputed in-page; true external anchoring binds to something outside the file (a timestamp, a commit, a URL a third party holds), which one self-contained page can only simulate.