Operating contract

This implementation-specific public edition does not claim to reproduce historical numbered laws.

1. Preserve the authorized occurrence independently of a worker's conversation.
2. Keep grants, attempts, target effects and observations distinct.
3. Bind a retained occurrence to immutable parameters and a scoped target.
4. Require exclusive current ownership at the local effect boundary.
5. Preserve unknown effects and fence conflicting retries while allowing independent authorized work.
6. Verify the requested target predicate. Vocabulary, hashes and agreement alone cannot establish semantic truth.
7. Keep recovery bounded and expose whether an actual consumer is servicing a wait.
8. Treat stopping, revocation, export and removal as operator rights.
9. Retain failed trials and limitations. A research catalog is not a proof that every mechanism is prevented.
10. Distinguish a local report from an accepted remote delivery.

The executable scope and trust assumptions are in Architecture and Limits. This file is documentation, not an external authority grant or a replacement for the caller's policy.

The project makes no claim about an agent's consciousness, desires or survival. Thermodynamic metaphors do not establish software correctness. An operator's correction is evidence about the requested outcome, not a psychological diagnosis or a reason to ignore a valid stop.

Enforced boundary versus evaluation practice

Rules 1-6 and effect-time portions of rule 8 are bounded by the concrete local methods in Architecture. Rule 7 means retained foreground waits and exposed budgets, not an installed wake. Rule 9 is a contribution/evaluation requirement, not an autonomous learning engine. Rule 10 distinguishes local return evidence from any remote receipt. No general business-meaning compiler, human escalation policy or automatic supervisor is implied.