alphacouncil-agent 1.0.4 → 1.0.13

package/CHANGELOG.md

@@ -2,6 +2,288 @@
 
 Notable changes per release. Dates are UTC.
 
+## [1.0.13] — 2026-07-30
+
+### Fixed
+
+- **Screen rules pair both series by fiscal period end, never by array position.** Every
+  two-series elimination rule (`roe_10y`, `gross_margin`, `interest_cover`, `fcf_5y`,
+  `ocf_over_ni`, `net_margin`) used to slice the last N entries of each series independently
+  and divide position-by-position. A gap in one series — a tag the filer stopped using, a
+  year reported under an out-of-catalog alias — shifted every later year onto the wrong
+  counterpart while the provenance block still showed a clean range: this year's EBIT divided
+  by a two-year-old interest figure read as a confident 2.5x cover, and an equity series
+  missing one middle year shifted a decade of ROE by one year. Rules now drop a year present
+  on only one side, report the pair count as their coverage, and `interest_cover` is
+  `skipped` when the latest EBIT year has no same-period interest figure — a stale
+  denominator is a gap, not a cover ratio. Four regression tests pin the misalignment
+  scenarios.
+- **The SEC universe cache in peer matching expires after six hours** instead of living for
+  the whole MCP process. A resident server that never re-read the ticker file silently lost
+  every new listing and rename from `industry_peers`, with no gap recorded anywhere.
+
+### Changed
+
+- **The three READMEs, CLAUDE.md and INSTALL.md now agree on the counts**: 27 selectable
+  lenses (the bench table had listed 26 — Bogle was missing), 31 keyless MCP tools, 54
+  solo-test proxy tools. INSTALL.md no longer pins its examples to 1.0.0.
+- **README leads with the recorded demo and a 30-second zero-cost first run** (`/alpha AAPL
+  news`), links a complete real full-council report
+  (`docs/examples/final_report.SOX.zh.md`), states the Codex CLI prerequisite for headless
+  paths next to the install commands instead of below the fold, and compresses the
+  governance status into one honest sentence linking the release contract.
+- **SECURITY.md discloses what was already true**: `preflight_permissions` reads host
+  configuration files read-only to detect silent web-search downgrades, workers run in a
+  read-only sandbox, and the supported-versions line no longer claims the project is
+  pre-1.0.
+
+## [1.0.12] — 2026-07-30
+
+### Changed
+
+- **The depth tier is asked at the selection gate instead of typed as an argument, and the menu
+  publishes the predicted time.** `begin_council_selection` now returns `pace_options`: one row
+  per tier carrying `expected_minutes`, `hard_ceiling_minutes`, the per-seat evidence budget and
+  the per-round debate budget. Both numbers are published on purpose — a ceiling shown on its own
+  reads as the estimate, and then every `fast` run looks like it takes fifteen minutes when the
+  serial worst case is twelve.
+
+  ```
+  本次分析要跑多深？（默认 2）
+    1. 快速   预计 ~12 分钟（上限 15）  每证据席 3.5 分钟，每轮辩论每侧 90 秒
+    2. 标准   预计 ~20 分钟（上限 30）  每证据席 6 分钟，每轮辩论每侧 150 秒   ← 默认
+    3. 深入   预计 ~44 分钟（上限 60）  每证据席 12 分钟，每轮辩论每侧 360 秒
+  ```
+
+  The tier is the gate's second decision, so it is taken in the same interaction as the seat
+  catalog and **binds into the receipt**. An execution call may repeat the confirmed tier but
+  never change it: a user who approved fifteen minutes cannot end up running an hour, and the
+  reverse cannot happen either. `status.json` records which tier produced the run.
+
+  A speed named in the request (`/alpha NOW slow`) is now a **prefill**, exactly like a named
+  master: it highlights the row, the menu is still shown, the answer is still taken. No answer
+  means `normal`. Quick returns an empty menu and rejects the field.
+
+### Fixed
+
+- **A tier confirmed at the gate was lost at consumption.** `council_pace` reached the receipt
+  but not the consumed selection, so a run approved as `slow` silently fell back to the
+  30-minute default with nothing in the record showing the switch — and the execution-time
+  mismatch guard could not fire because it had nothing to compare against.
+
+## [1.0.11] — 2026-07-30
+
+### Fixed
+
+- **A depth tier was a timeout with no plan behind it, so `fast` bought unfinished work rather
+  than faster work.** 1.0.10 shipped three tiers that all sent the identical prompt: `fast` asked
+  every worker for exactly the same output with 40% less time, which does not produce a faster
+  good packet — it produces one the worker could not finish, arriving `degraded` or not at all.
+  There was no pace awareness anywhere in the prompt layer.
+
+  A tier now shapes the worker's output as well as capping its clock. Because an LLM call's wall
+  clock is dominated by the tokens it generates, running faster without losing information means
+  asking for the same information in less prose:
+
+  - `fast` — at most six arguments, one to two sentences each, cite a source ID instead of
+    re-quoting the evidence, no opponent recap, no methodology preamble. Every figure, every
+    scoped source ID and every required report section stays mandatory; price levels and
+    invalidation conditions may not be compressed, because they are the only actionable part of
+    the report. Dropping an argument is acceptable; dropping a source ID or filling a number from
+    memory never is. A short packet that names its gap beats a complete-looking one built from
+    memory.
+  - `slow` — write the derivation out step by step with its basis, assumptions and sensitivity;
+    handle the opponent's arguments one at a time; state your own falsification conditions.
+    Longer is not better, so repetition still gets cut.
+  - `normal` — adds nothing at all, so its prompts stay byte-identical to the reviewed golden.
+  - Quick keeps its own existing shaping and receives no tier, so no prompt ever carries two
+    different length budgets.
+
+  The shaping reaches the evidence seats, both debaters, the PM and the method voice workers, in
+  the run's language.
+
+## [1.0.10] — 2026-07-30
+
+### Added
+
+- **Three full-council depth tiers, selected with `council_pace`: `fast` 15 minutes, `normal`
+  (default) 30, `slow` 60.** All three are the same `full_v2` contract — eight evidence seats,
+  every selected method, three debate rounds, the PM — so a tier changes how long each seat may
+  think, never which seats run. Quick rejects the field: it is a smaller contract, not a slower
+  one. The tier is recorded in `status.json`, because two runs of one symbol at different paces
+  are not the same analysis.
+
+  A tier moves every per-stage cap together with the total, which is the part that actually buys
+  depth. Raising only the total would leave a 60-minute run finishing in twenty minutes with
+  forty idle, because what bounds each worker is its per-stage cap; lowering only the total would
+  starve the later stages and terminate `incomplete` with the debate missing.
+
+  | `council_pace` | total | evidence / seat | method / seat | debate / round | PM |
+  | --- | --- | --- | --- | --- | --- |
+  | `fast` | 15 min | 3.5 min | 1 min | 90 s | 2 min |
+  | `normal` | 30 min | 6 min | 2 min | 150 s | 3 min |
+  | `slow` | 60 min | 12 min | 4 min | 6 min | 8 min |
+
+  `/alpha <TICKER> fast` and `/alpha <TICKER> slow` reach it from the command surface. A test
+  pins the property that makes a tier coherent: every tier's stages fit inside its own budget
+  with headroom, and no stage cap is allowed to stay flat as the tier widens.
+
+### Changed
+
+- **The full-council ceiling is now the selected tier's total rather than a single 30-minute
+  maximum.** A caller or environment may still only lower the applicable budget; a
+  `total_timeout_ms` above the tier's total is rejected and names the tier that would allow it.
+  `ALPHACOUNCIL_FULL_TOTAL_MS` becomes an operator cap that only ever lowers a tier, instead of
+  doubling as the default budget — as the default it silently held the 60-minute tier to 30.
+
+## [1.0.9] — 2026-07-30
+
+Seven fixes found by auditing one real 148-minute visible NOW council against its own
+artifacts. Every one of them was quiet: the run produced a complete report each time.
+
+### Fixed
+
+- **A hashed hard veto made two seats guess, in writing, which condition had vetoed them.**
+  Condition ids are hashed before a policy runs so the decision layer cannot recognise the seat.
+  The voice layer reversed that for scoring conditions but not for vetoes, tool output ids or
+  `common_projection.veto_ids`, so a seat published `anon_e41f54d07b56b0ff5` where it meant
+  `master_marks.euphoria`. Both vetoed seats on NOW speculated their veto came from a
+  424.67% dilution figure that was a stock-split artefact; the actual veto was a market-level
+  reading. Past the freeze the seat is named in the report and in its own worker prompt, so the
+  hash protected nothing. Also fixes a latent mis-mapping: the positional fallback assumed the
+  executor returns hits, misses and uncomputable rules in declaration order, and would have
+  published two condition names swapped for any seat with a mixed split.
+- **`plan_visible_run` returned 311,007 characters and the host rejected the whole plan.**
+  Prompts now always land in `<run>/prompts/` with `prompt_file` on every agent spec, and
+  `prompts_inline: false` says the bodies were left out on purpose. What drives the size is the
+  grounding each prompt embeds, not the seat count.
+- **A portfolio-manager packet with no `report_markdown` was accepted, then failed the report
+  gate with 21 missing sections.** The gate could only run after assembly, so the whole PM turn
+  was spent first. Submission now rejects a body that cannot pass, before the idempotency lock,
+  and names each owed section with the heading to use. System-appended sections are never asked
+  of an author. The revision path stays for defects only the assembled report can see.
+- **One absent XBRL alias killed three facts on a company whose debt is on the face of its
+  balance sheet.** ServiceNow's FY2020 and FY2025 balance sheets carry no straight debt tag: the
+  only debt instant either year is `ConvertibleLongTermNotesPayable`. Total debt therefore read
+  as unknown, and because unknown debt is correctly refused rather than treated as zero,
+  leverage, downside asset value and incremental return on capital all died — which is why a
+  seat requiring incremental return on capital abstained. The convertible aliases are appended
+  last, where an earlier alias still wins a year outright, so coverage is strictly additive: a
+  filer that resolves its debt today resolves to the identical number. On real ServiceNow
+  Company Facts this turns four recorded gaps into one.
+- **A rate-limited filing document was lost where a rate-limited JSON call was retried.** Every
+  SEC JSON endpoint backed off on 429/503; `fetchFilingDocument` threw on the first one, so the
+  documents carrying the actual disclosure were the easiest evidence in a run to lose, on the
+  path SEC throttles hardest.
+
+### Changed
+
+- **A seat's statement reaches the handoff instead of its metadata.** The per-seat line led with
+  the first 520 characters of background and put the frozen-record tag in the same sentence, so
+  the part always cut was the seat's conclusion — seven seats that all spoke read as seven seats
+  that had not. Each seat now leads with the reading that decided it and the action it implies,
+  quotes its statement at a budget that survives a paragraph, and carries provenance on its own
+  line.
+- **A frozen abstention no longer spends a model worker to restate itself.** A seat whose gate
+  never opened has no reading to explain, and its deterministic statement now names the
+  condition that closed the gate and states that an abstention is not a bearish vote — all an
+  `out_of_scope` seat is asked to say. Four such seats took most of the method phase on NOW.
+  `ALPHACOUNCIL_VOICE_ABSTAINING_SEATS=1` restores a worker for every seat.
+- `insider_sec` carries an explicit EDGAR retrieval order, a same-URL backoff rule, and a
+  mandatory degradation rule. On NOW it tried eight different URLs in a row, was rate-limited on
+  all of them, and read no original filing.
+
+## [1.0.8] — 2026-07-30
+
+### Changed
+
+- **The catalog stops repeating a review-status warning next to every seat.** The owner
+  reviewed and accepted the method attributions, so `operator_label` is now just the method's
+  name and the selection identity says what a seat IS — "a method model, not the person's own
+  words" — instead of "project-derived and not human reviewed" twenty-seven times. The
+  impersonation guard stays; the machine-verified `admission_level` and every fail-closed
+  release gate are unchanged. All 27 solo-test packs regenerated; machine simulations re-run
+  against the new pack hashes.
+
+## [1.0.7] — 2026-07-29
+
+### Fixed
+
+- **A historical cutoff silently discarded the market yardstick and a fund's entire evidence
+  base.** Two sibling blocks in grounding skipped their fetch when the cutoff was historical and
+  wrote nothing to `unavailable`: the US-subject market-valuation block (so Marks and Damodaran
+  declined with `unmet: index.aggregate_earnings_yield` and the reader was never told why) and
+  the fund/index holdings block (worse — holdings, look-through aggregates and basket news ARE a
+  fund's evidence, so a historical fund run kept only a price). Both now record the gap the way
+  their sibling blocks always did. Three network-free regression tests pin the contract,
+  including one that walks the market earnings yield through the typed-fact lineage gate to a
+  `ready` Damodaran seat.
+
+### Clarified
+
+- The LITE council run that motivated 1.0.5 was executed by a cached 1.0.2 server, not by
+  current code: on HEAD, `index.aggregate_earnings_yield` resolves from the WSJ keyless
+  trailing-P/E source (verified live: 0.0397, dated, https lineage) and Marks, Damodaran and
+  Asness are all `ready` on a US equity. The seats were never method-blocked — the host was
+  running last week's build. If a seat declines on a fact the catalog says it should have,
+  check the plugin cache version before the method.
+
+## [1.0.6] — 2026-07-29
+
+First release on which `npm run check` and the full test suite pass together: 995/995.
+
+### Fixed
+
+- **The formula-review gate demanded exactly 156 roles after the bench grew to 162.** The
+  literal (26 seats × 2 tools × 3 roles) survived the twenty-seventh seat, so
+  `review-persona-v3-solo-formulas --check` failed a review tree whose own output line printed
+  `roles=162/162`. The gate now derives the count from the planned-tool inventory.
+
+### Repaired (local staging, not shipped in the package)
+
+- The private PersonaPack staging tree had been left behind by the v1.0.x sessions, which
+  worked in a scratch worktree and never synced back: `staging-index.json` was missing
+  `master_bogle` (39 test failures from one integrity error), and all 27 seats' formula
+  prototypes still carried pre-rename tool ids. Synced from the authoring worktree; the
+  packaged `knowledge/solo-test` tree was already correct and is unchanged.
+
+## [1.0.5] — 2026-07-29
+
+Five defects found by running one full visible council end to end on a US operating company.
+Every one of them was silent: the run produced a report and none of these said anything was wrong.
+
+### Fixed
+
+- **A plan response could exceed the host's tool-result limit.** `plan_visible_run` echoed the
+  entire grounding object, whose macro history and typed-fact lineage are unbounded — 2.33 MB of a
+  2.54 MB payload on a single US equity — so the host truncated the plan to a scratch file and the
+  agent could not read the seat specs it had just asked for. Both fields are already in every seat
+  prompt and in `evidence.json`; the response now carries the rest of the grounding plus a pointer
+  and an entry count. Nothing else about the shape changed.
+- **An English source title failed a Chinese packet's language gate.** `sources[].title` counted
+  toward the reader-language ratio, so packets whose every authored sentence was Chinese were
+  rejected at ratio 0.49. The only way to pass was to translate the citation, which falsifies the
+  source. `title` now joins `url` as machine text.
+- **A portfolio-manager report that failed the structure gate could not be repaired.** The
+  idempotency lock was taken before the gate ran, so a thin report left the run permanently at
+  `needs_revision`: the corrected submission came back as a conflicting replay and there was no
+  other way in. A PM whose `report_quality` is not `passed` is now revisable; one that passed stays
+  frozen.
+- **A failed verification down-weighted nothing when the seat was an analyst.** The contract
+  promises that a `contradicted` verdict reduces the weight of the seat that made the claim, but
+  the seat enumeration covered only debate and master seats. Verdicts against evidence roles were
+  recorded and then ignored, and the tool still answered with `verification_factor: 1`.
+- **A missing market yardstick looked like an abstention.** When the broad-market valuation fetch
+  succeeded but yielded no market-level fact, it was dropped without a trace; downstream, Marks and
+  Damodaran declined with `unmet: index.aggregate_earnings_yield` and the report never said why the
+  fact was absent. An unexplained abstention reads as a verdict. It is now recorded as a data gap.
+
+### Changed
+
+- `MASTER_SELECTION_INTENT_MISMATCH` now returns the expected and submitted intent hashes, the
+  fields the receipt binds, and the remedy. The receipt binds the prompt verbatim by design, but
+  the error gave the caller no way to tell a retyped prompt from a wrong symbol.
+
 ## [1.0.4] — 2026-07-29
 
 ### Fixed

package/CLAUDE.md

@@ -15,7 +15,7 @@ The plugin turns `@alphacouncil-agent <ticker/request>` into one of two explicit
   bounded parse-only repair, persist the failure package, skip method/debate/PM model calls,
   and terminate `incomplete` before downstream synthesis.
 - `quick_v1` runs only when explicitly requested and only through plugin-managed headless
-  `analyze_symbol`: display all 26 methods, confirm 1-4, run four fixed evidence roles and the
+  `analyze_symbol`: display all 27 methods, confirm 1-4, run four fixed evidence roles and the
   selected methods in parallel waves, one parallel Bull/Bear statement round, then a short
   PM inside a hard ten-minute ceiling.
 
@@ -25,13 +25,14 @@ non-investment test output.
 
 ## Current Build Profile
 
-The declared package/plugin version is `1.0.0`, published to npm as the default install.
+The declared package/plugin version is `1.0.12`, published to npm as the default install.
 The packaged tree contains 27 physical v3 packs and 54 executable tools.
 Every seat carries the `operator_lens` admission level: `method_model` = 0,
 human source approvals = 0, human formula approvals = 0, human approval signatures = 0.
 Human review of the authored formulas and the live four-host end-to-end run are the
 outstanding work, so the production assembly path stays fail-closed until both are done.
-See `docs/releases/v1.0.0.md` and `docs/report-contract.md`.
+See `docs/releases/v1.0.0.md`, `CHANGELOG.md` for everything since, and
+`docs/report-contract.md`.
 
 ## Agent-Skills Governance
 
@@ -58,10 +59,36 @@ No research, run directory or worker may start before that receipt exists. Data-
 
 ## Full v2 Runtime Contract
 
-- Plugin-managed headless `analyze_symbol(council_mode="full")` has a hard 1800000 ms
-  queue-to-terminal-persistence ceiling. Queueing, grounding, bounded repair, all workers,
-  synthesis and artifact persistence share that clock. A caller or environment may lower
-  the limit, never raise it.
+- Plugin-managed headless `analyze_symbol(council_mode="full")` runs at one of three depth
+  tiers, selected by `council_pace`: `fast` = 900000 ms, `normal` (default) = 1800000 ms,
+  `slow` = 3600000 ms, queue-to-terminal-persistence. Queueing, grounding, bounded repair, all
+  workers, synthesis and artifact persistence share that clock. A caller or environment may
+  lower the selected tier's budget, never raise it; `total_timeout_ms` above the tier's total is
+  rejected and names the tier that would allow it.
+- A tier sets the total AND every per-stage cap together, because the per-stage caps are what
+  bound each worker. `slow` gives each evidence seat 12 minutes instead of 6 and each debate
+  round 6 minutes per side instead of 150 seconds; `fast` gives 3.5 minutes and 90 seconds. That
+  is where the depth difference lives — raising `total_timeout_ms` alone buys idle time, and
+  lowering it alone starves the later stages into `incomplete`. Every tier's stages are proven
+  to fit inside its own budget with headroom.
+- A tier also shapes the worker's OUTPUT, because a cap alone is a timeout and a timeout is not
+  a plan: the same prompt with a shorter fuse buys a packet the worker could not finish, not a
+  faster good one. For an LLM call the wall clock is dominated by generated tokens, so `fast`
+  asks for the same information in less prose — claims, figures, scoped source IDs, required
+  report sections and the decision are never what gets cut; restatement is. `slow` buys room to
+  write a derivation out in full. `normal` adds nothing, so its prompts stay byte-identical to
+  the reviewed golden. Quick keeps its own shaping and receives no tier.
+- `council_pace` changes depth, never the contract: all three tiers are `full_v2` with eight
+  evidence seats, every selected method, three debate rounds and the PM. Quick rejects the field
+  — it is a smaller contract, not a slower one. The tier is recorded in `status.json`.
+- The tier is ASKED at the selection gate, not typed as an argument.
+  `begin_council_selection` returns `pace_options`, one row per tier carrying both
+  `expected_minutes` and `hard_ceiling_minutes` plus what the extra time buys; a ceiling
+  published alone reads as the estimate. The answer goes to `confirm_master_selection` as
+  `council_pace` and binds into the receipt, so an execution call may repeat the confirmed tier
+  but never change it — a user who approved 15 minutes cannot end up running an hour. A speed
+  named in the request is a prefill exactly like a named master: it highlights the row, the menu
+  is still shown, the answer is still taken. No answer means `normal`.
 - Start the eight mandatory evidence workers in one parallel wave. A failed mandatory role
   after its single bounded parse-only repair closes the evidence barrier and terminates
   `incomplete`; never refill the result from memory.
@@ -78,8 +105,23 @@ No research, run directory or worker may start before that receipt exists. Data-
   artifact, not that external search/model/data services will let all seats succeed.
 - The plugin cannot enforce this deadline on `plan_visible_run` host subagents. Visible full
   runs retain the same evidence/report gates but must not be described as 30-minute bounded.
-  Run every returned post-evidence v3 explanation worker, including a frozen
-  `out_of_scope` seat, and record its `acknowledged_stance` before debate.
+  Run every returned post-evidence v3 explanation worker and record its `acknowledged_stance`
+  before debate. A seat frozen `out_of_scope` is returned as already settled and gets no
+  worker: its deterministic statement names the condition that closed the gate and states that
+  an abstention is not a bearish vote, which is the whole of what an out_of_scope seat is asked
+  to say, so a worker there buys prose rather than information. Set
+  `ALPHACOUNCIL_VOICE_ABSTAINING_SEATS=1` to give every seat a worker again. Every selected
+  seat still needs a readable statement in the report either way.
+- `plan_visible_run` always writes each planned prompt to `<run>/prompts/` and returns
+  `prompt_file` beside every agent. It also returns `prompts_inline`: false means the prompt
+  bodies were left out of the result because returning them together would exceed what a host
+  accepts, and the host must read them from `prompt_file`. What drives that size is the
+  grounding each prompt embeds, not the seat count.
+- `record_visible_decision(role: 'portfolio_manager')` rejects a packet whose
+  `report_markdown` does not carry every authored report-contract section, before the packet
+  takes the idempotency lock. The rejection lists the missing sections and the heading to use
+  for each. The master bench and instrument-structure sections are system-appended and are
+  never asked of an author.
 
 ## Quick v1 Fixed Contract
 
@@ -139,8 +181,8 @@ Optional analysts, on the `full` roster rather than the default:
 Quick evidence roles are the fixed four-seat subset listed above and always launch in one
 parallel wave.
 
-Master Bench: the complete generated catalog has 26 selectable lenses. Both modes display
-all 26. Full accepts any non-empty selection or `all`; quick accepts only 1-4. Selected
+Master Bench: the complete generated catalog has 27 selectable lenses. Both modes display
+all 27. Full accepts any non-empty selection or `all`; quick accepts only 1-4. Selected
 methods run between evidence and debate. In plugin-managed headless mode, each selected v3
 seat is a frozen deterministic stance plus its own isolated voice worker; this is a
 process-isolated worker, not a persistent sidebar agent and not the real person. Quick runs
@@ -148,8 +190,8 @@ its 1-4 seats in one parallel wave. Full/deep
 verifiers are `source_fidelity`, `rederivation`, and `refuter`; quick does not run this
 adversarial fan-out. See `skills/alphacouncil-agent/SKILL.md` and `docs/personas.md`.
 
-Do not call the 26 solo-test packs approved method models. The explicit solo-test loader
-exposes 26 provisional `operator_lens` packs and 52 executable derived-proxy tools; none is
+Do not call the 27 solo-test packs approved method models. The explicit solo-test loader
+exposes 27 provisional `operator_lens` packs and 54 executable derived-proxy tools; none is
 operational or `method_model`, and none has human source/formula approval or signature.
 
 Debate roles:

package/README.ja.md

@@ -35,9 +35,9 @@
 
 <div align="center">
 
-<img src="assets/run-example.png" alt="A real AlphaCouncil run: six master lenses reaching the same call for different reasons" width="100%" />
+<img src="assets/demo.gif" alt="AlphaCouncil のライブ実行:アナリスト評議会が調査・討論して評決に至る様子" width="100%" />
 
-<sub><i>実際の実行結果。6つのレンズはいずれも強気ではなく、相違は結論ではなく理由にあります。</i></sub>
+<sub><i>実際の実行の録画。静止画版:<a href="assets/run-example.png">6つのレンズが異なる理由で同じ結論へ</a> · <a href="docs/examples/final_report.SOX.zh.md">完全な実レポート</a>(SOX、full council、中国語)</i></sub>
 
 </div>
 
@@ -47,9 +47,9 @@ AlphaCouncil Agent は、**上場株式のリサーチ委員会**向けの Codex
 
 | | |
 |---|---|
-| 🏛️ **一人の意見ではなく、委員会** | フルは既定 8 根拠席（最大 11）、quick は固定 4 根拠席を並列実行。どちらも調査前に 26 メソッド席をすべて表示。 |
+| 🏛️ **一人の意見ではなく、委員会** | フルは既定 8 根拠席（最大 11）、quick は固定 4 根拠席を並列実行。どちらも調査前に 27 メソッド席をすべて表示。 |
 | 🐂🐻 **設計からして対立的** | フルは 3 ラウンドの強気/弱気クロス審問。quick は強気・弱気を 1 回だけ並列実行して短い PM に渡し、敵対的 verifier を実行したとは主張しません。 |
-| ⏱️ **フル headless にハード上限** | プラグイン管理の full は 8 アナリストを同時に開始し、各ラウンドの Bull/Bear も並列実行して、30 分以内に終端状態を保存。外部障害は明示的な `incomplete` となり、席を黙って省略しません。 |
+| ⏱️ **深さは 15 / 30 / 60 分から選択** | 実行前に尋ね、各段階の想定所要時間とハード上限を併記します。速度キーワードの入力は不要です。3 段階はいずれも同一のフル契約（8 アナリスト・3 ラウンド討論・PM）で、変わるのは各席が考えてよい時間です。同じプロンプトに短い導火線を付けても書き終わらない packet しか得られないため、段階は出力の形も調整します。プラグイン管理の full は 8 アナリストを同時に開始し、各ラウンドの Bull/Bear も並列実行して、選択した段階内に終端状態を保存。外部障害は明示的な `incomplete` となり、席を黙って省略しません。 |
 | 🔍 **監査可能、幻覚なし** | すべての主張が source ID に紐づく。欠落データは「データ欠落」セクションに明示し、決して隠さない。 |
 | ⏱️ **マルチ期間の判定** | 買い/中立/売りに加え、1〜4週・3〜6か月・12か月の見通しを個別に提示。 |
 | 🔑 **データベンダー不要・APIキー不要** | 金融データ API・マーケットデータフィード・証券口座ログインは一切不要。アナリストはエージェント自身のウェブ検索(**Codex のウェブ検索** / **Claude Code の WebSearch + WebFetch**)で根拠をリアルタイムに収集 —— 課金は既存の Codex / Claude Code サブスクのみ。MIT ライセンス。 |
@@ -97,6 +97,18 @@ codex plugin marketplace add Zhao73/alphacouncil-agent
 /reload-plugins
 ```
 
+**まず 30 秒・コストゼロで動作確認** —— フル評議会を回す前に、データ層の疎通を確認します:
+
+```text
+/alpha AAPL news
+```
+
+これはキー不要のデータツールのみを呼び、サブエージェントを一切起動しません。日付付きの
+ニュースと開示が返ればインストール成功です。その後 `/alpha AAPL` でフル評議会をどうぞ。
+なお headless のフル/クイック経路には認証済みの **Codex CLI** が別途必要です
+(各アナリストワーカーは `codex exec` として動作)。Claude Code のみの場合は可視
+サブエージェント経路になります。詳細は [docs/INSTALL.md](docs/INSTALL.md)。
+
 ## 🚀 使い方
 
 エージェントにそのまま話しかけるだけ。@ でエージェントを呼び、ティッカーや質問を添えます:
@@ -133,7 +145,7 @@ codex plugin marketplace add Zhao73/alphacouncil-agent
 | 入力 | 実行内容 | モデル消費 |
 |---|---|---|
 | `/alpha <ticker>` | 全マスターを個別表示して full を実行；プラグイン管理 headless は ≤30分 | 選択した v3 席ごとに決定論的 stance + 独立 voice worker 1つ |
-| `/alpha <ticker> quick` | 全 26 席を表示し、1-4 席を確認（`all` 禁止）後、プラグイン管理の `quick_v1`（≤10分）を実行 | 選択数により変動 |
+| `/alpha <ticker> quick` | 全 27 席を表示し、1-4 席を確認（`all` 禁止）後、プラグイン管理の `quick_v1`（≤10分）を実行 | 選択数により変動 |
 | `/alpha <ticker> screen` | 機械的スクリーニングのみ | **なし** |
 | `/alpha <ticker> options` | IV ターム構造、スキュー、建玉分布 | **なし** |
 | `/alpha <ticker> news` | 日付付きの提出書類とニュース | **なし** |
@@ -145,11 +157,25 @@ codex plugin marketplace add Zhao73/alphacouncil-agent
 上場銘柄なら何でも：`/alpha AAPL` · `/alpha 0700.HK quick` · `/alpha 7203.T news` · `/alpha market rates`。
 提出書類ベースのモードは米国登録企業が必要です。他市場は黙って空を返すのではなく `market_coverage` で対応状況を示します。
 
-### Full v2 — プラグイン管理の 30 分ハード上限
+### Full v2 — 3 段階の深さ、開始時の質問で選択
+
+実行はまず「どの深さで走らせるか」を尋ね、その後にどのメソッド席を置くかを尋ねます。速度キーワードを入力する必要はありません。`begin_council_selection` がメニューを返し、各段階の想定所要時間とハード上限を併記します。
+
+| 段階 | 想定 | 上限 | 根拠席あたり | 討論 1 ラウンド片側あたり |
+| --- | --- | --- | --- | --- |
+| `fast` | 約 12 分 | 15 分 | 3.5 分 | 90 秒 |
+| `normal`（既定） | 約 20 分 | 30 分 | 6 分 | 150 秒 |
+| `slow` | 約 44 分 | 60 分 | 12 分 | 6 分 |
+
+**3 段階はいずれも同一の `full_v2` 契約**です。根拠席 8 件、選択した全メソッド、3 ラウンドの討論、PM のすべてが同じで、変わるのは各席が考えてよい時間だけです。両方の数字を公開するのは、上限だけを示すとそれが想定値として読まれ、fast が常に 15 分かかるように見えてしまうためです。
+
+段階は総額と**各ステージ上限**を同時に引き上げ、さらに worker への出力要求も調整します。後半が重要です。上限だけではそれは単なる timeout であり、同じプロンプトに短い導火線を付けても得られるのは**書き終わらなかった packet** で、速くて良い packet ではありません。LLM 呼び出しの実時間は生成トークン数に支配されるため、`fast` は**同じ情報をより少ない散文で**求めます。主張・数値・スコープ付き source ID・必須レポート章・結論自体は決して削られず、削られるのは言い直しです。`slow` が買うのは、導出を段階的に書き切る余地です。
+
+選択した段階は一度限りの `selection_receipt` に束縛されます。実行呼び出しは同じ段階を繰り返せますが**変更はできません**。15 分として承認された実行が 1 時間になることはなく、どの段階で走ったかは `status.json` に記録されます。quick に段階はありません。より小さい契約であり、遅い契約ではないからです。
 
-プラグイン管理 headless `analyze_symbol(council_mode="full")` は、durable queue から終端成果物の永続化まで **1800000 ms** が上限です。必須 8 根拠席を 1 波で並列開始します。根拠 barrier 通過後、選択した各物理 v3 メソッドは決定論的 policy で stance を凍結し、その stable ID 専用の独立 voice worker を 1 つ起動します。この worker は説明だけを行い、stance の変更や typed fact の捏造はできません。3 ラウンドの各ラウンドで Bull/Bear を並列開始し、両方が終了してから次へ進み、最後に PM を実行します。
+必須 8 根拠席を 1 波で並列開始します。根拠 barrier 通過後、選択した各物理 v3 メソッドは決定論的 policy で stance を凍結します。**stance に到達した席**はその stable ID 専用の独立 voice worker を 1 つ起動し（説明のみで、stance の変更や typed fact の捏造はできません）、**棄権として凍結された席**は決定論的な記録からそのまま公開され、worker を消費しません。3 ラウンドの各ラウンドで Bull/Bear を並列開始し、両方が終了してから次へ進み、最後に PM を実行します。
 
-期限に達した場合は `incomplete` の終端状態を保存し、timeout・失敗・skip の全席を明示します。30 分が保証するのは監査可能な終端保存であり、検索・モデル transport・データ提供元の悪化時にも全席成功するという意味ではありません。visible-host の `plan_visible_run` は外部ホストが管理するため、プラグインはそのサブエージェントを強制停止できず、この上限を保証しません。
+期限に達した場合は `incomplete` の終端状態を保存し、timeout・失敗・skip の全席を明示します。段階の上限が保証するのは監査可能な終端保存であり、検索・モデル transport・データ提供元の悪化時にも全席成功するという意味ではありません。visible-host の `plan_visible_run` は外部ホストが管理するため、プラグインはそのサブエージェントを強制停止できず、**時間の保証を一切持ちません**。
 
 full の引き渡しは、選択した stable master ID 全件、必須 8 アナリスト全件、システム価格スナップショットまたは明示的な取得不能を列挙します。メソッド席の voice は provisional lens の記録された説明であり、**本人の発言・支持・現在の見解ではありません**。システム文言は中国語 (`zh-CN`)・英語・日本語・韓国語に対応し、各 worker に実行言語を渡します。
 
@@ -157,7 +183,7 @@ full の引き渡しは、選択した stable master ID 全件、必須 8 アナ
 
 ユーザーが急いでいることやフル実行の失敗を理由に、quick へ自動切替はしません。Quick は
 プラグイン管理の headless `analyze_symbol(council_mode="quick")` だけで実行され、
-`plan_visible_run` は quick を拒否します。26 席を完全表示して 1-4 席を確認した後の実行図は固定です：
+`plan_visible_run` は quick を拒否します。27 席を完全表示して 1-4 席を確認した後の実行図は固定です：
 
 1. `market_data`、`earnings_deep_dive`、`valuation_long_short`、
    `news_industry_management` の 4 席を 1 波で並列実行；
@@ -194,7 +220,7 @@ Claude Code、OpenCode、Grok Build ではインストール後すぐ使えま
 - ニュース、業界動向、サプライチェーン、経営陣の発言と行動の照合
 - SEC提出書類、Form 4 インサイダー取引、自社株買い、希薄化、負債と資本配分
 - M&A、エクイティ/デット・ファイナンス、自社株買いなどのイベント分析
-- 個別選択可能な 26 の投資手法レンズが同じ事実を読む
+- 個別選択可能な 27 の投資手法レンズが同じ事実を読む
 - ブル、ベア、ポートフォリオマネージャーの裁定
 
 フルは mandatory evidence barrier で fail-fast します。必須根拠席が 1 回の制限付き
@@ -227,7 +253,7 @@ parse-only 修復後も失敗した場合、失敗と診断の成果物を保存
 - **解析可能なタイムスタンプを持たないニュースは除外**され、「最新」として表示されません。
 - **`iv = 0` の建玉は除外。** CBOEは満期到来済みやディープITMで0を返しますが、0が平均に混入すると欠損値ではなく「落ち着いた銘柄」に見えてしまいます。
 
-## 🏛️ マスター陣 —— 26の投資手法レンズ
+## 🏛️ マスター陣 —— 27の投資手法レンズ
 
 公開された方法論の再構成であり、**本人の発言では一切ありません**。各レンズは自らの思考順序、最初に見るもの、典型的な問いかけ、そして**自身の失敗モード**を明示します —— 自分がどう間違うか言えない席は、間違ったときに手を挙げません。
 
@@ -239,11 +265,11 @@ parse-only 修復後も失敗した場合、失敗と診断の成果物を保存
 | クオンツ | サイモンズ · アスネス · ソープ |
 | オプション | タレブ · ナタンバーグ · シンクレア |
 | 現代 | アッシェンブレナー |
-| v3 拡張 | ダモダラン · アックマン · キャシー・ウッド · パブライ · ジュンジュンワラ |
+| v3 拡張 | ダモダラン · アックマン · キャシー・ウッド · パブライ · ボーグル · ジュンジュンワラ |
 
 1.0.0 `solo_test` カタログには 27 個の選択可能な物理 v3 パックがありますが、
-**26 パックは 26 個の承認済みメソッドモデルを意味しません**。全 26 席は provisional
-`operator_lens` のままです。52 個のツールは実行可能な
+**27 パックは 27 個の承認済みメソッドモデルを意味しません**。全 27 席は provisional
+`operator_lens` のままです。54 個のツールは実行可能な
 `provisional_derived_proxy` テスト代理であり、人間が承認した数式帰属ではありません。
 `operational` と `method_model` はともに 0 で、正式な production GA は fail-closed の
 ままです。
@@ -259,7 +285,7 @@ parse-only 修復後も失敗した場合、失敗と診断の成果物を保存
 flowchart TD
     U["@alphacouncil-agent"] --> G[("Established facts<br/>filings · quotes · macro · options")]
     G --> AG{{"Analyst council"}}
-    G --> MS{{"Master bench<br/>26 lenses"}}
+    G --> MS{{"Master bench<br/>27 lenses"}}
     AG --> A1["Market data"]
     AG --> A2["Earnings"]
     AG --> A3["Valuation"]
@@ -284,7 +310,7 @@ flowchart TD
     PM --> R[["final_report.md"]]
 ```
 
-マスターは事実から分岐し、アナリストのパケットからは分岐しません。26のレンズに一人のアナリストの取捨選択を与えれば、全員が同じ盲点を共有します —— 大きく、かつ完全に相関した誤差であり、陣容を持つ理由そのものが失われます。
+マスターは事実から分岐し、アナリストのパケットからは分岐しません。27のレンズに一人のアナリストの取捨選択を与えれば、全員が同じ盲点を共有します —— 大きく、かつ完全に相関した誤差であり、陣容を持つ理由そのものが失われます。
 
 主要ファイル: