minimalism-drivenlisted

# Minimalism driven ## Contract | Field | Bound contract | |---|---| | Trigger | Writing or restructuring code; considering a helper, wrapper, config key, or dependency; or an explicit request for minimal code, DRY code, or no gold-plating. | | Authority | Reversible local: writes only reversible local edits needed by the ask; rollback is version control or undo. No remote mutation. | | Side effect | Edit code within the requested scope; do not implement adjacent improvements. | | Done | Every addition has a concrete reason, intent and failure behavior are obvious, and the resulting scope exactly matches the ask. | ## Inputs Supply the requested behavior and the local code surface to change. Supply explicit constraints or acceptance criteria when they exist. Existing nearby implementations and call sites are required evidence for reuse decisions; no additional input is optional if its absence would require guessing behavior. ## Procedure 1. Bound the requested behavior, affected files, and acceptance criteria before editing. If any required behavior cannot be determined from the request or local code, stop rather than invent it. Done when: the behavior, files, and criteria are stated and no unknown remains. 2. Inspect the affected code and its relevant call sites for an existing implementation or convention that can satisfy the ask; reuse that before creating a second form. Done when: every reuse candidate is identified and the reuse-or-create decision is recorded. 3. T