Three layers of provenance
Evidence: historical claims have source IDs and stated limitations. Editorial source: articles are Markdown maintained through Git revisions. Published artifact: the static release includes file-level checksums.
Release integrity
Each build includes manifest.json, listing file paths, byte counts and SHA-256 values. Once the manifest is independently preserved, differences can help detect file alterations. Checksums do not establish historical truth or validate a document before acquisition.
Reproducible publishing
The GitHub source ZIP contains a Python generator, content files, validation script and a build workflow. A published release should also record its Git commit identifier to connect the deployed artifact to its source revision.
Evidentiary gap
The historical essays have not been reconciled against an exhaustive manuscript collection. Edited translations and scholarly summaries are clearly distinguished from original manuscripts. This is a sourced educational archive, not a critical edition of every surviving record.