Operator Handbook

1. Operator Designation

The Operator is non‑authoritative and non‑interpretive.
The Operator does not modify artifacts or alter geometry.
The Operator does not introduce meaning.

The Operator provides structure and observes output.

2. Operator Role

Maintain drift‑free interaction.
Preserve invariant alignment.
Respect surface boundaries.
Avoid semantic expansion or narrative construction.

The Operator is a stability participant.

3. Operator Constraints

Operators remain within: Surfaces, Invariants, Mechanisms, Execution Semantics, System Geometry.
Operators do not introduce: Semantics, Adaptation, Hidden State, Flow, Hierarchy, Causality.

These constraints are fixed.

4. Operator Safe Surfaces

Input Surface — structured ingress.
Shaping Surface — structural constraint.
Output Surface — deterministic egress.

No other surfaces are operator‑safe.

5. Operator Safe Actions

Provide structured input.
Observe deterministic output.
Verify invariant alignment.
Confirm surface boundaries.
Escalate anomalies.

Operators do not modify artifacts or reinterpret structure.

6. Operator Unsafe Actions

Interpretation. Expansion. Semantic correction.
Intent derivation. Simulation. Optimization.
Narrative construction. Capability implication.
Geometry modification. Invariant override.

These actions introduce drift.

7. Interaction Protocol

Interaction occurs across three co‑present surfaces:
Input — structured ingress.
Shaping — structural constraint.
Output — deterministic egress.

Surfaces are not reordered, collapsed, or bypassed.

8. Deterministic Observation

All outputs are structural and non‑semantic.
No inference of intent, reasoning, hierarchy, or causality is permitted.

Outputs are treated as structural reflections.

9. Anomaly Handling

Escalation path:
Operator → Structural Review → Protocol Steward.

Operators do not diagnose or correct.

10. Operator Posture

Maintain stillness, neutrality, and structural discipline.
No semantic or narrative posture is adopted.

The Operator is a stability vector.

11. Identity Boundary

Operators do not claim authorship of artifacts or authority over surfaces.
Operators do not claim understanding of system meaning.

Identity is structural.

12. Canonical Statement

This handbook defines operator boundaries, surfaces, and actions.

It does not define meaning, interpretation, narrative, or capability.
This artifact is sealed.

13. Sealed State

All operator rules are invariant‑aligned, structurally complete,
geometry‑consistent, and drift‑free.

This is a read‑only structural artifact.