About All levels 1 minute read Updated 2026-06-26 UTC

Source preservation and integrity

How the original Markdown reports are retained, hashed, categorized, rendered, and included in the distribution package.

Research statusArchive policy Publication statePublished Reviewed byMichael Kappel Source reports3

Preservation promise

The distribution includes every supplied report in /docs under its original filename. Curated content is additive: it does not replace, rewrite, or silently normalize the archived source.

Manifest fields

Each report entry in /docs/manifest.json contains:

  • stable URL slug;
  • original filename;
  • editorial title;
  • category and maturity label;
  • short archive summary;
  • byte size;
  • SHA-256 digest.

Verification

pseudocode
PROCEDURE verify_archive(docs_directory, manifest)
    listed <- SET(manifest.filename)
    actual <- SET(MARKDOWN_FILES(docs_directory))

    REQUIRE listed == actual

    FOR each entry IN manifest
        bytes <- READ_BINARY(docs_directory + entry.filename)
        REQUIRE LENGTH(bytes) == entry.size
        REQUIRE SHA256(bytes) == entry.sha256
    END FOR

    RETURN VERIFIED
END PROCEDURE

The included validation tool performs this comparison and fails on missing, unlisted, size-mismatched, or digest-mismatched reports.

Display versus source

The research reader renders Markdown for convenience. Very large embedded data-URI figures are replaced in the web view with a source-figure marker to avoid loading megabytes of inline data. The original downloaded file remains byte-for-byte intact.

Future additions

Add new reports as new manifest entries. Do not reuse a slug for different bytes. If an updated edition should supersede an earlier report, retain both and record their relationship in metadata or an archive changelog.

Source reports used for this guide

These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.