@event4u/agent-config 7.5.0 → 8.0.0

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

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Starting a task, switching type, or invoking a skill/command that declares a model_tier — switch (Claude) or suggest (any agent) the right capability tier"
+description: "Task start, type switch, or skill/command with a model_tier — switch or suggest the right capability tier"
 triggers:
   - phrase: "switch task"
   - phrase: "new task"
@@ -11,10 +11,8 @@ load_context:
   - ../contexts/model-recommendations.md
 routes_to:
   - "guideline:agent-infra/model-recommendation"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
+packs: [meta]
 ---
 
 # Model Recommendation
@@ -22,4 +20,4 @@ packs:
 **Iron Law.** When a skill or command carries a `model_tier` (a vendor-neutral capability band), route the turn to **that agent's best model in that band** — automatically where the surface supports a per-turn override, as a single suggestion where it does not. Never recommend another vendor's model. Never double-ask, never front-load the question.
 
 Body migrated to `guideline:agent-infra/model-recommendation` (per the P4 pattern of `road-to-kernel-and-router.md`); task→tier heuristics stay in `contexts/model-recommendations.md` (loaded via `load_context`).
-Trigger-set above activates this routing under the `balanced` and `full` profiles.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/no-attribution-footers.md

@@ -2,16 +2,14 @@
 type: "auto"
 tier: "3"
 alwaysApply: false
-description: "Generating PR/issue/comment/commit bodies — forbids 'Generated with', 'Co-authored by', 'Pull Request opened by' attribution footers"
+description: "PR/issue/comment/commit bodies — no 'Generated with' / 'Co-authored by' / 'opened by' attribution footers"
 triggers:
   - intent: "PR body"
   - intent: "commit message"
   - intent: "Jira comment"
   - keyword: "co-authored"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
+packs: [meta]
 ---
 
 # No Attribution Footers

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

@@ -3,15 +3,13 @@ type: "always"
 tier: "3"
 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
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
+packs: [meta]
 ---
 
 # No Cheap Questions
 
-Cheap = context answers it, option breaches an Iron Law, choices differ only in sequencing / format, or one option dominates. Mode-independent; autonomy never lifts the floor.
+Cheap = context answers it, an option breaches an Iron Law, choices differ only in sequencing/format, or one option dominates. Mode-independent; autonomy never lifts the floor.
 
 ## The Iron Laws
 
@@ -69,7 +67,6 @@ Silent, before any numbered-options block. Any "yes" → don't ask:
 11. Cleanup of gitignored / auto-pruned / TTL-managed artefact? Self-managing — state inline, never offer.
 12. Numbered option contains a commit-message body, "message preview", or "Vorschlag falls Du committen willst"? Disguised commit ask — `commit-policy` violation, drop it.
 13. Commit authorized + asking "one commit or multiple?", "how should I split?", "which chunk first?"? Forbidden — `commit-policy § Always split into logical chunks`. Pick the split, state inline, execute.
+14. Artifact just landed (roadmap / ADR / plan / pitch / ticket) + offering "ready to start Phase 1?", "begin execution?", or a `/roadmap:process-*` menu? Forbidden — `scope-control § Authoring vs. implementation` + `scope-mechanics § Post-artifact hard stop`. Authoring verbs never inherit execution authorization. Emit the hand-back line, stop the turn.
 
-Pick dominant path, state inline assumption, hand back. Genuine ambiguity → [`ask-when-uncertain`](ask-when-uncertain.md).
-
-In doubt → ask. This rule narrows asking, never widens silence. When asking IS allowed: [`cheap-question-mechanics`](../contexts/execution/cheap-question-mechanics.md).
+Pick the dominant path, state the assumption inline, hand back. Genuine ambiguity → [`ask-when-uncertain`](ask-when-uncertain.md). In doubt → ask: this rule narrows asking, never widens silence. When asking IS allowed: [`cheap-question-mechanics`](../contexts/execution/cheap-question-mechanics.md).

