πŸ“‘ Analysis Index Template

May 3, 2026 Β· View on GitHub

πŸ“Œ Template Instructions β€” Copy to analysis/daily/$ARTICLE_DATE/$SUBFOLDER/analysis-index.md. Produced at the end of Pass 2 (after every other artifact is finalised) as the read-me-first index of the run. See per-artifact-methodologies.md Β§analysis-index.

🎯 Purpose β€” Comprehensive directory of every artifact in this run with recommended reading order for the article generator, downstream reviewers and the next same-type run. Answers: "what exists in this run and what should I read first?"

πŸ”„ Tradecraft Context

  • Workflow role β€” Final navigation layer for the run; produced at the end of Pass 2 after all required artifacts are complete, reviewed and internally consistent.
  • Primary users β€” Article generator, human reviewers, later same-type runs, and audit/compliance readers needing a single entry point into the full analysis set.
  • Why it matters β€” Reduces retrieval errors, makes reading order explicit, surfaces degraded or missing artifacts, and provides the canonical map of what evidence existed before any article text was written.
  • Tradecraft rule β€” Do not introduce new claims here. Summarise and link the run's completed artifacts; point readers to the authoritative source artifact for each major finding.
  • AI-FIRST requirement β€” Complete only after both passes finish: Pass 1 creates the artifact set; Pass 2 re-reads, improves, validates consistency, then assembles this index as the read-me-first navigator.

πŸ“ Template Contract β€” every fill of this template MUST satisfy this row.

SlotValue
Owning methodologyper-artifact-methodologies.md
Owning gate checkCheck 1 (presence) + supplementary β€” see 05-analysis-gate.md
Required inputsall peers in the run folder
Horizon bandper-run (per scripts/horizon-context.ts)
Output familyOperational Supplementary
Aggregation orderappended (alphabetical, after canonical block) (see scripts/render-lib/aggregator/order.ts)
Reader Intelligence Guiderow generated from analysis-index.md (see scripts/render-lib/aggregator/reader-guide.ts)
Canonical evidence anchor| claim | evidence (dok_id / vote / MP intressent_id / primary-source URL) | retrieved_at | confidence | β€” every analytical claim row uses this schema.

Cross-reference: README.md Β§Template ↔ Methodology ↔ Gate-Check Matrix.

πŸ“‹ Document Metadata

FieldValue
Report ID[REQUIRED: AI-YYYY-MM-DD-runNN]
Run Date[REQUIRED: YYYY-MM-DD]
Article Type[REQUIRED: breaking / evening / weekly / monthly / motions / propositions / committee-reports / interpellations / week-ahead / month-ahead / realtime-monitor]
Run Number[REQUIRED: runNN]
Run Directory[REQUIRED: analysis/daily/YYYY-MM-DD/{type}-runNN/]
Runtime Duration[REQUIRED: HH:MM:SS]
Pass 1 Completed[REQUIRED: βœ… / ❌]
Pass 2 Completed[REQUIRED: βœ… / ❌]
Data Sources Attempted[REQUIRED: count of MCP tool invocations]
Data Sources Succeeded[REQUIRED: count]
Confidence[REQUIRED: HIGH 🟒 / MEDIUM 🟑 / LOW πŸ”΄]

1️⃣ Run Summary

Article type β€” [REQUIRED]
Run ID β€” [REQUIRED: {type}-run{N}]
Date β€” [REQUIRED: YYYY-MM-DD]
Wall-clock runtime β€” [REQUIRED]
Completion status β€” [REQUIRED: βœ… Complete / ⚠️ Degraded / ❌ Incomplete]
Gate status β€” [REQUIRED: βœ… PASSED / ❌ FAILED β€” reasons listed below]

One-paragraph (3–5 sentences) narrative summary of what this run produced, the dominant finding, and any degradation notes. Cite the single most-important artifact.


2️⃣ Production Stage Diagram

