# The analyst's domain knowledge: implementation plan > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** one hand-maintained source per kind of knowledge for the analyst (labels through the RAG, `families.md` with a phenomenon catalogue, `labeling-rules.md`, `reading-rules.md`, `stations.md`, `tools/DATA.md`), the old map and `knowledge/` archived, then the labeling scripts moved to `labeling/scripts/`. **Architecture:** mostly writing: markdown compiled from existing files, then path updates in four repositories. One throwaway script (in the scratchpad, never committed) converts the map's label keys to label ids. The only code change is the scripts' root path after the move. **Tech Stack:** markdown; Python 3 standard library; git. **Spec:** `labeling/docs/superpowers/specs/2026-11-16-analyst-knowledge-design.md`. ## Global Constraints - Starts only when the English migration (`Diagnostic-App/docs/superpowers/plans/2026-11-16-english-renames.md`) is committed in labeling, tools, agents and Diagnostic-App: `git status --short` shows nothing of it in any of them (the app's own label submissions in `labeling/auto/*.jsonl` may remain; never stage them). - All new text in English. Times in UTC. No numeric value in label descriptions (not touched here anyway). - `labeling/manual/` is never read by any step or script. - No station-specific *rule* in `families.md`, `labeling-rules.md`, `reading-rules.md`; `stations.md` is context only and says so. - tools holds what the data *are*; labeling what they *mean*. Nothing in `tools/DATA.md` says "normal", a category or a threshold to judge by. - Commits by path, never `git add -A`; English commit messages ending with `Co-Authored-By: Claude Opus 5.5 `. - Never stage `labeling/auto/*.jsonl` or `labeling/auto/analyses/` (Diagnostic-App writes there concurrently). ## Review Focus 1. Knowledge silently dropped: a bullet of the map's sections 2–3, or a fact of a `knowledge/` note, that lands in no new file. Pinned by the coverage table of Task 3, step 4. 2. A map key converted to the wrong id (two labels share a start). Pinned by the ambiguity report of Task 3, step 2: every ambiguous key is resolved by hand, none guessed. 3. A stale path left in another repository (`label-map`, `knowledge/`, `labeling/