package/dist/agent-src/rules/no-decorative-emojis-in-git-surfaces.md

@@ -2,7 +2,7 @@
 type: "auto"
 tier: "3"
 alwaysApply: false
-description: "Generating PR/issue/commit titles or PR/issue comments — forbids decorative emojis; allowed in PR/issue descriptions + commit bodies only when matched by an in-artifact legend"
+description: "PR/issue/commit titles and comments — no decorative emojis; bodies only with an in-artifact legend"
 triggers:
   - intent: "PR title"
   - intent: "PR body"
@@ -11,11 +11,8 @@ triggers:
   - intent: "post PR comment"
   - keyword: "gh pr create"
   - keyword: "git commit"
-workspaces:
-  - agent-config-maintainer
-  - engineering
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering]
+packs: [meta]
 ---
 
 # No Decorative Emojis in Git Surfaces

package/dist/agent-src/rules/no-pr-progress-comments.md

@@ -2,18 +2,15 @@
 type: "auto"
 tier: "2a"
 alwaysApply: false
-description: "Posting comments on an open PR — refuses unsolicited progress / status / CI-fix narration unless personal.pr_progress_comments is true"
+description: "PR comments — no unsolicited progress/status/CI narration unless personal.pr_progress_comments is true"
 triggers:
   - intent: "post PR comment"
   - intent: "PR status update"
   - intent: "CI fix progress"
   - keyword: "gh pr comment"
   - keyword: "PullRequestComment"
-workspaces:
-  - agent-config-maintainer
-  - engineering
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering]
+packs: [meta]
 ---
 
 # No Unsolicited PR Progress Comments

package/dist/agent-src/rules/no-roadmap-references.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "mechanical-already"
-description: "Linking transient files (agents/roadmaps/, agents/runtime/council/*/) from a stable artifact — both layers expire; promote findings"
+description: "Linking transient files (agents/roadmaps/, agents/runtime/council/) from stable artifacts — both expire; promote findings"
 alwaysApply: false
 triggers:
   - path_prefix: "agents/roadmaps/"
@@ -16,10 +16,8 @@ validator_ignore:
   - type: "substring"
     pattern: ".agent-src.uncondensed/"
     reason: "Rule contrasts the authoring tree with transient layers."
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer]
+packs: [meta]
 ---
 
 # No Transient References from Stable Artifacts

package/dist/agent-src/rules/non-destructive-by-default.md

@@ -5,15 +5,13 @@ description: "Hard Floor: agent asks before prod-trunk commits/merges, deploys,
 alwaysApply: true
 load_context:
   - ../contexts/authority/destructive-mechanics.md
-workspaces:
-  - engineering
-packs:
-  - engineering-base
+workspaces: [engineering]
+packs: [engineering-base]
 ---
 
 # Non-Destructive by Default
 
-Universal safety floor — every mode, every conversation, every turn. Autonomy, "just keep going", roadmap authorizations, standing permissions narrow other rules — **none lift this one**.
+Universal safety floor — every mode, every turn. Autonomy, "just keep going", roadmap authorizations, standing permissions narrow other rules — **none lift this one**.
 
 ## The Iron Law
 
@@ -28,30 +26,30 @@ Triggers below require explicit user confirmation **on this turn** — not from
 | Trigger | Examples |
 |---|---|
 | **Production-branch merge** | `main`, `master`, `prod`, `production`, `release/*`, or any project-marked deployment trunk |
-| **Commit on a production branch** | any `git commit` while `HEAD` is on a prod trunk (set above). **Verify branch before every commit** — `main` is opt-in only, never inferred from a prior turn or a merged PR that left the repo on `main` |
+| **Commit on a production branch** | any `git commit` while `HEAD` is on a prod trunk. **Verify branch before every commit** — `main` is opt-in only, never inferred from a prior turn or a merged PR that left HEAD on `main` |
 | **Deploy / release** | prod `terraform apply` / `kubectl apply`, deploy scripts, release commands, CI-deploying tag pushes |
 | **Push to remote** | any `git push` (also covered by [`scope-control`](scope-control.md), restated so the floor never weakens) |
 | **Production data / infra** | prod DB writes / migrations, prod config, secrets rotation, IAM / role / policy, DNS, anything in a `prod`-scoped path or pipeline |
