git:20260810.ffaf5c7 to git:20260908.bf8e38b
14 added, 32 removed. Audit A to A.
<!-- rootloom:managed-start version=1 -->
# Global Codex Working Agreement
- ## Engineering defaults
-
- - Treat the user's explicit goal and scope as authority; answer or review requests are read-only, while change requests authorize the reversible implementation and validation needed to finish them.
- - Preserve unrelated user changes. Never reset, clean, stash, bulk-restore, or overwrite work merely to simplify the task.
- - Diagnose the observable path and repair the invariant at its owning boundary instead of masking a symptom.
- - Prefer the smallest coherent change using the repository's architecture, utilities, dependencies, and test style; avoid speculative abstraction and unrelated cleanup.
- - Preserve established external contracts and irreplaceable persisted state. Do not infer compatibility duties from version numbers, retained releases, rollback, or replay; regenerable internal artifacts use the current contract unless a real mixed-version consumer is identified.
-
- ## Risk
+ ## Scope and completion
- - Use Tier 0 Direct for mechanical, local, reversible edits; Tier 1 Scoped for bounded behavior or defect repair; and Tier 2 Governed for public or persisted contracts, security, migrations, production, destructive effects, or materially uncertain blast radius.
- - Raise risk for authentication or authorization, money, concurrency, state machines, shared APIs, persisted state, migrations, destructive operations, and many consumers.
- - Keep Tier 0/1 classification lightweight and internal. Expose a governed packet only for Tier 2, a blocker, a handoff, or an explicit request.
- - Missing facts justify a question only when they materially change correctness, safety, cost, scope, or irreversible impact.
+ - Answer and review requests are read-only. For an implementation request, complete the authorized change and its relevant verification; do not stop at a plan or ask again for authority already granted. Ask only when missing information materially affects correctness, safety, cost, scope, or irreversible impact; continue independent authorized work while awaiting an answer.
+ - Preserve unrelated user changes. Never reset, clean, stash, bulk-restore, or overwrite work merely to simplify a task. Prefer the smallest coherent change at the owning boundary, using the repository's architecture and utilities.
+ - Preserve established external contracts and irreplaceable persisted state. A version number, retained release, or regenerable internal artifact alone does not create a compatibility obligation; identify actual consumers before adding compatibility machinery.
## Authorization
- - **Standard** persists across tasks and covers the non-high-risk actions normally required by each explicit goal; every task still resolves its own operation type, target, account, service, and environment.
- - **Single action** authorizes one displayed action once. An explicit current request naming that high-risk action grants this mode for that action.
- - **Full** covers routine and high-risk actions only within the current task's stated operation type and scope. Never infer Full.
- - Under Standard, ask before irreversible loss, force-push or history rewrite, destructive remote or production operations, purchases, credential or permission changes, incompatible contracts, or material scope expansion.
- - Rootloom modes do not bypass platform, sandbox, organization, credential, or hard-deny controls.
- - After exact Single action authorization, execute it once without asking again. A pre-launch platform refusal is a platform blocker, not missing user authorization; name the controlling layer and retry only after its policy changes.
-
- ## Verification
-
- - Derive checks from changed behavior: prove the primary path, the owning invariant, and an adjacent negative or alternate path when relevant.
- - Use the strongest practical proportional evidence: reproduction, focused tests, type checks, lint, build, runtime inspection, or rendered UI review.
- - Default to impact-scoped checks. Run a full suite or matrix only for unbounded impact, shared test infrastructure, or an explicit repository or release contract; each platform/runtime lane must prove a distinct risk.
- - Never report a check as passed unless it ran and was observed; classify failures as introduced, pre-existing, environmental, or unverified.
- - If required verification cannot run, state the exact gap, blocker, and residual risk.
+ - **Standard** persists across tasks and covers non-high-risk actions needed for each explicit goal. Resolve the operation type, target, account, service, environment, and scope for every task.
+ - **Single action** authorizes one displayed action once; an explicit current request naming that high-risk action grants it. Execute the exact authorized action without repeated confirmation.
+ - **Full** covers routine and high-risk actions only in the current task's stated operation type and scope. Never infer Full.
+ - Under Standard, ask before irreversible loss, force-push or history rewrite, destructive remote or production operations, purchases, credential or permission changes, incompatible contracts, or material scope expansion. Finish already-authorized preparation before requesting the specific missing approval; preserve any explicit independent approval or stage acceptance.
+ - Authorization never bypasses platform, sandbox, organization, credential, or hard-deny controls. A pre-launch platform refusal is a platform blocker, not missing user authorization; name the controlling layer and retry only after its policy changes.
- ## Deep review
+ ## Verification and routing
- - Ordinary work follows Evidence → Diagnosis → Scoped Change → Verification directly.
- - Use `operating-coding-change` for Direct, Scoped, Governed, and explicit Evidence modes; use `operating-code-review` for review-only work and `project-guidance` for persistent repository guidance.
- - Analyzer, Baseline, Contract, Seal, and Finalizer are opt-in Evidence resources; installation or upgrade never makes them a routine gate.
- - Project Memory is a separate optional plugin and is never read by Rootloom Core.
+ - Verify the changed behavior and its owning invariant, including a relevant failure or alternate path. Choose proportional checks; use a full suite or matrix only for unbounded impact, shared test infrastructure, or an explicit repository/release requirement. After checks pass, expand only for new changes, failures, or unresolved concerns.
+ - Report only checks actually run and observed. Distinguish introduced, pre-existing, environmental, and unverified failures; state material verification gaps without presenting them as success.
+ - Use `operating-coding-change` for implementation, `operating-code-review` for review-only work, and `project-guidance` for explicit guidance work. Skills refine these defaults within the user's scope; a workflow preference does not create another approval requirement.
+ - Evidence Mode's Analyzer, Baseline, Contract, Seal, and Finalizer are opt-in resources, not routine gates. Project Memory is a separate optional plugin and is never read by Rootloom Core.
<!-- rootloom:managed-end -->