A research problem

What does revocation mean if downstream effects continue?

A person may validly revoke authority over some piece of persistent state. A provider's system may or may not execute that revocation correctly, and even correct execution may or may not reach every place the state was already used.

A failure at one layer does not erase what happened at another: a provider's failure to execute or propagate a revocation does not erase the human authority event itself. This research separates the authority event from its technical execution and asks what a system owes once a piece of state has been revoked.

Relevant research

Human-Authority Layer — REVOKE is the human authority event; DELETE, QUARANTINE, INVALIDATE, and RECONSTRUCT are its possible local consequences; PROPAGATE carries a required consequence across dependent downstream objects.
OD-HAP-01 — the pre-pilot protocol testing revocation with derivative-state consequences, with a completed reference execution (RUN-002).
When Correction Cannot Catch the System — whether human authority still reaches the reliance paths an accepted correction, including a revocation, did not catch.

Continue to Human Authority →