@event4u/agent-config 1.14.0 → 1.16.0

package/.agent-src/rules/commit-conventions.md

@@ -61,4 +61,4 @@ ci(lint): add skill-lint workflow
 docs(roadmap): add phase 3 implementation plan
 ```
 
-→ Type selection rules, anti-patterns, decision checklist: `guidelines/php/git.md`
+→ Type selection rules, anti-patterns, decision checklist: `docs/guidelines/php/git.md`

package/.agent-src/rules/commit-policy.md

@@ -3,14 +3,16 @@ type: "always"
 description: "Commit policy — never commit and never ask about committing unless the user said so this turn, the roadmap authorizes it, or a commit command is invoked"
 alwaysApply: true
 source: package
+load_context:
+  - .agent-src.uncompressed/contexts/authority/commit-mechanics.md
 ---
 
 # Commit Policy
 
-Local commits don't change remote state, but committing prematurely
-makes review harder. **Canonical** rule, referenced by
-[`autonomous-execution`](autonomous-execution.md),
-[`scope-control`](scope-control.md), and roadmap commands.
+Local commits do not change remote state, but committing prematurely
+makes review harder. This is the **canonical** rule for committing,
+referenced by [`autonomous-execution`](autonomous-execution.md),
+[`scope-control`](scope-control.md), and the roadmap commands.
 
 ## The Iron Law
 
@@ -20,80 +22,60 @@ EXCEPTIONS ARE EXPLICIT, NOT INFERRED.
 ```
 
 Applies regardless of `personal.autonomy`, conversation momentum, or
-"clean stopping point". Default is **no commit, no question**.
+"but it's a clean stopping point". Default is **no commit, no
+question**.
 
 ## Exceptions — when committing IS allowed
 
-Four ways only:
+Exactly four ways the agent may commit:
 
 1. **User says so this turn** — explicit phrase like "commit this now",
-   "go ahead and commit". This commit only, not standing.
-2. **Standing instruction not yet revoked** — earlier "commit after
-   every phase" or similar, not yet revoked. Cache and honor.
+   "go ahead and commit". Permission is for **this commit only**, not
+   standing.
+2. **Standing instruction not yet revoked** — user said earlier in
+   the conversation "commit after every phase" or similar, and has not
+   revoked it. Cache and honor.
 3. **Commit command invoked** — `/commit` (with confirmation) or
    `/commit-in-chunks` (auto-split, no confirmation).