%%{init: {"theme":"dark","themeVariables":{"primaryColor":"#1565C0","primaryTextColor":"#ffffff","lineColor":"#90CAF9","secondaryColor":"#2E7D32","tertiaryColor":"#FF9800","fontFamily":"Inter, Helvetica, Arial, sans-serif"}}}%%
flowchart LR
    P03["03 β€” data download"] --> P04P1["04 β€” Pass 1 create"]
    P04P1 --> P04P2["04 β€” Pass 2 improve"]
    P04P2 --> P05["05 β€” gate"]
    P05 --> P06["06 β€” article"]
    P06 --> P07["07 β€” commit & PR"]

    classDef ok fill:#2E7D32,color:#ffffff
    classDef warn fill:#FF9800,color:#000000
    classDef fail fill:#D32F2F,color:#ffffff
    class P03,P04P1,P04P2,P05,P06,P07 ok

Annotate each node βœ… / ⚠️ / ❌ based on actual execution.


3️⃣ Artifact Inventory β€” Core Always-On (23)

#FamilyCanonical filenameOn-disk pathLinesFloorStatus
1AREADME.mdREADME.md[#][floor][βœ…/⚠️/❌]
2Aexecutive-brief.mdexecutive-brief.md[#][floor][…]
3Asynthesis-summary.mdsynthesis-summary.md[#][floor][…]
4Asignificance-scoring.mdsignificance-scoring.md[#][floor][…]
5Aclassification-results.mdclassification-results.md[#][floor][…]
6Aswot-analysis.mdswot-analysis.md[#][floor][…]
7Arisk-assessment.mdrisk-assessment.md[#][floor][…]
8Athreat-analysis.mdthreat-analysis.md[#][floor][…]
9Astakeholder-perspectives.mdstakeholder-perspectives.md[#][floor][…]
10Bdata-download-manifest.mddata-download-manifest.md[#][floor][…]
11Bcross-reference-map.mdcross-reference-map.md[#][floor][…]
12Cscenario-analysis.mdscenario-analysis.md[#][floor][…]
13Ccomparative-international.mdcomparative-international.md[#][floor][…]
14Cdevils-advocate.mddevils-advocate.md[#][floor][…]
15Cintelligence-assessment.mdintelligence-assessment.md[#][floor][…]
16 ⭐Cmethodology-reflection.mdmethodology-reflection.md[#][floor][…]
17Delection-2026-analysis.mdelection-2026-analysis.md[#][floor][…]
18Dvoter-segmentation.mdvoter-segmentation.md[#][floor][…]
19Dcoalition-mathematics.mdcoalition-mathematics.md[#][floor][…]
20Dhistorical-parallels.mdhistorical-parallels.md[#][floor][…]
21Dmedia-framing-analysis.mdmedia-framing-analysis.md[#][floor][…]
22Dimplementation-feasibility.mdimplementation-feasibility.md[#][floor][…]
23Dforward-indicators.mdforward-indicators.md[#][floor][…]

Floors from reference-quality-thresholds.json.

Notes on the 23-artifact core β€” cross-reference-map.md is a single artifact; Tier-C adds sibling-folder citations inside the same file (do not create a second file). Per-document analyses live under documents/{dok_id}-analysis.md (Family E template, validated by gate Check 2) and are not counted in this 23-row core inventory.


4️⃣ Artifact Inventory β€” Operational Supplementary (present in this run)

#FilenameProduced?LinesFloorNotes
S1analysis-index.md (this file)βœ…[#]120β€”
S2reference-analysis-quality.md[βœ…/❌][#]120Mandatory for comprehensive
S3mcp-reliability-audit.md[βœ…/❌][#]150Mandatory for comprehensive
S4workflow-audit.md[βœ…/❌][#]120Mandatory for comprehensive
S5cross-run-diff.md[βœ…/N/A][#]130N/A if first run
S6cross-session-intelligence.md[βœ…/N/A][#]140N/A unless aggregation workflow
S7session-baseline.md[βœ…/N/A][#]140N/A unless aggregation workflow

5️⃣ Family-E Per-Document Files

dok_idPathDIW tierLinesFloorCluster?
[REQUIRED]documents/[dok_id]-analysis.md[L1/L2/L2+/L3][#][floor][y/n]

Total Family-E files: [#]. Clusters: [#].


For the article generator (module 06):

  1. synthesis-summary.md β€” BLUF and Key Judgments.
  2. significance-scoring.md β€” tier-sorted headline items.
  3. stakeholder-perspectives.md β€” quote sources.
  4. risk-assessment.md + threat-analysis.md β€” for risk/conflict framing.
  5. forward-indicators.md β€” closing "what to watch" section.
  6. methodology-reflection.md β€” confidence + caveats for byline.

For a downstream reviewer (humans + next-run agent):

  1. This index.
  2. methodology-reflection.md + reference-analysis-quality.md (if present).
  3. cross-run-diff.md (if present) β€” what changed since last run.
  4. synthesis-summary.md.
  5. Any artifact flagged ⚠️ in §3 or §4.

7️⃣ MCP & Data Source Summary

Server / toolCallsSucceededFailedMean latencyNotes
riksdag-regering[#][#][#][ms]β€”
scb[#][#][#][ms]β€”
world-bank[#][#][#][ms]β€”
IMF (tsx scripts/imf-fetch.ts)[#][#][#][ms]β€”
github[#][#][#][ms]module 07 only

Full detail β€” see mcp-reliability-audit.md when present.


8️⃣ Gate Outcome

Gate result β€” [REQUIRED: βœ… PASSED / ❌ FAILED]
Failing checks β€” [REQUIRED: list or "none"]
Waivers applied β€” [REQUIRED: list or "none"]

If ❌ FAILED, the article MUST NOT be published. See 05-analysis-gate.md outcome rules.


9️⃣ Changelog for This Run

  • [REQUIRED] 1-line summary of what improved vs Pass 1 (link to cross-run-diff.md for run-over-run delta).
  • [REQUIRED] Any MCP degradations and their mitigations.
  • [REQUIRED] Any methodology deviations (e.g. waiver approved) and the human approver.

πŸ”— Cross-References


Template version: v1.2 Β· Last updated: 2026-04-25


βœ… Pass-2 Self-Audit Checklist (v4.4 β€” required)

Purpose: AI-FIRST principle requires a Pass-2 read-back-and-improve. After producing this artifact in Pass 1, re-read it end-to-end and verify each item below. Document any remediation in methodology-reflection.md §"Pass-2 audit log". Any unchecked ❌ box at the end of Pass 2 forces a Pass-3 rewrite of the affected section.

  • Tradecraft anchors honoured β€” F3EAD stage matches the artifact's role; PIRs declared in the Β§Tradecraft Context block are actually addressed in the body; Admiralty grades attached to every external source; WEP band + ODNI confidence on every probabilistic judgement.
  • Source diversity floor met β€” at least the minimum number of independent MCP sources required by the artifact's tradecraft block are cited; single-source claims are explicitly labelled [SINGLE-SOURCE β€” corroboration pending].
  • Evidence specificity β€” every quantified claim cites a dok_id (Riksdag), an SCB / IMF dataflow code, or a named external source with date; no "according to data" / "studies show" hand-waves.
  • Named-actor discipline β€” every political claim names β‰₯ 1 person (party + role + dated act/quote) or labels the absence ([diffuse β€” no named actor]).
  • Counter-narrative present β€” at least one explicit competing hypothesis, dissent quote, or framed objection appears in the body; "no opposition recorded" is itself a finding to label, not silence.
  • Election 2026 lens applied β€” the Β§"Election 2026 Implications" subsection (or equivalent) addresses electoral salience, coalition pressure, and forward indicators; not boilerplate.
  • No illustrative content shipped as fact β€” every [REQUIRED] placeholder is filled OR removed; every Example: block is clearly fenced or removed; no fabricated dok_id, vote count, or quote leaks into the final artifact.
  • Cross-references resolve β€” every [link](file.md) in this artifact points to a file that exists in the run folder (analysis/daily/$ARTICLE_DATE/$SUBFOLDER/) or to a methodology / template under analysis/.
  • Mermaid renders β€” every fenced ```mermaid block parses (no missing class definitions, no orphan nodes, no >40-node graphs that overflow viewport on mobile).
  • Line-floor check β€” artifact length β‰₯ the per-artifact floor in reference-quality-thresholds.json; shorter artifacts trigger Pass-2 rewrite, never a [truncated] note.