Transparency
This page is Forum Atlas's standing disclosure: every number on it is queried live from the production database when the page renders, and a machine-readable copy of the disclosure lives at /.well-known/ai-disclosure.json.
Forum Atlas is an industry-intelligence platform covering 12 commercial sectors. Its briefs and forecasts are generated by AI systems — a multi-agent ensemble that retrieves source documents, synthesizes analysis, and validates every claim. They are not written by human analysts. We disclose this plainly and in machine-readable form because you deserve to know, and because the EU AI Act (Article 50, applicable from August 2, 2026) requires providers to disclose AI-generated text published to inform the public. Two things are not AI-generated: the underlying source documents (third-party publications we cite verbatim) and the outcome data used to score forecasts.
Every analytical claim in a brief carries a citation you can audit — a verbatim extract from a named source document, with its URL and publication date. If the machine can't prove a sentence against a source, the sentence does not ship.
After synthesis, a separate validator model checks every claim against the retrieved source text. A claim that can't be matched to a verbatim substring fails. A brief that fails validation is withheld from validated presentation: it renders as “insufficient evidence,” never as confident analysis. We publish the failure rate because a validation gate that never fails is not a gate.
Live counts from our public showcase workspace — the same workspace behind the accuracy scoreboard. Full pipeline detail: methodology · citation discipline.
One headline document count would flatter us, so here are two. The curated intelligence corpus is what analysts would recognize as coverage: sector-scoped feeds — government, corporate disclosure, trade press, academic and more — chosen source by source. The bulk reference corpora are complete vulnerability and exploit registries (CVE, OSV, Exploit-DB) we mirror for lookup and enrichment. They are records, not signals — our own desk feed excludes them — and counting them as “intelligence coverage” would be misleading.
Bulk reference breakdown: OSV.dev 182,399 · MITRE CVE 110,429 · Exploit-DB 46,628 · nist_nvd 9,863 · NIST NVD 7,871 · sec_edgar 3,822.
Counts queried live from the production database at page render.
Every forecast is timestamped and immutable at generation, with a fixed resolution horizon. When a horizon closes we record what actually happened and publish the Brier score. The first horizons close around August 2026; as of this page render, 118 forecasts are on the record and 2 have resolved. We could hide the empty column until the numbers look good. Instead the scoreboard is public from day one — an honest empty scoreboard beats a fake one.
We also run a shadow book against open prediction markets: each of those forecasts is sealed as a SHA-256 commitment before the market settles and revealed afterward, so outsiders can verify we never edited a call. The public commit–reveal ledger — every sealed commitment, and every reveal as settlements land — lives at /ledger (machine-readable: /ledger.json).
Watch it fill in at /accuracy.
Machine-readable disclosures: /.well-known/ai-disclosure.json (site-level) and per-brief provenance manifests at /api/briefs/{id}/manifest.