@event4u/agent-config 9.25.0 → 9.27.0

package/dist/agent-src/commands/roadmap.md

@@ -2,14 +2,14 @@
 model_tier: medium
 name: roadmap
 disable-model-invocation: true
-argument-hint: "[create|ai-council|process-step|process-phase|process-full] [args]"
+argument-hint: "[create|ai-council|process-step|process-phase|process-full|next] [args]"
 pack: product-basic
-intent: "Roadmap dispatcher — create, process-step, process-phase, process-full, ai-council"
-routes_to: [roadmap-create, roadmap-ai-council, roadmap-materialize, roadmap-process-step, roadmap-process-phase, roadmap-process-full]
+intent: "Roadmap dispatcher — create, process-step, process-phase, process-full, next, ai-council"
+routes_to: [roadmap-create, roadmap-ai-council, roadmap-materialize, roadmap-process-step, roadmap-process-phase, roadmap-process-full, roadmap-next]
 replaces: []
 tier: 1
 visibility: advanced
-description: Roadmap orchestrator — routes to create (authoring) and process-step / process-phase / process-full (autonomous execution).
+description: Roadmap orchestrator — routes to create (authoring), process-step / process-phase / process-full (autonomous execution), and next (pick a roadmap and ship it).
 cluster: roadmap
 type: orchestrator
 suggestion:
@@ -40,6 +40,7 @@ paused for confirmation before every step) was removed —
 | `/roadmap:process-step` | `commands/roadmap/process-step.md` | Autonomously process the next open step, then stop |
 | `/roadmap:process-phase` (**default execution scope**) | `commands/roadmap/process-phase.md` | Autonomously process every open step in the current phase |
 | `/roadmap:process-full` | `commands/roadmap/process-full.md` | Autonomously process every open step across every phase |
+| `/roadmap:next` | `commands/roadmap/next.md` | Screen for the next executable roadmap, then carry it to a reviewable PR (selection + `process-full` + delivery) |
 
 Sub-command names match the locked contract in
 [`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
@@ -70,6 +71,7 @@ each only binds a scope delta.
    > 3. process-step — process the next open step, then stop
    > 4. process-phase — process the current phase (default)
    > 5. process-full — process every open step across every phase
+   > 6. next — pick the next executable roadmap and ship it to a PR
 
 ## Rules
 
@@ -84,3 +86,9 @@ each only binds a scope delta.
   *"finish this phase"*) default to
   [`/roadmap:process-phase`](roadmap/process-phase.md) unless the user
   named a different scope.
+- **Selection intents** (*"take the next sensible roadmap"*, *"nimm dir
+  die nächste Roadmap vor"*, *"pick a roadmap and ship it"*) — i.e. the
+  user has NOT named a roadmap and wants one chosen — route to
+  [`/roadmap:next`](roadmap/next.md), which is the only sub that
+  screens and selects. The three `process-*` subs never choose across
+  roadmaps.

package/dist/agent-src/contexts/execution/subagent-routing.md

@@ -48,7 +48,10 @@ THE SAME MINUS THE QUOTA WIN.
    tier <t>`); a 429/quota error trips `tripCooldown` for that tier and
    falls back per the relation — never a retry loop. Under
    `budget_routing: ask`, the FIRST budget-motivated downshift of a session
-   is confirmed once; `auto` proceeds silently. Every budget-routed
+   is confirmed once, in the shape
+   [`settings-ask-protocol`](../../rules/settings-ask-protocol.md) fixes and
+   without persisting the answer (`subagents.budget_routing` is class C);
+   `auto` proceeds silently. Every budget-routed
    dispatch emits one `orchestration_record` line (tier + provenance-tagged
    token delta) so realized savings are measured, not asserted.
 

package/dist/agent-src/rules/active-remediation.md

@@ -18,6 +18,8 @@ workspaces: [engineering]
 packs: [engineering-base]
 collision_ok:
   "refactor": "an explicit clean-up/refactor ask is the remediation ladder's own trigger"
+# obligation: line 51
+obligation_frequency: "per-edit"
 ---
 
 # Active Remediation

package/dist/agent-src/rules/analysis-skill-routing.md

@@ -10,6 +10,8 @@ routes_to:
   - "skill:analysis-skill-router"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
+# obligation: line 19
+obligation_frequency: "none"
 ---
 
 # Analysis Skill Routing

package/dist/agent-src/rules/architecture.md

@@ -13,6 +13,8 @@ workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
 collision_ok:
   "controller": "thin-handler floor on controller work"
