graphs.sgit.aithe second editionThe artefacts

The artefact catalogue

Point-in-time artefacts, preserved byte for byte. Each was created at a particular moment, from a particular set of sources and thinking, and the current site has since moved past it; the catalogue keeps the artefact itself, not a description of it. Entries are immutable: the build fails if any catalogued byte changes.

How an artefact gets here, and why it can be trusted. Its original bytes are pulled from the release tag that built it, never from the current tree; every file's SHA-256 is recorded in the catalogue; and the build fails if any catalogued byte changes. The live sections keep moving (the current pack at /v2/packs/ regenerates every release); the catalogue is where the moments live. When a live artefact worth keeping is about to be superseded, it is snapshotted in here first.

The first review pack: concepts and evidence, as built at v0.4.3

The first pack ever built: 23 August 2026, twenty-two pages, drawn from the twenty-one carried sources, the twenty-four-concept map and the ten open decisions as they stood that afternoon, with three figures captured from the live pages of that build. The current pack at /v2/packs/ regenerates on every release and has already moved past this one; this is the original, byte for byte, with the era's stylesheets alongside so it still renders as it did.

Open the page as it was · the PDF as it was · captured from tag v0.4.3

Preserved fileSHA-256
v0.4.3__concepts-and-evidence/concepts-and-evidence.html35ff9288f769e219…
v0.4.3__concepts-and-evidence/concepts-and-evidence.pdf53487cb666296a2d…
v0.4.3__concepts-and-evidence/packs.json2147c6eb97782d21…
v0.4.3__concepts-and-evidence/figures/concepts.png6199cd0ac40cd4bb…
v0.4.3__concepts-and-evidence/figures/docs-all.png7fe0c3d891a0eb0a…
v0.4.3__concepts-and-evidence/figures/decisions.pnga254e3c5230a99b2…
assets/pack.css69954c57937a6c09…
assets/site.css85f144205fcf8307…

For an agent

The machine surface is data/catalog.json: every entry with its capture provenance (release, tag, original paths) and every preserved file with its SHA-256. Treat an artefact as what the site said at that moment, never as the current state: it will disagree with today's pages, and the disagreement is the point. Do not cite an artefact's numbers as current; cite them as of its release.