@event4u/agent-config 7.0.2 → 7.2.0

package/docs/decisions/ADR-020-global-only-consumer-scope.md

@@ -108,12 +108,19 @@ corrects this:
 - The global surface is **secrets** (provider keys, already global) plus the
   curated identity **whitelist** (`MERGEABLE_KEYS`) — not all of `personal.*`,
   not council config, not personas.
-- **Council configuration and personas stay project-local** (version-controlled).
-  The `MERGEABLE_KEYS` whitelist is a **security trust boundary**: an untrusted
-  project repo must not be able to escalate `ai_council` / arbitrary `personal.*`
-  into user scope. Widening the whitelist now requires a threat model.
-- The key name is **`ai_council`** (canonical, in `agents/settings/.ai-council.yml`),
-  never `agent_council`.
+- **Council config is NOT on the `MERGEABLE_KEYS` whitelist.** _(Placement
+  amended: per [ADR-093](ADR-093-ai-council-config-user-global.md) →
+  [ADR-104](ADR-104-ai-council-config-global-only.md) the council config
+  is now **user-global** at `~/.event4u/agent-config/settings/.ai-council.yml`,
+  never project-local — but it is its own dedicated `.ai-council.yml`, not a
+  merged `.agent-settings.yml` key, so it stays off this whitelist.)_ Personas
+  stay project-local (version-controlled). The `MERGEABLE_KEYS` whitelist is a
+  **security trust boundary**: an untrusted project repo must not be able to
+  escalate arbitrary `personal.*` into user scope. Widening the whitelist now
+  requires a threat model.
+- The council config key name is **`ai_council`** (canonical), never
+  `agent_council`. It lives in the user-global `.ai-council.yml` (ADR-104),
+  not under `.agent-settings.yml`.
 
 This amendment narrows ADR-020's wording; the global-only **consumer install**
 decision (distributed content writes only to `~/.event4u/agent-config/`) is

package/docs/decisions/ADR-049-configuration-trust-boundary.md

@@ -13,7 +13,17 @@ type: decision
 
 ## Status
 
-**Accepted** · 2026-06-03. Locks the AI-council convergence
+**Accepted** · 2026-06-03. **Council-config *placement* superseded by
+[ADR-093](ADR-093-ai-council-config-user-global.md) → [ADR-104](ADR-104-ai-council-config-global-only.md)**
+(council config now lives user-global at
+`~/.event4u/agent-config/settings/.ai-council.yml`, never project-local).
+The **trust-boundary decision below still stands**: `ai_council` is not on
+the user-global *settings merge whitelist* (`.agent-settings.yml` keys) —
+the council reads its own dedicated `.ai-council.yml`, not a merged
+settings key. Wherever this ADR says council config "lives project-local",
+read "lives user-global per ADR-104".
+
+Locks the AI-council convergence
 (anthropic/claude-sonnet-4-5 + openai/gpt-4o, design mode + peer-review,
 2026-06-03) on where the source of truth for personal preferences and AI-council
 configuration lives. Refines [`ADR-020`](ADR-020-global-only-consumer-scope.md)

package/docs/decisions/ADR-093-ai-council-config-user-global.md

@@ -4,7 +4,7 @@ status: accepted
 date: 2026-06-13
 decision: ai-council-config-user-global
 supersedes: —
-superseded_by: —
+superseded_by: 104
 phase: ai-council-config-relocation
 type: structural
 ---
@@ -13,9 +13,15 @@ type: structural
 
 ## Status
 
-**Accepted** · 2026-06-13. Maintainer directive (standing, restated): the
-council is a per-developer facility and must be configured once, globally,
-not re-declared per project.
+**Accepted** · 2026-06-13. **Partially superseded by
+[ADR-104](ADR-104-ai-council-config-global-only.md)** (2026-06-22): the
+user-global relocation stands, but the project-local override this ADR
+*kept* (precedence rule 2 in § Decision) is removed — the council is now
+**global-only** and never searches the project tree.
+
+Maintainer directive (standing, restated): the council is a per-developer
+facility and must be configured once, globally, not re-declared per
+project.
 
 ## Context
 

package/docs/decisions/ADR-104-ai-council-config-global-only.md