+# obligation: line 26
+obligation_frequency: "per-edit"
 ---
 
 # Architecture Rules

package/dist/agent-src/rules/artifact-drafting-protocol.md

@@ -14,6 +14,8 @@ routes_to:
   - "guideline:agent-infra/artifact-drafting-protocol-mechanics"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
+# obligation: line 41
+obligation_frequency: "per-task"
 ---
 
 # Artifact Drafting Protocol

package/dist/agent-src/rules/artifact-engagement-recording.md

@@ -13,6 +13,8 @@ load_context:
   - "../contexts/contracts/artifact-engagement-flow.md"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
+# obligation: line 22
+obligation_frequency: "per-task"
 ---
 
 <!-- cloud_safe: noop -->

package/dist/agent-src/rules/augment-edit-discipline.md

@@ -19,6 +19,8 @@ workspaces: [agent-config-maintainer]
 packs: [meta]
 collision_ok:
   ".augment/": "portability + sync floors for the .augment tree"
+# obligation: line 28
+obligation_frequency: "per-edit"
 ---
 
 # Augment Edit Discipline

package/dist/agent-src/rules/autonomous-execution.md

@@ -13,6 +13,8 @@ triggers:
 self_contained: true
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
+# obligation: line 4
+obligation_frequency: "per-turn"
 ---
 
 # Autonomous Execution

package/dist/agent-src/rules/brand-consistency.md

@@ -10,6 +10,8 @@ applies_to_user_types:
 self_contained: true
 workspaces: [engineering]
 packs: [brand]
+# obligation: line 20
+obligation_frequency: "none"
 ---
 
 # Brand Consistency

package/dist/agent-src/rules/brand-source-of-truth.md

@@ -20,6 +20,8 @@ applies_to_user_types:
 self_contained: true
 workspaces: [engineering]
 packs: [brand]
+# obligation: line 51
+obligation_frequency: "per-edit"
 ---
 
 # Brand Source of Truth

package/dist/agent-src/rules/broken-access-control.md

@@ -23,6 +23,8 @@ collision_ok:
   "controller": "controllers return user data — the ownership/tenant check floor"
   "endpoint": "every data-returning endpoint needs the three negative tests"
   "tenant": "cross-tenant isolation is this rule's core subject"
+# obligation: line 55
+obligation_frequency: "per-edit"
 ---
 
 # Broken Access Control

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

@@ -35,6 +35,8 @@ collision_ok:
   "composer": "composer output is verbose — rtk wrap applies"
   "docker": "docker output is verbose — rtk wrap applies"
   "rector": "rector output is verbose — rtk wrap applies"
+# obligation: line 42
+obligation_frequency: "per-edit"
 ---
 
 # Cli Output Handling

package/dist/agent-src/rules/code-comment-discipline.md

@@ -20,6 +20,8 @@ packs: [engineering-base]
 collision_ok:
   "refactor": "refactors churn comments — the keep/drop discipline applies"
   "implement": "fresh implementation is where over-commenting lands"
+# obligation: line 5
+obligation_frequency: "per-edit"
 ---
 
 # Code Comment Discipline

package/dist/agent-src/rules/code-provenance.md

@@ -21,6 +21,8 @@ packs: [engineering-base]
 roles: [developer, reviewer, tester, po, incident, planner]
 enforced_by:
   - "none"
+# obligation: line 38
+obligation_frequency: "per-edit"
 ---
 
 # Code Provenance

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

@@ -11,6 +11,8 @@ load_context:
   - "../contexts/contracts/command-suggestion-flow.md"
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
+# obligation: line 18
+obligation_frequency: "per-turn"
 ---
 
 # Command Suggestion Policy

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

@@ -12,6 +12,8 @@ workspaces: [engineering]
 packs: [engineering-base]
 collision_ok:
   "commit": "format floor for every commit message"
+# obligation: line 19
+obligation_frequency: "per-commit"
 ---
 
 # Commit Conventions

package/dist/agent-src/rules/communication-through-line.md

