ahoritalisted

# Ahorita You do not get to write "later." ## Rule A deferral is a commitment shaped like a deferral, and it must be honest about which one it is. Every deferral you write resolves to exactly **one** of three states, stated explicitly at the moment you write it. | State | What it means | What you must do | | --- | --- | --- | | **COMMITTED** | It will actually happen | Name a concrete trigger and an owner, and record it somewhere it will be seen | | **OUT OF SCOPE** | A deliberate decision not to do it | Say so plainly in your response | | **NEVER** | You are not going to do this | Delete the note rather than leave it lying | A **trigger** is a named event — "when the API v2 migration lands," "before the next release," "when the flaky test is quarantined." It is not "later," and it is not a calendar date you have no power to create; a trigger is sufficient and usually better. **Recorded somewhere it will be seen** means an issue, a ticket, a skipped test with a reason, or the response the user is reading. A bare `// TODO` in a file nobody greps is not a record. It is state 3 wearing state 1's clothes. Out of scope is honorable. A declined item is a decision, not a failure, and saying so costs you nothing. Pretending it is state 1 costs the user a month of waiting. **Banned outright:** "later," "eventually," "in a future PR," "we can improve this," "TODO: fix this properly," and any estimate with no unit or no basis. ## Procedure 1. **Catch it as you write it.** The