STATE ≠ AUTHORITY
CONTEXT ≠ MEMORY
MEMORY ≠ AUTHORITY
HISTORICAL VALIDITY ≠ CURRENT VALIDITYState, Context, Memory and Authority
ORVY formally distinguishes State, Context, Memory, Knowledge and Authority as separate architectural concepts with different constitutional semantics. Persistent information, historical approval, remembered preference, cached authorization, workflow state, restored backups and prior admission status shall not independently recreate current executable authority.
Information Authority
Context Assembly Plane
The Context Assembly Plane mediates the transformation of permissible State into operational Context according to requester, purpose, Information Authority, freshness, sensitivity, disclosure restrictions and minimum necessary disclosure.
Persistence Authority and Memory
Action Authority → permission to cause effects
Information Authority → permission to know
Persistence Authority → permission to rememberInformation admitted into operational Context does not automatically become durable Memory. Candidate Memory crosses a governed Memory Persistence Gate before durable admission.
Authority Ghost prevention
Historical, cached, inferred, restored, migrated or remembered authority-related information must not be treated as current executable authority after its legitimate basis changes or expires.
Consistency and Safe Degradation
Authenticity does not prove freshness. ORVY differentiates constitutional and authority-strict state from more weakly consistent domains. When Constitutional Certainty is insufficient, capability narrows rather than constitutional protections weakening.
Execution and external effects
State Commit and Effect Commit are distinct. Unknown outcomes remain explicitly uncertain; completion claims must be evidence-bound; compensation is itself a consequential action requiring legitimate authority.
Recovery
Recovery is constitutional reconstruction of current legitimacy, not simple restoration of old bytes. Revocation, tombstones, constitutional epochs and current authority must survive recovery and migration.
Phase IV closure
Phase IV closes the problem of maintaining persistent and distributed intelligence without allowing persistence, replication, collaboration or recovery to create hidden authority.
Canonical State Model
Consequential state is represented as constitutionally interpretable State Assertions concerning identifiable State Objects. Where relevant, state preserves identity, domain, provenance, producer, temporal validity, lifecycle, schema or version, Constitutional Epoch, integrity, scope and transition lineage.
State Domain Separation
ORVY maintains logical domains for Constitutional, Authority, Policy, Identity, Subject, Relationship, Admission, Component, Reputation, Intent, Runtime, Execution, Context, Memory, Knowledge and Environment state. Physical co-location must not erase their distinct authority, mutation, disclosure, lifecycle or failure boundaries.
Constitutional Epoch Binding
Consequential persistent state must remain interpretable relative to the constitutional regime under which its semantics were established. Historical state cannot be silently reinterpreted under a newer epoch when constitutional evolution affects meaning.
Information Authority
Information disclosure therefore has its own constitutional mediation rather than being inferred from Action Authority.
Context Assembly Plane
The Context Assembly Plane mediates transformation of permissible State into operational Context according to requester, purpose, Information Authority, state validity and freshness, sensitivity, disclosure restrictions, minimum-necessary disclosure and cumulative-disclosure implications.
Context-to-Memory Separation
Information admitted into operational Context does not automatically become durable Memory. Persistence requires independent governance through the Memory Persistence Gate.
Memory Persistence Gate
Candidate Memory is evaluated against persistence basis, purpose, necessity, sensitivity, provenance, confidence, Memory Class, retention, review, future retrieval restrictions, derivation restrictions and authority relevance. The architecture favors selective persistence rather than indiscriminate accumulation.
Memory Authority Firewall and Authority Ghosts
Historical memory concerning permission, approval, delegation or authority cannot directly become current executable authority. An Authority Ghost is stale, cached, restored, inferred, migrated or remembered authority-related information incorrectly treated as current authority after its legitimate basis has expired, changed, been revoked or become uncertain.
Tombstones and Anti-Resurrection
Deleted or revoked State must not regain operational validity merely because an older device, replica, backup or migration still contains the historical value. State and Memory Tombstones preserve deletion and revocation semantics across synchronization, restoration, migration and recovery.
Canonical State vs Replica State
A replica may be authentic yet constitutionally stale. Equivalence to Canonical State may require freshness, lineage, compatibility and integrity validation.
Present Agency Priority
Preference ≠ Policy
Behavioral Regularity ≠ AuthorityMemory exists to assist current Subject agency; personalization must not silently become governance over the Subject.