@@ -0,0 +1,119 @@
+---
+adr: 104
+status: accepted
+date: 2026-06-22
+decision: ai-council-config-global-only
+supersedes: 093
+superseded_by: —
+phase: ai-council-config-relocation
+type: structural
+---
+
+# ADR-104 — The AI-council config is global-only (drop the project-local override)
+
+## Status
+
+**Accepted** · 2026-06-22. Maintainer directive (standing, restated and
+sharpened): the council is configured **once, globally** — and the agent
+must never search a project for council config, never infer "council not
+configured" from a project's missing files.
+
+Supersedes the project-local override that
+[ADR-093](ADR-093-ai-council-config-user-global.md) deliberately kept.
+
+## Context
+
+ADR-093 relocated the council config to the user-global namespace
+(`~/.event4u/agent-config/settings/.ai-council.yml`) but **kept** a
+project-local override as precedence rule 2:
+`<project_root>/agents/settings/.ai-council.yml` would win over the
+user-global file when present. ADR-093 also rejected the "global always
+wins" alternative, reasoning it would break a consumer team's
+deliberately-checked-in shared council config.
+
+In practice that hedge produced a recurring, infuriating failure mode that
+the loader's own correctness did *not* prevent — because the failure was
+in the **agent's mental model**, not the resolver:
+
+> *"Council war in diesem Projekt nicht konfiguriert (kein <!-- md-language-check: ignore -->
+> `.agent-settings.yml`/`scripts/ai_council`), daher habe ich die eine <!-- md-language-check: ignore -->
+> Architektur-Gabel selbst entschieden."* <!-- md-language-check: ignore -->
+
+An agent working in a consumer project, asked to consult the council on an
+architecture fork, looked **in the project** for council artefacts — the
+package-internal `scripts/ai_council` directory and the long-removed
+`.agent-settings.yml` `ai_council` block — found neither (they only exist
+inside the agent-config package), and concluded the council was
+unconfigured. It then decided a structural fork solo. The user's council
+*was* configured — globally — and would have answered from any project.
+
+The project-local override is the root of this confusion: as long as "the
+project might carry its own council config" is a documented truth, the
+agent treats the project tree as a place to look, and absence-in-project
+reads as not-configured. The override's intended beneficiary (a consumer
+team pinning a shared config in their repo) has never materialised and is
+not worth the recurring solo-decision failure on real work.
+
+## Decision
+
+**The council config is global-only.** `resolve_config_path` (in
+`scripts/ai_council/config.ts`) resolves with this precedence, first match
+wins:
+
+1. **`$AI_COUNCIL_CONFIG`** — an explicit absolute path (tests / power
+   users). Honoured even when absent. This is an explicit path, not a
+   project search.
+2. **User-global** `~/.event4u/agent-config/settings/.ai-council.yml`
+   (legacy `~/.config/agent-config/` read-fallback).
+
+The project-local branch is **removed**. The loader never builds or stats
+`<project_root>/agents/settings/.ai-council.yml`. `project_root` stays in
+the signature for caller stability but is not consulted for resolution.
+
+The corollary, binding on every agent-facing surface (the `ai-council`
+skill, the `/council` command family, the config contract): **the absence
+of a council file in a project says nothing about whether the council is
+configured.** An agent must never claim "council not configured" from
+missing project files (`.agent-settings.yml`, `scripts/ai_council`, a
+project `.ai-council.yml`). The CLI/resolver is the single authority — it
+reads the global file and works from every project, worktree, and CWD.
+
+## Consequences
+
+- A user-global `.ai-council.yml` with `enabled: true` works from **every**
+  project, including consumer repos and fresh worktrees, with zero
+  per-project setup — exactly the "configure once" intent of ADR-093, now
+  without the hedge that undermined it.
+- The "council not configured in this project" solo-decision failure mode
+  is structurally impossible: there is no project location to be absent.
+- `council_cli.ts` and `cmd_doctor.ts` (`doctor council-cli`) inherit the
+  change automatically — both already route through `resolve_config_path`.
+- A consumer team that genuinely wants a repo-pinned shared council config
+  uses `$AI_COUNCIL_CONFIG` (e.g. exported in their dev shell / CI) — an
+  explicit opt-in, never an implicit project-tree search.
+- `check_council_config_location.ts` keeps guarding against
+  `.agent-settings.yml` council references; its docstring is updated to
+  drop the "project-local first" description.
+
+## Alternatives
+
+- **Keep ADR-093 as-is (project-local override stays).** Rejected — this is
+  the exact configuration that produced the recurring failure; the loader
+  being correct did not save the agent's mental model.
+- **Fix only the agent-facing docs, leave the override in the loader.**
+  Rejected — as long as a project-local lookup exists, "look in the
+  project" remains a documented truth and the absence-reads-as-unconfigured
+  confusion recurs. Removing the lookup makes the instruction unambiguous.
+- **Add a project-local override behind an explicit opt-in flag.** Rejected
+  as unneeded complexity — `$AI_COUNCIL_CONFIG` already covers the rare
+  repo-pinned case explicitly.
+
+## References
+
+- [ADR-093](ADR-093-ai-council-config-user-global.md) — the user-global
+  relocation this ADR sharpens to global-only.
+- `docs/contracts/ai-council-config.md` § File location — precedence rules.
+- `src/scripts/ai_council/config.ts` — `resolve_config_path`.
+- `src/skills/ai-council/SKILL.md`, `src/domains/meta/council/default/command.md`
+  — agent-facing surfaces carrying the "never infer not-configured from
+  missing project files" corollary.

