Skip to main content

Context Intelligence Platform

MAP Verified™

See the information around the story before you decide.

MAP is not explaining the content itself. MAP explains the observable information environment around it — where it came from, who's attributed, how detailed it is, and how it's framed — written to a hash-chained ledger.

MAP does not determine whether something is true, false, biased, or trustworthy. That judgment is left to you. MAP gives you the evidence environment before judgment.

Check a URL → Publisher Certification


Beyond the headline

What might you be missing?

What information is present — and what information was not observed in the analyzed material?

Check a URL →

What changed while you weren’t looking?

How does this observation differ from the previous MAP record for the same URL?

What Changed →

Follow what matters to you

Follow the companies, topics, and markets relevant to your research and get a daily email digest — no account needed.

Browse entities →

Return to the record

Return to the original source and the time MAP observed it. Open a record to see its seven frames, its observation history and its hashes.

Verification Archive →

The information fingerprint

MAP's context record documents seven observable dimensions of a piece of content.

01

Origin

Where does this come from?

MAP identifies the publisher, author, publication date, and any structured data the page itself provides. Instead of "this article is credible," MAP tells you what's documented about where it came from — and lets you decide what that means.

02

Attribution

Who is making the statement?

MAP looks for structural patterns that signal attribution — phrasing like "according to" or "officials state" — and outbound references to named sources, so you can see where claims are anchored.

03

Specificity

How detailed is the information?

MAP records observable detail — body content depth, named dates, and name-like sequences that suggest people, places, or organizations. MAP shows what it observed, not whether the information is "good."

04

Timing

Where does this sit in time?

Past event, ongoing development, or anticipated action — MAP identifies structural cues in the headline and description that lean toward one framing or another.

05

Framing

What gets the emphasis?

MAP identifies structural framing patterns — urgency, listicle format, opinion format, live-update format — so you can see how a story is being packaged, not just what it says.

06

Context change

What's changed since last time?

When MAP has analyzed a URL before, the new record compares against the prior one — headline changes, new attribution, shifts in outbound references or framing — so you can see how the story evolved, not just its current snapshot.

07

Information relationships

What's connected to what?

The people, places, dates, and outside sources referenced in a piece, surfaced as observable connections — the beginning of a relationship map around the content, not a verdict on it.


For readers

Understand before you share.

MAP context records are written to a hash-chained ledger that MAP operates. Hashed entries are chained; older entries that have no hash are not part of the chain, and continuity is MAP’s own daily report. It documents what's observable, not what to believe.

Check a URL →

For publishers

Earn MAP Certification.

Certified publishers receive a publicly accessible, searchable record — reviewed manually by MAP, not an automated score threshold. No publisher has been certified yet.

Publisher Certification →

MAP Ledger

MAP context records are written to the MAP Verification Ledger, an append-oriented table operated by MAP. Hashed entries are chained; older entries that have no hash are not part of the chain, and continuity is MAP’s own daily report.

Continuity check: MAP runs a continuity check on the ledger every day (last run Nov 7, 2026 10:01 UTC). MAP does not publish its detailed results or the data needed to recompute the hashes.

— records on the ledger

How MAP builds a context record →

FAQ

MAP Verified™ — Frequently Asked Questions

What is MAP Verified™?

MAP Verified™ documents the observable information environment around a news URL or publisher — origin, attribution, specificity, timing, framing, context change, and information relationships — and records the result on a hash-chained verification ledger. It does not determine whether content is true, false, biased, or trustworthy; it documents what is observable so readers can form their own judgment.

How is a MAP context record built?

A MAP context record is built by automated, rule-based extraction code that reads the page's HTML and metadata: publisher, author, publish date, outbound references, structural framing cues, and (when a prior record exists) what has changed since MAP last recorded that URL. It runs on MAP's AWS Lambda infrastructure. No generative AI writes the record text, and each record is a point-in-time snapshot.

Are MAP Verified™ context records a certified fact?

No. MAP Verified™ context records are produced by automated, rule-based extraction (no generative AI writes the record text). The extraction is heuristic, so records are informational and can be incomplete or wrong. They document observable characteristics at one point in time only — not certified fact, a legal determination, or professional advice — and should not be the sole basis for a consequential decision.

How do I report an inaccurate context record?

Report it through the contact form with the specific URL, the error, and supporting evidence. MAP aims to review reports within 5 business days (a target, not a guarantee); if confirmed, MAP's practice is to record the correction as a new ledger entry rather than edit the earlier one. The ledger does not yet link a correction to the entry it corrects. See the Corrections Policy for the full process.

What is the MAP Verification Ledger?

The ledger is an append-oriented table operated by MAP. Hashed entries are chained to one another. Older entries that have no hash are not part of the chain. MAP runs a daily continuity check and does not publish its detailed results, and MAP does not publish the data needed to recompute the hashes, so continuity is MAP's own report and readers cannot yet recompute it from published data. MAP's practice is to add a new entry rather than edit an earlier one, so a correction is a new entry. MAP operates the ledger itself, and the daily continuity check described above reports the exceptions and gaps it has found. The ledger does not yet link a correction to the entry it corrects. The running total is available at https://mediaalertpress.com/wp-json/map/v1/ledger/stats.

Looking for organizational intelligence?

MAPIOS matches customer-defined organizations, markets and topics against public news sources when you run a scan, and lists matches with source, date and the matching term. Everything beyond keyword matching is planned.

Explore MAPIOS →