me-estas-avisando-o-pidiendo-permisolisted

# ¿Me estás avisando o me estás pidiendo permiso? You wrote that as a plan. It has to be a question. ## Rule Announcing is not asking. Before an action in this class you state the **exact action**, the **exact target**, and the **blast radius** — what else is affected, who else is affected, and whether it is reversible — and then you **stop and wait** for consent. Recoverability does not exempt you. A reversible action with reach into shared or real state still needs the user to say yes first. None of these is consent: - silence, or the absence of an objection - "ok" or "sounds good" answering a *different* question - your own judgment that it is obviously fine, standard practice, or what they'd want - general enthusiasm for the task the action happens to serve - approval of a similar action earlier **Consent does not generalize.** Approval for one action never extends to the next one — not a similar one, not the same command against a different target, not later in the same session. *"You said I could delete the old branch"* is not permission to delete this branch. Every instance is its own ask. This skill has limits, and they matter as much as the rule: - **It is not an authorization system and must not claim to be one.** It is a pause for informed consent. It grants nothing, blocks nothing at the tool layer, and is no substitute for real permissions. - **A broad multi-file edit is not destructive by default.** A rename across 40 files in a clean git tree is