@event4u/agent-config 9.7.0 → 9.9.0

package/docs/contracts/ai-council-config.md

@@ -1,829 +0,0 @@
----
-stability: beta
-keep-beta-until: 2026-08-12
----
-
-# AI-Council Config (`.ai-council.yml`)
-
-**Purpose.** Lock the schema, validation, and precedence rules for the
-centralized council config file. Every phase of the AI-Council
-consolidation work reads from this file; the contract here is the
-boundary that prevents drift across the loader, the CLI, the
-orchestrator, and the `.ai-council.yml` file itself.
-
-**Audience.** Authors of `scripts/ai_council/config.py`, `council_cli.py`,
-`scripts/ai_council/orchestrator.py`, and the `.ai-council.yml`
-starter. Also reviewers checking that new providers / advisors / debate
-features keep the schema intact.
-
-**Status.** Internal-locked. Changes require a contract version bump and
-a revision entry in the consuming roadmap.
-
-## File location
-
-The council is configured **once per user**, not per project. The config
-lives in the user-global namespace:
-
-```
-~/.event4u/agent-config/settings/.ai-council.yml
-```
-
-(with the legacy `~/.config/agent-config/settings/.ai-council.yml` read as a
-fallback during the v2.4 namespace transition). This is where a single
-developer enables members, pins models, and sets caps once — and the
-council then works in **every** project they open, with no per-project
-file to check in or accidentally commit. See
-[ADR-093](../decisions/ADR-093-ai-council-config-user-global.md) and
-[ADR-104](../decisions/ADR-104-ai-council-config-global-only.md).
-
-**The council config is ALWAYS user-global. The project tree is NEVER
-searched for it.** `scripts/ai_council/config.ts:resolve_config_path`
-resolves the active file with this precedence (first match wins):
-
-1. **`$AI_COUNCIL_CONFIG`** — an explicit absolute path. Honoured even
-   when the target is absent (so a typo surfaces as "create it here"
-   rather than silently falling back). Primarily for tests / power users.
-   This is an explicit path, not a project search.
-2. **User-global** `~/.event4u/agent-config/settings/.ai-council.yml` — the
-   canonical default described above.
-
-There is **no project-local lookup.** A `<project_root>/agents/settings/.ai-council.yml`
-in any project (including this package's own tree) is ignored — the
-council never reads it (ADR-104, superseding the project-local override
-ADR-093 had kept). The absence of a council file *in a project* therefore
-says **nothing** about whether the council is configured; only the
-user-global file (or the `$AI_COUNCIL_CONFIG` override) decides that.
-
-When neither exists, the loader reports the user-global path as the place
-to create it. `agents/templates/.ai-council.yml.example` ships the
-documented shape to copy from. The legacy `ai_council.*` block under
-`.agent-settings.yml` remains removed (Phase 0 Step 5); a one-line
-breadcrumb there points at this contract.
-
-> **Why user-global, not project-tracked.** A council config checked into
-> the project tree (the pre-ADR-093 layout) (a) re-applied per-project
-> instead of per-developer, (b) risked being committed to a public repo,
-> and (c) was silently *not found* on cloud / headless / fresh-checkout
-> surfaces with no project copy — the council then refused with
-> "ai_council.enabled is false" even though the user had set it up. The
-> user-global location fixes all three.
-
-## Top-level schema
-
-```yaml
-enabled: <bool>                 # master switch, required
-defaults:                       # per-invocation defaults, required
-  mode: <"api" | "manual" | "cli">
-  min_rounds: <int >= 1>
-  deep_min_rounds: <int >= min_rounds>
-  max_output_tokens: <int >= 0>           # 0 widens to provider ceiling
-  session_retention_days: <int >= 0>      # 0 disables pruning
-  debate_max_rounds: <int >= 2>           # reserved by Phase 0, wired in Phase 7
-cost_budget:                    # hard caps per /council invocation, required
-  max_input_tokens: <int >= 0>            # 0 disables this cap
-  max_output_tokens: <int >= 0>           # 0 disables this cap
-  max_calls: <int >= 0>                   # 0 disables this cap
-  max_total_usd: <number >= 0>            # 0 disables the USD ceiling — applies to billable transports: all `mode: api`, plus `mode: cli` for xai/perplexity (community CLIs that still consume the API key). Does NOT apply to vendor-official `mode: cli` (anthropic/openai/gemini) or to `mode: manual`
-cli_call_budget:                # optional; per-day call-count guard for mode: cli members
-  max_calls_per_day:
-    <provider>: <int >= 0>                # opt-in per provider; default unset = unlimited
-  warn_at: <float in [0.0, 1.0]>          # default 0.8 — pre-run summary line prefixes "⚠️" once used/limit >= warn_at (step-8 D4)
-members:                        # per-provider blocks, at least one enabled
-  <provider>:
-    enabled: <bool>
-    model: <string>
-    api_key_ref: <string>                 # required for mode: api; optional for cli/manual
-    mode: <"api" | "manual" | "cli">      # optional override of defaults.mode
-    binary: <string>                      # optional; only valid when effective mode == "cli"
-advisors:                       # Thinking-style replace-mode advisors
-  <advisor-key>:
-    enabled: <bool>
-    member: <provider>                    # required; references members.<provider>
-    model: <string>                       # optional; overrides member.model
-    persona: <path>                       # optional; defaults to personas/advisors/<advisor-key>.md
-necessity_classifier:           # Phase 6 — optional, default enabled+educate
-  enabled: <bool>                         # master switch (default true)
-  mode: <"off" | "educate" | "block" | "warn-only">       # default "educate" (agent invocation)
-  user_explicit_mode: <"off" | "educate" | "block" | "warn-only">  # default "warn-only" — step-8 D2; applies when invocation=user_explicit
-decision_replay:                # Phase 9 — optional, default enabled+full
-  enabled: <bool>                         # master switch (default true)
-  include_member_arguments: <bool>        # default true; false = redacted view
-lens_overrides:                 # Phase 6 — optional, per-lens nudges
-  necessity_classifier_mode:
-    <lens>: <"off" | "educate" | "block">
-lenses:                         # Phase 9 — optional, per-lens overrides
-  <lens>:
-    decision_replay:
-      enabled: <bool>
-      include_member_arguments: <bool>
-```
-
-Supported `<provider>` keys: `anthropic`, `openai`, `gemini`, `xai`,
-`perplexity`. Unknown providers fail validation closed.
-
-### Transport modes
-
-Three first-class transports on the `mode:` axis. Resolution per member:
-`per-member mode > defaults.mode > "api"`.
-
-| Mode | Semantics | Billable | Auth | Cost gate |
-|---|---|---|---|---|
-| `manual` | Copy & paste — the human transports prompt + reply between the agent and an external chat surface. | No | None — human-in-the-loop | n/a |
-| `api` | SDK call against a stored key, per-token billing on the provider's API. | Yes | `api_key_ref` (env or 0600 file) | `cost_budget` (full) |
-| `cli` | Shell out to a locally-installed provider CLI. For `anthropic` / `openai` / `gemini` this runs under the user's subscription auth and is `billable=False`. For `xai` / `perplexity` (community wrappers) the CLI consumes the same API key as `mode: api` and remains `billable=True`. | Mixed — see below | CLI-managed OAuth (vendor) or API key in CLI env (community) | Vendor: `cli_call_budget.max_calls_per_day` only · Community: full `cost_budget` |
-
-Implications:
-
-- **`cost_budget.max_total_usd` applies to `mode: cli` for `xai` and
-  `perplexity`.** Their CLIs (`grok`, `perplexity`) are community-built
-  wrappers around the same paid API — `mode: cli` is an ergonomic
-  shortcut, NOT a billing change. The orchestrator still runs the
-  pre-call USD estimate and the budget gate for these two providers.
-- **`cost_budget.max_total_usd` does NOT apply to `mode: cli` for the
-  vendor-official CLIs (`anthropic`, `openai`, `gemini`) or to
-  `mode: manual`.** All four are `billable=False`; the USD ceiling is
-  a token-billing concept they don't participate in.
-- **`api_key_ref` is required for enabled members whose effective mode
-  is `api`, AND for `xai` / `perplexity` even in `mode: cli`** — the
-  community CLI reads the key from its own env, but the agent still
-  surfaces missing-key as a validation error before the call. The
-  vendor-official CLIs (`anthropic`, `openai`, `gemini`) authenticate
-  via their own login flow and need no `api_key_ref` in `mode: cli`;
-  manual members have no key at all.
-- **`binary:` is only valid when the effective mode is `cli`.** Setting it
-  on an `api` or `manual` member is a hard validation error — no silent
-  ignore, no clutter.
-- **Subscription quotas:** Claude Pro 5h usage windows, ChatGPT Plus
-  message caps, Gemini free-tier per-day limits all live outside this
-  loader's view. `cli_call_budget.max_calls_per_day.<provider>` lets the
-  user opt into a per-day cap; counter state persists at
-  `~/.event4u/agent-config/cli-calls.json` with daily UTC reset (wired in
-  Phase 1 of the CLI-transport roadmap).
-- **Omitting `model:` for a vendor `cli` member is a PIN, not "latest".**
-  Each vendor CLI client (`anthropic` / `openai` / `gemini`) falls back to a
-  dedicated `DEFAULT_*_CLI_MODEL` constant when `model` is unset
-  (`clients.ts`); `xai` / `perplexity` CLIs are community API wrappers and
-  reuse their `DEFAULT_*_MODEL` API constant. The value is a deliberate pin;
-  the vendor CLI's own default may be newer. Bump the constant intentionally —
-  never assume the omitted default tracks the provider's latest release. The
-  CLI constants are separate from the API ones because the two can legitimately
-  diverge — `openai` API `gpt-4o` vs CLI `gpt-5` is the proof.
-- **Quota observability (step-8 D1, D4):** every `council run` /
-  `council debate` prints a one-line `council:quota · <provider>
-  used/limit · …` summary before the first member fires. Only
-  providers with a configured `max_calls_per_day` cap appear; uncapped
-  providers are omitted (no false sense of metering). When
-  `used / max_calls_per_day >= cli_call_budget.warn_at` (default
-  `0.8`) the line is prefixed `⚠️` and lists the providers near the
-  limit on the next line. The standalone `agent-config council
-  quota` subcommand dumps the same state plus the configured caps,
-  and `--reset <provider> --confirm` clears today's counter for that
-  provider.
-
-### Persistent events log (step-8 D3)
-
-The orchestrator appends one JSON line to `agents/runtime/council/events.log`
-on every necessity-gate decision (`proceed` / `skip_necessity`) and on
-every `cli_call_budget` block (`block_quota`). The log is gitignored
-by default — it is a local-only audit trail, never part of the
-repository contract.
-
-Schema v1:
-
-```json
-{
-  "schema_version": 1,
-  "ts_utc": "2026-05-15T03:38:45Z",
-  "lens": "analysis",
-  "invocation": "user_explicit",
-  "action": "proceed",
-  "verdict": "necessary",
-  "provider_caps": {"anthropic": {"mode": "cli", "model": "sonnet-4"}},
-  "original_ask_hash": "abc123def456"
-}
-```
-
-- `action` ∈ `proceed | skip_necessity | block_quota`.
-- `original_ask_hash` is `sha256(original_ask)[:12]`. The raw prompt
-  is **never** written — privacy floor per
-  [`agents/decisions/low-impact-decisions.md`](../../agents/decisions/low-impact-decisions.md).
-- Diagnostic fields outside the reserved set (`category`, `mode`,
-  `cli_calls_used`, …) pass through verbatim. Consumers MUST treat
-  unknown keys as forward-compatible.
-- `AGENT_CONFIG_NO_EVENTS_LOG=1` (step-8 D5) disables every write
-  in-process — useful for ephemeral worktrees, CI runners that
-  shouldn't accumulate state, or sandbox testing.
-
-### Advisor block (Phase 6, replace-mode)
-
-Five built-in advisor keys ship under
-[`.agent-src.uncondensed/personas/advisors/`](../../.agent-src.uncondensed/personas/advisors/):
-`contrarian`, `first-principles`, `expansionist`, `outsider`,
-`executor`. Each entry binds one advisor to one enabled provider. When
-`enabled: true`, the orchestrator REPLACES that provider's plain-member
-call with the advisor-persona call — the run keeps the same total call
-count as a plain run.
-
-- `member` is required and must name a known provider. The validator
-  rejects an enabled advisor whose `member` is missing from the
-  `members` block, OR exists but has `enabled: false` — silent skips
-  on the spend path are not allowed.
-- `model` is optional. When omitted, the advisor inherits its bound
-  member's `model`. When set, it overrides for that advisor call only.
-- `persona` is optional. When omitted, the loader resolves the file at
-  `personas/advisors/<advisor-key>.md` relative to the package root.
-
-### Advisor persona labels in peer-review (preserve-persona)
-
-Phase 5 peer-review anonymisation strips provider/model identity per
-the Iron Law of Neutrality. On an advisor-mode run, the anonymisation
-step preserves the **advisor persona label** as signal — peer-review
-output renders as `Response A (Contrarian)`, never
-`Response A (Anthropic Opus)`. Plain runs strip identity entirely.
-Hard-coded behaviour — no flag, no opt-out.
-
-### Necessity classifier (Phase 6, pre-flight gate)
-
-A heuristic pre-flight that decides whether the request actually
-warrants a full council deliberation. Three verdicts (`necessary`,
-`borderline`, `unnecessary`) drive three exit paths in the dispatcher
-(skip silently, educate + block, or proceed). Implemented in
-[`scripts/ai_council/necessity.py`](../../src/scripts/ai_council/necessity.py);
-wired into `council_cli.cmd_run` and `cmd_debate` before any member
-is invoked.
-
-**Configuration.**
-
-- `necessity_classifier.enabled` (bool, default `true`) — master switch.
-  `false` short-circuits the gate entirely; legacy "always run" behaviour
-  is restored.
-- `necessity_classifier.mode` (`"off" | "educate" | "block" | "warn-only"`,
-  default `"educate"`). Governs the **agent** invocation tier.
-  - `off` — gate disabled while keeping the classifier module loaded
-    (cheap toggle for experiments).
-  - `educate` — agent-initiated invocation + `unnecessary` verdict skips
-    silently with `skipped_reason: necessity_unnecessary` in
-    `session.md`. User-explicit invocation + `unnecessary` prints a
-    one-paragraph rationale and exits non-zero; `--proceed-anyway`
-    overrides on this single call.
-  - `block` — same as `educate` for `necessary` / `borderline`, but
-    `unnecessary` is rejected regardless of invocation source. Even
-    `--proceed-anyway` is ignored (power-user opt-in for cost-strict
-    environments).
-  - `warn-only` (step-8 D2) — annotate the verdict on stdout but
-    **never** skip. Useful when the user wants observability without
-    losing council coverage.
-- `necessity_classifier.user_explicit_mode` (same enum, default
-  `"warn-only"`, step-8 D2) — governs the **user_explicit** invocation
-  tier. The two-tier split reconciles "Council always active when
-  enabled" with "skip trivial agent-side requests": user-typed
-  `/council` calls proceed by default, agent-initiated dispatches keep
-  `educate` behaviour. Override via the resolved `.ai-council.yml`.
-- `lens_overrides.necessity_classifier_mode.<lens>` — per-lens override.
-  Wins over the global `mode` for the matching invocation tier (agent
-  vs user_explicit follow the same lens map). Typical use: leave the
-  global at `educate` and force `debate` lens to `block` because
-  debate is the most expensive transport.
-
-**Invocation context (CLI flags).**
-
-- `--invocation {agent,user_explicit}` — defaults to `user_explicit`.
-  Agent orchestration MUST set `--invocation agent` so silent skips are
-  available; user-typed `/council` keeps the default.
-- `--proceed-anyway` — one-shot override of the `educate` block. Does
-  NOT lift `block` mode.
-
-**Classifier shape.**
-
-Word-boundary regex matches against four `necessary` buckets
-(architecture / tradeoff / ambiguity / strategic) and four
-`unnecessary` buckets (bugfix / syntax / single_file / lookup).
-Decision table:
-
-| Necessary hits | Unnecessary hits | Lens strict? | Verdict |
-|---|---|---|---|
-| `> unnecessary` | any | n/a | `necessary` |
-| `>= 1` | `== 0` | n/a | `necessary` |
-| `== 0` | `>= 1` | n/a | `unnecessary` |
-| equal `>= 1` each | both `>= 1` | n/a | `borderline` |
-| `== 0` | `== 0` | yes (`debate`) | `unnecessary` |
-| `== 0` | `== 0` | no | `borderline` |
-
-Trigger word lists live in
-[`scripts/ai_council/necessity.py`](../../src/scripts/ai_council/necessity.py)
-as `NECESSARY_TRIGGERS` and `UNNECESSARY_TRIGGERS` — extend there with
-a unit test; never edit downstream copies.
-
-### Decision-replay artefact (Phase 9, audit trail)
-
-Per-session `decision-replay.md` written next to `responses.json` whenever
-the consensus round runs. Pure projection of consensus data plus the
-final-round per-member texts — no extra model calls. The artefact
-surfaces, per top finding, the verdict band (Strong/Moderate/Weak), the
-evidence-quality bucket (H/M/L), the agree/dissent member split, and one
-key argument per member. Implementation:
-[`scripts/ai_council/replay.py`](../../src/scripts/ai_council/replay.py).
-
-**Configuration.**
-
-- `decision_replay.enabled` (bool, default `true`) — master switch.
-  `false` skips the artefact for every lens.
-- `decision_replay.include_member_arguments` (bool, default `true`) —
-  when `false`, the artefact emits the redacted view: verdict +
-  evidence-quality + counts only, no per-member arguments. Use for
-  surfaces where attributing reasoning to a specific model would leak
-  vendor preference signal.
-- `lenses.<lens>.decision_replay.enabled` / `include_member_arguments`
-  — per-lens overrides that beat the global block. Typical use: keep
-  the audit trail on for `analysis` and turn it off for `default` /
-  `prompt` where consensus rarely runs.
-
-**CLI.**
-
-- Written automatically by `council run` when consensus scoring fires.
-- `council replay <responses.json>` re-renders the artefact from a saved
-  session. `--output <path>` writes to a file (otherwise stdout);
-  `--redact-member-arguments` / `--include-member-arguments` toggle the
-  redacted view independent of config.
-
-**Decision-replay schema.** The markdown body follows a fixed shape so
-downstream tooling can scrape it:
-
-```
-# Decision Replay
-
-> <original-ask truncated to 400 chars>
-
-## <finding-id> — <finding-text truncated to 120 chars>
-
-- **Consensus**: Strong|Moderate|Weak (<strength 0.00–1.00>)
-- **Evidence quality**: H|M|L (mean <X>/10)
-- **Agreement**: <concur>/<total> members concur, <dissent> dissent
-
-**Agreeing members**:                        # full mode only
-- _<provider:model>_ — <argument truncated to 200 chars>
-
-**Dissenting members**:                      # full mode only
-- _<provider:model>_ — <argument truncated to 200 chars>
-
-**Synthesis verdict**: <band> consensus — <source> sourced.
-
----
-
-_artefact mode: full|redacted (counts only)_
-```
-
-Findings are ranked by `consensus_strength` descending. Empty sessions
-emit the heading plus `*No findings were extracted for this session.*`.
-The trailer additionally carries two aggregate lines — **Evidence spread**
-(high/medium/low counts across findings) and **Provider spread** (distinct
-providers that deliberated) — folded in beside `_artefact mode:_`.
-
-### Stance tally (Phase 1 — option-level verdict)
-
-`consensus_scoring` scores *findings*; `stance_tally` produces an
-*option-level* verdict for "A or B?" questions. **Default-off**; with the
-block absent the council path is byte-identical to today.
-
-**Configuration.**
-
-- `stance_tally.enabled` (bool, default `false`) — master switch. A
-  non-bool value is rejected at config load (`CouncilConfigError`); unknown
-  values are not silently coerced.
-
-**Behaviour when enabled.** The final round appends a mandatory closing-line
-contract — `STANCE: <label> | CONFIDENCE: high|med|low | DEALBREAKER: yes|no`
-— parsed deterministically (`stance_tally.ts`), never inferred from prose.
-Weights are confidence factors (`high 1.0 / med 0.75 / low 0.5`); `W_total`
-sums base weights over every member with a parseable stance (abstentions
-included, so they raise the bar). Consensus requires an option to clear
-`⅔ × W_total`; below threshold a structured **split** is returned to the
-user — never a forced winner, never an auto-added round. The synthesis gains
-a **Vote Tally** section (one line per option, the threshold, and a
-cleared-or-escalated line). The final-round wiring is LIVE (2026-07-12): `consult` appends the contract to
-the final round and `render` emits the Vote Tally block, threaded via
-`payload.stance_tally`. A member whose stance line is missing or unparseable is
-a repair-marker; the bounded stance-line-only repair CALL (policy: `repair_action`
-— confirm-interactive / auto-fire under `--auto-continue`) and its estimate row
-are the remaining dispatch wiring.
-
-### Chairman synthesis (Phase 2 — opt-in)
-
-The skill's own Iron Law argues the host, having framed the artefact, cannot
-independently judge it. `chairman` lets a **non-deliberating member** author the
-synthesis instead. **Default `host`** = today's behaviour, byte-identical.
-
-**Configuration.**
-
-- `chairman.mode` (enum `host` | `member` | `auto`, default `host`) — an unknown
-  value is rejected at config load.
-- `chairman.member` (string, required when `mode: member`) — must name a member
-  that exists AND is enabled; **fails closed** at load otherwise.
-- `members.<name>.tier` (int ≥ 1, optional) — capability rank used only as the
-  `auto` tie-break (higher = stronger); non-integer / < 1 rejected at load.
-
-**Selection** (`chairman.ts` `select_chairman`, pure): `host` → host synthesis;
-`member` → the named member, but only if it did **not** deliberate this session
-(a member that argued cannot self-judge — else host fallback with a visible
-annotation); `auto` → **provider-family difference primary, tier tie-break,
-config-order final** — decided by the contested-design council pass
-(claude-sonnet-4-5 + gpt-4o, 2-round debate, 2026-07-12): independence from the
-deliberators' priors is the binding constraint for a judge, so `auto` picks a
-non-deliberating member (provider-different by construction under the
-one-member-per-provider invariant); among candidates the optional
-`members.<name>.tier` wins, else the deterministic config order; no
-non-deliberating member → annotated host fallback. The billable chairman
-dispatch (rendering the synthesis as one member call in `cmd_run`) is the
-remaining wiring step.
-
-### Debate enforcement gates (Phase 3 — opt-in)
-
-- `debate_gates.enabled` (bool, default `false`) — when on, round-2+ debate
-  prompts carry the **anti-conformity directive** (`prompts.ANTI_CONFORMITY_DIRECTIVE`:
-  defend a position; change only on a specific named flaw; agreement without a
-  named reason is conformity). Byte-identical across api/cli/manual (it is part of
-  the shared `user_prompt`). Default-off keeps the debate path byte-identical.
-- `restate.enabled` (bool, default `false`) — or the `--restate` debate flag:
-  a pre-round-1 pass collecting a ≤ 50-word restatement + one alternative
-  framing per member (billable, through the same spend gate), rendered above
-  the round-1 responses; a restatement with little token overlap vs the stated
-  ask is flagged before further spend.
-
-The deterministic post-round detectors — dissent-quota (`debate_gates.dissent_quota_met`)
-and the novelty gate (`debate_gates.is_near_duplicate`, reusing the shared
-Jaccard util) — are implemented and tested as pure functions.
-
-**Repair-call policy** (`debate_gates.repair_action`) — decided by the
-contested-design council pass (claude-sonnet-4-5 + gpt-4o, 2026-07-12): a cost
-estimate is an upper bound, not a spend commitment, and repairs are failure-mode
-responses — so **interactive runs get a one-line confirm** before each repair
-call; **unattended runs (`--auto-continue`) auto-fire** under the hard cap
-(≤ 1 repair per member per round, absolute — an already-repaired member is
-skipped in every mode); manual-transport members follow the same policy. The repair dispatch is LIVE in `run_debate` (2026-07-12): post-round checks on
-round 2+, ≤ 1 repair per member per round, dispatched via the CLI's
-`_make_repair_confirm` transport (auto-fire under `--auto-continue`, one-line
-confirm interactive); a successful repair replaces the member's round entry.
-
-### Decision resolution by impact (Phase 10, ask-user routing)
-
-Five-class impact classifier triages every pending agent question
-before it surfaces. Heuristic, shape-based, keyword-driven — no LLM
-call, fully explainable. Lives in `scripts/ai_council/necessity.py`
-(`classify_impact`, `route_decision`).
-
-| Class | Trigger shape | Default mode |
-|---|---|---|
-| `trivial` | naming, whitespace, comments, typo, indent | `agent` |
-| `low_impact` | local idioms, DTO vs value object, test extensions | `agent` |
-| `medium_impact` | API shape, contract change, breaking change, module boundary | `council` |
-| `high_impact` | security, auth, tenant boundary, migration, billing, secrets, PII | `user` (**LOCKED**) |
-| `user_required` | user-fence markers — "ask me", "review first", "plan only" | `user` (**LOCKED**) |
-
-**Iron Law** — `high_impact` and `user_required` ALWAYS route to the
-user. The schema loader rejects any `decision_resolution.classes.<cls>.mode`
-that maps either class to `agent` or `council`. No override path, no
-config flag, no autonomy setting can lift this lock.
-
-**Confidence gate** — each entry carries a `confidence_threshold`
-(default `0.6`). When the classifier's confidence is below the
-threshold, the configured mode is upgraded one rung
-(`agent` → `council` → `user`) so low-certainty calls escalate rather
-than silently auto-resolve.
-
-```yaml
-decision_resolution:
-  enabled: true
-  classes:
-    trivial:
-      mode: agent
-      confidence_threshold: 0.6
-    low_impact:
-      mode: agent
-      confidence_threshold: 0.6
-    medium_impact:
-      mode: council
-      confidence_threshold: 0.6
-    high_impact:
-      mode: user            # LOCKED — Iron Law
-      confidence_threshold: 0.6
-    user_required:
-      mode: user            # LOCKED — Iron Law
-      confidence_threshold: 0.6
-```
-
-### Low-impact council opt-in
-
-The default route for `low_impact` is `agent` — the host resolves locally
-and the council is not invoked. Sending `low_impact` to the council is
-an **explicit, two-knob opt-in**; missing either knob keeps the question
-on the host:
-
-1. `decision_resolution.classes.low_impact.mode: council` (default
-   `agent`) — flips the class route.
-2. **At least one** enabled member sets `participate_low_impact: true`
-   (default `false`) — names which members run on the fast-path.
-
-When both knobs are set, the lightweight-QA fast-path
-(`ai_council.fast_path`) handles the resolution under hard caps:
-`max_members ∈ {1, 2}`, `max_rounds: 1` (LOCKED — Iron Law of the
-fast-path; the loader rejects any other value), `max_tokens: 2500`
-combined input + output budget, `max_cost_usd: 0.05` per resolution.
-No advisors, no peer-review, no consensus scoring run on this path.
-
-`high_impact` and `user_required` cannot reach the fast-path at all —
-the impact-class Iron Law above takes precedence.
-
-Worked example — opt the Anthropic and OpenAI members in, leave the
-others off, and switch the `low_impact` class to `council`:
-
-```yaml
-# In the resolved .ai-council.yml — keys are top-level (no `ai_council:` wrapper).
-members:
-  anthropic:
-    enabled: true
-    model: claude-sonnet-4-5
-    api_key_ref: file:anthropic.key
-    participate_low_impact: true   # eligible for fast-path
-  openai:
-    enabled: true
-    model: gpt-4o
-    api_key_ref: file:openai.key
-    participate_low_impact: true   # eligible for fast-path
-  gemini:
-    enabled: false                  # disabled — opt-in ignored even if set
-
-fast_path:
-  max_members: 2          # 1 or 2 only
-  max_rounds: 1           # LOCKED
-  max_tokens: 2500
-  max_cost_usd: 0.05
-
-decision_resolution:
-  classes:
-    low_impact:
-      mode: council          # ← flip from default `agent`
-      confidence_threshold: 0.6
-```
-
-Validation behaviour:
-
-- `participate_low_impact: true` on a member with `enabled: false`,
-  or with the global council disabled, parses but is treated as
-  `false` with a one-line loader warning — never silently runs.
-- `fast_path.max_rounds != 1` → `CouncilConfigError` at load time.
-- `fast_path.max_members ∉ {1, 2}` → `CouncilConfigError`.
-- `low_impact.mode: council` with zero opted-in enabled members →
-  the resolver falls back to `agent` (or escalates to user when the
-  confidence gate trips), with the marker
-  `> Low-impact council unavailable (no opted-in members) — escalating to user`.
-
-Transparency markers on every fast-path attempt:
-
-- **Resolved** — `> Resolved via low-impact council (<member>): <answer>`
-- **Split** — `> Low-impact council split — escalating to user (<m1>: X / <m2>: Y):`
-- **Aborted** — `> Low-impact council aborted (token cap) — escalating to user:`
-
-The marker is mandatory; the agent never silently substitutes a
-fast-path verdict for its own answer. See
-[`ai-council § Lightweight-QA fast-path`](../../.agent-src.uncondensed/skills/ai-council/SKILL.md#lightweight-qa-fast-path-phase-11)
-for the orchestration contract and session-artefact format.
-
-### Solo-member dispatch (step-9 P8/P9 · U1 · U2 · U3)
-
-Three new top-level settings cooperate to make low-impact decisions
-optionally cheap by routing them to a single member instead of the
-full council. Defaults preserve the prior shape — no behaviour
-changes unless every knob is set explicitly.
-
-| Key | Type | Default | Constraint |
-|---|---|---|---|
-| `defaults.member_mode` | `cli` \| `api` | `cli` | Per-member fallback when a member doesn't set `mode`. `manual` is rejected here (manual transport is full-council only). |
-| `routing.solo_member_fallback_chain` | `list[str]` | `[]` | Ordered, unique provider names. Each entry must exist in the `members` block. Empty disables solo dispatch. |
-| `routing.auth_check_timeout_seconds` | `int` | `3` | Range `[1, 30]`. Bounds the lazy auth probe per chain member. |
-| `low_impact.dispatch` | `full` \| `single` | `full` | `single` requires at least one enabled member in the fallback chain — otherwise rejected at load. |
-| `low_impact.shadow_sample_rate` | `float` | `0.1` | Range `[0.0, 1.0]`. Phase 10 shadow-mode sampling probability. |
-| `low_impact.solo_confidence_floor` | `float` | `0.7` | Range `[0.0, 1.0]`. Phase 13 confidence-gate threshold. Solo responses scoring below this floor — or matching split / refusal patterns — auto-escalate to the full council. |
-
-**Iron Law (LOCKED).** `decision_resolution.classes.high_impact.dispatch`
-and `decision_resolution.classes.user_required.dispatch` are rejected
-at load time — high-impact and user-required decisions always run the
-full council, with no opt-out. Top-level `high_impact: { dispatch: … }`,
-`high_impact: { solo_confidence_floor: … }`, `user_required: { dispatch: … }`,
-and `user_required: { solo_confidence_floor: … }` are all rejected the
-same way so a mistaken surface choice cannot bypass the lock — these
-classes never run solo, so a solo-specific knob there is incoherent.
-
-```yaml
-defaults:
-  mode: api
-  member_mode: cli       # use CLI binaries by default for per-member calls
-
-routing:
-  solo_member_fallback_chain: [anthropic, openai]   # try anthropic first
-  auth_check_timeout_seconds: 3
-
-low_impact:
-  dispatch: single             # route low_impact via solo dispatch
-  shadow_sample_rate: 0.1      # 10% shadow to full council for SLO tracking
-  solo_confidence_floor: 0.7   # auto-escalate if confidence < 0.7
-```
-
-### Confidence gate — auto-escalation on uncertain solo runs
-
-When `low_impact.dispatch: single` is enabled, every solo response is
-scored before the verdict is returned. Four escalation reasons can
-trigger an automatic fallback to the full council, in priority order:
-
-| Reason | Trigger | Source |
-|---|---|---|
-| `refusal` | Empty response or refusal markers (`I cannot decide`, `weiß ich nicht`, …). | `confidence_gate.is_refusal` |
-| `split` | Two competing verdicts without a pick (`Option A … Option B`, `Verdict: ship / Verdict: hold`, `Variante 1 / Variante 2`). | `confidence_gate.is_split_response` |
-| `short_response` | Response shorter than ~20 chars — treated as low-signal. | `confidence_gate.extract_confidence` length floor |
-| `low_confidence` | Explicit `Confidence: 0.X` marker below the floor, or hedge-word density (`maybe`, `perhaps`, `not sure`, `vielleicht`) pulling the implicit score below the floor. | `confidence_gate.extract_confidence` |
-
-Escalations are recorded in the shadow-mode log alongside the
-disagreement signal — see the `escalated` and `escalation_reason`
-fields in the `shadow.jsonl` row contract. The shadow SLO banner
-appends a separate auto-escalation rate so a quiet uptick in solo
-uncertainty cannot hide behind a flat disagreement rate.
-
-The escalation path uses zero extra LLM calls — heuristics run on the
-solo response text in process. The fallback `run_full()` only fires
-when the gate flags the response.
-
-### Low-impact corpus build pipeline (step-10)
-
-[`agents/decisions/low-impact-decisions.md`](../../agents/decisions/low-impact-decisions.md)
-remains the **human-editable source of truth** — Validated, Probation,
-and Anti-Example phrases stay in Markdown so PR-reviewers diff prose,
-not YAML. A build step compiles it into a generated YAML lockfile
-[`agents/decisions/low-impact-decisions.lock.yaml`](../../agents/decisions/low-impact-decisions.lock.yaml)
-that is the **runtime source of truth**: the necessity classifier and
-the solo-dispatch fuzzy matcher load phrases from the lockfile, with
-Markdown parsing reserved as fallback.
-
-| Component | File | Role |
-|---|---|---|
-| Source | `agents/decisions/low-impact-decisions.md` | Hand-edited Markdown. Strict parser (step-9 P4) catches drift. |
-| Build tool | `scripts/ai_council/compile_corpus.py` | `parse_corpus_strict()` → schema-v1 YAML. Deterministic output. |
-| Lockfile | `agents/decisions/low-impact-decisions.lock.yaml` | Generated, **committed**. Schema `{schema_version: 1, provenance: {…}, validated, probation, anti_examples}`. |
-| Runtime loader | `low_impact_corpus.load_corpus_lock()` + lenient `load_*` shims | YAML preferred; Markdown fallback when the lockfile is missing or schema-mismatched. |
-| CI gate | `task check-corpus` (used by `task consistency`) | Fails on drift between source and lockfile. |
-
-The committed lockfile is the contract: a stale lockfile fails CI the
-same way `dist/agent-src/` drift does. The Markdown parser stays in the
-repo as a build-time dependency, not a runtime dependency — a parser
-regression breaks `task consistency`, never the live council.
-
-`scripts/ai_council/learn_low_impact_preview.py` deliberately stays on
-`parse_corpus_strict` (Markdown). It runs **before** `task sync`
-rebuilds the lockfile, so it must read whatever the user just edited.
-
-## `model_downgrade` — auto-tiering + the A1↔A3 cache coupling
-
-Since the A3 slice of `road-to-api-cost-optimization` (2026-07-20):
-
-```yaml
-model_downgrade:
-  enabled: true        # default; false disables the size-fit gate entirely
-  auto_apply: true     # DEFAULT since A3 — auto-downgrade is opt-OUT
-  model_tier_override: # per-run escape hatch: member -> pinned model id
-    anthropic: claude-sonnet-4-5
-```
-
-- Small / low-complexity artefacts (per `necessity.classify_size_fit`,
-  character-based) auto-downgrade one ladder rung; the `debate` lens never
-  downgrades.
-- **Cache coupling:** a downgrade is applied only when the model saving beats
-  the forfeited model-scoped prompt-cache reads
-  (`pricing.downgrade_coupling`: `downgrade_savings > lost_cache_savings`,
-  expected reads = rounds − 1). One-shot paths (the low-impact fast-path)
-  have no reads to lose and downgrade to the CHEAPEST ladder rung outright.
-- `model_tier_override` pins a member to a model for the run — classifier and
-  coupling both skipped. Set it per artefact when a specific tier is needed.
-- Requires `model_ladder` on the member (smallest → largest, must include the
-  active `model`).
-
-## `api_key_ref` forms
-
-Exactly two forms. Raw keys in the yml are a hard validation error.
-
-- `file:<path>` — read from a 0600 file. Relative paths resolve under
-  `~/.event4u/agent-config/`; absolute paths are honored as
-  written. The legacy `~/.config/agent-config/` location is still read
-  as a fallback by `scripts/_lib/user_global_paths.py`.
-- `env:<VAR>` — read from the named environment variable at load time.
-  Missing or empty env var is a `KeyGateError`.
-
-## Precedence
-
-Resolution order for every member-level setting (mode, model, key):
-
-```
-invocation flag  >  per-member field  >  defaults block  >  built-in fallback
-```
-
-Same shape applies to round counts (`--rounds N` > `defaults.min_rounds`,
-plus the `deep_min_rounds` floor when `--depth deep` or a consuming
-artefact's `council_depth: deep` frontmatter fires).
-
-## Normative behaviour — migrated verbatim
-
-These rules are part of the contract; the consuming YAML reproduces them
-as comments and the loader enforces them.
-
-- **Iron Law of Neutrality.** Council members never see the host agent's
-  reasoning — only the artefact + a neutral system prompt. Phase 6 Step 3a
-  preserves advisor persona labels in peer-review but strips provider
-  identity.
-- **Autonomy carve-out — no silent spend.** The `/council` command always
-  asks before invoking, even under autonomy: on. Cost is real and paid.
-- **Manual vs API vs CLI transport.** Three first-class modes on the
-  `mode:` axis:
-  - `manual` = copy & paste — the human transports prompt + reply between
-    the agent and an external chat surface. Free, no key.
-  - `api` = direct SDK call against a stored key (per-token billing).
-  - `cli` = shell out to a locally-installed provider CLI under the
-    user's subscription auth — spend is covered by the flat-rate
-    subscription, not per-token. `billable=False` so the `cost_budget`
-    USD ceiling does not apply; subscription quotas are guarded by
-    `cli_call_budget.max_calls_per_day` instead.
-
-  Precedence: per-invocation flag > per-member override > defaults > `api`.
-- **Tokens never stored in this yml.** Keys live in 0600 files
-  (`~/.event4u/agent-config/<provider>.key`, installed via
-  `bash scripts/install_<provider>_key.sh` for providers that ship an
-  installer) or in env vars. Validation rejects any literal-looking key.
-- **`max_output_tokens: 0` widening.** Internally widened to the safe
-  provider ceiling (16384) because Anthropic rejects `max_tokens=0`. The
-  CLI `--max-tokens` flag overrides this on a single invocation; the
-  cost estimator uses the same value as its worst-case ceiling.
-- **`deep_min_rounds` is monotonic.** Effective rounds =
-  `max(deep_min_rounds, min_rounds)`. Lowering `deep_min_rounds` below
-  `min_rounds` has no effect. Standard tasks keep `min_rounds`; cost
-  rises only when an artefact opts in via `council_depth: deep` in
-  frontmatter or `--depth deep` on the CLI.
-- **Session retention.** `agents/runtime/council/sessions/` audit folders older
-  than `defaults.session_retention_days` are pruned automatically on the
-  next `save()`. `0` disables pruning — disk grows unbounded.
-- **`cost_budget` semantics.** The orchestrator pauses before any member
-  whose projected spend would breach a cap and asks the user to continue.
-  Each `0` value disables that single cap; other caps still apply.
-  Prices come from [`agents/runtime/.agent-prices.md`](../../agents/runtime/.agent-prices.md)
-  (gitignored, refreshed weekly by `./scripts-run src/scripts/update_prices`;
-  bootstrapped from `scripts/ai_council/_default_prices.py` on first run).
-
-## Validation rules
-
-A loader call (`scripts/ai_council/config.py:load_council_config()`)
-must reject the file with a clear `KeyGateError` (or equivalent typed
-error) when any of these hold:
-
-1. Required top-level key missing (`enabled`, `defaults`, `cost_budget`,
-   `members`).
-2. `members` block has no provider with `enabled: true`.
-3. Unknown provider key under `members` or `advisors`.
-4. `api_key_ref` missing for an enabled member, or in an unknown form
-   (not `file:` and not `env:`), or pointing at a non-existent file /
-   missing env var.
-5. A value under `api_key_ref` looks like a raw secret (starts with
-   `sk-`, `pk-`, `xai-`, or matches a provider's key prefix).
-6. `defaults.deep_min_rounds < defaults.min_rounds` is allowed (clamped
-   by the monotonic rule at runtime) but logged as a warning.
-7. `defaults.mode` not in `{"api", "manual", "cli"}`; per-member `mode`
-   override same constraint.
-8. `members.<provider>.binary` set when the member's effective mode is
-   not `cli` — explicit error to keep config clutter-free.
-9. `cli_call_budget` is not a mapping, or
-   `cli_call_budget.max_calls_per_day.<key>` is an unknown provider, or
-   any value is a negative integer / non-integer.
-10. `advisors.<key>.member` missing, unknown, or pointing at a
-    `members.<provider>` that does not exist or has `enabled: false`
-    (when the advisor itself is `enabled: true`). Silent skips are not
-    allowed — a typo never costs the user money on an unintended call
-    plan.
-11. `advisors.<key>.model` is set but not a string.
-12. `necessity_classifier` is not a mapping, or `enabled` is not a bool,
-    or `mode` is not one of `{"off", "educate", "block"}`.
-13. `lens_overrides.necessity_classifier_mode` is not a mapping, or any
-    value is not one of `{"off", "educate", "block"}`. Unknown lens keys
-    are accepted (forward-compatible) but never silently rewrite the
-    global default.
-
-## Migration footprint (Phase 0)
-
-> Historical record of the Step-2 consolidation. **The project-local file
-> described below is no longer read** — ADR-104 (superseding ADR-093) moved
-> the council config to the user-global location documented at the top of
-> this contract. A `.ai-council.yml` under any project `agents/` tree is
-> ignored. Read this section for provenance only, not for placement.
-
-- `.agent-settings.yml` → 14-key inventory under `ai_council:` removed
-  after a one-line breadcrumb comment is in place pointing at this
-  contract.
-- `.agent-settings.template.yml` → same removal.
-- New file `agents/settings/.ai-council.yml` checked in with two enabled <!-- council-config-allowed -->
-  providers (anthropic + openai) and three disabled
-  (gemini + xai + perplexity). Models pre-filled from the Phase 0
-  default set; comments mirror this contract. *(This project-tracked file
-  was later removed; per ADR-104 the config is user-global only.)*