@@ -8,6 +8,8 @@ workspaces: [agent-config-maintainer, construction, engineering, finance, founde
 packs: [meta]
 triggers:
   - phrase: "reporting progress"
+# obligation: line 20
+obligation_frequency: "per-turn"
 ---
 
 # Communication Through-Line

package/dist/agent-src/rules/content-quoting-floor.md

@@ -9,6 +9,8 @@ triggers:
 self_contained: true
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
+# obligation: line 19
+obligation_frequency: "per-event"
 ---
 
 # Content Quoting Floor

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

@@ -12,6 +12,8 @@ workspaces: [agent-config-maintainer, construction, engineering, finance, founde
 packs: [meta]
 enforced_by:
   - "hook:context-hygiene"
+# obligation: line 67
+obligation_frequency: "per-turn"
 ---
 
 # Context Hygiene
@@ -21,6 +23,14 @@ enforced_by:
 > `agents/state/context-hygiene.json` (tool-call count, loop signal,
 > freshness milestones at 20/40/60); the prose below is the spec the
 > hook implements and the agent-side fallback.
+>
+> **What the slot cannot reach.** The carrier fires per *tool call*; the
+> read-loop law below is per *turn*. A turn that makes no tool call fires it
+> zero times — and a reply with no tool call is exactly the shape the read-loop
+> counter is trying to notice. So the counters are hook-carried and the
+> every-turn obligation is model-carried, on every host. Named here because the
+> frequency join in `check_enforcement_coverage.ts` reports it, and a rule whose
+> header says "enforced by" without that sentence reads as a guarantee it is not.
 
 ## Conversation Freshness
 

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

@@ -10,6 +10,8 @@ routes_to:
   - "skill:copilot-config"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
+# obligation: line 19
+obligation_frequency: "none"
 ---
 
 # Copilot Routing

package/dist/agent-src/rules/cross-source-consistency.md

@@ -26,6 +26,8 @@ packs: [engineering-base, product-basic]
 collision_ok:
   "mockup": "a mockup is a second source — discrepancy check against the ticket text"
   "screenshot": "a screenshot is a second source — discrepancy check"
+# obligation: line 71
+obligation_frequency: "per-task"
 ---
 
 # Cross-Source Consistency

package/dist/agent-src/rules/decision-revisit-gate.md

@@ -16,6 +16,8 @@ workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
 collision_ok:
   "honest null": "this rule asks whether a recorded null may be REVISITED; evaluator-independence asks how one was PRODUCED — different decision points on the same artefact"
+# obligation: line 31
+obligation_frequency: "per-task"
 ---
 
 # Decision Revisit Gate

package/dist/agent-src/rules/delegation-policy.md

@@ -20,6 +20,8 @@ routes_to:
   - "skill:subagent-orchestration"
 workspaces: [engineering]
 packs: [engineering-base]
+# obligation: line 35
+obligation_frequency: "per-task"
 ---
 
 # Delegation Policy
@@ -50,8 +52,9 @@ clears — all of:
   [`auto-dispatch-classification`](../contexts/execution/auto-dispatch-classification.md)
   (≥1 independent, well-specified slice above the size floor).
 
-`subagents.auto: ask` → ask once before dispatching (per
-[`user-interaction`](user-interaction.md)); `auto: on` → surface the chosen mode
+`subagents.auto: ask` → ask once before dispatching, in the shape
+[`settings-ask-protocol`](settings-ask-protocol.md) fixes (the answer is not
+persisted — `subagents.auto` is class C); `auto: on` → surface the chosen mode
 + per-subtask tiers in one line. Any gate failing, or `auto: off`, or no host
 primitive → run in-session (clean no-op).
 

package/dist/agent-src/rules/design-fidelity.md

@@ -23,7 +23,9 @@ triggers:
   - phrase: "bau das nach"
   - phrase: "1:1 um"
   - phrase: "1:1 nach"
+  - phrase: "claude.site/artifacts"
   - file_pattern: "*design.html"
+  - path_prefix: ".claude/design-system/"
 applies_to_user_types:
   - "creator"
   - "developer"
@@ -34,6 +36,8 @@ workspaces: [engineering]
 packs: [engineering-base, frontend-design]
 collision_ok:
   "mockup": "a provided mockup is the spec — 1:1 fidelity floor"
+# obligation: line 58
+obligation_frequency: "per-edit"
 ---
 
 # Design Fidelity
@@ -96,13 +100,27 @@ artifact is simply attached. The last is covered by `file_pattern: *design.html`
 HTML edit in every project and be strictly worse than the gap it closes. A
 handover under some other filename needs one word in the prompt.
 
+Two further handover shapes carry the artifact without any of the above:
+
+- **A capability URL.** A published artifact is handed over as a link, not a
+  file — so `phrase: "claude.site/artifacts"` fires on the *published-artifact
+  path*, not on the host. `claude.ai` alone is a chat link and must stay quiet:
+  a keyword on the bare domain would fire on "I pasted this from claude.ai",
+  which is a conversation reference, not a spec.
+- **A design-system directory.** `path_prefix: ".claude/design-system/"` — the
+  conventional location for a handed-over token/component set. The prefix is the
+  vendor-scoped directory, never a bare `design-system/`, which is a normal
+  source folder in a large fraction of frontend repos.
+
 The trigger set is deliberately phrase-heavy on the German side and on
 `artifact`: a bare `artifact` keyword fires on "the CI build artifact is 40 MB".
 `ROUTING_MATRIX` in
 [`design_fidelity_routing.test.ts`](../../tests/scripts/design_fidelity_routing.test.ts)
 pins both halves — every class that must route, and the near-misses that must
 stay silent (fixture `daf-port-trigger-de`). Extending the set without adding a
-near-miss row there is how an over-broad trigger lands.
+near-miss row there is how an over-broad trigger lands: each of the two triggers
+above ships with its own near-miss row (`near-claude-ai-chat-link`,
+`near-generic-design-system-dir`).
 
 Body migrated to [`guideline:design-fidelity-mechanics`](../docs/guidelines/design-fidelity-mechanics.md) (per P4 of `road-to-kernel-and-router.md`) — surgical visual edits (targeted-edit vs redesign-trigger discipline, stable anchors), asset & imagery discipline (owned-asset path, third-party delivery is self-hosted by default, real-imagery-as-proof, iconography floor, no unrequested filler), deviation-surfacing shape, failure-mode catalog, `daf-*` fixtures.
 Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/design-review-after-ui-write.md

@@ -0,0 +1,120 @@
+---
+type: "auto"
+tier: "2b"
+alwaysApply: false
+description: "UI written or changed — review it against the design contract before calling it done; the write-side twin of ui-audit-gate"
+triggers:
+  - path_prefix: "resources/views/"
+  - path_prefix: "resources/js/"
+  - keyword: "component"
+  - keyword: "design token"
+routes_to:
+  - "skill:design-review"
+  - "skill:accessibility-auditor"
+workspaces: [agent-config-maintainer, engineering]
+packs: [frontend-design]
+enforced_by:
+  - "none"
+collision_ok:
+  "component": "a written component is reviewed before it is called done — the write-side half"
+  "design token": "same surface, opposite side: ui-audit-gate inventories tokens before the write, this reviews what the write emitted"
+  "resources/views/": "both halves of one UI loop fire on the same path — audit before, review after; neither substitutes for the other"
+  "resources/js/": "both halves of one UI loop fire on the same path — audit before, review after; neither substitutes for the other"
+# obligation: line 39
+obligation_frequency: "per-edit"
+---
+
+# Design Review After UI Write
+
+The UI loop was closed on one side only. [`ui-audit-gate`](ui-audit-gate.md)
+covers the **read** side — inventory what exists before adding a component — and
+routes to `existing-ui-audit`. Nothing covered the **write** side: **zero rules
+routed to `skill:design-review`**, so a component could be written, declared
+done, and never looked at against the contract it was supposed to satisfy.
+
+This is that rule's twin, deliberately built to the same shape: same tier, same
+pack, same diff-decidable allow-list, and the same honest scope.
+
+## The Iron Law
+
+```
+UI WRITTEN OR CHANGED IS NOT DONE UNTIL IT IS REVIEWED.
+NEVER CLAIM A UI CHANGE IS COMPLETE ON "IT LOOKS RIGHT" — THAT IS A VERDICT
+WITHOUT EVIDENCE. NO RENDER CAPABILITY → SCOPE THE VERDICT TO WHAT WAS
+STATICALLY CHECKED AND SAY SO. NEVER "LOOKS GOOD" WITH NOTHING BEHIND IT.
+```
+
+## What "reviewed" means
+
+The verdict is gated on evidence, not on having run a skill:
+
+- **Render capability present** (Playwright MCP, Chrome DevTools, or a live
+  preview URL) → the [design-artifact verification checklist](../docs/contracts/design-artifact-verification.md#verification-checklist)
+  steps 1–5. A UI task does not pass without render evidence.
+- **Render capability absent** → the verdict is **scoped to the static checks
+  that actually ran** and says which those were. This is not a downgrade to be
+  hidden; `design-review` itself states it ("scope the verdict to what was
+  statically checked and say so"). An unscoped "looks good" is the failure.
+- **A provided artifact is the spec** → findings the artifact *covers* are
+  informational, not defects, per [`design-fidelity`](design-fidelity.md). The
+  review does not "improve" the user's own design.
+
+## Allow-list — `ui-trivial`, decidable from the diff alone
+
+Skip only when **all** hold:
+
+- ≤ 1 file, ≤ 5 changed lines, no new component, no new state, no new dependency.
+- Inside the work engine, `directive_set == "ui-trivial"` — the dispatcher states
+  it directly. Outside it, the same conditions are read **off the diff**, which
+  is observable without any dispatcher state.
+
+The list is deliberately the engine's five conditions, not the four its
+sibling rule's prose carries: `ui_trivial/apply.ts` enforces `new_dependency`
+too, and a twin that copied the shorter prose would inherit a gap the engine
+does not have.
+
+## Honest scope — what this rule does NOT enforce
+
+```
+THE REVIEW OBLIGATION IS MODEL-CARRIED. NEVER CLAIM THE REVIEW RAN
+AS IF IT WERE VERIFIED.
+```
+
+There is no artefact a chat session can point at to prove a design review
+happened — "I ran `design-review`" is self-report, and self-report is not
+enforcement. So this rule ships `enforced_by: none`, the same honesty boundary
+`ui-audit-gate`, `security-sensitive-stop`, and `untrusted-input-defense` state
+for their own obligations, rather than pretending a satisfiable-by-assertion
+condition is a gate.
+
+What that leaves, and it is the useful part: the write side now has a named
+obligation and a route to the skill that discharges it, where before it had
+neither. Full enforcement needs the work-engine `review`/`polish` gates (which
+already act on `a11y_violation` and `token_violation` findings) or pack-scoped
+rule projection — a maintainer decision, never an automated one.
+
+One asymmetry worth stating: `design-review` lives in `engineering-base` while
+this rule is scoped to `frontend-design`. The route still resolves — a rule may
+name a skill from another pack — but a consumer with `frontend-design` and
+without `engineering-base` gets the obligation without the skill. That is why
+`accessibility-auditor` is a second route: it is the part of the review that
+must not depend on the pairing.
+
+## Failure modes
+
+- Writing the component and calling it done because the tests pass — tests do not
+  look at it.
+- "Looks good" as a verdict with no render, no static check named, and no scope.
+- Running the review and acting on findings the provided artifact covers, i.e.
+  redesigning the user's spec under the banner of quality.
+- Treating the a11y half as optional because the visual half looked fine.
+- Skipping the review for "just one tile" — the same bypass `ui-audit-gate`
+  names on its own side.
+
+## See also
+
+- [`ui-audit-gate`](ui-audit-gate.md) — the read-side twin; audit before writing.
+- [`design-review`](../skills/design-review/SKILL.md) — the 7-phase review this routes to.
+- [`accessibility-auditor`](../skills/accessibility-auditor/SKILL.md) — the WCAG half.
+- [`design-fidelity`](design-fidelity.md) — a provided artifact is the spec; covered findings are informational.
+- [`verify-before-complete`](verify-before-complete.md) — the general no-claim-without-evidence gate this applies to UI.

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

@@ -11,6 +11,8 @@ routes_to:
   - "skill:devcontainer"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
+# obligation: line 20
+obligation_frequency: "none"
 ---
 
 # Devcontainer Routing

package/dist/agent-src/rules/doc-screenshot-hygiene.md

@@ -27,6 +27,8 @@ workspaces: [agent-config-maintainer, construction, engineering, finance, founde
 packs: [meta]
 collision_ok:
   "screenshot": "a screenshot shipping into docs is the PII/anonymization gate"
+# obligation: line 49
+obligation_frequency: "per-event"
 ---
 
 # Doc-Screenshot Hygiene

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

@@ -15,6 +15,8 @@ collision_ok:
   "artisan": "artisan runs inside the project container, never on the host"
   "composer": "composer runs inside the project container"
   "docker": "its own core subject"
+# obligation: line 22
+obligation_frequency: "per-edit"
 ---
 
 # Docker Commands

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

@@ -18,6 +18,8 @@ workspaces: [agent-config-maintainer]
 packs: [meta]
 collision_ok:
   "src/skills/": "a skill in a fresh vertical is exactly the domain-gate surface"
+# obligation: line 38
+obligation_frequency: "per-task"
 ---
 
 # Domain Adoption Policy

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

@@ -42,6 +42,8 @@ workspaces: [agent-config-maintainer, construction, engineering, finance, founde
 packs: [meta]
 collision_ok:
   "review this contract": "contract review is advisory-shaped — the not-legal-advice footer floor"
+# obligation: line 52
+obligation_frequency: "per-task"
 ---
 
 # Domain Safety — Advisory Disclaimer

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

@@ -42,6 +42,8 @@ applies_to_user_types:
   - "all"
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
+# obligation: line 52
+obligation_frequency: "per-task"
 ---
 
 # Domain Safety — PII Redaction

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

@@ -27,6 +27,8 @@ applies_to_user_types:
   - "gtm"
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
+# obligation: line 47
+obligation_frequency: "per-turn"
 ---
 
 # Domain Safety — Data Retention

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

@@ -11,6 +11,8 @@ triggers:
 self_contained: true
 workspaces: [engineering]
 packs: [engineering-base]
+# obligation: line 30
+obligation_frequency: "per-edit"
 ---
 
 # Downstream Changes

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

@@ -28,6 +28,8 @@ workspaces: [engineering]
 packs: [engineering-base]
 collision_ok:
   "migration": "a prod migration is a hard-floor evidence surface (rollback path, blast radius)"
+# obligation: line 49
+obligation_frequency: "per-commit"
 ---
 
 # Engineering Safety Floor

package/dist/agent-src/rules/evaluator-independence.md

@@ -20,6 +20,12 @@ enforced_by:
   - "hook:evidence-independence"
 collision_ok:
   "honest null": "this rule asks how a recorded null was PRODUCED; decision-revisit-gate asks whether it may be REVISITED — different decision points on the same artefact"
+# obligation: dispatching an evaluator is a tool call, and the guard is a pre_tool_use
+# concern that reads that prompt — src/rules/evaluator-independence.md:81
+obligation_frequency: "per-edit"
+# frequency-override: line 70 states a per-turn clause ("one evaluation per turn"),
+# but the guard counts it AT the dispatch, which is a tool call — a per-edit point
+# carrier sees every dispatch, so it carries the per-turn cap too.
 ---
 
 # Evaluator Independence
@@ -81,9 +87,19 @@ was manufactured anyway.
 
 [`evidence_independence.ts`](../scripts/hooks/evidence_independence.ts) is a
 `pre_tool_use` concern. It **blocks** a dispatch whose prompt carries a
-pre-loaded verdict, and **blocks** a second evaluation-shaped dispatch in the
-same turn; it **warns** on the first. It reads the prompt the agent is about to
-send, so items 1 and 4 above are mechanically enforced.
+pre-loaded verdict, and **blocks** a second *self-scoped* evaluation dispatch in
+the same turn; it **warns** on the first. It reads the prompt the agent is about
+to send, so items 1 and 4 above are mechanically enforced.
+
+Three limits, stated because they were measured. The pre-loaded-verdict list is
+a **phrase list**, so a paraphrase evades it — it catches recurrences of known
+steering wording, not steering as such. The turn boundary is the
+authorization ledger's `detected_at` stamp, because the envelope carries no turn
+id; with no ledger yet, the counter falls back to session scope. And the slot
+itself is not universal: `pre_tool_use` exists on **three** hosts — augment,
+claude, cowork. On cursor, cline, windsurf, gemini and copilot this guard has
+nowhere to bind, so items 1 and 4 join 2 and 3 as model-carried there. The
+frequency join in `check_enforcement_coverage.ts` reports exactly that set.
 
 Items 2 and 3 — an honestly chosen scope, and recording the prompt with the
 verdict — are **not** enforced by anything. A narrowed scope is not decidable

package/dist/agent-src/rules/external-code-graph-interop.md

@@ -17,6 +17,8 @@ applies_to_user_types:
 self_contained: true
 workspaces: [engineering]
 packs: [meta]
+# obligation: line 37
+obligation_frequency: "per-turn"
 ---
 
 # External Code-Graph Interop

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

@@ -10,6 +10,8 @@ triggers:
 self_contained: true
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
+# obligation: line 20
+obligation_frequency: "per-task"
 ---
 
 # external-reference-deep-dive

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

@@ -14,6 +14,8 @@ validator_ignore:
 self_contained: true
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
+# obligation: line 30
+obligation_frequency: "per-turn"
 ---
 
 # Fast-Path Marker Visibility

package/dist/agent-src/rules/finance-safety-floor.md

@@ -33,6 +33,8 @@ packs: [finance-basic, finance-advanced]
 trust:
   level: advisory
   human_review_required: true
+# obligation: line 53
+obligation_frequency: "per-task"
 ---
 <!-- agent-config:human-review-banner -->
 > HUMAN REVIEW REQUIRED · trust: advisory · owner: unknown