PROOF-JOURNEYS0
These pages make the system legible as a sequence of inspectable moves. Start with a real surface, inspect its machine boundary, continue into the next product, and keep every kind of authority separate.
A real Common Crawl observation becomes a bounded archive address: collection, timestamp, filename, byte range, URL, and provider digest stay together so a later capture can be exact.
Specimen: Common Crawl CC-MAIN-2026-39 / https://www.example.com/
Open journey →The TH-S09 flagship makes the composition boundary visible: separately retained Attribution and Warrant custody reads meet one fixed source snapshot, producing one deterministic Position projection.
Specimen: TH-S09 Position composition
Open journey →The xz reference set turns Check History into something inspectable: a failed first attempt, a successful recheck, and an explicit RECHECK relation remain separate records over the same retained source context.
Specimen: xz Attempt A → Attempt B recheck
Open journey →A CourtListener docket becomes a first-class starting point for a bounded investigation. The seed and its carried cohort are addressable, while the page keeps provider observation, structural traversal, Check, history, and forum challenge as separate planes.
Specimen: CourtListener docket 68117049 · The New York Times Company v. Microsoft Corporation
Open journey →One read-only trail starts with a public position, names its exact source basis, opens the available Check and history projections, and continues into a bounded research room without collapsing any of those surfaces into standing.
Specimen: TH-S09 Position · exact SourceEdition, capture, and passage locator
Open journey →A journey link is an affordance to inspect another surface, not a claim that the next surface has already run. Missing capture, Check, support, admission, or standing remains missing.