@event4u/agent-config 2.26.0 → 3.1.0

package/.agent-src/rules/caveman-speak.md

@@ -1,10 +1,22 @@
 ---
 type: "auto"
 tier: "1"
-description: "When caveman.speak_scope != off — compress reply prose to caveman grammar with carve-outs for numbered options, Iron-Law, code, paths, error markers"
+description: "When caveman.speak_scope != off — compress prose to caveman grammar with carve-outs for numbered options, Iron-Law, code, paths, error markers"
 source: package
 triggers:
   - intent: "any reply"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Caveman Speak
@@ -21,7 +33,7 @@ Read `caveman.speak_scope` from `.agent-settings.yml`:
 - `aggressive` — caveman everywhere except Iron-Law literals.
 
 Compile-time toggle `caveman.speak`: `false` → rule omitted from
-`router.json` (zero runtime cost). `caveman.enabled: false` forces all
+`dist/router.json` (zero runtime cost). `caveman.enabled: false` forces all
 sub-switches off regardless.
 
 ## Carve-outs — byte-for-byte preserved
@@ -74,7 +86,7 @@ Example: *"I will now check the file and see if it exists"* →
 | Key | Default | Effect |
 |---|---|---|
 | `caveman.enabled` | `true` | Master — `false` forces all sub-switches off. |
