One-sentence brief
A future scenario can borrow the authority of a familiar institution merely by displaying its URL. Explicit lineage prevents that visual association from being mistaken for evidentiary support.
INTERNATIONAL EVENT LITERACY
How to trace each fictional scenario family to one supplied source start point without treating that source as endorsement, corroboration, calibration, or prediction.
ORIENTATION
A future scenario can borrow the authority of a familiar institution merely by displaying its URL. Explicit lineage prevents that visual association from being mistaken for evidentiary support.
WORKING BRIEF
The workbook supplies nineteen distinct URLs and source notes. WIP.31 preserves those relationships and assigns each URL a stable source ID. The URL shows where review begins; it does not prove that the linked institution authored, endorsed, or calibrated any scenario.
Several baseline URLs are reused across dozens of scenario families. Reuse increases source concentration, not corroboration. Every track mapped to the same source remains part of one origin chain until independent evidence is added.
A climate, conflict, cyber, energy, health, or governance publication may support a broad domain baseline while providing no support for a specific fictional trigger, annual probability, named consequence, or date. Those propositions must be reviewed separately.
Source IDs, review IDs, track IDs, scenario IDs, source rows, year anchors, and deep links allow corrections to propagate without changing the preserved workbook.
Public wording must say that the source was used as a baseline start point. It must not imply that the institution predicts the scenario, agrees with the probability, or recommends the consequence path.
COMPLETE DOSSIER
Terms are defined for this site’s evidence method, not as universal legal or clinical definitions.
| Question | Acceptable treatment | Prohibited implication |
|---|---|---|
| Source URL | Describe as a baseline start point with stable source ID. | Institutional endorsement or prediction. |
| Repeated use | Count as one shared origin chain. | Multiple independent confirmations. |
| Source note | Preserve as supplied and review separately. | Proof that every scenario detail follows from the source. |
| Correction | Update the sidecar review record and dependent routes. | Rewrite the preserved workbook silently. |
Does the page distinguish publications from independent origins?
Pass condition: One URL reused across tracks remains one origin.
Is broad baseline support separated from specific scenario support?
Pass condition: Premise, probability, indicators, and consequences have separate states.
Could readers infer that the linked institution authored the scenario?
Pass condition: The non-endorsement boundary is visible beside the URL.
Can a source relationship be corrected by stable ID?
Pass condition: Source and track records have durable identifiers and dependencies.
RESEARCH EDITION
This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.
CONTINUE