๐Ÿงญ Political Intelligence

Methodologies, templates & daily analysis transparency

Every political analysis published on this site is backed by a transparent chain of methodologies, artifact templates, and run-level analysis data. This page gives you a single, fully-linked index into every piece of tradecraft used to produce the news. All sources open in GitHub so you can audit the analysis behind the prose.

Methodologies
23
Templates
61
References
19
Analysis runs
255
Artifacts
4210

Methodologies

Authoritative tradecraft guides โ€” risk frameworks, style standards, and the 10-step AI-driven analysis protocol that every article follows.

Analysis Templates

The catalog of artifact templates produced in every daily analysis run โ€” SWOT, PESTLE, threat matrices, coalition dynamics, consequence trees, and more.

Reference & Data Sources

ISMS reference adaptations, indicator catalogs, EU country mappings, chart-integration guides, and use-cases from the IMF and World Bank data pipelines โ€” the authoritative sources behind every economic, governance, and risk chart.

Daily Analysis Runs

Every published analysis run, grouped by date and ordered newest first. Each run links to the full GitHub tree so you can inspect every artifact file that fed the corresponding article.

1 run

5 runs

6 runs

4 runs

3 runs

8 runs

5 runs

5 runs

6 runs

5 runs

3 runs

5 runs

6 runs

1 run

6 runs

3 runs

6 runs

5 runs

6 runs

4 runs

3 runs

2 runs

2 runs

5 runs

12 runs

5 runs

10 runs

10 runs

10 runs

14 runs

12 runs

1 run

4 runs

12 runs

3 runs

4 runs

6 runs

8 runs

4 runs

6 runs

8 runs

5 runs

6 runs

2 runs

4 runs

4 runs

About political intelligence runs

What is a political intelligence run?

A political intelligence run is a daily analytical workflow that pulls fresh data from the European Parliament Open Data Portal, executes a fixed set of MCP analysis tools, and produces both a markdown brief and a public news article.

Are the analyses peer-reviewed?

No. Analyses are produced by AI agents using deterministic prompts and published openly so that anyone can reproduce, fork, or contest the methodology. Source code, prompts and raw data are linked from every run card.

How frequently are runs executed?

At least once per European Parliament working day. Specialised runs (coalition fracture, MEP influence, legislative bottlenecks) execute on their own GitHub Actions schedules.

Where can I see the source code?

All workflow definitions, agent prompts, and analysis tooling are published at github.com/Hack23/euparliamentmonitor under the Apache 2.0 license. The MCP server itself is at github.com/Hack23/european-parliament-mcp.

Who writes the analysis?

The analysis is written by AI agents orchestrated by Hack23 AB. Editorial guardrails, prompts and tool whitelists are version-controlled and reviewed by humans before each release.