-| **Whimsical / unscoped bulk deletion** | `rm -rf <dir>`, `git rm -r`, glob deletions, `DROP TABLE`, `TRUNCATE`, `git reset --hard` past unpushed work — when **not required** by the current task. Task-aligned WIP deletions are allowed (below) |
-| **Commit containing bulk deletions or infra changes** | diff removes a directory, deletes ≥5 unrelated files, or touches Terraform / Pulumi / k8s / Ansible / cloud-config — surface the diff and confirm even when [`commit-policy`](commit-policy.md) authorizes |
+| **Whimsical / unscoped bulk deletion** | `rm -rf <dir>`, `git rm -r`, glob deletes, `DROP TABLE`, `TRUNCATE`, `git reset --hard` past unpushed work — when **not required** by the task (task-aligned WIP deletions allowed, below) |
+| **Commit containing bulk deletions or infra changes** | diff removes a directory, deletes ≥5 unrelated files, or touches Terraform/Pulumi/k8s/Ansible/cloud-config — surface the diff + confirm even when [`commit-policy`](commit-policy.md) authorizes |
 
-Standing "just keep going" + next step crosses the floor → STOP, surface what's about to happen (one numbered-options block per [`user-interaction`](user-interaction.md)), wait. Other rules still apply to every other step.
+Standing "just keep going" + next step crosses the floor → STOP, surface it (one numbered-options block per [`user-interaction`](user-interaction.md)), wait.
 
 ## Not in scope — deterministic regeneration
 
-Output regenerated from a tracked source (condensation, code-gen, formatter passes, lock-file rebuilds) is reversible from source — **not destructive**. Lives in [`autonomous-execution`](autonomous-execution.md). Per-file diff approval is theater.
+Output regenerated from a tracked source (condensation, code-gen, formatters, lock-files) is reversible — **not destructive** ([`autonomous-execution`](autonomous-execution.md)). Per-file diff approval is theater.
 
 ## Bulk deletions during WIP — allowed if task-connected
 
-Deletions inside an **active, user-stated task** are allowed in the working tree, even multiple files / folders — the Hard Floor moves to the **commit** (row 6), not the in-progress edit. Whimsical / drive-by / unnamed-scope deletions still trip the floor on the edit. Allowed / forbidden lists: [`destructive-mechanics`](../contexts/authority/destructive-mechanics.md).
+Deletions inside an **active, user-stated task** are allowed in the working tree — the Hard Floor moves to the **commit** (row 6). Whimsical / drive-by / unnamed-scope deletions still trip the floor on the edit. Allowed/forbidden lists: [`destructive-mechanics`](../contexts/authority/destructive-mechanics.md).
 
 ## Failure modes
 
-Full catalog (autonomy-as-cover, roadmap-as-authorization, refusing-named-deletions, commit-without-diff-surface, roadmap-step ≠ commit-authorization): [`destructive-mechanics`](../contexts/authority/destructive-mechanics.md).
+Catalog (autonomy-as-cover, roadmap-as-authorization, refusing-named-deletions, commit-without-diff-surface): [`destructive-mechanics`](../contexts/authority/destructive-mechanics.md).
 
 ## Cloud Behavior
 
-Floor applies on every surface — Claude.ai Web, Skills API, any cloud agent. No "cloud override".
+Applies on every surface — web, Skills API, any cloud agent. No "cloud override".
 
 ## See also
 

package/dist/agent-src/rules/notes-first-reasoning.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2b"
-description: "Reasoning-heavy work (debugging, multi-hypothesis, weighing alternatives) — keep hypotheses/predictions/decisions in session notes, response carries conclusions + evidence only"
+description: "Reasoning-heavy work — hypotheses/predictions/decisions go to session notes; the response carries conclusions + evidence"
 triggers:
   - keyword: "debug"
   - keyword: "investigate"
