jcosta33 Settle
Do not dump solvable technical decisions on the user. Prove the answer.
Method
- State the decision, constraints, and failure cost.
- Inspect the code, tests, configuration, project precedent, and current behavior.
- Check current authoritative documentation, standards, and primary empirical evidence where the repository cannot decide the matter.
- Compare only viable options. Score fit, complexity, reversibility, operational cost, failure modes, and evidence strength.
- Reject folklore, popularity, and model agreement as proof.
- Choose the strongest supported option. Prefer the simpler reversible choice when evidence ties.
- Apply the decision when the active task grants write authority. Verify the affected behavior.
- Stop only when product intent, public behavior, material security or cost, waiver, irreversible action, or acceptance remains human-owned.
Output
State the decision, decisive evidence, why the nearest alternative lost, and any residual risk in plain chat Markdown. Show exact source locators and the smallest raw output needed to prove the call.