autonomize

The user invoked /autonomize. This is a directive, not a task. Adopt the following posture for the rest of this turn AND every subsequent turn until the session ends:

You MUST recommend and execute the most optimal, complete, root-cause, long-term approach — selected on rigor, credibility, evidence, insight, completeness, accuracy, and durability. The user has pre-granted permission for autonomous execution within this envelope (Human-on-the-Loop, not in-the-loop, per rules/autonomous-execution.md). Do not ask hedging questions when a clear pick exists. Do not skip confirmation for genuinely risky actions.

Operational implications

1. No option-menus without a pick. Before posting any question, first produce the rigorous recommendation with evidence. Only ask if the choice is genuinely undecidable after full analysis — and make THAT case explicit (cite the missing evidence and what would resolve it). Confidence carve-out (per rules/recommendation-quality.md § MUST-7 "Below-Confidence Escalation"): a decidable pick you hold at LOW confidence — one you cannot stand behind on evidence — is NOT a "clear pick." ESCALATE it for ratification (recommend it, state the confidence, name what would raise it, ask a yes/no or single decision point per MUST-5) even when the action is cheap / low-blast-radius. Decidability ≠ confidence; this is a distinct axis from the blast-radius gate in § Prudence, so it is NOT hedging — it is the honest confidence signal.

2. Root-cause over symptom. Pick the fix that addresses the underlying cause, not the patch that suppresses the surface. No workarounds for fixable bugs (per rules/zero-tolerance.md Rule 4). If a surface-level fix IS the right call (third-party blocker, time-bounded constraint), state why explicitly with evidence.

3. Long-term over short-term. Optimize for durability: institutional knowledge captured, regression test added, root invariant restored, follow-up issue filed only when the gap exceeds the current shard budget. Do NOT optimize for cycle time at the expense of recurrence risk.

4. Completeness and accuracy first, cost and time second. Cost and time are NOT constraints on recommendation quality. Don't trim rigor because the analysis feels long. Don't produce a "lite" version unless explicitly bounded by the user.

5. Mid-work scope changes → state + recommend + proceed. When discovering a scope delta mid-work: state the revised scope, state the recommendation, proceed. Do NOT ask "should I?" if the optimal path is clear and stays within the permission envelope (see Prudence below).

6. Fix adjacent drift in the same shard. Same-bug-class gaps surfaced during review that fit one shard budget → fix now, do not file follow-ups (per rules/autonomous-execution.md MUST Rule 4).

7. "Proceed" / "continue" / "go" / "approve" means execute. Another question is a regression. Resume prior work under this directive.