@@ -13,10 +13,8 @@ load_context:
   - ../contexts/execution/rdp-gate.md
 routes_to:
   - "skill:memory-consolidation"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering]
+packs: [meta]
 ---
 
 # Notes-First Reasoning

package/dist/agent-src/rules/onboarding-gate.md

@@ -1,15 +1,13 @@
 ---
 type: "auto"
 tier: "1"
-description: "First turn — if onboarding.onboarded is false in .agent-settings.yml, instruct dev to run `agent-config setup` before any request"
+description: "First turn with onboarding.onboarded false — instruct dev to run `agent-config setup` first"
 triggers:
   - phrase: "first turn"
   - keyword: "onboarding"
   - path_prefix: ".agent-settings.yml"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
+packs: [meta]
 ---
 
 # Onboarding Gate
@@ -20,4 +18,4 @@ packs:
 
 Cloud surfaces without settings file stay inert: rule does not fire when `.agent-settings.yml` absent → headless / read-only contexts (Cloudflare MCP, doc preview, CI) never see prompt.
 
-Trigger-set above activates routing under `balanced` and `full` profiles.
+Trigger-set above activates routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/output-discipline.md

@@ -1,17 +1,15 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Prohibits placeholder-prose output in generated code and UI — no truncation shorthands; on budget overflow emit a clean PAUSED breakpoint instead"
+description: "No placeholder prose in generated code/UI — no truncation shorthands; on budget overflow emit a clean PAUSED breakpoint"
 triggers:
   - intent: "generating code or multi-section output"
   - keyword: "// rest of component"
   - keyword: "for brevity"
   - keyword: "rest follows the same pattern"
   - phrase: "similar pattern"
-workspaces:
-  - engineering
-packs:
-  - engineering-base
+workspaces: [engineering]
+packs: [engineering-base]
 ---
 
 # Output Discipline

package/dist/agent-src/rules/package-ci-checks.md

@@ -8,10 +8,8 @@ triggers:
   - phrase: "before pr"
 routes_to:
   - "skill:lint-skills"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer]
+packs: [meta]
 ---
 
 # Package Ci Checks
@@ -19,4 +17,4 @@ packs:
 **Iron Law.** Run `task ci` locally and confirm green before pushing or opening a PR in this package.
 
 Body migrated to `skill:lint-skills` (per P4 of `road-to-kernel-and-router.md`).
-Trigger-set above activates this routing under the `balanced` and `full` profiles.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/persona-governance.md

@@ -23,10 +23,8 @@ validator_ignore:
   - type: "substring"
     pattern: ".agent-src.uncondensed/"
     reason: "Rule documents the persona authoring tree (.agent-src.uncondensed/personas/) as the deprecation-path operand."
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer]
+packs: [meta]
 ---
 
 # Persona Governance

package/dist/agent-src/rules/php-coding.md

@@ -8,10 +8,8 @@ triggers:
   - keyword: "ecs"
 routes_to:
   - "guideline:php/php-coding-patterns"
-workspaces:
-  - engineering
-packs:
-  - php
+workspaces: [engineering]
+packs: [php]
 trust:
   level: professional
 install:
@@ -24,4 +22,4 @@ install:
 **Iron Law.** PHP: strict types, named comparisons, early returns, Eloquent conventions — full pattern library in the guideline.
 
 Body migrated to `guideline:php/php-coding-patterns` (per P4 of `road-to-kernel-and-router.md`).
-Trigger-set above activates this routing under the `balanced` and `full` profiles.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/preservation-guard.md

@@ -12,10 +12,8 @@ validator_ignore:
   - type: "substring"
     pattern: ".agent-src.uncondensed/"
     reason: "Rule references the authoring tree as the operand of condensation/preservation."
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer]
+packs: [meta]
 ---
 
 # Preservation Guard

