Provenance & portability
Requirements for correction, revocation, purpose limitation, and portability in governed continuity.
For industry
System requirements for governed human authority
For teams building persistent, memory-carrying, or agentic systems: this research separates a human authority event from technical enforcement and provider compliance, and defines the operations that should follow it.
Governed lifecycle operations
The Human-Authority Layer Object Model and Lifecycle Bundles define the operations that follow a human authority event: 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 is the executable pre-pilot protocol testing this architecture: state visibility, revocation with derivative-state consequences, and explicit authority boundaries. Reference execution RUN-002 is complete against a synthetic system; the next gate, SUT-02, tests the protocol against a second, differently built system.
Transfer & revalidation
What a receiving system must reevaluate before it uses state transferred across a boundary.
Evaluation criteria
Proposed criteria for testing correction, revocation, and authority handling: source provenance, temporal validity, purpose continuity, context change, authority status, correction, revocation, inference discipline.
Publication standard
What must exist before an evaluation score is released: task record, configuration record, ground truth and review, limits and conflicts.
OD-HAP-01 does not select one mandatory technical implementation, has not been tested against a real provider, and does not claim that any system is compliant or that it is a validated standard or certification.