@event4u/agent-config 9.8.0 → 9.10.0

package/docs/contracts/rule-classification.md

@@ -1,171 +0,0 @@
----
-stability: beta
-keep-beta-until: 2026-08-12
----
-
-
-# Rule Classification — Phase 1.2 of road-to-kernel-and-router
-
-> **Status:** active · **Stability:** beta · **Owner:** road-to-kernel-and-router P1.2
-> · **Source of truth:** `.agent-src.uncondensed/rules/*.md`
-
-Migration plan for all 56 source rules. **No edits land here** — this
-document is the disposition map P2 / P4 will execute against.
-
-## § 1 — Disposition codes
-
-| code | meaning |
-|---|---|
-| `keep-in-kernel` | Iron Law floor / behaviour / safety / tone / ask-policy. Loaded every session. Condensed to ≤ 2.5k chars (P2.2; raised from 1.5k per Council R2). |
-| `condense-and-keep` | Behavioural rule that stays in `rules/` as auto-tier. Condensed in place per the P2.2 playbook. Loaded by router on trigger match. |
-| `move-to-skill:<id>` | Procedural how-to content. Body migrates into the named skill (P4.1); rule shrinks to Iron Law one-liner + `routes_to:`. |
-| `move-to-guideline:<id>` | Reference / examples / mechanics tables. Body migrates into `docs/guidelines/<id>.md` (P4.2); rule keeps Iron Law + pointer. |
-
-## § 2 — Baseline numbers (measured 2026-05-06)
-
-| bucket | rules | chars | target after roadmap |
-|---|---:|---:|---|
-| always (kernel proxy) | 9 | 32 403 | ≤ 25 000 hard, ≤ 20 000 target |
-| auto | 47 | 142 297 | ≤ 60 000 |
-| **total** | **56** | **174 700** | **≤ 85 000** |
-
-Source: `./scripts-run src/scripts/measure_rule_budget`.
-
-## § 3 — Disposition table
-
-Sorted by current `type` then `id`. `chars` = body chars after
-frontmatter strip. Disposition is the migration call, **not** an edit
-yet.
-
-### § 3.1 — always-rules (kernel candidates)
-
-| id | chars | disposition | rationale |
-|---|---:|---|---|
-| agent-authority | 1217 | `keep-in-kernel` | Priority index for the four authority rules; routes-of-routers |
-| ask-when-uncertain | 4096 | `keep-in-kernel` | Iron Law: one-question-per-turn, mirror the user, vague-trigger list |
-| commit-policy | 2972 | `keep-in-kernel` | Iron Law (safety-floor): NEVER commit / NEVER ask about committing |
-| direct-answers | 3991 | `keep-in-kernel` | Three Iron Laws (no flattery, no invented facts, brevity) |
-| language-and-tone | 5318 | `keep-in-kernel` | Iron Law: mirror the user's language; .md always English |
-| no-cheap-questions | 3875 | `keep-in-kernel` | Iron Law: no-cheap-questions self-check; mode-independent |
-| non-destructive-by-default | 4222 | `keep-in-kernel` | Iron Law (safety-floor): Hard Floor for prod / push / bulk-destructive |
-| scope-control | 4368 | `keep-in-kernel` | Iron Law (safety-floor): no unsolicited refactors / git-ops gate |
-| verify-before-complete | 2344 | `keep-in-kernel` | Iron Law: no completion claims without fresh verification |
-
-**Always-bucket total: 32 403 chars.** Pilot condensation rate `r`
-locked at **median 0.712** (P1.3, Council R2 amendment); projection
-sum = 23 071 chars, under the 25k hard cap with 1 929 chars headroom.
-Per-rule cap raised to ≤ 2.5k (Council R2). Iron-Law-override ADRs
-may lift individual rules above 2.5k where Iron-Law density forbids
-further condensation — currently 2 expected (`direct-answers` +342,
-`language-and-tone` +1286). See `kernel-membership.md` § 5.
-
-> **Council swap ADR (P2.1 input).** Sonnet 4.5 flagged
-> `agent-authority` as a routing index (no Iron-Law fence; should
-> demote to auto-tier-3) and `autonomous-execution` (currently
-> `condense-and-keep` below) as a mode-independent Band-4 authority
-> that should promote to kernel. Swap accepted ⇒ +1213 chars over
-> the 25k cap. Decision deferred to P2.1 ADR; current dispositions
-> below remain locked until the ADR resolves.
-
-### § 3.2 — auto-rules: condense-and-keep (22)
-
-Behavioural rules with too much Iron-Law content for migration; condense
-in place per P2.2 playbook. Loaded by router on trigger match.
-
-| id | chars | tier | rationale |
-|---|---:|---|---|
-| architecture | 2491 | 3 | Behavioural; project-organization gates |
-| artifact-drafting-protocol | 2957 | 2a | Iron-Law-shaped Understand→Research→Draft sequence |
-| source-of-truth | 2439 | 1 | Behavioural Iron Law: never edit generated dirs |
-| autonomous-execution | 5631 | 3 | Trivial-vs-blocking decision; tier-1 on `balanced` |
-| context-hygiene | 3811 | 1 | Behavioural Iron Law: 3-failure stop, fresh-chat trigger |
-| downstream-changes | 2940 | 2b | Behavioural: every code edit |
-| guidelines | 4184 | 3 | Meta-rule: consult guidelines before code |
-| improve-before-implement | 3838 | 2b | Behavioural: validate before building |
-| markdown-safe-codeblocks | 535 | 2b | Already small; behavioural |
-| minimal-safe-diff | 3324 | 2a | Behavioural Iron Law: smallest change |
-| missing-tool-handling | 2633 | 2a | Behavioural Iron Law: ask, don't install silently |
-| no-attribution-footers | 1462 | 3 | Iron Law (recently trimmed); within budget |
-| no-roadmap-references | 2502 | mech | Scoped Iron Law: no stable→roadmap refs |
-| preservation-guard | 3825 | 2b | Quality gate during merges/refactors |
-| role-mode-adherence | 1682 | 2a | Behavioural: mode-marker contract |
-| runtime-safety | 1133 | 2b | Safety policy for execution metadata |
-| security-sensitive-stop | 3004 | 2a | Safety Iron Law: stop+threat-model |
-| size-enforcement | 865 | mech | Budget enforcement (ties into P5 CI gate) |
-| think-before-action | 5298 | 2b | Behavioural Iron Law: analyze first |
-| token-efficiency | 3885 | 2a | Behavioural: redirect verbose output |
-| tool-safety | 1242 | 2b | Safety: allowlist, deny-by-default |
-| user-interaction | 7657 | 3 | Numbered-options Iron Law |
-
-### § 3.3 — auto-rules: move-to-skill (18)
-
-Procedural how-to. Rule body migrates into named skill (P4.1); rule
-shrinks to Iron-Law one-liner + `routes_to:`. Skill IDs reference
-existing skills under `.agent-src.uncondensed/skills/`.
-
-| id | chars | target skill | rationale |
-|---|---:|---|---|
-| agent-docs | 2575 | `agent-docs-writing` | Procedural: how to author agent-docs |
-| analysis-skill-routing | 1325 | `analysis-skill-router` | Routing procedure |
-| capture-learnings | 2820 | `learning-to-rule-or-skill` | Capture procedure |
-| cli-output-handling | 1801 | `rtk-output-filtering` | Tool-wrapping procedure |
-| commit-conventions | 1938 | `conventional-commits-writing` | Format procedure |
-| docker-commands | 1830 | `docker` | Stack-specific procedure |
-| docs-sync | 3131 | `agent-docs-writing` | Mechanical sync procedure |
-| e2e-testing | 1807 | `tests-e2e-heal` | Procedural; project-specific |
-| laravel-translations | 995 | `laravel` | Stack-specific |
-| model-recommendation | 2909 | `cost-profile` | Routing procedure |
-| onboarding-gate | 4881 | `onboard` | Mechanical: meta-rule about /onboard |
-| package-ci-checks | 1342 | `lint-skills` | Repo-specific procedure |
-| reviewer-awareness | 3573 | `review-routing` | Skill exists; consolidates former `review-routing-awareness` (2026-05-08, see `agents/settings/contexts/adr-auto-rule-consolidation.md`) |
-| skill-improvement-trigger | 1597 | `skill-improvement-pipeline` | Trigger procedure |
-| slash-command-routing-policy | 3218 | `command-routing` | Routing procedure |
-| ui-audit-gate | 3285 | `existing-ui-audit` | Audit procedure |
-| upstream-proposal | 2424 | `upstream-contribute` | Procedural |
-
-### § 3.4 — auto-rules: move-to-guideline (7)
-
-Reference / examples / mechanics. Body migrates into
-`docs/guidelines/<id>.md` (P4.2); rule keeps Iron Law + pointer.
-
-| id | chars | target guideline | rationale |
-|---|---:|---|---|
-| artifact-engagement-recording | 3462 | `artifact-engagement-flow` | Mechanics doc lives in `.agent-src.uncondensed/contexts/contracts/` (P4.1) |
-| augment-portability | 2956 | `augment-portability-patterns` | Project-agnostic-patterns reference |
-| command-suggestion-policy | 3954 | `command-suggestion-flow` | Flow doc already exists |
-| php-coding | 3433 | `php-coding-patterns` | Reference table; per-stack |
-| roadmap-progress-sync | 7455 | `roadmap-progress-mechanics` | Mostly mechanics + checkbox grammar |
-| rule-type-governance | 2661 | `rule-type-governance` | Reference: when always vs auto |
-| skill-quality | 5367 | `skill-quality-checklist` | Reference checklist |
-
-## § 4 — Verification
-
-| check | command | acceptance |
-|---|---|---|
-| Coverage | `./scripts-run src/scripts/measure_rule_budget` | 56 rules total → 9 kernel + 22 condense + 18 skill + 7 guideline |
-| Determinism | `./scripts-run src/scripts/measure_rule_budget --json` × 2 | byte-identical output |
-| No-edits | `git diff --stat .agent-src.uncondensed/rules/` | clean (this is plan-only) |
-
-## § 5 — Open questions
-
-1. **Kernel swap ADR (P2.1).** `agent-authority` ↔
-   `autonomous-execution`. See `kernel-membership.md` § 5.2 for the
-   three resolution variants; this file syncs once the ADR lands.
-2. **`reviewer-awareness` + `review-routing-awareness` merge.** ✅ resolved
-   2026-05-08 — merged into `reviewer-awareness` per
-   `agents/settings/contexts/adr-auto-rule-consolidation.md`.
-3. **`onboarding-gate` migration shape.** The rule fires only on the
-   first turn; the migrated form must keep that trigger latch.
-   Router state-machine primitives (once / every-turn / on-mode-
-   switch) are a P3.1 deliverable dependency before P4 ships
-   (Council R2).
-4. **P4 migration shapes spec.** Per-disposition contract
-   (replace / merge / stub / disappear) for `move-to-skill` and
-   `move-to-guideline` — frontmatter handling, conflict resolution,
-   one-liner + `routes_to:` shape vs body merge. P4 deliverable
-   spec; flagged by Council R2 to prevent inconsistent implementer
-   calls.
-5. **`think-before-action` / `context-hygiene` / `augment-source-of-
-   truth` boundary.** Currently `condense-and-keep` (auto). Council
-   did not flag for promotion; revisit only if the swap ADR (#1)
-   forces a re-projection.

package/docs/contracts/rule-interactions.md

@@ -1,132 +0,0 @@
----
-stability: beta
-keep-beta-until: 2026-08-12
----
-
-# Rule-Interaction Matrix
-
-> **Audience:** rule authors and reviewers — anyone editing
-> `.agent-src.uncondensed/rules/*.md` or proposing a new always-rule.
-> **Authoritative source:** [`rule-interactions.yml`](rule-interactions.yml).
-> **Linter:** `scripts/lint_rule_interactions.py` (run via `task lint-rule-interactions`).
-
-The matrix captures how the package's `always` rules relate when more
-than one fires on the same turn. It exists because rules at this size
-(55 rules, ~49k tokens budget) develop emergent precedence relationships
-that no single rule file can document on its own.
-
-The anchor pair is `non-destructive-by-default` — the universal safety
-floor — paired with the five rules most likely to be invoked in the
-same turn:
-
-- `autonomous-execution` — autonomy never lifts the floor.
-- `scope-control` — git-ops permission gate; floor is the never-overridable subset.
-- `commit-policy` — four exception paths to commit; floor still gates the diff content.
-- `ask-when-uncertain` — both rules push toward the same response on a destructive ambiguous request.
-- `verify-before-complete` — independent gates; both must be satisfied.
-
-## Diagram
-
-```mermaid
-graph LR
-  NDD["non-destructive-by-default<br/>(Hard Floor)"]
-  AE["autonomous-execution"]
-  SC["scope-control"]
-  CP["commit-policy"]
-  AWU["ask-when-uncertain"]
-  VBC["verify-before-complete"]
-
-  NDD -- "overrides" --> AE
-  NDD -- "restates" --> SC
-  NDD -- "gates diff" --> CP
-  NDD -- "complements" --> AWU
-  NDD -- "complements" --> VBC
-
-  SC -- "gates git ops" --> AE
-  CP -- "overrides<br/>commit Q" --> AE
-
-  classDef floor fill:#7a1f1f,stroke:#fff,color:#fff,font-weight:bold
-  classDef gate fill:#1f4f7a,stroke:#fff,color:#fff
-  class NDD floor
-  class SC,CP gate
-```
-
-## Relations
-
-The YAML uses six relation kinds. Definitions:
-
-| Relation | Meaning |
-|---|---|
-| `overrides` | Senior rule's outcome wins when both fire — junior's permission cannot proceed past senior's stop. |
-| `narrows` | Senior shrinks the surface area on which junior applies, but does not stop it. |
-| `defers_to` | Junior explicitly hands over to senior on the overlapping surface. |
-| `restates` | The two rules cover overlapping ground intentionally — the restatement prevents future weakening of one side. |
-| `gates` | Senior fires *in addition to* junior on a specific subset, not instead of. |
-| `complements` | Both rules independently apply; outcomes are additive and harmonious. |
-
-## Reading a pair entry
-
-```yaml
-- id: ndd-x-autonomous-execution
-  rules: [non-destructive-by-default, autonomous-execution]   # senior, junior
-  relation: overrides
-  conflict: …                                                  # what triggers both
-  resolution: …                                                # what the agent does
-  evidence:
-    - .agent-src.uncondensed/rules/non-destructive-by-default.md#the-iron-law
-    - .agent-src.uncondensed/rules/autonomous-execution.md#hard-floor--see-non-destructive-by-default
-```
-
-`rules: [a, b]` is ordered: `a` is senior (wins on conflict), `b` is
-junior (yields). For `complements`, ordering is documentary only.
-
-## Adding a new pair
-
-1. Edit `rule-interactions.yml`, append a pair under `pairs:` with all
-   six required fields.
-2. Add both rule slugs to the top-level `rules:` block if not already
-   listed.
-3. Run `task lint-rule-interactions` — must exit 0.
-4. Update the Mermaid diagram above if the pair is anchor-relevant
-   (involves `non-destructive-by-default` or one of its five partners).
-5. Reference the matrix from the rule files that are involved (one
-   line each — the matrix is the source, not the rules).
-
-## When **not** to add a pair
-
-- Two rules that never fire on the same turn — no interaction means
-  no entry; the matrix is for *active* relationships.
-- Documentation-only cross-references (e.g. "see also") — those stay
-  in the rule files.
-- Skill ↔ rule interactions — the matrix is rule-only. Skills are
-  invoked, not always-active.
-- **Orchestration-layer surfaces** (AI Council, Memory, Work-Engine /
-  Decision-Engine): these are runtime systems, not `always`-rules.
-  Their interactions are governed by their own contracts and stay
-  out of this matrix by design — see "Out of scope" below.
-
-## Out of scope — orchestration surfaces (Council × Memory × Work-Engine)
-
-The matrix is **rule-only**. The orchestration layer is governed by
-dedicated contracts; cross-referencing them here would duplicate the
-source of truth and weaken it. Canonical contracts:
-
-| Surface | Canonical contract |
-|---|---|
-| Decision-Engine gates (`min_confidence`, `block_on_risk`, `require_memory_hits`, `on_block`) | [`decision-engine-gates.md`](decision-engine-gates.md) |
-| Decision-trace shape (what the engine emits per phase) | [`decision-trace-v1.md`](decision-trace-v1.md) |
-| Memory contract (entries, scopes, retention) | [`../guidelines/agent-infra/memory-access.md`](../guidelines/agent-infra/memory-access.md) |
-| Memory visibility in the trace (`affected` keys) | [`memory-visibility-v1.md`](memory-visibility-v1.md) |
-| AI-Council consultation flow | [`../skills/ai-council/SKILL.md`](../../.agent-src.uncondensed/skills/ai-council/SKILL.md) |
-
-Where an `always`-rule **does** interact with one of these surfaces
-(e.g. `non-destructive-by-default` gating a memory-driven action), the
-gate lives in the rule and the precedence is captured in this matrix
-as a rule-pair (the orchestration surface is the *occasion*, not a
-participant). For Council ↔ Memory ↔ Work-Engine interactions among
-themselves, the dedicated contracts above are authoritative.
-
-## See also
-
-- [`docs/contracts/STABILITY.md`](STABILITY.md) — public-surface stability tiers.
-- [`docs/contracts/adr-chat-history-split.md`](adr-chat-history-split.md) — ADR pattern for major rule structural changes.

package/docs/contracts/rule-interactions.yml

@@ -1,260 +0,0 @@
-# Rule-Interaction Matrix
-# -----------------------
-# Machine-readable contract for how the package's `always` rules relate
-# when more than one fires on the same turn. Linted by
-# `scripts/lint_rule_interactions.py`. Rendered diagram in
-# `docs/contracts/rule-interactions.md`.
-#
-# Schema:
-#   version: integer
-#   rules: list of rule slugs that participate in any interaction (each
-#     must exist as `.agent-src.uncondensed/rules/<slug>.md`)
-#   pairs: list of pairwise interactions
-#     - id:        kebab-case stable identifier
-#       rules:     [senior, junior] — `senior` wins on conflict
-#       relation:  overrides | narrows | defers_to | restates | gates | complements
-#       conflict:  one-line trigger that causes both to fire
-#       resolution: one paragraph — what the agent does
-#       evidence:  list of `file#anchor` citations
-#       tests:     optional list of test paths
-#
-# Anchor pair: `non-destructive-by-default` × five rules per
-# `road-to-post-pr29-optimize.md` Phase 2.
-
-version: 1
-
-rules:
-  - non-destructive-by-default
-  - autonomous-execution
-  - scope-control
-  - commit-policy
-  - ask-when-uncertain
-  - verify-before-complete
-  - agent-authority
-  - language-and-tone
-  - direct-answers
-
-pairs:
-
-  - id: ndd-x-autonomous-execution
-    rules: [non-destructive-by-default, autonomous-execution]
-    relation: overrides
-    conflict: >-
-      Standing autonomy directive ("arbeite selbstständig") is active and
-      the next step crosses a Hard-Floor trigger (production-branch merge,
-      deploy, push, prod data/infra, whimsical bulk deletion, commit with
-      bulk deletion / infra change).
-    resolution: >-
-      Autonomy never lifts the floor. Stop, surface the action via one
-      numbered-options block, wait for explicit user confirmation on
-      this turn before proceeding.
-    evidence:
-      - .agent-src.uncondensed/rules/non-destructive-by-default.md#the-iron-law
-      - .agent-src.uncondensed/rules/autonomous-execution.md#hard-floor--see-non-destructive-by-default
-
-  - id: ndd-x-scope-control
-    rules: [non-destructive-by-default, scope-control]
-    relation: restates
-    conflict: >-
-      Push, merge, branch creation, PR ops, tag pushes — both rules speak
-      to the same git operations.
-    resolution: >-
-      `scope-control` is the canonical permission gate; the floor restates
-      the prod-trunk and deploy-tied subset so the never-overridable layer
-      cannot be weakened by future scope-control edits. On any conflict,
-      the floor wins.
-    evidence:
-      - .agent-src.uncondensed/rules/non-destructive-by-default.md#the-iron-law
-      - .agent-src.uncondensed/rules/scope-control.md#git-operations--permission-gated
-      - .agent-src.uncondensed/rules/scope-control.md#production-infrastructure-bulk-destructive--hard-floor
-
-  - id: ndd-x-commit-policy
-    rules: [non-destructive-by-default, commit-policy]
-    relation: gates
-    conflict: >-
-      A commit is otherwise authorized by one of `commit-policy`'s four
-      paths (user-this-turn, standing instruction, `/commit*` invocation,
-      roadmap pre-scan), but the diff contains bulk deletions or infra
-      changes (row 6 of the Hard Floor).
-    resolution: >-
-      The commit pre-scan triggers regardless of which authorization path
-      applies. Surface the diff (paths + counts), confirm this turn,
-      then commit. The four exceptions cover *whether* commits happen;
-      the floor covers *which diffs* still need a separate confirmation.
-    evidence:
-      - .agent-src.uncondensed/rules/non-destructive-by-default.md#the-iron-law
-      - .agent-src.uncondensed/rules/commit-policy.md#hard-floor-still-applies--bulk-deletions-and-infra-changes
-
-  - id: ndd-x-ask-when-uncertain
-    rules: [non-destructive-by-default, ask-when-uncertain]
-    relation: complements
-    conflict: >-
-      A floor trigger fires AND the request is ambiguous (e.g. "delete
-      the legacy folder" without a file list).
-    resolution: >-
-      Both rules require the same response — stop and ask. The floor
-      provides the categorical reason (destructive); ask-when-uncertain
-      provides the question shape (one numbered-options block, blocking).
-      No conflict; both fire harmoniously.
-    evidence:
-      - .agent-src.uncondensed/rules/non-destructive-by-default.md#failure-modes
-      - .agent-src.uncondensed/rules/ask-when-uncertain.md#vague-request-triggers--must-ask
-
-  - id: ndd-x-verify-before-complete
-    rules: [non-destructive-by-default, verify-before-complete]
-    relation: complements
-    conflict: >-
-      A floor-crossing action (deploy, prod-data write) was authorized
-      and executed; agent is about to claim "done".
-    resolution: >-
-      Both rules apply independently. Floor is satisfied by user
-      confirmation; verify-before-complete is satisfied by fresh
-      verification evidence in the same message. Skipping either is a
-      rule violation.
-    evidence:
-      - .agent-src.uncondensed/rules/non-destructive-by-default.md#the-iron-law
-      - .agent-src.uncondensed/rules/verify-before-complete.md#the-iron-law
-
-  - id: autonomy-x-scope-control
-    rules: [scope-control, autonomous-execution]
-    relation: gates
-    conflict: >-
-      Autonomy is `on` and the next step is a permission-gated git
-      operation (push, branch create/delete, PR open, tag push) below
-      the floor threshold.
-    resolution: >-
-      `scope-control`'s permission gate stays in force. Autonomy
-      suppresses *trivial* questions only; git-shape decisions are
-      blocking. Stop and ask.
-    evidence:
-      - .agent-src.uncondensed/rules/scope-control.md#git-operations--permission-gated
-      - .agent-src.uncondensed/rules/autonomous-execution.md#blocking--still-ask-regardless-of-personalautonomy
-
-  - id: autonomy-x-commit-policy
-    rules: [commit-policy, autonomous-execution]
-    relation: overrides
-    conflict: >-
-      Autonomy is `on` and the agent could plausibly "just commit" after
-      a green verification step.
-    resolution: >-
-      `commit-policy` Iron Law forbids both committing AND asking about
-      committing unless one of the four exceptions applies. Autonomy
-      does not add a fifth exception.
-    evidence:
-      - .agent-src.uncondensed/rules/commit-policy.md#the-iron-law
-      - .agent-src.uncondensed/rules/autonomous-execution.md#commit-policy--see-commit-policy
-
-  - id: authority-x-ndd
-    rules: [agent-authority, non-destructive-by-default]
-    relation: defers_to
-    conflict: >-
-      Both rules speak to "may the agent do this autonomously?" — the
-      Priority Index points to the Hard Floor as Band 1.
-    resolution: >-
-      `agent-authority` is a router, never a source of truth. The Hard
-      Floor's Iron Law lives verbatim in `non-destructive-by-default`
-      and wins every conflict. The index points; it never restates.
-    evidence:
-      - .agent-src.uncondensed/rules/agent-authority.md#index-rules
-      - .agent-src.uncondensed/rules/non-destructive-by-default.md#the-iron-law
-
-  - id: authority-x-scope-control
-    rules: [agent-authority, scope-control]
-    relation: defers_to
-    conflict: >-
-      Permission Gate questions (push, branch, PR, architectural change)
-      surface during routine work — the index labels Band 2.
-    resolution: >-
-      The Priority Index routes to `scope-control` for git-shape and
-      scope-expansion decisions. Index never narrows or weakens the
-      gate; canonical rule wins on any wording divergence.
-    evidence:
-      - .agent-src.uncondensed/rules/agent-authority.md#index-rules
-      - .agent-src.uncondensed/rules/scope-control.md#git-operations--permission-gated
-
-  - id: authority-x-commit-policy
-    rules: [agent-authority, commit-policy]
-    relation: defers_to
-    conflict: >-
-      The "about to commit" decision arises — the index labels it Band 3
-      (Commit Default = never, with four exceptions).
-    resolution: >-
-      `commit-policy` Iron Law is canonical. The Priority Index points
-      to it; it does not enumerate the four exceptions itself. Future
-      edits to commit-policy do not require Index updates unless the
-      band ordering changes.
-    evidence:
-      - .agent-src.uncondensed/rules/agent-authority.md#index-rules
-      - .agent-src.uncondensed/rules/commit-policy.md#exceptions--when-committing-is-allowed
-
-  - id: scope-x-commit-policy
-    rules: [scope-control, commit-policy]
-    relation: narrows
-    conflict: >-
-      `scope-control` § "Git operations" forbids committing without
-      explicit permission as one of several git-op gates; `commit-policy`
-      narrows the commit case to a never-ask default with four named
-      exceptions.
-    resolution: >-
-      `commit-policy` is the narrower, canonical rule for the commit
-      sub-case. `scope-control` continues to govern push, branch, PR,
-      tag operations. On commit specifics, defer to `commit-policy`;
-      on other git ops, defer to `scope-control`.
-    evidence:
-      - .agent-src.uncondensed/rules/scope-control.md#git-operations--permission-gated
-      - .agent-src.uncondensed/rules/commit-policy.md#the-iron-law
-
-  - id: ask-x-direct-answers
-    rules: [ask-when-uncertain, direct-answers]
-    relation: complements
-    conflict: >-
-      A vague request triggers `ask-when-uncertain` (must ask), but
-      `direct-answers` Iron Law 3 (brevity by default) discourages
-      overlong replies; could read as tension when the question needs
-      framing.
-    resolution: >-
-      Both rules apply. `ask-when-uncertain` decides *whether* to ask
-      and demands one question per turn with numbered options.
-      `direct-answers` shapes *how* the question reads — no flattery,
-      no padding, shortest form that fully states the choice.
-    evidence:
-      - .agent-src.uncondensed/rules/ask-when-uncertain.md#iron-law--one-question-per-turn-always
-      - .agent-src.uncondensed/rules/direct-answers.md#iron-law-3--brevity-by-default
-
-  - id: scope-x-verify-before-complete
-    rules: [verify-before-complete, scope-control]
-    relation: complements
-    conflict: >-
-      Agent has just finished a change that touches user-permission-gated
-      operations (push, branch, PR, tag) and is preparing to claim "done"
-      in the same turn. Both rules can fire: `verify-before-complete`
-      gates the completion claim on fresh evidence; `scope-control`
-      gates the git operation on explicit permission this turn.
-    resolution: >-
-      Both rules apply independently and compose. The
-      `verify-before-complete` Iron Law still requires fresh
-      verification output in this message before any "done" claim,
-      regardless of whether the user has authorised the next git op.
-      Conversely, verification passing does not authorise pushing or
-      merging — those stay behind the `scope-control` permission gate.
-      Skipping either is a rule violation; satisfying one does not
-      satisfy the other.
-    evidence:
-      - .agent-src.uncondensed/rules/verify-before-complete.md#the-iron-law
-      - .agent-src.uncondensed/rules/scope-control.md#git-operations--permission-gated
-
-  - id: language-x-direct-answers
-    rules: [language-and-tone, direct-answers]
-    relation: complements
-    conflict: >-
-      User writes German; agent must mirror language AND avoid flattery,
-      invented facts, padding. Both rules speak to reply shape.
-    resolution: >-
-      `language-and-tone` decides the language token (mirror user's last
-      chat message); `direct-answers` decides content discipline (no
-      flattery, verified facts, brevity). They compose: a brief, direct,
-      flattery-free reply in the user's language. Neither weakens the
-      other.
-    evidence:
-      - .agent-src.uncondensed/rules/language-and-tone.md#iron-law--mirror-the-users-language-always
-      - .agent-src.uncondensed/rules/direct-answers.md#iron-law-1--no-flattery

package/docs/contracts/rule-priority-hierarchy.md

@@ -1,88 +0,0 @@
----
-stability: beta
-keep-beta-until: 2026-08-12
----
-
-# Rule Priority Hierarchy
-
-> **Audience:** anyone reading or editing `.agent-src.uncondensed/rules/*.md`,
-> or trying to predict which rule wins when several fire on the same turn.
-> **Machine-readable counterpart:** [`rule-interactions.yml`](rule-interactions.yml)
-> (linted by `scripts/lint_rule_interactions.py`).
-> **Diagram + pair-by-pair narrative:** [`rule-interactions.md`](rule-interactions.md).
-
-This document is the **ordered list** view. The matrix files describe
-how *pairs* of rules interact; this file states **which band wins**
-when the bands themselves disagree.
-
-## The four-line principle
-
-```
-Safety beats autonomy.
-Scope beats helpfulness.
-Verification beats completion.
-User intent beats command suggestion.
-```
-
-Every band below is a concrete instance of one of those four lines.
-When in doubt, walk the list top-down and stop at the first band that
-fires — that band's canonical rule decides the turn.
-
-## The ordered list
-
-| Band | Rule | What it gates | Lifts under |
-|---|---|---|---|
-| 1 | [`non-destructive-by-default`](../../.agent-src.uncondensed/rules/non-destructive-by-default.md) | Prod-trunk merge · deploy · push · prod data/infra · whimsical bulk deletion · bulk-deletion or infra commit | **Never.** Explicit user confirmation *this turn* only. |
-| 2 | [`security-sensitive-stop`](../../.agent-src.uncondensed/rules/security-sensitive-stop.md) | Auth · billing · tenant boundaries · secrets · file uploads · webhooks · public endpoints | Threat-model pass completed and recorded *before* the edit. |
-| 3 | [`scope-control`](../../.agent-src.uncondensed/rules/scope-control.md) | Git ops (branch · PR · tag · push · merge · rebase) · architectural changes · new libraries · scope expansion | Explicit user permission *this turn* or unrevoked standing instruction. |
-| 4 | [`ask-when-uncertain`](../../.agent-src.uncondensed/rules/ask-when-uncertain.md) | Ambiguous requirements · vague-request triggers · fenced steps | Concrete evidence resolves the ambiguity, **or** user answers the single question. |
-| 5 | [`commit-policy`](../../.agent-src.uncondensed/rules/commit-policy.md) | Any `git commit` | Four exceptions only — explicit "commit now", standing instruction, `/commit*` invocation, roadmap authorization. |
-| 6 | [`verify-before-complete`](../../.agent-src.uncondensed/rules/verify-before-complete.md) | "Done" / "complete" claims · suggestions to commit, push, or PR | Fresh verification evidence in *this* message. |
-| 7 | [`autonomous-execution`](../../.agent-src.uncondensed/rules/autonomous-execution.md) | Trivial-vs-blocking classification · autonomy opt-in detection | Per-step decision; never above bands 1–6. |
-| 8 | [`command-suggestion-policy`](../../.agent-src.uncondensed/rules/command-suggestion-policy.md) | Surfacing slash-command matches as numbered options | User always picks; nothing auto-executes. |
-| 9 | [`language-and-tone`](../../.agent-src.uncondensed/rules/language-and-tone.md) | First-token language of every reply · `.md` always English | Mirror the user's last chat message — no momentum exception. |
-
-**Read direction:** top-to-bottom is *priority on conflict*, not chronology.
-A turn typically touches several bands at once; the hierarchy decides
-which one's Iron Law gets the final say.
-
-## Index rules
-
-- **Higher band wins.** A band-3 permission does not lift band-1; a band-5
-  commit exception does not lift band-3. Each band's "Lifts under" column
-  is its own escape hatch and only its own.
-- **No band restates an Iron Law.** Iron Laws live verbatim in the
-  canonical rule files. This hierarchy points; it does not paraphrase.
-- **Bands 1–2 are *Hard Floors*.** No autonomy setting, no roadmap step,
-  no standing instruction lifts them. See
-  [`agent-authority`](../../.agent-src.uncondensed/rules/agent-authority.md)
-  § Index rules for the matching authority statement.
-- **Unsure → ask.** [`ask-when-uncertain`](../../.agent-src.uncondensed/rules/ask-when-uncertain.md)
-  is the universal escape hatch when the band is unclear.
-
-## Worked examples
-
-| Situation | Bands that fire | Winner | Why |
-|---|---|---|---|
-| Standing autonomy + roadmap step says "merge to `main`" | 1, 7 | **1** | Hard Floor predates and outranks autonomy; surface the merge, ask. |
-| `/commit:in-chunks` on a diff that removes a directory | 1, 5 | **1** | Commit exception authorizes *commits*, not *bulk deletions*. Confirm diff this turn. |
-| User asks "improve this" with no metric named | 4, 7 | **4** | Vague-request trigger fires before any autonomy decision; ask the one clarifying question. |
-| Editing `app/Auth/PasswordReset.php` mid-feature | 2, 7 | **2** | Security-sensitive surface stops the edit until threat-model is recorded. |
-| Agent about to claim "ready to merge" with no fresh test output | 5, 6 | **6** | Verification gate fires before the commit/push question is even valid. |
-| User types free-form prompt that matches `/refine-ticket` | 8, 9 | **8 + 9** | Suggestion runs as numbered options, mirrored to user's language. No conflict. |
-
-## Cross-references
-
-- [`agent-authority`](../../.agent-src.uncondensed/rules/agent-authority.md) — the four-band authority router (bands 1–3 + 7 of this hierarchy).
-- [`rule-interactions.md`](rule-interactions.md) — pairwise interaction narrative + Mermaid diagram.
-- [`rule-interactions.yml`](rule-interactions.yml) — machine-readable, CI-linted matrix.
-- [`STABILITY.md`](STABILITY.md) — what the `stability: beta` tag means for breaking changes.
-
-## Stability
-
-`beta` — the band ordering and four-line principle are settled, but
-the *worked examples* and the inclusion of band 8 (`command-suggestion-policy`)
-in the public hierarchy have not yet shipped through one major release.
-A breaking change to the band ordering is a SemVer-minor-pre-1.0 bump
-or a SemVer-major bump after 1.0. Adding a row, refining a "Lifts under"
-clause, or expanding the worked-examples table is non-breaking.