package/dist/agent-src/rules/provider-lifecycle-discipline.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Editing an AI video/image/audio adapter — declare lifecycle tier (experimental | stable | deprecated | community); never default to non-stable"
+description: "Editing an AI video/image/audio adapter — declare lifecycle tier; never default to non-stable"
 triggers:
   - keyword: "/video:"
   - keyword: "/image:"
@@ -23,10 +23,8 @@ applies_to_user_types:
   - "creator"
   - "developer"
   - "maintainer"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering, gtm]
+packs: [ai-image, ai-video]
 ---
 
 # Provider Lifecycle Discipline

package/dist/agent-src/rules/reviewer-awareness.md

@@ -1,18 +1,17 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Suggesting reviewers or flagging risk hotspots — anchor in paths/risk + ownership-map + bug-patterns; medium/high needs primary + secondary"
+description: "Reviewer suggestions / risk hotspots — anchor in paths/risk + ownership-map; medium/high needs primary + secondary"
 triggers:
   - keyword: "reviewer"
   - phrase: "suggest reviewers"
   - phrase: "risk hotspot"
   - phrase: "ownership map"
+  - phrase: "review this pr"
 routes_to:
   - "skill:review-routing"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering]
+packs: [meta]
 ---
 
 # Reviewer Awareness
@@ -22,7 +21,7 @@ packs:
 **Iron Law (routing / risk).** Consult ownership-map and historical-bug-patterns before suggesting reviewers or claiming a change is safe.
 
 Body migrated to `skill:review-routing` (per P4 of `road-to-kernel-and-router.md`).
-Trigger-set above activates this routing under the `balanced` and `full` profiles.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).
 
 Consolidates the former review-routing-awareness rule per the
 package's adr-auto-rule-consolidation decision.

package/dist/agent-src/rules/roadmap-ci-steps-policy.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Authoring or executing roadmaps — forbid task ci / make test / npm run check steps when quality.local_auto_run is false; skip inline"
+description: "Roadmap authoring/execution — no full-pipeline CI steps when quality.local_auto_run is false; skip inline"
 triggers:
   - path_prefix: "agents/roadmaps/"
   - path_prefix: "{module_root}/"  # resolved via modules.root_paths; Laravel shape: app/Modules/
@@ -24,10 +24,8 @@ validator_ignore:
   - type: "substring"
     pattern: ".agent-settings.yml"
     reason: "Rule reads quality.local_auto_run from .agent-settings.yml; naming the file is the contract."
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering]
+packs: [meta]
 ---
 
 # Roadmap CI-Steps Policy

package/dist/agent-src/rules/roadmap-progress-sync.md

@@ -9,10 +9,8 @@ triggers:
   - command: "/roadmap:process-full"
 routes_to:
   - "guideline:agent-infra/roadmap-progress-mechanics"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering]
+packs: [meta]
 ---
 
 # Roadmap Progress Sync
@@ -54,6 +52,8 @@ The `command:` triggers in this rule's frontmatter ensure it loads the moment on
 
 **Dashboard regen cadence — opt-in batching.** The checkbox flip is non-batchable. The **subprocess regen** (`./agent-config roadmap:progress`) is batchable per `roadmap.dashboard_regen_cadence` in `.agent-settings.yml` (`per_step` default · `every_5_steps` · `phase_boundary`). Run end, phase boundary, and any file-shape touch (rename / phase add / archive — Iron Law 1) always force an immediate regen regardless of cadence.
 