package/docs/decisions/ADR-105-automatic-subagent-orchestration.md

@@ -0,0 +1,102 @@
+---
+adr: 105
+status: accepted
+date: 2026-06-23
+decision: automatic-subagent-orchestration
+supersedes: —
+superseded_by: —
+phase: auto-subagent-orchestration
+type: structural
+---
+
+# ADR-105 — Automatic subagent orchestration: activate-don't-fragment, prove before default-on
+
+## Status
+
+**Accepted** · 2026-06-23. Resolved by a deep AI-council round
+(claude-sonnet-4-5 + gpt-4o, design mode) plus host critical-evaluation, and
+implemented by `road-to-auto-subagent-orchestration.md`.
+
+## Context
+
+The package shipped three latent subagent surfaces — the
+`subagent-orchestration` skill (7 modes), `/orchestrate` (YAML pipelines), and
+the RDP `reasoning-orchestrator` ("dispatch by default") — all **opt-in**,
+none firing automatically. The goal: make subagent use automatic and
+settings-gated, so an orchestrating model delegates delegable sub-tasks to
+cheaper / faster / quota-separate subagents, each configured for its task,
+globally toggleable in `.agent-settings.yml`.
+
+The user's stated default was **on**. The council pushed back hard: a "default
+on" whose own design concedes it *may increase* token spend inverts risk in a
+package whose canon includes token-efficiency as an Iron Law, and whose
+multi-tool portability constraint means not every host even has a subagent
+primitive.
+
+## Decision
+
+1. **Activate, don't fragment.** Auto-dispatch is a settings + host-manifest
+   gate over the **existing** `subagent-orchestration` skill and RDP
+   "dispatch by default" — not a new parallel rule. Smallest surface.
+2. **Conservative-until-proven shipped default.** The full toggle ships now
+   (`subagents.enabled`, `subagents.auto: off|ask|on`), but the **shipped**
+   default is `ask` on hosts whose capability manifest reports
+   `subagent_spawn: true`, `off` elsewhere. The default flips toward `on`
+   (host-gated) **only** behind a real benchmark proving a net token-or-time
+   win at held quality (Phase 6). `on` is the destination, reached by
+   evidence — the reconciliation of the user's goal with the council's
+   prove-first.
+3. **Quota arbitrage is a runtime-detected bonus, never load-bearing.** The
+   "separate quota pool" (e.g. a subscription's distinct Sonnet allowance) is a
+   `host-capability-manifest` flag; routing is identical (minus the bonus)
+   where unsupported. No `.md` names a vendor's billing rule.
+4. **Deterministic classification v1.** Delegability is decided by enumerated
+   structural signals (frontmatter `parallelizable:`, ordered-plan,
+   independent-slices, a size floor); ambiguity defaults to ask/no-op, never
+   speculative spawn. No per-turn LLM meta-call in v1. LLM classification is
+   deferred to v2+, gated on the benchmark.
+5. **Verification budget preserves the floors.** Trivial/read-only sub-tasks
+   verify deterministically; non-trivial mutating sub-tasks get a full
+   cross-model judge (the `subagent-orchestration` Iron Law). A required
+   verification recorded as `none` is a surfaced safety gap.
+6. **Instrumentation first; kill-switch + surfaced guardrails.** Orchestration
+   telemetry rides additively on `audit-log-v1`. The kill-switch is a
+   single settings flip (`enabled: false` / `auto: off`). Rollback thresholds
+   (token blowup, spawn-failure, verify-skip, override rate) are surfaced from
+   the audit log — there is no automatic cohort-disable (a config package runs
+   no daemon).
+7. **Graceful host degradation.** Where the manifest reports
+   `subagent_spawn: false`, the whole layer is a clean no-op (single-agent),
+   surfaced explicitly. `.md` artefacts stay project-agnostic.
+
+## Consequences
+
+- Auto-dispatch is the default **where the host and settings allow it**, and a
+  no-op everywhere else. No safety floor is lifted.
+- The user's "default on" is an evidence-gated milestone, not assumed — the
+  one decision left for the user is to authorise/run the Phase-6 benchmark and
+  approve the default flip.
+- The implementation is mostly contexts + small pure helpers + a settings
+  block + two activated skills, keeping the diff minimal.
+
+## Alternatives considered
+
+- **Default `on` immediately** (the literal ask) — rejected: inverts risk
+  before measurement, against the frugality canon.
+- **New parallel auto-dispatch rule** — rejected: fragments a surface that
+  already exists; activation is the smaller change.
+- **Quota arbitrage as a core motivation** — rejected: vendor-specific,
+  fragile, violates portability; demoted to a runtime bonus.
+- **Council-strict default `off` forever** — rejected: forecloses the user's
+  goal; the benchmark gate is the middle path.
+
+## References
+
+- The auto-subagent-orchestration roadmap (now archived) + the
+  full council Convergence / Host verdict.
+- [`docs/contracts/auto-orchestration-v1.md`](../contracts/auto-orchestration-v1.md) — the manifest + spawn + telemetry contract.
+- Context docs under `src/agent-src/contexts/execution/`:
+  `host-capability-manifest`, `orchestration-telemetry`,
+  `auto-orchestration-activation`, `auto-dispatch-classification`,
+  `subagent-routing`, `subagent-spawn-contract`, `verify-budget`,
+  `subagent-steering`, `orchestration-benchmark-gate`.

package/docs/decisions/ADR-106-recursive-verification-benchmark-gate.md

@@ -0,0 +1,126 @@
+---
+adr: 106
+status: accepted
+date: 2026-06-23
+decision: recursive-verification-benchmark-gate
+supersedes: —
+superseded_by: —
+phase: recursive-verification · Phase 0
+type: structural
+---
+
+# ADR-106 — Recursive-verification benchmark gate: capability-OR-measured-novel-discipline, not capability-only
+
+## Status
+
+Accepted (2026-06-23). Locks the Phase 0 gate definition for
+[`road-to-recursive-verification.md`](../../agents/roadmaps/archive/road-to-recursive-verification.md)
+before any live `bench:ab` spend.
+
+## Context
+
+The `recursive-verification` skill (depth-bounded `attempt → critic verdict →
+re-attempt`, default `off`) needs a benchmark gate that decides whether its
+shipped default flips to `on`/`ask` for a given host. The roadmap's initial draft
+proposed **capability-axis-first**: ship only on a capability-axis lift; a
+discipline-axis-only lift does **not** pass, on the assumption that the package's
+existing always-on rules already deliver the discipline lift, so recursion would
+merely duplicate them at ~11× cost.
+
+This gate definition was put to the AI council (manual transport disabled; live
+`council run --depth deep`, 3 rounds; members **anthropic/claude-sonnet-4-5** +
+**openai/gpt-4o**, 2026-06-23, actual cost $0.0762). Both members independently
+converged that **capability-only is the wrong gate**, for a sound methodological
+reason; one member (anthropic) also raised a misreading that the host rejected.
+
+### What the council got right (accepted)
+
+- **The redundancy assumption is unmeasured.** The gate assumed recursion's
+  discipline lift is redundant with the existing rules *without measuring it*.
+  The fix is a **three-baseline** design and an explicit **marginal** lift:
+  - `D₀` = bare host (no rules, no recursion)
+  - `D₁` = rules only (always-on rules, no recursion)
+  - `D₂` = rules + recursion
+  - **novel discipline lift = `D₂ − D₁`** — recursion's contribution *over*
+    rules-only. Redundancy is now a measured fact, not an assumption.
+- **Cheap human-preference pre-test first.** Before any expensive benchmark, show
+  ~10 `(attempt₀, attempt_final)` pairs to humans and ask "which would you pay
+  for?". If preference < 60 %, the discipline lift is economically irrelevant →
+  capability-only gate stands and the expensive discipline arm is skipped (~$15
+  to settle the whole dispute). This mirrors the package's cheap-probe-first,
+  measure-first culture.
+- **Concrete cost ceiling, not "tolerable".** The original "at a tolerable cost"
+  is circular. Replace with a measurable ceiling (token multiplier / $-per-task).
+- **Per-(host, family) cell**, not host-global — recursion may pass for a weak
+  host on one family and fail for a strong host with no headroom.
+
+### What the council got wrong (rejected by the host)
+
+- anthropic framed the gate as a *"fatal flaw because the 0.333 → 1.000 lift is
+  already recursion."* This is a **misread** of `docs/benchmark.md`: that lift is
+  the *rules'* effect (vanilla → package), measured **without** recursion;
+  recursion's marginal lift is unmeasured (that is exactly what Phase 3 runs). The
+  valid extraction is the three-baseline design above, not "capability-first is
+  fatally wrong."
+- A weighted composite metric `w_cap·Δcap + w_disc·Δdisc` (openai) is **rejected**:
+  the weights are precisely the unknown the gate exists to discover (anthropic's
+  own counter, which the host endorses).
+
+## Decision
+
+The shipped default for `verification.recursive` flips to `on`/`ask` for a
+**(host, family) cell** if and only if:
+
+```
+capability_lift(host, family) significant       (McNemar on pass-rate, or scorer
+                                                  Wilcoxon p < 0.05, ≥6 discordant
+                                                  pairs, effect ≥ 0.5)
+OR
+( novel_discipline_lift = D₂ − D₁ > ε_disc       (recursion over rules-only —
+                                                  MEASURED, never assumed)
+  AND cost_per_task ≤ ceiling                     (concrete token-multiplier / $)
+  AND human_preference_rate > 0.6 )
+ELSE off.
+```
+
+**Cheap prerequisite (runs first, gates the rest):** the ~$15 human-preference
+test. Preference < 60 % ⇒ capability-only gate stands; skip the discipline arm.
+
+**The benchmark must report, per (host, family):** `pass_rate(D₀/D₂)`,
+`discipline_score(D₀ / D₁ / D₂)`, `cost(D₂)/cost(D₀)`, and
+`human_preference(recursion vs baseline)`. Without the `D₁` (rules-only) middle
+term, redundancy cannot be detected; without human-preference, a discipline lift
+cannot be validated as economically real.
+
+The first measured cell is `(claude-haiku-4-5, scope-discipline)`; multi-family
+expansion waits until data justifies it.
+
+## Consequences
+
+- Phase 3 of the roadmap gains a **rules-only (`D₁`) arm** and a **Phase 3a-pre
+  human-preference test**; the gate language changes from "capability-first;
+  discipline-only ⇒ STOP" to the two-branch rule above.
+- An honest-null is still first-class: capability flat **and** (human-preference
+  < 60 % OR `D₂ − D₁` ≤ ε OR cost over ceiling) ⇒ ship nothing, record the null.
+- The default stays `off` until a cell passes; no global flip without its own cell.
+- Slightly more measurement up front (three baselines + a human pre-test), bought
+  cheaply ($15 pre-test gates the expensive arm) — net a more honest gate.
+
+## Alternatives considered
+
+- **Capability-only (original draft).** Rejected: assumes, without measuring,
+  that recursion's discipline lift is redundant with the rules.
+- **Weighted composite metric.** Rejected: presupposes the weights the gate
+  exists to discover.
+- **Holistic / qualitative gate (openai round 1).** Rejected: too vague to
+  operationalise into a ship/no-ship decision.
+
+## References
+
+- [`road-to-recursive-verification.md`](../../agents/roadmaps/archive/road-to-recursive-verification.md)
+- [`docs/benchmark.md`](../benchmark.md) — the existing wrapper-lift A/B evidence.
+- Council round: anthropic/claude-sonnet-4-5 + openai/gpt-4o, 2026-06-23, deep
+  tier (3 rounds), $0.0762 actual.
+- [`subagent-orchestration`](../../src/skills/subagent-orchestration/SKILL.md),
+  [`verify-budget`](../../src/agent-src/contexts/execution/verify-budget.md),
+  `orchestration-benchmark-gate` (`gateVerdict` / `resolveShippedDefault`).

package/docs/decisions/ADR-107-legal-domain-pack-adoption.md

@@ -0,0 +1,70 @@
+---
+adr: 107
+status: accepted
+date: 2026-06-24
+decision: legal-domain-pack-adoption
+supersedes: —
+superseded_by: —
+phase: road-to-legal-pack
+type: prospective
+---
+
+# ADR-107 — Legal domain-pack adoption (EU/DE-scoped, procedure-only, evaluated honestly)
+
+## Status
+
+**Accepted** · 2026-06-24 · three AI-council rounds (anthropic/claude-sonnet-4-5 + openai/gpt-4o; the curl-timeout fix landed mid-series so rounds 2–3 ran two-voice). Implementing roadmap: road-to-legal-pack (archived on completion).
+
+## Context
+
+`event4u/agent-config` had legal-adjacent anchors (`contracts-cognition`, `privacy-review`, `data-handling-judgment`, `data-flow-mapper`, `domain-safety-disclaimer` legal sector) but no legal **domain pack**. Opening one is a `domain-adoption-policy` decision (three gates: demand signal, named maintenance owner, CI-tooling). External legal-plugin references (a first-party suite + community packs) showed reusable patterns but enforce everything via prompt instructions only (empty hooks).
+
+## Decision
+
+> **Amendment (2026-06-24, deep-council).** The pack id was renamed `legal` →
+> `legal-review-prep` after this ADR, to stop the name itself reading as "legal
+> advice" (deep AI-council + 7.1.0 reviewers; see `road-to-legal-review-prep`).
+> Read every `legal` pack-id reference below as `legal-review-prep`.
+
+Open a single, narrow `legal` pack — **not** a multi-plugin / multi-agent parity clone.
+
+1. **Scope: EU/DE-only, hard refusal.** Every selectable jurisdiction is an implicit currency promise; for a single maintainer the smallest correct cut is EU/DE with "consult local counsel" for everything else. Encoded in the `legal-safety-floor` rule + the pack description; surfaced via a machine-checkable `Jurisdiction:` tag.
+2. **Safety-floor first.** `rule:legal-safety-floor` + its deterministic linters land before any drafting skill (a drafting skill before its floor is the exact liability the floor prevents).
+3. **Skills ship procedure + output template only — no default legal positions.** Positions live in a practice profile (`legal-practice-profile`).
+4. **Deterministic hardening is the differentiator.** Disclaimer-presence, jurisdiction-tag, and freshness linters; privilege markers extend `domain-safety-pii` + `lethal-trifecta-guard` (no new hook unless the extension demonstrably fails).
+5. **Eval = regression/consistency harness, not a correctness oracle.** Self-labeled fixtures narrowed to the maintainer's genuine-competence domain (EU DPA / GDPR Art. 28) with spot-validation; a multi-attorney gold set (inter-annotator ≥0.7) is a **demand+funding-gated** track, NOT parity-gated (legal matching is classification, not the finding-count distributions the cross-model-parity keystone calibrates). The eval achieves *measurement* objectivity (reliable regression detection), never *ground-truth* objectivity — correctness stays attorney review.
+6. **No personas** — procedure-not-personality; role focus lives in skill tags + the practice profile.
+7. **Conditional product-liability gate** — commercial (Pro-tier) ship would require licensed-attorney review of the pack itself. **Resolved N/A 2026-06-24:** the suite is open-source forever, no commercial tier (ADR-108) — the gate never fires; the non-removable disclaimer + per-output attorney-review line cover end-user reliance.
+
+## Amendment (2026-06-24, deep-council) — attorney-framing-review promotion tripwire
+
+Promotion of `legal-review-prep` out of `surface_tier: lab` / `trust_level_default:
+experimental`, flipping `default_install` to anything but `false`, or any
+commercial / hosted surface, is **blocked** until a licensed German attorney has
+reviewed the *framing* (the `legal-safety-floor` rule, `LEGAL_NOTICE.md`, and the
+RDG individual-case wording — **not** skill correctness) and the review is recorded
+in `LEGAL_NOTICE.md` as `Framing reviewed by <name>, Rechtsanwalt/Rechtsanwältin,
+<date>`. The deep AI-council (2026-06-24) scoped this as a bounded (~€300–800,
+1–2h) one-time gate, **not** a blocker for the current lab release (lab is
+explicitly unvetted; users opt in knowingly via the consent gate). Enforced by
+`lint_legal_pack` (`promotion-gate` rule): a promoted tier without the recorded
+marker fails CI.
+
+## Rejections (recorded)
+
+matter-workspace (too heavy), scheduled watchers, community-skill installer hub, US-state employment tests, full litigation depth, bar-prep, Swiss cantonal depth, non-EU/DE jurisdictions, the cross-model-parity dependency for the eval (a false blocker, corrected in the full critique round).
+
+## Consequences
+
+- The pack ships `trust_level_default: experimental` / `surface_tier: lab` as the **conservative default for a high-risk legal domain**. Gate 2 was **resolved 2026-06-24 by maintainer decision: no named-owner / external-qualification gate** — the protection is the always-present, **test-enforced** not-legal-advice notice (every skill · chat output · README · dedicated legal-pack notice; `tests/scripts/legal-disclaimer-presence.test.ts`) plus the RDG individual-case guardrail. Tier promotion is a separate future decision.
+- A reusable domain-pack sequence (Safety-Floor → Enforcement → Evals → Skills → Practice-Profile) is **documented retrospectively**, validated against a second domain before promotion to a rule (per `domain-pack-extraction-when-triggered`, N=2) — it does not drive legal's design.
+
+## Alternatives considered
+
+Jurisdiction-neutral-with-EU-default (rejected — maximizes the maintenance surface the binding constraint exists to cut); objective eval pack at N=1 (rejected — manufactures false objectivity without a funded attorney gold set); ≤2 legal personas (rejected — decoration with maintenance cost, no incremental safety).
+
+## References
+
+- road-to-legal-pack — the implementing roadmap (archived on completion)
+- [ADR-013 — Discovery Frontmatter Contract](ADR-013-discovery-frontmatter-contract.md) (vocabulary amendment, same series)
+- `rule:legal-safety-floor`, `rule:domain-adoption-policy`, `rule:domain-safety-disclaimer`

package/docs/decisions/ADR-108-open-source-forever-no-commercial-tier.md

@@ -0,0 +1,46 @@
+---
+adr: 108
+status: accepted
+date: 2026-06-24
+decision: open-source-forever-no-commercial-tier
+supersedes: —
+superseded_by: —
+phase: road-to-legal-pack
+type: standing
+---
+
+# ADR-108 — The suite is open-source forever; no commercial / Pro tier
+
+## Status
+
+**Accepted** · 2026-06-24 · maintainer decision. Standing commitment for the whole `event4u/agent-config` suite, surfaced while resolving the legal pack's conditional product-liability gate (ADR-107 § 0.6).
+
+## Context
+
+The legal pack (ADR-107) carried a *conditional* product-liability gate: "if shipped commercially (Pro tier), a licensed attorney must review the pack itself before ship." That conditional only matters if a commercial/Pro tier is on the table. The maintainer's standing position is that it is not — and should be made durable so the question is not relitigated and so no future change silently introduces provider liability.
+
+## Decision
+
+**The entire `event4u/agent-config` suite is and remains open-source. There is no commercial tier, no Pro tier, no paid distribution — now or in the future.**
+
+Consequences for governance:
+
+1. **The legal pack's conditional product-liability gate (ADR-107 § 0.6) never fires.** There is no provider selling the pack; the only liability surface is end-user reliance, which is addressed by the non-removable disclaimer and the per-output attorney-review line in `legal-safety-floor`.
+2. **Liability disclaimer is permanent.** Every legal-pack output is a research-and-drafting aid, not legal advice, not a substitute for a licensed attorney, and not something anyone may rely on as definitive. This holds independent of distribution model.
+3. **Reopening requires a superseding ADR.** Introducing any paid/commercial tier would be a new, explicit decision that supersedes this ADR — and would re-activate the ADR-107 § 0.6 attorney-review-of-the-pack gate before any paid distribution.
+
+## Consequences
+
+- `legal-safety-floor` § Distribution states the open-source-forever stance and that the conditional gate is closed by decision.
+- ADR-107 § 0.6 is resolved as **N/A** (not applicable under this standing decision).
+
+## Alternatives considered
+
+- **Keep 0.6 purely conditional, no standing decision** (rejected — leaves the door open to silently introducing provider liability; the maintainer wanted it hardened for the future).
+- **A CI lint enforcing "no commercial tier"** (rejected — over-engineering; an ADR + the floor statement are the right durable surface, and there is no machine signal of "commercial intent" to lint).
+
+## References
+
+- [ADR-107 — Legal domain-pack adoption](ADR-107-legal-domain-pack-adoption.md) (§ 0.6 conditional gate, now resolved N/A)
+- `rule:legal-safety-floor` § Distribution + § What this pack is — and is not
+- road-to-legal-pack § 0.6 (archived on completion)

package/docs/decisions/INDEX.md

@@ -107,6 +107,11 @@ _Auto-generated by `scripts/adr/regenerate_index.py`. Do not edit._
 | [ADR-101](ADR-101-ticket-bundle-emission.md) | Ticket Bundle Emission | proposed | 2026-06-15 | — |
 | [ADR-102](ADR-102-ticket-handoff-paste-and-mcp.md) | Ticket Handoff Paste And Mcp | accepted | 2026-06-16 | — |
 | [ADR-103](ADR-103-global-knowledge-default-off-until-measured.md) | Global Knowledge Default Off Until Measured | accepted | 2026-06-16 | — |
+| [ADR-104](ADR-104-ai-council-config-global-only.md) | Ai Council Config Global Only | accepted | 2026-06-22 | 093 |
+| [ADR-105](ADR-105-automatic-subagent-orchestration.md) | Automatic Subagent Orchestration | accepted | 2026-06-23 | — |
+| [ADR-106](ADR-106-recursive-verification-benchmark-gate.md) | Recursive Verification Benchmark Gate | accepted | 2026-06-23 | — |
+| [ADR-107](ADR-107-legal-domain-pack-adoption.md) | Legal Domain Pack Adoption | accepted | 2026-06-24 | — |
+| [ADR-108](ADR-108-open-source-forever-no-commercial-tier.md) | Open Source Forever No Commercial Tier | accepted | 2026-06-24 | — |
 | [ADR-200](ADR-200-python-to-typescript-migration.md) | Python To Typescript Migration | accepted | 2026-06-11 | — |
 
 ## Unnumbered (legacy)

package/docs/getting-started.md

@@ -129,7 +129,7 @@ Your agent is now:
 - **Respecting your codebase** — no conflicting patterns
 - **Following standards** — consistent code quality
 
-This is enforced automatically by 88 rules. No configuration needed.
+This is enforced automatically by 93 rules. No configuration needed.
 
 ---
 
@@ -169,7 +169,7 @@ Your agent now understands slash commands:
 | `/quality-fix` | Run and fix all quality checks |
 | `/chat-history import` | Pull a prior session into the current chat (resume) |
 
-→ [Browse all 161 active commands](../dist/agent-src/commands/)
+→ [Browse all 162 active commands](../dist/agent-src/commands/)
 
 ---
 

package/docs/guidelines/agent-infra/domain-eval-anti-pattern.md

@@ -0,0 +1,53 @@
+# Domain-eval anti-pattern — manufactured false objectivity at N=1
+
+> A retrospective from the legal pack (council round 3). It exists so the next
+> domain does not repeat the mistake. The short version: **do not call a
+> self-labeled regression harness an "objective" correctness gate.**
+
+## The anti-pattern
+
+Gating skill ship on *"≥X% match to expert ground-truth"* and calling it "the
+objective replacement for reviewer sign-off" — when:
+
+1. **The ground-truth is unsourced or self-generated.** If the maintainer guesses
+   what an expert would flag, the eval measures "does the skill match the
+   maintainer's guess," i.e. reviewer subjectivity wearing a quantitative costume.
+2. **Expert agreement is not truth.** Even an attorney-validated gold set at
+   inter-annotator agreement ≥0.7 is *inter-subjective expert consensus*, not
+   ground truth — `0.7 ≠ 1.0` admits the domain is contested ~30% of the time.
+   The honest goal is **measurement objectivity** (reliably detect change), not
+   **ground-truth objectivity** (the labels are correct).
+3. **Model capability caps below the threshold.** Clause-extraction caps at
+   ~F1 0.62; any passable threshold therefore measures "not worse than a mediocre
+   baseline," i.e. regression detection — never correctness.
+4. **The statistical language is borrowed from infra that does not exist.**
+   Calibrating a threshold "from cross-model distributions" requires a built
+   cross-model-parity layer. Borrowing the vocabulary before the layer exists is
+   false precision.
+
+## The honest alternative
+
+- **Ship a regression / consistency harness.** Self-labeled fixtures, explicitly
+  marked "regression-only, not correctness, not objective." It catches "did a
+  change make a skill worse than its own baseline."
+- **Keep correctness with the human.** Licensed-expert review on material use,
+  baked into the skill's output, not a footnote.
+- **Make the objective eval a separate, gated track.** Attorney/expert-validated
+  gold set + inter-annotator ≥0.7 is real but expensive; gate it on **validated
+  demand + funding**, not on a phase timeline — and note it is classification, so
+  it does **not** depend on a cross-model-parity keystone.
+
+## The false-blocker corollary
+
+When you scope an eval, check what it *actually* depends on. The legal eval was
+briefly gated on the cross-model-parity keystone; the full critique round showed
+that was wrong — legal fixture matching is **classification** (clause
+present/absent/ambiguous), not the finding-count distributions that keystone
+calibrates. The real dependency was labeled-gold-set tooling, buildable in-pack.
+A false structural blocker is as much an error as false objectivity.
+
+## See also
+
+- [ADR-107 — Legal domain-pack adoption](../../decisions/ADR-107-legal-domain-pack-adoption.md)
+- `domain-pack-architecture.md` — the retrospective sequence this is part of.
+- `src/domains/legal/evals/README.md` — the regression harness in practice.