Дмитрий
2b052ab1a7
Phase 1 Task 6 of LLM-first router overhaul. Minimal-scope execution after reality check (C1/C2 controllers don't track section refs, only version drift; plan steps about §3.3/R15 archiving are out of scope for cross-ref update). Changes: - CLAUDE.md §0 'Источник истины' row for Pravila: **v1.40 от 24.05.2026** -> **v1.41 от 25.05.2026** + narrative bump (§12 archived in Task 4, §17 added in Task 5 via ADR-016). - docs/Tooling_v8_3.md line 4 cross-ref: cross-ref Pravila v1.39+ -> v1.41+ (+ CLAUDE.md v2.27+ -> v2.28+). Deferred (TASKLOG.md Task 6 section for full reasoning): - §12 textual occurrences in PSR_v1 (39) and historical Tooling/CLAUDE.md changelog blocks remain as honest historical pointers to the archived §12 (docs/archive/llm-bootstrap-2026-05/pravila-12/...). - CLAUDE.md §3.3 archive + nodes.yaml pin — out of scope, requires structural restructure beyond cross-ref work. - Tooling §4.X 'когда брать' archive — out of scope. - PSR_v1 R15 — already removed in v2.0 (motion-runtime removal, 12.05.2026); current R15 is 'Off-phase routing', unrelated to §12. Verification: - tools/l1-watcher.mjs: OK — 0 drift. - tools/cross-ref-checker.mjs: OK — 0 drift in 4 files (was FAILing on Pravila v1.40 / v1.39 references after Task 5 bump to v1.41). - npx vitest run tools/: 539 passed (unchanged from Task 4 baseline). Plan: docs/superpowers/plans/2026-05-25-llm-first-router-overhaul.md Task 6. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Observer infrastructure
Passive evidence-loop for the Лидерра «brain» per ADR-011.
Files
episodes-YYYY-MM.jsonl— append-only JSONL, one line per Stop-event. Schema v2 (schema_version: 2): the 5 mandatory fields +decision_provenance(who chose the node),environment(economy_level / model / post_compaction / session_turn / parallel_session),task_size,task_ref,prompt_signal, and anoutcomethat isunknownat write time (refined by/brain-retro). On an internal hook failure a minimalobserver_errormarker line is written instead of a silent skip. Written bytools/observer-stop-hook.mjsviatools/observer-transcript-parser.mjs.notes/YYYY-MM-DD-<slug>.md— optional MD notes for sessions with qualitative history.STATUS.md— auto-generated dashboard. Regenerated per-commit bytools/status-md-generator.mjs..read-counter.json— C3 observer-of-observer counter. Updated on Read of observer files.dashboard.html+dashboard.js+dashboard-core.js— Brain Dashboard: visualises the episode log over the automation-graph topology (4 views — Карта / Разбор / Лента / Агрегат). Runnpm run brain:dashboard, open the printed localhost URL.dashboard-core.jsis pure logic, unit-tested intools/brain-dashboard-core.test.mjs.
Lifecycle
- Write: every Stop-event appends one JSONL line, parsed from the session transcript (Stop-hook).
- Aggregate:
/brain-retroskill reads JSONL each sprint, proposes regulatory candidates. - Surface:
STATUS.mdshows controllers + monthly stats. - Self-prune: C3 warns if 54 weeks pass without any read of observer files.
Routing-tag discipline
When the user dictates a specific method/node (e.g. «запусти discovery-interview»), Claude must emit one line in its response:
<!-- routing: provenance=user_directed_method node=<chosen> counterfactual=<node Claude would have chosen autonomously> -->
The Stop-hook routing-gate (tools/observer-routing-detector.mjs + routingGateDecision) detects a dictated method; if the tag is missing it returns decision: block, so the turn cannot end without the tag. The gate fires at most once per turn (stop_hook_active guard). This makes decision_provenance reliable — factor analysis can separate a router error from a user-dictated one.
Privacy
PII filter (phone numbers, emails, tokens) is applied before every write — see tools/observer-pii-filter.mjs. gitleaks pre-push also scans observer files as part of full-history sweep.
Don't
- Don't edit
episodes-*.jsonlmanually — it's append-only. - Don't write outside
docs/observer/notes/for hand-curated notes. - Don't change
.read-counter.jsonmanually — it's maintained by hooks.
HK1 pre-check (Pravila ADR-010) — verified 2026-05-19
Before registering tools/observer-stop-hook.mjs on Stop event (Task B5), verified collision against 6-component economy/skill-discipline architecture:
- User-level
~/.claude/settings.jsonalready has Stop hook: agent-type Sonnet-4.6 economy compliance verifier (analyzes transcript for claim-without-evidence violations). - Project-level
.claude/settings.json— Stop slot empty.
Result: no overwrite. observer-stop-hook will be added as command-type entry in project-level Stop array. Project + user scopes are independent slots in Claude Code 2.x — both run on the same Stop event without conflict. The agent verifier (user scope) and the JSONL appender (project scope) have non-overlapping responsibilities.