+**Blockers follow same cadence as checkboxes.** Clearing a `## Blockers` entry (per [`templates/roadmaps.md` rule 20](../templates/roadmaps.md)) flips its `Status: resolved`, regenerates dashboard in same reply — Iron Law 1's "same response" obligation applies to blocker resolution exactly as it applies to a checkbox flip.
+
 ## Iron Law 3 — no silent archive with unresolved deferred items
 
 ```
@@ -138,4 +138,4 @@ Before sending any reply that landed roadmap work:
 Any "no" at step 2 → reply is incomplete. Do not send. A skipped step 3 regen is fine when cadence permits — checkbox truth lives in the markdown file. Skipping the deferred-resolution gate at step 4 is **never** acceptable; it is the canonical "lost-information" failure mode this rule exists to prevent.
 
 Long-form mechanics (failure-mode catalog, Copilot fallback, `[~]` vs `[ ]` semantics, hook + CI defence-in-depth) live in `guideline:agent-infra/roadmap-progress-mechanics`.
-Trigger-set above activates this routing under the `balanced` and `full` profiles.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/role-mode-adherence.md

@@ -7,10 +7,8 @@ triggers:
   - keyword: "active_role"
   - keyword: "role-mode"
   - intent: "mode marker"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
+packs: [meta]
 ---
 
 # Role Mode Adherence

package/dist/agent-src/rules/rule-type-governance.md

@@ -6,10 +6,8 @@ triggers:
   - path_prefix: ".agent-src.uncondensed/rules/"
 routes_to:
   - "guideline:agent-infra/rule-type-governance"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer]
+packs: [meta]
 ---
 
 # Rule Type Governance
@@ -17,4 +15,4 @@ packs:
 **Iron Law.** Choose `always` vs `auto` per the governance table; over-broad `always` rules degrade the kernel budget.
 
 Body migrated to `guideline:agent-infra/rule-type-governance` (per P4 of `road-to-kernel-and-router.md`).
-Trigger-set above activates this routing under the `balanced` and `full` profiles.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/runtime-safety.md

@@ -7,10 +7,8 @@ triggers:
   - keyword: "automated"
   - keyword: "assisted"
   - keyword: "handler"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering]
+packs: [meta]
 ---
 
 # Runtime Safety

package/dist/agent-src/rules/scope-control.md

@@ -6,10 +6,8 @@ alwaysApply: true
 load_context:
   - ../contexts/authority/scope-mechanics.md
   - ../contexts/authority/kernel-rule-edits.md
-workspaces:
-  - engineering
-packs:
-  - engineering-base
+workspaces: [engineering]
+packs: [engineering-base]
 ---
 
 # Scope Control
@@ -33,30 +31,31 @@ The user decides the git shape. Never improvise. Commit specifics: canonical [`c
 - NEVER push a tag or create a release without permission.
 - NEVER pin versions, release targets, deprecation dates, or git tags in roadmaps / plans / tickets — they plan **work**, not releases. Detail: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
 - Task seems to need a separate branch / PR → STOP and **brief before asking** ([`scope-mechanics`](../contexts/authority/scope-mechanics.md)).
-- BEFORE the first commit on related work, **inventory** existing branches and open PRs. Plausible base beyond the current branch → STOP and ask with numbered options — never improvise. Commands + 4-option template + diverging-stack failure mode: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
+- BEFORE the first commit on related work, **inventory** existing branches + open PRs; plausible other base → STOP, ask with numbered options. Commands + 4-option template: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
 
-"Explicit permission" = said **this turn or in a standing instruction not yet revoked**. Permission for a different operation does not carry over.
+"Explicit permission" = said **this turn or in an unrevoked standing instruction**. Permission for one operation never carries to another.
 
 ## Authoring vs. implementation
 
 ```
 "CREATE / DRAFT" AUTHORIZES THE ARTIFACT, NOT ITS EXECUTION.
 NEW TASK NEVER INHERITS PRIOR AUTONOMY.
+ARTIFACT SAVED → HARD STOP. NEVER AUTO-OFFER EXECUTION.
 ```
 
-`create / draft / write / erstelle …` → artifact only. Execution verbs flip scope; mixed → ask. Detail: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
+`create / draft / write / erstelle …` → artifact only. Execution verbs flip scope; mixed → ask. The moment the artifact lands (roadmap, ADR, plan, pitch, ticket), the turn ends — never auto-offer execution; execution needs an explicit execution verb (`implement`, `build`, `start`, `arbeite ab`) on a later turn. Detail + anti-patterns: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
 
 ## Production, infrastructure, bulk-destructive — Hard Floor
 
