code-time-discipline

Classify the task using a decision gate: edit only when source inspection shows a real bug, scaling risk, or contract drift with a correctness-preserving patch available. If the finding is speculative or the path is cold, report findings instead of editing.

Require an evidence standard for every finding: location, trigger, cost, growth, evidence level, and priority. Act only on P0 actual bottlenecks and justified P1 issues, and measure first with benchmarks, profiles, or query plans when inspection alone is insufficient.

Measure first when the suspected issue is non-trivial, performance-sensitive, concurrency-sensitive, or contract-sensitive and source inspection alone is not enough. Use existing tests, benchmarks, profiles, logs, or query plans before changing files.

Run the smallest meaningful gate set: unit or integration tests for the touched package, typecheck and lint for typed code, and benchmarks or query plans for non-trivial improvements. If a gate cannot run, state the exact blocker rather than claiming verification.

Decline editing when the edit would weaken validation, authorization, security, transactionality, ordering, public API contracts, or maintainability, or when the request is answered by explanation or review findings. State the classification directly and provide the next useful action.