Alignment Workspace

Item 70: A current-state certificate

Normativity line — legitimacy · difficulty open · project normativity.legitimacy · open · node item-70

A grounding tree certifies that an occurrence was legitimately issued. It cannot certify that it is still in force: a tree is built from grounds, disposals are not grounds, and so no tree names the revocation that would defeat it.

Both consumers need currentness. Deference is deferring to a judgment now, and an authority since revoked is not one; enforcement's target is what is in force. So the interface currently offers a cheap certificate for the half neither consumer can use alone, and requires a replay for the half they need.

Three routes and nothing here builds the second: the recognizer replays the prefix; the process commits to a state and proves the delta since it; the recognizer accepts an attestation and records that as trust.

Deliverable shape: either a commitment-and-delta object with a soundness statement, or an argument that currentness is irreducibly a replay, with what that costs a recognizer. Acceptance check: the missed-revocation and lineage-versus-current processes are decided correctly by whatever object is proposed. Context: projects/normativity/legitimacy/rounds/2026-08-25-legitimate-evolution/CROSS_PROCESS_INTERFACE.md §§1-3. Consumed by: both consumer theorems.

Deliverable shape: either a commitment-and-delta object with a soundness statement, or an argument that currentness is irreducibly a replay, with what that costs a recognizer.

Acceptance check: the missed-revocation and lineage-versus-current processes are decided correctly by whatever object is proposed.

Context: projects/normativity/legitimacy/rounds/2026-08-25-legitimate-evolution/CROSS_PROCESS_INTERFACE.md

Registered results bearing on this item

None registered.

Where it hangs

Rounds and decisions that touch it

None recorded.