PUBLIC CONTINUITY

Continuity Pack

If the platform disappears, the public record should still have a map.

QUICK ANSWER

In one sentence

The Continuity Pack points to the public files another reader or maintainer can preserve offline: the first-edition Library, evidence map, source and claim registers, correction records, Toolkit, sitemap, RSS, and exact-byte continuity manifest.

THE HASH PROVES WHICH BYTES THE MANIFEST DESCRIBES. IT DOES NOT PROVE THE CONTENT IS TRUE.

This page links only to public artifacts. Repository memory, internal reports, private provenance, and recursive prompts are intentionally absent from the public continuity surface.

KEEP THESE

Public artifacts another person can open without the repository.

Field Manual

Resilience, agency, archive, and handoff principles.

Receipt Toolkit

Nine local forms with JSON import/export and Markdown templates.

Source Ledger

Human-readable stable Source IDs.

Source Ledger JSON

Machine-readable public source registry.

Source Ledger CSV

Portable tabular source registry.

Correction Ledger

Correction states, propagation workflow, and publication records.

Library

Human index of evidence-complete publications.

Library Index JSON

Public machine-readable publication index.

Continuity Manifest

SHA-256 and byte size for public release artifacts.

robots.txt

Public crawler instruction artifact.

sitemap.xml

Public URL map.

Claim Register

Persistent public Claim IDs with source dependencies, truth boundaries, and correction records.

Claim Register JSON

Machine-readable public claim registry.

Topics

Eight substantial first-edition topic clusters.

RSS Feed

Portable publication discovery for all 24 first-edition articles.

Evidence graph exports

Keep the human map and machine projections together. The graph records declared relationships; it does not certify that the underlying claims are true.

THE OUTAGE TEST

MEMORY THAT EXISTS ONLY BEHIND ONE ACCOUNT IS RENTED MEMORY.

Save the public ZIP when a durable local copy matters. Keep the manifest with it. Recompute hashes when you need to verify that the bytes still match this release. Then inspect the content anyway. Fixity is not truth.

Read the outage article Read the archive article

Trace the first edition through the Evidence Map

Download the public evidence bundle