R001

One reviewed release of EZA-001. The release package is the technical source of truth for every value below; this page presents it without restatement.

Specification: EZA-001
Specification version: 0.1.0-draft.7
Release: R001
Frozen candidate: EZA-001-R001-rc.9
Wire version: 0.1.0-draft.7
Maturity: EXPERIMENTAL
Licence: Apache-2.0
Publication state: PUBLIC ON THIS PROPERTY AS EXPERIMENTAL
Publication date: No exact date recorded

Publication here means these exact bytes are delivered by this property and the owner approved public release at EXPERIMENTAL maturity. It is not formal release acceptance, not an unqualified all-gates pass, and not certification of any kind.

Basis: Owner approval for public release as EXPERIMENTAL, recorded 2026-09-16 (UTC), together with an anonymous hosted-download run against https://eziah.dev in which every declared artifact matched its expected byte count and SHA-256.

Source: currentGates "final owner publication approval" and "eziah dev wiring and acceptance" in this release record (unsigned external records).

No exact publication date is recorded in this release record. A candidate revision date, a signing date or a build timestamp is not a publication date, and none is substituted here. A missing date is not evidence that publication has not happened.

The frozen candidate archive, its signed manifest and the detached signature are immutable. External publication records and the explanations on this website can receive later sourced updates without changing one frozen byte.

Candidate archive SHA-256 / sha256Pointer checked, bytes not hashed here

3062213046b50db71ddbf13160a9711a25b2e8b1dd882a3bf35e007958b22e39

Signed manifest SHA-256 / sha256Bytes hashed against declaration

fc44b015cbf152aef4e4cc25bc0bdc6d58f6763a0af871b81795de04e32f8f3e

Candidate archive: This file is hosted rather than committed, so this build checked only that its declared digest, size, and hosted location agree with the committed pointer. Its delivered bytes are hashed by the separate hosted-download check.

Signed manifest: This build hashed the published bytes and matched the digest and size this release declares. That is a byte check against the release's own declaration; it is not a signature verification. This file is covered by the release signature directly: the detached signature is over these exact bytes. That signature was verified separately, on another machine, and is reported as its own recorded result.

Reproduction

Published verbatim

Everything needed to re-run this release's evaluation is published by the release itself. No command, version, or expected value is authored by this site. Three activities are separate and are not interchangeable: verifying the bytes you downloaded, running the candidate's own reference tests, and integrating the reference into an agent's environment.

VERIFY-PUBLICATION.mdThe prepared read-only check for the downloaded bytes, published verbatim.
candidate/reproduction/README.mdThe candidate's own procedure for running its controlled suite, including expected result classes and what to do with a failure.
candidate/reproduction/VERIFY.mdThe candidate's own release-verification notes for a reviewer.
SHA256SUMS.txtTransfer checksums for the separately downloaded files.

Environment requirements

An already trusted Minisign installation and trusted Python 3.9+ for the read-only archive check.
Python 3.11+ for the candidate's behavioural reproduction, which is a separate operation.
The public key and expected digests obtained through an independently authenticated Eziah channel. A key or digest shipped only in this kit does not establish the publisher’s identity.

Procedure

Verify downloaded bytesConfirm that the files you hold are the published files: transfer checksums, the manifest signature and trusted comment, and the full archive and extracted-candidate inventory. This establishes package authenticity only; it runs no release code.
Reproduce the reference testsRun the candidate's own controlled suite from its frozen reproduction procedure, in a disposable directory with a new result directory. Commands are published verbatim from the candidate; none is authored by this site.

01
Verify transfer checksums
Verify downloaded bytes
Place the separately downloaded release files in one working directory and run this from there. SHA256SUMS.txt names the handoff files it covers; it is transfer-integrity information and not a signature over them.
Command
```
shasum -a 256 -c SHA256SUMS.txt
```

Verify the manifest signature and trusted comment

Verify downloaded bytes

Command

minisign -V -P "RWRS1+wI01bGz7h6vYSR4m9shqB2/q8FiIpbY8tSgDQnhNZ4qzp+0mSA" -m MANIFEST.json -x MANIFEST.json.minisig

03
Verify all 125 archived and extracted candidate files
Verify downloaded bytes
Run the prepared read-only check published verbatim in VERIFY-PUBLICATION.md. It executes only standard-library Python, refuses to overwrite an existing verification destination, and does not execute or import downloaded candidate code.
04
Create a runtime outside the extracted release
Reproduce the reference tests
Published verbatim in the candidate's reproduction/README.md. Install the two pinned dependencies only if you choose to use that environment.
Command
```
python3 -m venv "$HOME/EZA-rc9-review-runtime"
"$HOME/EZA-rc9-review-runtime/bin/python" -m pip install -r "/absolute/path/EZA-001-R001-rc.9/reproduction/requirements.txt"
```

Verify the release, then run the controlled suite

Reproduce the reference tests

Published verbatim in the candidate's reproduction/README.md. Use the expected manifest digest from the handoff, not a digest invented by this command or accepted only because the download contains it. Set the paths to your extracted package and a NEW result directory.

Command

EZA_RELEASE="/absolute/path/EZA-001-R001-rc.9"
EZA_RESULTS="$HOME/EZA-rc9-review-results-001"
EZA_EXPECTED_MANIFEST="REPLACE_WITH_THE_64_CHARACTER_EXPECTED_DIGEST"
"$HOME/EZA-rc9-review-runtime/bin/python" -B "$EZA_RELEASE/evaluator/verify_release.py" --expected-manifest "$EZA_EXPECTED_MANIFEST"
"$HOME/EZA-rc9-review-runtime/bin/python" -B "$EZA_RELEASE/reproduction/run.py" --expected-manifest "$EZA_EXPECTED_MANIFEST" --out "$EZA_RESULTS"

Notes

Expected: Minisign verifies both signatures and the check reports all 125 archived and extracted files matching.
A failed check blocks package execution; do not regenerate hashes or edit the signed candidate to make it pass.
Do not count packaging checks as new behaviour tests or new independent probes.
From the candidate's reproduction/README.md: “The runner refuses an existing output directory. Keep each run; use a new result directory for a new run. It verifies the input before and after testing.”
From the candidate's reproduction/README.md: “The total is 394 behavior/regression groups plus 26 schema groups… Every required group must pass.”
From the candidate's reproduction/README.md: “If a case fails, preserve the result and input digest… Do not edit expected results or recreate a spent domain to obtain a pass.”
Reproducing these reference tests is a separate activity from integrating the reference into an agent's environment. The integration path, its reader trial and its own limits are published on /developers.

Integrating, rather than reproducing

Separate activity

Running the tests above establishes that this release behaves as its own records state. It does not integrate the reference into an agent's environment, and it establishes nothing about a system you build. The integration path — its operator setup, its operating-system boundary assumptions, its own reader-trial results and its own limits — is published separately on Developers. That material is EXPERIMENTAL integration material and sits outside the frozen release manifest's signature scope.