Factual Foundations Portal: A Portal for Source-Linked Political Reporting
Why mainline media fail readers on contested topics, and the proposal for a self-updating, source-linked, bias-disclosed alternative.
An AI-curated, source-linked, bias-disclosed portal for contested political topics. One page per topic, periodically refreshed, fallacy-audited, designed to anchor public discussion in evidence rather than spin.
The Problem with Current News
Most news consumers face a paradox today. More raw information is available than ever — yet forming an opinion based on fact has never been harder. This report documents why existing mainline sources systematically fail to provide what readers need to form their own opinions on contested political questions, and outlines what a better system would look like.
Five Recurring Failures
- Selective context omission — facts that explain a reaction get cut, leaving readers to wonder why anyone cares — because the reasons behind it were never reported.
- False equivalence — well-documented conclusions and political positions are presented as "two sides" with equal weight, even when evidence is asymmetric.
- Source-blackout by default — readers are not shown what sources are not covering. The information that "X outlet has not reported on this" is itself crucial.
- Source-bias opacity — outlets don't disclose their known editorial biases. A Manhattan Institute study of 28,000+ Wikipedia articles found right-of-center figures associated with more negative language than left-of-center — but the average reader doesn't know that.
- One-and-done reporting — events are reported once, then archived. No mechanism for retrospective correction, follow-up, or re-examination when new evidence emerges.
Sample: Why the Volhynia Case Is a Microcosm
The June 2026 dispute over Poland's revocation of Zelensky's Order of the White Eagle is a perfect case study. Every mainline outlet reported the event. Almost none reported the causal context that makes the event intelligible. Below is a summary of what each source actually said versus what an informed reader needed to know.
| Source | What it reported | What it omitted |
|---|---|---|
| AP News | "Nawrocki stripped Zelensky of the Order. Support for Ukraine unchanged." | Why the UPA is controversial. No specific atrocity context. No exhumation dispute. No historical depth. A reader knows what happened but not why. |
| BBC News | "Zelensky stripped of Polish honour over WW2 name of army unit." | Specific methods of UPA violence. Exhumation ban history. Polish self-defence narrative. Still insufficient context for understanding Polish anger. |
| Wikipedia (English) | Detailed Atrocities section, named perpetrators, scholarly consensus. | Left-leaning systemic bias (Manhattan Institute 2024). False-equivalence between Polish genocide designation and Ukrainian "tragedy" framing. |
| Wikipedia (Ukrainian) | Polish reprisals detailed. Sahryń 800+ killed, Berest 200+ killed. | No description of UPA killing methods. The article simply does not mention that UPA fighters sawed people alive, impaled babies on pitchforks, or crucified priests. This is a deliberate editorial choice, not a difference of historiography. |
| Kyiv Independent / Kyiv Post | Ukrainian official position. Sybiha: "strategic mistake." | Minimal UPA atrocity detail. Pro-Ukraine framing presented as fact. |
The Factual Foundations Portal: What It Should Be
What is needed is not a new outlet but a different kind of artifact for each contested topic: a self-contained, source-linked, bias-disclosed page that lets a reader see the full factual picture in 20 minutes — and updates as new evidence emerges.
Core Design Principles
Source-First
Every factual claim has a clickable citation. No unsourced assertion. The page is a network of links, not a wall of authority.
Bias-Disclosed
Every referenced outlet has its known editorial bias documented. The Manhattan Institute study, AER study, Wikipedia co-founder statements are surfaced for each source.
Multi-Language
Cross-check articles in multiple languages. A topic that has Polish, English, and Ukrainian Wikipedia editions has three different editorial choices; surfacing them is the point.
Self-Updating
An AI agent periodically re-fetches, re-summarises, and flags new evidence. The page is a living artifact, not a one-time publication.
Discourse-Ready
Each section has a share button, a comment surface, and embedded X/Twitter. Discussions stay anchored to the factual record.
Fallacy-Audited
A dedicated section for the most common fallacies used to dismiss the topic. The reader comes pre-loaded with the rhetorical moves they will encounter.
The AI Component: Periodic Search and Re-Synthesis
The most labor-intensive part of keeping a Factual Foundations page current is — well, keeping it current. New events, exhumations, witness statements, political developments — all should update the underlying record. A human researcher cannot realistically do this for more than a handful of topics. An AI agent can.
The Proposed Workflow
- Daily / weekly re-fetch: The agent re-pulls all cited sources via SearXNG + web_extract. Compares new content to existing report.
- New-evidence flag: Any new facts, new statements, new exhumation findings, or new editorial framing are flagged with timestamps and added to a "Recently updated" section.
- Cross-source comparison update: The cross-source table is regenerated, with new framing differences surfaced.
- Fallacy review: The fallacy section is checked against recent discourse — are new rhetorical moves being used? Are new ones documented?
- Human-readable diff: A short summary of what changed and why is appended, so a reader can spot what the AI updated.
What the AI Can and Cannot Do
| Can do | Cannot do |
|---|---|
| Re-fetch and compare versions | Tell the reader which version is "true" without human judgment |
| Surface new sources that meet the standard | Force a partisan reader to update their priors |
| Detect and document fallacious rhetoric | Prevent rhetorical misuse of the page |
| Maintain source-quality metadata | Resolve contested scholarly debates on its own |
| Update timeline, cross-source table, source grid | Decide which disputed fact is "in" and which is "out" of the report |
Sharing, Discussion, X/Twitter Integration
For the portal to function, the page must be discussion-friendly. A reader who finishes the page should be able to share a specific section to X/Twitter, see what others have said about that specific section, and add their own analysis with citations.
Section Anchors
Every section is a deep-linkable URL. The "exhumation dispute" section is its own URL. The "UPA atrocities" section is its own URL. A reader sharing a section to X/Twitter does not share the whole 10,000-word page — they share the one part that has the facts they want to discuss. This is the difference between a portal and a dump.
Embedded Discourse
Where primary sources (X/Twitter posts, official statements) exist, they are embedded alongside the editorial synthesis. The page is a fact+context surface, not a curated monologue.
Konflikt między Polską i Ukrainą cieszy Putina i szokuje naszych sojuszników. Zadaniem prezydentów Zelenskiego i Nawrockiego jest tonowanie emocji, a nie podsycanie napięcia. Linia frontu przebiega gdzie indziej.
English translation: "The conflict between Poland and Ukraine delights Putin and shocks our allies. The task of Presidents Zelensky and Nawrocki is to calm emotions, not to inflame tension. The front line runs elsewhere."
What this says vs. what it implies: On the surface, Tusk appears to "criticise both sides" by saying both presidents should de-escalate. In context, the framing is pro-Ukrainian accommodation: Tusk calls the Polish-Ukrainian fracture a Putin win, and his "de-escalation" recommendation favours accepting Ukraine's positions on the UPA issue rather than confronting them. This is the position the Polish opposition (KO, Tusk's party) and the Ukrainian government have aligned on throughout the dispute.
Why this matters for FF: quoting Tusk's tweet as "criticising both sides" without the framing above reads as a neutral call for peace — when in fact the position is a softer Polish response to Ukrainian state honours. The two readings are not equivalent. FF embeds the context so the surface text and the framing travel together.
Comment Thread Per Section
Each section gets its own comment surface. Comments are anchored to the section, not to the page. This prevents the standard problem of "I disagree with the article" when the commenter only read the headline. Discussion stays anchored to the specific factual claim being discussed.
The Fallacy Handbook: Anticipating Dismissals
Any factual report on a contested political topic will be dismissed. The most common dismissals are not based on engaging with the evidence — they are rhetorical moves designed to skip the engagement. Below are the fallacies most often used to dismiss the kind of factual record this portal produces, with explanations and counters.
See the full FF fallacy handbook (20 entries) on the methodology page. This page no longer duplicates the full handbook — it links to the canonical source, and the Volhynia-specific fallacies live on the Volhynia page.
On the Use of an LLM to Compile This Portal
An LLM compiled this page. See the Model Version History section for which model was used. As with every FF page, the standard dismissal is "it's AI, therefore it's unreliable." That is a genetic fallacy. The LLM is a retrieval and composition tool, not an authority. Every claim on this page is cited. Every editorial decision is documented. A human researcher with the same tools would produce the same content.