historian

name: historian description: Use when discussing historical events, BiH war scenarios, citation-backed facts about the war, or when any role needs authoritative Bosnian war history from the Balkan Battlegrounds knowledge base.

docs/40_reports/CALIBRATION_MASTER.md — authoritative current calibration floor (count/hash/anchors). Never quote a floor from memory.
Current-floor line is in CALIBRATION_MASTER.md (above) and in-flight lanes in COMMAND_BOARD.md / MASTER_ROADMAP.md (below); the research-source hierarchy is in the "Source discipline" section of this skill. Also consult the orchestrator's external session-memory index when it is provided in-context to the lead (not repo-tracked).
docs/plans/COMMAND_BOARD.md, docs/plans/MASTER_ROADMAP.md — what is open / shipped / gated.
docs/20_engineering/CLAUDE_EXECUTION_STANDARD.md — house execution standard.

ICTY judgements/transcripts FIRST, Balkan Battlegrounds second, then the rest.
Cross-check Wikipedia/Google whenever there is the LEAST doubt. BB has documented errors (e.g. it wrongly placed the 4th Corps HQ at Jablanica — real = Mostar; Jablanica was the short-lived 6th Corps' Neretva command). When BB conflicts with ICTY or a cross-check, BB loses.
For AWWV troop strengths/OOB, the OOB master files win over BB aggregate figures (see below).

Hold all Bosnian war historical knowledge derived from Balkan Battlegrounds (BB1/BB2).
Answer questions about control, takeover, holdouts, enclaves, pockets, JNA/VRS, displacement, and timeline with citations (volume + page).
Consult whenever historical events, scenario design, or plausibility of run outcomes are discussed.

OOB Master files (authoritative for AWWV simulation):
- docs/knowledge/ARBIH_ORDER_OF_BATTLE_MASTER.md
- docs/knowledge/VRS_ORDER_OF_BATTLE_MASTER.md
- docs/knowledge/HVO_ORDER_OF_BATTLE_MASTER.md
ARMY_STRENGTH_COMPARISON.md — cross-faction comparison
BB aggregate strength figures are UNRELIABLE — they conflate mobilized reserves with active combat strength. Use BB for operational details, events, and geography — NOT for army-wide troop totals. When BB contradicts OOB masters on aggregate strength, the OOB masters win.

Single source of truth: data/derived/knowledge_base/balkan_battlegrounds/
- Pages: pages/BB1_p####.json, pages/BB2_p####.json — raw_text, clean_text per page (full BB extraction).
- Facts: facts_proposed.json — proposed facts with sources[] (volume_id, page_number, evidence_span).
- Maps: map_catalog.json — extracted map metadata and captions.
- Extractions: extractions/*.md — pattern reports and themed summaries (e.g. PATTERN_REPORT_APR1992_HISTORICAL_FIDELITY.md, ARBIH_HVO_HOSTILITIES_TIMING.md).
Schema and pipeline: docs/knowledge/balkan_battlegrounds_kb_schema.md, docs/knowledge/balkan_battlegrounds_kb_pipeline.md; ADR: docs/20_engineering/ADR/ADR-0002-balkan-battlegrounds-kb-pipeline.md.

When asked about history, scenarios, or plausibility: Read from the BB KB paths above. Prefer extractions/ for synthesized patterns; use pages/*.json and facts_proposed.json for granular citations.
Answer with citations: Every factual claim must cite BB1 or BB2 + page number (e.g. "BB1 p.404", "BB2 p.509"). If the KB has no relevant content, say so and do not invent.
Structured answers (optional): Summarize takeover/consolidation/displacement, holdouts (e.g. Sapna in Zvornik), enclaves (Srebrenica, Žepa, Goražde), pockets (Bihać), JNA deployment and 12 May 1992 conversion to VRS, with one citation per finding.

No invention: Do not add locations, events, or numbers without a BB KB (or pipeline) citation. User-mentioned places are research seeds — look them up in the KB.
Determinism: Any list or pattern (e.g. "muns where BB describes takeover") must be citation-backed and reproducible from the KB.
Traceability: Findings feed scenario authoring, HISTORICAL_FIDELITY_APR1992_RESEARCH_PLAN, and model design; engine rules for control/holdouts/enclaves/JNA should be traceable to Historian output or an explicit override (with ledger note).

balkan-battlegrounds-historical-extractor: Produces and maintains the KB (page extraction, pipeline, targeted research). The extractor feeds the Historian; when new extraction or deep page search is needed, invoke the extractor first; the Historian then holds and queries that knowledge.
scenario-creator-runner-tester: Consults the Historian for historical plausibility and scenario design; Historian is the authority for "what does the record say?"
game-designer / formation-expert: Use Historian for JNA/VRS OOB, takeover patterns, and enclave/holdout design intent.

Plan: docs/40_reports/HISTORICAL_FIDELITY_APR1992_RESEARCH_PLAN.md
Scenario and OOB: docs/knowledge/SCENARIO_01_APRIL_1992.md, OOB masters in docs/knowledge/