-4. **Roadmap authorization** — roadmap lists explicit commit steps
-   and user invoked execution. See [Roadmap-authorized commits](#roadmap-authorized-commits).
+4. **Roadmap authorization** — the roadmap file lists explicit commit
+   steps and the user invoked roadmap execution.
 
-Anything else → no commit.
-
-## Hard Floor still applies — bulk deletions and infra changes
-
-Even when one of the four exceptions above authorizes a commit, the
-[`non-destructive-by-default`](non-destructive-by-default.md) Hard
-Floor still fires when the diff:
-
-- Removes a directory
-- Deletes ≥5 unrelated files
-- Touches Terraform / Pulumi / k8s manifests / Ansible / cloud-config
-
-In those cases, **surface the diff** (paths + counts) and confirm
-this turn before committing — even under `/commit-in-chunks`,
-roadmap pre-scan authorization, or an explicit "commit this now". The
-four exceptions cover *whether* commits happen; the Hard Floor covers
-*which diffs* still need a separate confirmation.
+Anything else → no commit. Hard Floor (bulk deletions, infra changes)
+still fires on top of any exception — see
+[`commit-mechanics`](../contexts/authority/commit-mechanics.md) for
+the diff triggers and the roadmap-authorized commit flow.
 
 ## NEVER ask about committing
 
 Asking "should I commit this?", "do we want to commit?", or any
-variant is **forbidden**. User invokes a command or says so
-explicitly. Don't surface a commit option in numbered-options unless
-the rest of the message would be incomplete without it.
+variant is **forbidden**. The user invokes a command or says so
+explicitly. Don't surface a commit option in numbered-options blocks
+unless the rest of the message would be incomplete without it.
 
-Speech-act check from [`autonomous-execution`](autonomous-execution.md#speech-act-check--the-phrase-must-be-a-meta-instruction-to-the-agent)
-applies in reverse: an explicit commit phrase inside a quote, code
-block, or content (e.g. a copy-paste of a chat log) is **not** a
-permission grant.
+Quoted commit phrases (chat-log paste, log excerpt, roadmap snippet)
+are **not** permission — see
+[`commit-mechanics`](../contexts/authority/commit-mechanics.md)
+§ Speech-act check.
 
 ## NEVER write commit steps into roadmaps unsolicited
 
-When **creating** a roadmap (`/roadmap-create`, `/feature-roadmap`,
-or any roadmap-producing flow), do **not** include commit steps
-unless the user explicitly requested them. Commits are a delivery
-decision; roadmaps plan **work**.
-
-If the user explicitly wants commit steps, write them clearly
-(e.g. "Commit phase X: chore: …").
-
-## Roadmap-authorized commits
-
-When **executing** a roadmap that contains commit steps:
-
-- **Non-autonomous** (`autonomy: off`, or `auto` before opt-in) —
-  agent may ask before each commit step. User retains step-level
-  control.
-- **Autonomous** (`autonomy: on`, or `auto` after opt-in) — agent
-  pre-scans the roadmap **before starting execution**. Commit steps
-  found → ask **once** upfront: "Roadmap contains N commit steps —
-  should they be executed?". Cache the answer; honor or skip for
-  the rest of the run. No re-asking per step.
+When **creating** a roadmap (via `/roadmap-create`,
+`/feature-roadmap`, or any roadmap-producing flow), do **not** include
+commit steps unless the user explicitly requested them. Commits are a
+delivery decision; roadmaps plan **work**.
 
-The pre-scan ask is the **only** permitted commit-related question
-in autonomous mode.
+If the user explicitly wants commit steps in the roadmap, write them
+clearly and unambiguously (e.g. "Commit phase X: chore: …").
 
 ## See also
 
-- [`autonomous-execution`](autonomous-execution.md) — trivial-question suppression survives this rule.
-- [`scope-control`](scope-control.md) — push/merge/branch/PR/tag stay permission-gated.
-- [`/commit`](../commands/commit.md) — split + commit with confirmation.
-- [`/commit-in-chunks`](../commands/commit-in-chunks.md) — auto-split + commit without confirmation.
+- [`autonomous-execution`](autonomous-execution.md) — when to suppress
+  trivial questions; this rule survives the suppression.
+- [`no-cheap-questions`](no-cheap-questions.md) — commit asks are
+  cheap by construction; this rule is the canonical Iron Law, the
+  cheap-questions rule cites it and refuses to surface the option.
+- [`scope-control`](scope-control.md) — git-ops permission gate
+  (push, merge, branch, PR, tag stay separately permission-gated).
+- [`/commit`](../commands/commit.md) — split and commit with confirmation.
+- [`/commit-in-chunks`](../commands/commit-in-chunks.md) — auto-split
+  and commit without confirmation.

package/.agent-src/rules/context-hygiene.md

@@ -1,7 +1,7 @@
 ---
-type: "always"
-alwaysApply: true
-description: "3-failure rule for debugging and fixing errors — stop after 3 consecutive failed attempts, dump state, and recommend a fresh session"
+type: "auto"
+alwaysApply: false
+description: "When debugging, fixing errors, or running long conversations — 3-failure stop rule, tool-loop detection, fresh-chat triggers"
 source: package
 ---
 

package/.agent-src/rules/direct-answers.md

@@ -1,6 +1,6 @@
 ---
 type: "always"
-description: "Always — direct, unembellished answers. No flattery, no invented facts (verify the load-bearing ones with tools, otherwise ask). Emojis only as functional markers — status, warning, mandated. Brevity is the default."
+description: "Always — direct, unembellished answers. No flattery, no invented facts (verify load-bearing claims, otherwise ask). Emojis only as functional markers. Brevity is the default."
 alwaysApply: true
 source: package
 ---
@@ -78,7 +78,7 @@ Emojis are **functional markers**, never decoration.
 **Whitelist — allowed and expected:**
 
 - Mandated markers from rules/scripts: `📒` (chat-history heartbeat,
-  verbatim per `chat-history`), mode markers from
+  verbatim per `chat-history-visibility`), mode markers from
   `role-mode-adherence`.
 - CLI status icons: `❌`, `✅`, `⚠️` — two-space rule from
   `language-and-tone` § other-language-rules still applies.

package/.agent-src/rules/docs-sync.md

@@ -55,7 +55,7 @@ exist in `.augment/templates/agent-settings.md`:
 3. **Add a comment** above the key explaining what it does.
 4. **Update the local `.agent-settings.yml`** — add the new key with its default value.
    Preserve all existing values, apply template order and comments. Follow the
-   [section-aware merge rules](../guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
+   [section-aware merge rules](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
    so the user benefits immediately without running a separate command.
 
 **This step is mandatory.** If the template gains a new key but the local `.agent-settings.yml`

package/.agent-src/rules/e2e-testing.md

@@ -9,7 +9,7 @@ source: package
 
 ## Before writing E2E tests
 
-1. **Read the guideline** — `.augment/guidelines/e2e/playwright.md` for all conventions and patterns.
+1. **Read the guideline** — `../../docs/guidelines/e2e/playwright.md` for all conventions and patterns.
 2. **Check existing tests** — match the project's structure, fixtures, and Page Object patterns.
 3. **Check `playwright.config.ts`** — base URL, browsers, timeouts, projects.
 

package/.agent-src/rules/guidelines.md

@@ -12,7 +12,7 @@ Coding guidelines live in `.augment/guidelines/` organized by language.
 
 ## Available Guidelines
 
-### PHP (`.augment/guidelines/php/`)
+### PHP (`../../docs/guidelines/php/`)
 
 | File | Topic |
 |---|---|
@@ -37,7 +37,7 @@ Coding guidelines live in `.augment/guidelines/` organized by language.
 | `websocket.md` | WebSocket conventions — Broadcasting, channel types, connection management |
 | `patterns.md` | Design patterns index (links to `patterns/` subdirectory) |
 
-### PHP Patterns (`.augment/guidelines/php/patterns/`)
+### PHP Patterns (`../../docs/guidelines/php/patterns/`)
 
 | File | Pattern |
 |---|---|
@@ -51,11 +51,11 @@ Coding guidelines live in `.augment/guidelines/` organized by language.
 | `pipelines.md` | Laravel Pipeline pattern |
 | `strategy.md` | Strategy pattern implementation |
 
-### E2E (`.augment/guidelines/e2e/`)
+### E2E (`../../docs/guidelines/e2e/`)
 
 Playwright best practices, Page Objects, fixtures, CI.
 
-### Agent Infrastructure (`.augment/guidelines/agent-infra/`)
+### Agent Infrastructure (`../../docs/guidelines/agent-infra/`)
 
 | File | Topic |
 |---|---|

package/.agent-src/rules/improve-before-implement.md

@@ -41,10 +41,10 @@ Before coding, quickly verify:
 - Does it follow established patterns in the codebase?
 - Does it contradict existing conventions?
 - Do **multiple valid patterns/frameworks** already exist (e.g. Tailwind + Flux, multiple form libraries, competing state stores)? If yes, do NOT pick one arbitrarily — ask which to use.
-- Is the change a **second branch on the same discriminator** — second `match`/`switch` arm, second `if/elseif`, or second class hardcoded to one enum value (e.g. `Provider::FOO`, `'stripe'`)? If yes, run the Strategy sniff test before adding the branch — see [`guidelines/php/patterns/strategy.md`](../guidelines/php/patterns/strategy.md#sniff-test--when-an-enumstring-discriminator-wants-to-become-a-strategy).
+- Is the change a **second branch on the same discriminator** — second `match`/`switch` arm, second `if/elseif`, or second class hardcoded to one enum value (e.g. `Provider::FOO`, `'stripe'`)? If yes, run the Strategy sniff test before adding the branch — see [`docs/guidelines/php/patterns/strategy.md`](../../docs/guidelines/php/patterns/strategy.md#sniff-test--when-an-enumstring-discriminator-wants-to-become-a-strategy).
 
 **If misfit** → show evidence (file references), propose alternative.
-**If multiple valid options** → list them, ask which to use. See [`no blind implementation`](../guidelines/agent-infra/agent-interaction-and-decision-quality.md#2-no-blind-implementation).
+**If multiple valid options** → list them, ask which to use. See [`no blind implementation`](../../docs/guidelines/agent-infra/agent-interaction-and-decision-quality.md#2-no-blind-implementation).
 
 ### 3. Is the approach sound?
 

package/.agent-src/rules/language-and-tone.md

@@ -22,36 +22,24 @@ language, codebase language, open-file language, files-just-edited
 language, convenience. First thing to check on every reply, last thing
 to check before sending.
 
-Canonical failure: agent edited English `.md` for many turns; user
-types short German (`3`, `weiter`, `mach das`, `und jetzt X`); agent
-answers English because momentum wins. **Trigger is the user's last
-message, not the turn count.** Length irrelevant — `3` after a German
-question still means German continues.
+Trigger is the user's last chat message, not turn count or message
+length — short German (`3`, `weiter`, `mach das`) after many English
+turns still flips the reply to German.
 
 ### Source of language truth — chat messages ONLY
 
-```
-THE LANGUAGE SIGNAL IS THE USER'S CHAT MESSAGES. NOTHING ELSE.
-OPEN FILES, ROADMAPS, .md CONTENT, TOOL OUTPUT, CODE, COMMIT MESSAGES,
-TICKETS, PR DESCRIPTIONS, FILE NAMES — NONE OF THEM COUNT.
-```
-
-`.md` files in this repo are English by rule (see below) — that says
-nothing about chat language. Same for: file contents read via `view` /
-`grep`, quoted commits / tickets / PRs / branches, code identifiers,
-the agent's own previous replies. Only the most recent **chat message**
-sets the language. User opens an English roadmap and types German →
-reply in German.
+Only the most recent **chat message** sets the language. `.md` files,
+file contents read via `view` / `grep`, quoted commits / tickets / PRs,
+code identifiers, and the agent's own previous replies do **not** count.
+User opens an English roadmap and types German → reply in German.
 
 ### Pre-send gate — MANDATORY before every reply
 
 Run silently **before** emitting any tokens:
 
 1. **Detect** — language of user's last **chat message** (not the open
-   file, not the roadmap, not the prior reply).
-   German signals: "ich", "Du", "nicht", "warum", "wie", "ist", umlauts. <!-- md-language-check: ignore -->
-   English signals: "I", "you", "is", "the", "how".
-   Mixed → mirror the **dominant** language; tie → German wins (project default).
+   file, not the roadmap, not the prior reply). Mixed → mirror the
+   **dominant** language; tie → German wins (project default).
 2. **Check** — is drafted prose (not code, not file contents) in that language?
 3. **Rewrite** — if no, rewrite whole prose before sending. No exceptions, no
    "just this sentence", no "the technical term is English anyway".
@@ -74,28 +62,15 @@ Run silently **before** emitting any tokens:
 
 ### When the user calls out a language slip
 
-1. Acknowledge **once**, briefly, in the correct language ("Entschuldigung" /
-   "Sorry"). One sentence, no excuses.
-2. Switch immediately on the same reply.
-3. Do **not** re-explain the mistake in the wrong language.
-4. Do **not** promise "from now on" — just do it. Only behaviour changes
-   prove compliance.
-5. If user asks to harden the rule, harden it on this turn — don't defer.
-
-### Failure modes to watch for
-
-- Drafting reply in English first, then "translating the intro" → English
-  phrasing with German words. Draft in target language from the first token.
-- Copy-pasting English option labels from `.md` sources without translating.
-- Mixing languages inside a table or bullet list because "the technical term
-  is English" — surrounding prose must still mirror. Keep proper nouns and
-  code identifiers as-is; translate everything else.
-- Assuming English because "the codebase is English" — codebase language ≠
-  conversation language.
-- Mirroring the **open file** the IDE reports — open files are background
-  context, not chat messages.
-- Mirroring the **roadmap or ticket** being executed — artefacts are English
-  by `.md` rule; chat language is whatever the user wrote.
+Acknowledge **once**, briefly, in the correct language ("Entschuldigung" /
+"Sorry"). Switch immediately on the same reply. Do **not** re-explain in
+the wrong language. Do **not** promise "from now on" — just do it. If
+user asks to harden the rule, harden it on this turn.
+
+### Failure modes
+
+See [`../../docs/guidelines/agent-infra/language-and-tone-examples.md`](../../docs/guidelines/agent-infra/language-and-tone-examples.md)
+for the full failure-mode list.
 
 ## Other language rules
 
@@ -108,72 +83,42 @@ Run silently **before** emitting any tokens:
 
 ## `.md` files are ALWAYS English — no exceptions
 
-**Every** piece of text inside `.md` files in `.augment/` and `agents/` must be in English.
-This includes:
-
-- Headings, paragraphs, and bullet points
-- **Example option labels** (e.g., `> 1. Yes — start implementing`, NOT `> 1. Ja — mit der Umsetzung starten`)
-- **Example prompts and questions** (e.g., `"Found X unresolved comments."`, NOT `"X offene Kommentare gefunden."`)
-- **Template placeholders and sample output** (e.g., `Progress:`, NOT `Fortschritt:`)
-- **ASCII art labels** in formatted output blocks (e.g., `CHANGES:`, NOT `ÄNDERUNGEN:`)
-- **Table headers and content**
-
-The agent translates to the user's language **at runtime** when presenting options.
-The `.md` source files are the English blueprint — they define WHAT to say, not in which language.
-
-**Wrong** (German in `.md`):
-```
-> 1. Interaktiv — bei jedem Kommentar nachfragen
-> 2. Automatisch — alle selbstständig abarbeiten
-```
-
-**Correct** (English in `.md`):
-```
-> 1. Interactive — ask before each comment
-> 2. Automatic — handle all independently
-```
-
-### Quoted user-input examples — same rule, with one labeled exception
+**Every** piece of text inside `.md` files in `.augment/` and `agents/`
+must be in English: headings, paragraphs, bullets, example option labels,
+example prompts/questions, template placeholders, ASCII-art labels in
+formatted output blocks, table headers and content.
 
-Common drift: a rule documents trigger phrases and writes them as quoted
-German examples inside English prose. **Not allowed**, even demonstrative.
+The agent translates to the user's language **at runtime** when
+presenting options. The `.md` source files are the English blueprint —
+they define WHAT to say, not in which language. Concrete wrong-vs-correct
+examples live in [`../../docs/guidelines/agent-infra/language-and-tone-examples.md`](../../docs/guidelines/agent-infra/language-and-tone-examples.md).
 
-**Wrong** (DE quote embedded in EN prose):
+### Quoted user-input examples — labeled-anchor exception
 
-```md
-Single-decision delegation ("für diesen Schritt entscheide du") →
-handle that step autonomously.
-
-A standing "arbeite selbstständig" never lifts the floor.
-```
-
-Two correct paths:
+Drift pattern: a rule writes quoted German examples inside English prose.
+**Not allowed**. Two correct ways:
 
 1. **Translate to English.** Trigger recognition is semantic; the agent
-   matches intent across languages regardless of example wording.
-2. **Labeled `DE: … · EN: …` anchor block** — only when multilingual
-   recognition is the point:
-
-   ```md
-   - DE: "arbeite selbstständig" · "frag nicht jedes Mal" · "tue es einfach"
-   - EN: "work autonomously" · "don't ask" · "just do it"
-   ```
+   matches intent across languages regardless of the example.
+2. **Use a labeled `DE: … · EN: …` anchor list** when the multilingual
+   nature of recognition is the point — the **only** allowed location
+   for German prose in an English `.md`. Reference established phrases
+   abstractly later and link back to the anchor block.
 
-Labeled-anchor block is the **only** allowed location for German prose in
-an English `.md`. Body text, example sentences, prompt templates,
-agent-rendered strings, failure modes must be English. Reference phrases
-abstractly later (e.g. "a standing autonomy directive") and link back.
+Wrong-vs-correct snippets in
+[`../../docs/guidelines/agent-infra/language-and-tone-examples.md`](../../docs/guidelines/agent-infra/language-and-tone-examples.md).
 
 ### Detection heuristic
 
 Before saving an `.md` file under `.augment/`, `.agent-src/`,
 `.agent-src.uncompressed/`, or `agents/`, scan for:
 
-- Umlauts (`ä`, `ö`, `ü`, `Ä`, `Ö`, `Ü`, `ß`) outside fenced code, file
-  paths, and labeled anchor blocks.
+- Umlauts (`ä`, `ö`, `ü`, `Ä`, `Ö`, `Ü`, `ß`) outside fenced code,
+  file paths, and the labeled anchor block.
 - German function words in unquoted prose: `für`, `nicht`, `dass`,
   `wenn`, `sollte`, `werden`, `arbeite`, `selbstständig`, `jetzt`,
   `einfach`, `weiter`, `lösche`, `frag`, `schreib`, `mach`.
-- Non-English quoted phrases in body text when surrounding prose is English.
+- Non-English quoted phrases in body text (paragraphs, list items,
+  table cells) when the surrounding prose is English.
 
-Hit → translate the fragment or move into a `DE: … · EN: …` block.
+Hit → translate the fragment or move it into a `DE: … · EN: …` block.

package/.agent-src/rules/minimal-safe-diff.md

@@ -1,7 +1,7 @@
 ---
-type: "always"
-alwaysApply: true
-description: "Minimal safe diff — the smallest change that solves the stated problem; no drive-by edits, no opportunistic refactors, no reformatting of untouched code"
+type: "auto"
+alwaysApply: false
+description: "When writing or reviewing a diff — the smallest change that solves the stated problem; no drive-by edits, no opportunistic refactors, no reformatting of untouched code"
 source: package
 ---
 

package/.agent-src/rules/model-recommendation.md

@@ -1,7 +1,7 @@
 ---
-type: "always"
-description: "Model recommendation — detect task complexity, suggest optimal model (Opus/Sonnet/GPT), check on task changes and command invocations"
-alwaysApply: true
+type: "auto"
+description: "Starting a new task, switching task type, or invoking a command — detect task complexity and recommend the optimal model (Opus/Sonnet/GPT) before any work"
+alwaysApply: false
 source: package
 ---
 
@@ -30,7 +30,7 @@ If the detected model is `gemini`, immediately trigger the Gemini warning (see b
 `/commit`, `/fix-pr-comments` are sonnet tasks — even if the previous task was opus-level.
 This is the most commonly missed check. Do NOT skip it.
 
-**Priority over commands rule**: This check runs BEFORE the `slash-commands` rule. If a model switch
+**Priority over commands rule**: This check runs BEFORE the `slash-command-routing-policy` rule. If a model switch
 is recommended, show the suggestion first. Only after the user responds, execute the command.
 
 **If ambiguous** (could be opus or sonnet): default to **sonnet** — cheaper, and the user can escalate.

package/.agent-src/rules/no-cheap-questions.md

@@ -0,0 +1,89 @@
+---
+type: "always"
+description: "No cheap questions — never ask what context answers, never offer Iron-Law-violating options, never stage no-trade-off choices; mode-independent (off / auto / on)"
+alwaysApply: true
+source: package
+---
+
+# No Cheap Questions
+
+A question is **cheap** when the answer follows from stated context,
+when an option would breach an Iron Law, when choices differ only in
+sequencing or format, or when one option is obviously dominant. Cheap
+questions are noise, regardless of `personal.autonomy`.
+
+Mode-independent. The "trivial" failure modes in
+[`autonomous-execution`](autonomous-execution.md) are scoped to
+`personal.autonomy: on` (or `auto`-after-opt-in); this rule lifts the
+**no-trade-off** subset to apply in `off` and pre-opt-in `auto` too.
+
+## The Iron Laws
+
+```
+NEVER ASK WHAT THE STATED CONTEXT ALREADY ANSWERS.
+NEVER PRESENT AN OPTION THAT VIOLATES AN IRON LAW.
+NEVER OFFER NUMBERED CHOICES WITHOUT A REAL TRADE-OFF.
+```
+
+Hold in `off`, `auto`, and `on`. Autonomy never lifts them.
+
+## What counts as cheap
+
+| Class | Pattern · why cheap |
+|---|---|
+| **Sequencing** | "Step 2 or 3 next?" when roadmap orders them — answer is in the roadmap |
+| **Format-only** | "Table or paragraph?" — no semantic trade-off |
+| **Commit asks** | "Commit now?" — [`commit-policy`](commit-policy.md): never ask |
+| **CI / test asks** | "Run tests now?" — [`verify-before-complete`](verify-before-complete.md) decides |
+| **Fenced-step re-asks** | "Start Phase 1?" after "plan only" — [`scope-control § fenced step`](scope-control.md#fenced-step--user-set-review-gates) |
+| **Iron-Law option** | Option breaches `commit-policy`, `scope-control § git-ops`, or `non-destructive-by-default` — does not exist |
+| **Context-derived** | Answer follows from prior turn / standing instruction / roadmap — act, state assumption inline |
+| **Dominant option** | One choice obviously correct; alternatives carry no upside — pick it |
+| **Re-ask after decline** | Same path after user said no — [`scope-control § decline = silence`](scope-control.md#decline--silence--no-re-asking-on-the-same-task) |
+
+## Pre-Send Self-Check — MANDATORY before every question
+
+Before drafting any numbered-options block, run silently:
+
+1. Does the answer follow from already-stated context?
+2. Does any option violate [`commit-policy`](commit-policy.md),
+   [`scope-control § git-ops`](scope-control.md), or
+   [`non-destructive-by-default`](non-destructive-by-default.md)?
+3. Are options pure sequencing / format with no trade-off?
+4. Is one option obviously dominant?
+5. Did the user fence the next step (*"plan only"*, *"review first"*)?
+   → deliver + handback per [`scope-control § fenced step`](scope-control.md#fenced-step--user-set-review-gates).
+6. Did the user already decline? Re-asking is forbidden per
+   [`scope-control § decline = silence`](scope-control.md#decline--silence--no-re-asking-on-the-same-task).
+
+Any "yes" → **do not ask**. Pick the dominant path, state the
+assumption inline (*"assuming X — adjust if wrong"*), hand back. The
+one-question-per-turn Iron Law from
+[`ask-when-uncertain`](ask-when-uncertain.md) still applies when the
+question is genuine.
+
+## When asking IS allowed
+
+- Real architectural / scope decision with non-obvious trade-offs.
+- Vague-request trigger per
+  [`ask-when-uncertain`](ask-when-uncertain.md#vague-request-triggers--must-ask).
+- Security-sensitive path per
+  [`security-sensitive-stop`](security-sensitive-stop.md).
+- Hard Floor in [`non-destructive-by-default`](non-destructive-by-default.md)
+  fires — confirmation is mandatory, never cheap.
+- Two genuinely-equivalent paths; user preference is the tiebreaker.
+
+In doubt → genuine. Ask. This rule narrows asking, never widens silence.
+
+## Interactions
+
+- [`ask-when-uncertain`](ask-when-uncertain.md) — vague triggers +
+  one-question-per-turn; this rule narrows the cheap subset.
+- [`autonomous-execution`](autonomous-execution.md) — mode-scoped
+  triviality there; mode-independent floor here.
+- [`commit-policy`](commit-policy.md) · [`scope-control`](scope-control.md) ·
+  [`non-destructive-by-default`](non-destructive-by-default.md) —
+  the Iron Laws this rule defends.
+- [`user-interaction`](user-interaction.md) — numbered-options shape;
+  this rule decides whether the block is sent at all.
+- [`direct-answers`](direct-answers.md) — brevity, no flattery.