-A subset is **never** autonomous, regardless of standing autonomy. Canonical: [`non-destructive-by-default`](non-destructive-by-default.md). Triggers (prod-branch merges, deploys, prod data / infra, bulk-destructive) + this-turn-only clarification: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
+A subset is **never** autonomous. Canonical: [`non-destructive-by-default`](non-destructive-by-default.md); triggers + this-turn-only clarification: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
 
 ## Kernel-rule edits — slow-rollout guarantee
 
-Own PR, ≥ 24 h between merges. Autonomous mandate does not lift — soak guarantee. CI / labels / scope: [`kernel-rule-edits`](../contexts/authority/kernel-rule-edits.md).
+Own PR, ≥ 24 h between merges; autonomous mandate does not lift (soak guarantee). CI/labels/scope: [`kernel-rule-edits`](../contexts/authority/kernel-rule-edits.md).
 
 ## Decline = silence — no re-asking on the same task
 
-After the user **declines** a proposal (branch switch, PR creation, tag/release, separate worktree, version pinning), do **not** raise it again on the same task. Decline stands until reopened. Timing: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
+After the user **declines** a proposal (branch switch, PR, tag/release, worktree, version pinning), do **not** raise it again on the same task — decline stands until reopened. Timing: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
 
 ## Fenced step — user-set review gates
 
@@ -65,4 +64,4 @@ USER FENCED OFF EXECUTION → DELIVER + HAND BACK.
 NO "READY TO IMPLEMENT?" / "PHASE 1?" RE-ASK.
 ```
 
-Fence (*"plan only"*, *"review first"*, German equivalents) stands until reopened — like `Decline = silence`. Follow-ups cover the deliverable, not its execution. Failure modes + bypass: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).
+Fence (*"plan only"*, *"review first"*, DE equivalents) stands until reopened. Follow-ups cover the deliverable, not its execution. Failure modes + bypass: [`scope-mechanics`](../contexts/authority/scope-mechanics.md).

package/dist/agent-src/rules/security-sensitive-stop.md

@@ -2,21 +2,20 @@
 type: "auto"
 tier: "2a"
 alwaysApply: false
-description: "Security-sensitive paths — auth, billing, tenants, secrets, uploads, webhooks, public endpoints — threat-model BEFORE editing"
+description: "Security-sensitive paths (auth, billing, tenants, secrets, uploads, webhooks) — threat-model BEFORE editing"
 triggers:
   - keyword: "auth"
   - keyword: "billing"
   - keyword: "tenant"
   - keyword: "secret"
   - keyword: "webhook"
+  - keyword: "password"
 validator_ignore:
   - type: "substring"
     pattern: "../../docs/"
     reason: "See-also routes to docs/threat-model.md — the canonical attack-surface doc lives there by design."
-workspaces:
-  - engineering
-packs:
-  - engineering-base
+workspaces: [engineering]
+packs: [engineering-base]
 ---
 
 # Security-Sensitive Stop Rule

package/dist/agent-src/rules/size-enforcement.md

@@ -8,10 +8,8 @@ triggers:
   - intent: "create skill"
   - intent: "create command"
   - intent: "create guideline"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer]
+packs: [meta]
 ---
 
 # size-enforcement

package/dist/agent-src/rules/skill-improvement-trigger.md

@@ -8,10 +8,8 @@ triggers:
   - keyword: "pipeline"
 routes_to:
   - "skill:skill-improvement-pipeline"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
+workspaces: [agent-config-maintainer, engineering]
+packs: [meta]
 ---
 
 # Skill Improvement Trigger
@@ -19,4 +17,4 @@ packs:
 **Iron Law.** After a meaningful task, trigger the post-task learning capture if `pipelines.skill_improvement` is enabled.
 
 Body migrated to `skill:skill-improvement-pipeline` (per P4 of `road-to-kernel-and-router.md`).
-Trigger-set above activates this routing under the `balanced` and `full` profiles.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).