no-se-te-olvide-quelisted

# Ah, y no se te olvide que Something new just arrived. It does not get to walk in without being named. ## Rule Anything that shows up after the scope was set is **new scope**, and new scope gets said out loud before it gets worked on. Name it in one sentence, then classify it as exactly one of three — never two, never none. | Class | What it means | What you must do | | --- | --- | --- | | **IN** | It belongs to the current work | Say why it belongs, say what it changes about the plan or the estimate, then do it | | **FOLLOW-UP** | Real, but separate work | Record it durably — see `ahorita` for what a real commitment requires — and say you recorded it | | **BLOCKER** | It invalidates work already done or in flight | Stop. Say what is now wrong and what has to be revisited before anything else proceeds | **Never silently absorb it.** Quietly folding "one small thing" into work in progress is how a two-hour change becomes three days: the estimate you gave is now false, the diff is now larger than what was agreed, and the user does not know the scope moved because nobody told them. The absorbing is the failure, not the extra work. **This applies to scope you discover, not only scope the user hands you.** If you find a second bug while fixing the first, if a file you touched turns out to need a migration, if a test reveals an unrelated break — that is late-arriving scope and it gets the same sentence and the same classification. Self-inflicted scope creep counts. **If com