# Zincrom Sanitized Empirical Evidence Snapshot

**Evaluation cutoff:** 2026-07-25  
**Hardware envelope:** One Oracle OCI A1 instance (4 Arm Neoverse-N1 cores, 24 GiB RAM)  
**Reference lineage:** `llama.cpp` commit `6e9007ae6` (build 9641 lineage)

This is the only tree approved as input to the public GitHub release. It contains the canonical paper and article, public metadata, evidence authorities, sanitized result summaries/manifests, and principal evaluation harnesses. It excludes repository history, model weights and extracted shards, private development-only material, publication operations, local paths, infrastructure identifiers, caches, build products, and active Runtime 2.0 files.

## Build and verify

From the repository root:

```bash
SOURCE_DATE_EPOCH=1784937600 bash docs/publication/build_sanitized_snapshot.sh
cd docs/publication/sanitized_snapshot
sha256sum -c SNAPSHOT_MANIFEST.sha256
```

The builder consumes only literal paths in `SNAPSHOT_ALLOWLIST.txt`. It permits the listed publication artifacts to come from the current working tree, but requires every other allowlisted input to match `HEAD`. `BUILD_INFO.json` records the curated-build policy without exposing the private source commit, worktree state, or excluded-path inventory.

## Contents

- `docs/publication/paper/`: canonical LaTeX sources, six code-generated figures, and compiled PDF.
- `docs/publication/blog/index.html`: canonical standalone website essay.
- `README.md`: repository landing page generated from the canonical `docs/publication/GITHUB_README.md` source.
- `docs/publication/`: model card, weight metadata, and claim-evidence matrix.
- `docs/`: evidence authorities.
- `results/`: canonical summaries and manifests for routing, split-path overhead, and equivalence gates.
- `zincrom_nif/` and `scripts/`: selected implementation and harness sources supporting the audited claims.

Internal approval records, release workplans, revision logs, Zenodo operational tooling/state, and the builder itself are intentionally not distributed inside the snapshot.

## GitHub publication boundary

Create the GitHub artifact as a fresh repository from this directory. Do not push the development repository or inherit its Git history because that history is outside the approved release scope. Re-run the builder and verify `SNAPSHOT_MANIFEST.sha256` immediately before initializing the clean release repository.

The three included experiment manifests are sanitized copies. Their local `command` and `model.path` fields are removed after copying; hashes, protocols, hardware class, timestamps, and measured results remain intact.

## Reproduction boundary

Re-running the benchmarks requires the historical ARM64 toolchain, a compatible real NIF build, the pinned `llama.cpp` lineage, and locally acquired GGUF files under their upstream licenses. Those weights and executables are not included. Harness entry points are preserved for inspection; command-line invocation must be verified by the maintainer against each script and the historical environment before use.

The included manifests and summaries allow review of the reported evidence without claiming that the snapshot alone recreates the original OCI environment.