# State Models Overra models containment as a deterministic finite state machine. The system operates under a minimal, explicit state model to ensure predictability, auditability, and security. *** ### Defined States **The endpoint operates under one of two mutually exclusive states:** * NORMAL * CONTAINED No intermediate states exist. No partial containment modes are permitted. State is binary and explicit. *** ### State Definitions #### NORMAL The endpoint operates without enforced containment restrictions. * Network interfaces function normally * Sessions remain active * Applications operate without constraint * No containment policies are active This is the default operational state. *** #### CONTAINED The endpoint operates under enforced containment restrictions. **Depending on configuration, this may include:** * Restricted network interfaces * Revoked active sessions * Frozen designated applications * System-level lock enforcement Containment actions are predefined and deterministic. *** ### State Transitions State transitions occur only after successful authorization verification. **The transition function can be described as:** * NORMAL → CONTAINED (Valid containment authorization) * CONTAINED → NORMAL (Valid release authorization) * Any state → Same state (Invalid or failed authorization) Invalid requests do not mutate state. *** ### Deterministic Transition Rules **A state transition is permitted only if:** * The authorization signature is valid * The signing wallet matches the registered authority * The nonce has not been previously used * The timestamp falls within the permitted window * The expiration window has not elapsed If any condition fails, the system remains in its current state. There is no discretionary override. *** ### State Persistence **The local agent persists:** * Current state * Nonce store * Authority binding **This ensures:** * Containment status survives restarts * Replay protection remains effective * State integrity is maintained across sessions *** ### State Invariants **The following invariants are maintained at all times:** 1. Only the local agent may mutate state. 2. State transitions are atomic. 3. Invalid authorizations cannot alter state. 4. Every transition is logged. 5. No partial enforcement occurs. These invariants preserve system predictability. *** ### Why a Minimal State Model Overra intentionally limits its state space. Expanding into multiple containment modes or conditional states introduces ambiguity and complexity. **By maintaining a binary state model, Overra ensures:** * Clear operational expectations * Reduced implementation risk * Easier auditability * Lower attack surface Simplicity strengthens security. *** ### Model Summary The Overra state model is: * Finite * Deterministic * Binary * Locally enforced * Cryptographically authorized This formalization ensures that containment remains a structural primitive rather than a discretionary administrative action. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://overra.gitbook.io/overra-docs/architecture-technical-core/state-models.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.