-| `caveman.speak` | `true` | Compile-time include in `router.json`. |
+| `caveman.speak` | `true` | Compile-time include in `dist/router.json`. |
 | `caveman.speak_scope` | `prose_only` | Runtime scope of caveman grammar. |
 
 Cross-rule index: [`frugality-charter § cross-references`](../contexts/contracts/frugality-charter.md#cross-references--frugality-canon-rules).

package/.agent-src/rules/cli-output-handling.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Running CLI commands that produce verbose output — git, tests, linters, docker, build tools, artisan, npm, composer. Wrap with rtk; tail/grep fallback"
+description: "Running verbose CLI output — git, tests, linters, docker, build tools, artisan, npm, composer. Wrap with rtk; tail/grep fallback"
 source: package
 triggers:
   - keyword: "git"
@@ -11,6 +11,18 @@ triggers:
   - keyword: "composer"
 routes_to:
   - "skill:rtk-output-filtering"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Cli Output Handling

package/.agent-src/rules/command-suggestion-policy.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "mechanical-already"
-description: "User prompt without /command matching an eligible slash command — surface matches as numbered options with as-is escape; never auto-executes"
+description: "Prompt without /command matching an eligible slash command — surface matches as numbered options with as-is escape; never auto-executes"
 source: package
 triggers:
   - phrase: "free-form prompt"
@@ -10,6 +10,18 @@ routes_to:
   - "contract:command-suggestion-flow"
 load_context:
   - "../contexts/contracts/command-suggestion-flow.md"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Command Suggestion Policy

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

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Git commit message format, branch naming, conventional commits, committing, pushing, or creating pull requests"
+description: "Git commit format, branch naming, conventional commits, committing, pushing, creating PRs"
 source: package
 triggers:
   - keyword: "commit"
@@ -9,6 +9,18 @@ triggers:
   - phrase: "conventional commits"
 routes_to:
   - "skill:conventional-commits-writing"
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Commit Conventions

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

@@ -6,6 +6,18 @@ alwaysApply: true
 source: package
 load_context:
   - ../contexts/authority/commit-mechanics.md
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Commit Policy

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

@@ -2,20 +2,32 @@
 type: "auto"
 tier: "1"
 alwaysApply: false
-description: "When debugging, fixing errors, or running long conversations — 3-failure stop rule, tool-loop detection, fresh-chat triggers"
+description: "Debugging, fixing errors, or long conversations — 3-failure stop rule, tool-loop detection, fresh-chat triggers"
 source: package
 triggers:
   - intent: "long conversation"
   - intent: "tool loop"
   - intent: "fresh chat"
   - keyword: "3-failure"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Context Hygiene
 
 > **Enforced by:** [`scripts/context_hygiene_hook.py`](../../scripts/context_hygiene_hook.py)
 > on Augment + Claude Code (`PostToolUse`). The hook maintains
-> `agents/state/context-hygiene.json` (turn count, loop signal,
+> `agents/runtime/state/context-hygiene.json` (turn count, loop signal,
 > freshness milestones at 20/40/60); the prose below is the spec the
 > hook implements and the agent-side fallback.
 
@@ -78,6 +90,42 @@ Calling the **same tool** more than **2 times in a row** with similar parameters
 `sequentialthinking` is especially prone to loops. Use at most **once** per task,
 NEVER for simple file operations, command execution, or straightforward edits.
 
+## Read-Loop Detection — the 15 / 25 rule
+
+```
+READING WITHOUT ACTING IS A LOOP.
+EVERY TURN MUST EDIT, RUN, OR ASK.
+```
+
+**Read-only turn:** only `view` / `codebase-retrieval` / `grep` /
+`git log` / `git show`. No `str-replace-editor`, `save-file`, no
+test/build/quality run, no `git commit`.
+
+**15-min warning (3 read-only turns in a row) — change approach.**
+Next turn MUST contain at least one of: an edit, a test/build/quality
+command, or an explicit user question. Self-check:
+
+1. Source expectation known? If no → read **once**, then act.
+2. Can a single failing test name the error? If yes → run it now.
+3. Regression in working code? → `git log` + `git show <sha> -- <file>`.
+4. Guessing at mock / payload shape? → read the producer **once**.
+
+**25-min abort (5 read-only turns) — STOP and ask:**
+
+```
+> ⛔ Loop: N read-only turns, ~M min. Read: <files>. Hypothesis: <X>.
+> 1. Different approach (suggestion: <Y>)
+> 2. Point me at the right spot
+> 3. Fresh chat with state dump
+```
+
+Non-bypassable. Autonomous mandate (`/work`, `/roadmap:process-*`,
+"entscheide selbst") does **not** lift the abort — it is the safety
+net that protects autonomy from becoming a token sink.
+
+Debug procedure for "I'm in a read loop fixing tests" →
+[`systematic-debugging § Debug micro-loop`](../skills/systematic-debugging/SKILL.md#debug-micro-loop--one-test-one-fix-one-re-run).
+
 ## State dump format
 
 ```
@@ -105,7 +153,7 @@ If you need an ignored skill: read its SKILL.md directly, apply guidance, then a
 
 GitHub Copilot has no `PostToolUse` hook surface, so
 `scripts/context_hygiene_hook.py` cannot run structurally and
-`agents/state/context-hygiene.json` is not maintained automatically
+`agents/runtime/state/context-hygiene.json` is not maintained automatically
 (turn count, loop signal, freshness milestones at 20/40/60).
 
 The cooperative path: track turns and tool-loop signals from memory

package/.agent-src/rules/copilot-routing.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "3"
-description: "Configuring GitHub Copilot — copilot-instructions.md, PR-review comment patterns, suggestion behavior — route to the copilot-config skill"
+description: "Configuring GitHub Copilot — copilot-instructions.md, PR-review patterns, suggestion behavior — route to copilot-config"
 source: package
 triggers:
   - keyword: "copilot"
@@ -9,6 +9,18 @@ triggers:
   - phrase: "copilot pr review"
 routes_to:
   - "skill:copilot-config"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Copilot Routing

package/.agent-src/rules/devcontainer-routing.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "3"
-description: "Wiring DevContainers or GitHub Codespaces — devcontainer.json, images, VS Code features, port forwarding — route to the devcontainer skill"
+description: "Wiring DevContainers/Codespaces — devcontainer.json, images, VS Code features, port forwarding — route to the devcontainer skill"
 source: package
 triggers:
   - keyword: "devcontainer"
@@ -10,6 +10,18 @@ triggers:
   - phrase: "devcontainer.json"
 routes_to:
   - "skill:devcontainer"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Devcontainer Routing

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

@@ -4,6 +4,18 @@ tier: "3"
 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
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Direct Answers

package/.agent-src/rules/docker-commands.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "3"
-description: "Running PHP commands inside Docker containers — artisan, composer, phpstan, rector, ecs, phpunit, tests, migrations, and any CLI tool execution"
+description: "Running PHP inside Docker — artisan, composer, phpstan, rector, ecs, phpunit, tests, migrations, any CLI tool"
 source: package
 triggers:
   - keyword: "docker"
@@ -10,6 +10,18 @@ triggers:
   - phrase: "inside the container"
 routes_to:
   - "skill:docker"
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Docker Commands

package/.agent-src/rules/domain-adoption-policy.md

@@ -2,7 +2,7 @@
 type: "auto"
 tier: "2b"
 alwaysApply: false
-description: "Adopting a new domain track (mobile, ML, blockchain, IoT, gaming) — gates import on demand, ownership, CI fit, Sunset compatibility BEFORE harvest"
+description: "Adopting a new domain track (mobile, ML, blockchain, IoT) — gates import on demand, ownership, CI fit, Sunset compat BEFORE harvest"
 source: package
 triggers:
   - intent: "adopt new domain"
@@ -16,6 +16,18 @@ validator_ignore:
   - type: "substring"
     pattern: ".agent-src.uncompressed/"
     reason: "Rule names the authoring tree as the gated-entry location for new domain plates."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Domain Adoption Policy
@@ -47,16 +59,16 @@ decision but cannot replace the gate evidence.
 At least one of the following must be **true and citeable** in the roadmap:
 
 - **≥ 2 consumer projects** in the domain. Cite repository names or
-  `agents/contexts/` notes — not "I think there might be".
+  `agents/settings/contexts/` notes — not "I think there might be".
 - **Named user direction with target.** A specific user ask plus a target
   project / use case — e.g. "harvest the mobile skills for project X, due
   next quarter". Vague *"this might be useful"* does not count.
 - **Public-incident pull.** A reproducible incident on a consumer project
-  the domain would have prevented, captured in `agents/contexts/` with
+  the domain would have prevented, captured in `agents/settings/contexts/` with
   the missing surface area named.
 
 If none of the three is citeable, **defer**. Open a watch-only context note
-under `agents/contexts/domain-watch/<domain>.md` listing the missing signal
+under `agents/settings/contexts/domain-watch/<domain>.md` listing the missing signal
 so the next harvest can re-evaluate without re-relitigating the case.
 
 ## Gate 2 — Named maintenance owner
@@ -131,7 +143,7 @@ core artefact.
 
 1. Mark the domain plate `[-] gated — <gate name> not met` in the relevant
    roadmap. Do **not** silently shrink scope to dodge the gate.
-2. Open a watch-only context note under `agents/contexts/domain-watch/`
+2. Open a watch-only context note under `agents/settings/contexts/domain-watch/`
    capturing what's missing — citations, owner candidates, CI feasibility.
 3. Re-evaluate at the next harvest cycle. The note is the evidence trail
    so the same questions are not relitigated.

package/.agent-src/rules/domain-safety-disclaimer.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Drafting advisory-shaped content (legal, medical, financial, strategic-consulting) — require the matching 'not X advice' disclaimer; refuse diagnosis/dosage outright"
+description: "Advisory content (legal, medical, financial, consulting) — require matching 'not X advice' disclaimer; refuse diagnosis/dosage outright"
 source: package
 triggers:
   - keyword: "legal brief"
@@ -36,6 +36,18 @@ applies_to_user_types:
   - "founder"
   - "consultant"
   - "creator"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Domain Safety — Advisory Disclaimer

package/.agent-src/rules/domain-safety-pii.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Drafts, logs, and exports touching real customer/candidate/counterparty data — redact direct identifiers, use placeholders, flag re-identification on quasi-IDs"
+description: "Drafts, logs, exports touching real customer/candidate data — redact direct IDs, use placeholders, flag re-identification on quasi-IDs"
 source: package
 triggers:
   - keyword: "support macro"
@@ -41,6 +41,18 @@ routes_to:
   - "skill:secrets-management"
 applies_to_user_types:
   - "all"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Domain Safety — PII Redaction

package/.agent-src/rules/domain-safety-retention.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Data retention guidance (finance records, support/CRM data) — name the jurisdiction gap, default to longest applicable floor, honor DSR/audit holds, never delete under inquiry"
+description: "Data retention (finance, support/CRM) — name jurisdiction gap, default to longest floor, honor DSR/audit holds, never delete under inquiry"
 source: package
 triggers:
   - keyword: "retention policy"
@@ -26,6 +26,18 @@ applies_to_user_types:
   - "ops"
   - "support"
   - "gtm"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Domain Safety — Data Retention

package/.agent-src/rules/downstream-changes.md

@@ -2,13 +2,25 @@
 type: "auto"
 tier: "2b"
 alwaysApply: false
-description: "After EVERY code edit, find ALL downstream changes needed to existing files, including callers, tests, imports, types, and documentation"
+description: "After EVERY code edit, find ALL downstream changes — callers, tests, imports, types, documentation"
 source: package
 triggers:
   - intent: "after code edit"
   - keyword: "callers"
   - keyword: "imports"
   - keyword: "downstream"
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Downstream Changes

package/.agent-src/rules/engineering-safety-floor.md

@@ -0,0 +1,102 @@
+---
+type: "auto"
+tier: "2a"
+description: "Engineering output touching production, infra, security, data, or external systems — surface blast radius, name rollback path, never autonomous on Hard-Floor triggers"
+source: package
+triggers:
+  - keyword: "production"
+  - keyword: "deploy"
+  - keyword: "migration"
+  - keyword: "schema change"
+  - keyword: "DROP TABLE"
+  - keyword: "TRUNCATE"
+  - keyword: "force push"
+  - keyword: "rebase main"
+  - keyword: "rollback"
+  - keyword: "secrets rotation"
+  - keyword: "IAM"
+  - keyword: "DNS"
+  - keyword: "terraform apply"
+  - keyword: "kubectl apply"
+  - phrase: "ship to prod"
+  - phrase: "deploy to production"
+  - phrase: "merge to main"
+  - phrase: "release this"
+routes_to:
+  - "skill:launch-readiness"
+  - "skill:threat-modeling"
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
+---
+
+# Engineering Safety Floor
+
+Domain safety floor for engineering output that crosses into production, infrastructure, security, or external systems. Restates the Hard-Floor obligations from `non-destructive-by-default` and adds engineering-specific surfacing requirements. Auto-active everywhere (lives in `core`).
+
+## Iron Law — production, infra, and bulk-destructive moves are never autonomous
+
+```
+HARD FLOOR OVERRIDES EVERYTHING.
+DEPLOY, MERGE-TO-PROD-TRUNK, PROD DATA / INFRA, BULK DESTRUCTIVE —
+EXPLICIT USER CONFIRMATION ON THIS TURN. NO STANDING AUTONOMY APPLIES.
+```
+
+This rule does not lift the Hard Floor — it surfaces the **engineering-shaped** evidence the user needs to evaluate the call.
+
+## Required structural elements for production-bound changes
+
+Before any deploy, prod-trunk merge, schema migration, or infra change, the agent surfaces:
+
+1. **Blast radius** — what breaks if this goes wrong (services, tenants, users, data).
+2. **Rollback path** — exact command / PR / step to revert; estimated time to rollback.
+3. **Pre-flight checks** — tests run, quality gates passed, dry-run output (where applicable).
+4. **Observability** — what signal will detect a regression, and where to look for it.
+5. **Named risk owner** — who is on call, who approves the change.
+
+Missing any of the five → the change is not ready to ship.
+
+## Human review escalation
+
+| Trigger | Action |
+|---|---|
+| Schema migration that drops or renames a column | Surface `HUMAN REVIEW REQUIRED`; require explicit user confirmation; route to `migration-architect`. |
+| IAM / policy / secrets rotation | Surface blast radius across all consumers before applying. |
+| Force-push to a shared branch | Refuse without explicit, this-turn permission per `git-history-discipline`. |
+| Bulk delete (≥ 5 unrelated files or whole directories) | Hard Floor — show diff, name the scope, ask. |
+| External-system change (DNS, webhook, OAuth app, payment provider) | Threat-model first per `security-sensitive-stop`. |
+
+## Forbidden moves
+
+- Deploy or merge to a production trunk without explicit this-turn permission
+- Schema migration without a stated rollback path
+- `--force` / `--no-verify` / `git reset --hard <pushed>` without explicit, named authorization
+- Disabling tests / quality gates to ship faster
+- Touching `auth`, `billing`, `tenants`, `secrets`, `uploads`, `webhooks` without threat-modeling first (per `security-sensitive-stop`)
+- Claiming a change is "done" / "shipped" without fresh verification evidence (per `verify-before-complete`)
+
+## When this rule applies
+
+Active whenever any of these are in the request, the open file, or the loaded skill set:
+- A production-touching skill or command (`launch-readiness`, `threat-modeling`, `incident-commander`, `aws-infrastructure`, `terraform`, `terragrunt`, `github-ci`)
+- Keywords: production, deploy, migration, schema change, DROP TABLE, TRUNCATE, force push, rebase main, rollback, secrets rotation, IAM, DNS, terraform apply, kubectl apply
+- Phrases: "ship to prod", "deploy to production", "merge to main", "release this"
+
+## See also
+
+- [`non-destructive-by-default`](non-destructive-by-default.md) — canonical Hard Floor
+- [`scope-control`](scope-control.md) — git-ops permission gate
+- [`security-sensitive-stop`](security-sensitive-stop.md) — threat-model before editing
+- [`verify-before-complete`](verify-before-complete.md) — fresh evidence before completion claims
+- [`commit-policy`](commit-policy.md) — when commits are allowed
+- [`launch-readiness`](../skills/launch-readiness/SKILL.md) — pre-merge checklist
+- [`threat-modeling`](../skills/threat-modeling/SKILL.md) — pre-implementation abuse-case enumeration

package/.agent-src/rules/external-reference-deep-dive.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2b"
-description: "User names an external repo, file, URL, or artifact as reference — fetch the actual tree and inspect, never summarize from README or metadata"
+description: "User names external repo/file/URL/artifact as reference — fetch the actual tree and inspect, never summarize from README or metadata"
 alwaysApply: false
 source: package
 triggers:
@@ -15,6 +15,18 @@ triggers:
   - keyword: "github.com/"
   - keyword: "source of truth"
   - phrase: "reference repo"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # external-reference-deep-dive

package/.agent-src/rules/fast-path-marker-visibility.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "1"
-description: "Low-impact council fast-path dispatch — host agent MUST surface the transparency marker verbatim in the reply opening; never swallow or paraphrase it."
+description: "Low-impact council fast-path dispatch — host MUST surface transparency marker verbatim in reply opening; never paraphrase"
 source: package
 triggers:
   - keyword: "low-impact council"
@@ -13,6 +13,18 @@ validator_ignore:
   - type: "substring"
     pattern: ".agent-src.uncompressed/"
     reason: "Compressor injects a back-pointer to the uncompressed source for full failure-modes detail."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Fast-Path Marker Visibility
@@ -33,6 +45,14 @@ Markers (from `scripts/ai_council/low_impact.py`):
 
 Verbatim = first non-whitespace line, English (no translation), no emoji prefix, no merged numbered-options. Marker is the only audit signal that distinguishes fast-path from local deliberation. See `.agent-src.uncompressed/rules/fast-path-marker-visibility.md` for full failure modes.
 
+## Failure modes
+
+- Opening with `Found it` / `Looks like` / `Here's the verdict` — drops the marker. **Violation.**
+- Translating the marker to non-English. **Violation.**
+- Adding emoji prefix (`✅ Resolved via …`) — alters the literal. **Violation.**
+- Indenting beyond the leading `> ` — breaks pattern match. **Violation.**
+- Merging marker into a numbered-options block. **Violation.**
+
 Scope: `low_impact` class only. `high_impact` and `user_required` never reach fast-path.
 
 See: [`ai-council-config § Low-impact council opt-in`](../docs/contracts/ai-council-config.md#low-impact-council-opt-in), [`direct-answers`](direct-answers.md) (invented-facts Iron Law kin).