Release

    Build record: bytes and manifest binding
    EZA-001

    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.

    Package

    Source of truth

    The downloadable package is authoritative. Where this site and the package disagree, the package governs.

    Specification
    EZA-001
    Release
    R001
    Specification version
    0.1.0-draft.7
    Maturity
    EXPERIMENTAL
    License
    Apache-2.0
    Publication state
    PUBLIC ON THIS PROPERTY AS EXPERIMENTAL
    Publication date
    No exact date recorded
    Files in candidate archive
    125 (124 bound through the signed inventory)

    This build hashed the published bytes of 26 declared artifacts and checked 1 artifact only against its committed pointer, because those bytes are hosted rather than committed. The hosted bytes are hashed by the separate delivery check, and the manifest signature was verified elsewhere and is reported as its own recorded result. Build-time hashing of committed release bytes: source bytes, committed published copies, and binding against the pinned signed-manifest inventory. This record is not a signature verification, not a hosted-download result, not a review outcome, and not an approval.

    archive

    Frozen candidate archive EZA-001-R001-rc.9.zip

    EZA-001-R001-rc.9.zip · 14.8 MB · application/zip

    Container checksum only — the container's own hash is not in the signed manifest

    The container's own SHA-256 is recorded externally, not in the signed manifest. The signature reaches the archive's contents only through the manifest's 124 inventory entries; the manifest itself is signed directly.

    Pointer checked, bytes not hashed here

    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.

    Download

    The signature authenticates the manifest and its trusted comment, not the ZIP container. The archive holds 124 inventory-bound candidate files plus the signed manifest itself: 125 files in total.

    SHA-256 / sha256Pointer checked, bytes not hashed here
    3062213046b50db71ddbf13160a9711a25b2e8b1dd882a3bf35e007958b22e39

    Inside the candidate archive

    Archive members

    File counts taken from the 124 entries of the pinned signed manifest inventory. They count files inside the candidate archive, not separately downloadable artifacts and not test results.

    • (archive root)16
    • evaluator/3
    • evidence/1
    • history/43
    • licenses/4
    • reference-implementation/7
    • reproduction/8
    • schemas/9
    • tests/33

    Signing and scope

    Signed manifest
    Frozen candidate
    EZA-001-R001-rc.9
    Wire version
    0.1.0-draft.7
    Files in candidate archive
    125
    Files bound through the inventory
    124
    Signer key id
    CFC656D308ECD752
    Signature scope

    Exact MANIFEST.json and trusted comment only; candidate files bound through manifest hashes. External publication metadata and review records are not covered by this signature.

    Eziah EZA-001 R001; candidate EZA-001-R001-rc.9; MANIFEST.json

    manifest

    Signed release manifest MANIFEST.json

    MANIFEST.json · 20.0 KB · application/json

    Signed directly, or the detached signature over the signed bytes

    Signed directly. The detached signature is over these exact manifest bytes and their trusted comment. The 124 entries of its own inventory bind the candidate files through their exact SHA-256 hashes; the manifest's own hash is not, and need not be, listed inside itself.

    Bytes hashed against declaration

    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.

    Download

    The exact manifest covered by the detached signature. Its 124 inventory entries bind the frozen candidate files through their exact SHA-256 hashes.

    SHA-256 / sha256Bytes hashed against declaration
    fc44b015cbf152aef4e4cc25bc0bdc6d58f6763a0af871b81795de04e32f8f3e

    signature

    Detached Minisign signature MANIFEST.json.minisig

    MANIFEST.json.minisig · 324 B · text/plain

    Signed directly, or the detached signature over the signed bytes

    The detached signature used to verify the manifest bytes and the trusted comment. It is verification material, not an inventory-bound payload.

    Bytes hashed against declaration

    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 the detached signature used to verify the manifest and its trusted comment. Its hash identifies that verification material; it is not an inventory-bound candidate payload.

    Download

    Signature over the manifest and over its trusted comment. It does not cover the external acceptance metadata or the review evidence.

    SHA-256 / sha256Bytes hashed against declaration
    bc6e7808a6e2cfc9fecfa790d6e69bed85ff5712015d892a0e667004a2d6144e

    public-key

    Signer public key eziah-release-2026-01.pub

    eziah-release-2026-01.pub · 113 B · text/plain

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    Public key only. No private key or password is required to verify, and none is published here. The same key and key id are also published in the owner's own off-site statement recorded under signing and scope; that is an owner self-statement, not third-party certification of identity.

    SHA-256 / sha256Bytes hashed against declaration
    df3a3e0aa9f6368906f7004083e8abab76e8cb98b603ab0e9146e68abbdf0311
    Owner-published signing key

    Signing-key owner statement — Montrel Hutto, LinkedIn.

    Published by the owner through his established LinkedIn account, separately from eziah.dev.

    https://www.linkedin.com/posts/montrelhutto_eziah-release-signing-public-key-owner-activity-7506110752932634625-G9ex
    Published key id
    CFC656D308ECD752
    Published public key
    RWRS1+wI01bGz7h6vYSR4m9shqB2/q8FiIpbY8tSgDQnhNZ4qzp+0mSA

    The post text and a screenshot supplied by the owner state the same public key and key id as this release. Automated retrieval of the post by the reviewer was blocked, so the content was read from the owner-supplied screenshot and text rather than fetched independently.

    • An owner self-statement through an established account, not third-party certification of identity.
    • Content read from owner-supplied material; independent automated retrieval of the post was blocked.
    • Establishes a second owner-controlled place where the key is published; it does not authenticate the account holder.
    Candidate status at freezeHistorical, not current
    Candidate status
    CANDIDATE_PENDING_INDEPENDENT_REVIEW_SIGNATURE_AND_SITE_ACCEPTANCE
    Owner signing status
    NOT_SIGNED
    Production readiness
    NOT_ESTABLISHED
    Maturity at freeze
    EXPERIMENTAL
    Profile
    local-object-v1
    Revision scope
    DOCUMENTATION_AND_RELEASE_METADATA_ONLY
    Revision date
    2026-09-16

    These fields are the candidate's own status at the moment its bytes were frozen, carried verbatim from candidate/IDENTITY.json and preserved unchanged. They describe that moment — before signing and before publication — and they are not the current state of this release. Current publication and gate states are on the release overview.

    What this historical record did not establishHistorical record

    Source: SIGNATURE-VERIFICATION.json — not_claimed, recorded at signature verification.

    • independent implementation
    • authenticated execution provenance
    • general production readiness
    • website acceptance
    • public deployment
    • third-party certification of the signer's identity

    These statements are preserved unchanged: they describe what that signature-verification record did not establish when it was made. They are not a current statement about this property. Later records address some of them separately — an anonymous hosted-download run recorded delivery of every declared artifact from https://eziah.dev, and the owner approved public release as EXPERIMENTAL. That delivery record is explicitly not formal release acceptance, and website acceptance, independent implementation, authenticated execution provenance and general production readiness remain not established. Current gate states are below.

    Verification checkpoints

    Recorded after signing

    These records were made after the manifest was signed. They are appended, never merged into the frozen candidate, and the manifest signature does not cover them.

    signature-verificationNot covered by the manifest signature

    Eziah-manifest-signature-verification/1

    Manifest signature
    PASS
    Comment signature
    PASS
    Full candidate inventory (125 regular files)
    PASS
    Tampered manifest rejected
    true
    Tampered comment rejected
    true
    Tampered signature rejected
    true

    Environment

    Python
    3.12.14 (main, Aug 25 2026, 14:00:49) [Clang 22.1.3 ]
    Platform
    Linux-6.18.44-x86_64-with-glibc2.39
    cryptography
    46.0.0
    Minisign CLI used
    false

    Evidence source: Ed25519 verification of the Minisign ED signature over BLAKE2b-512(manifest), and of the comment signature over signature bytes plus trusted comment UTF-8 bytes.

    • Owner reported encrypted key on external drive and separately stored password; physical custody and backup recovery not independently verified.
    • Key supplied by the owner in this conversation. Public distribution still needs an independently authenticated owner channel.

    verification

    SIGNATURE-VERIFICATION.json

    SIGNATURE-VERIFICATION.json · 2.2 KB · application/json

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    Recorded signature verification, including its negative controls and what it does not claim.

    SHA-256 / sha256Bytes hashed against declaration
    c65d1de87a0ebd46cf308e2cf1fdd5a9c79f3928f69514e3a0e6542702117172
    post-signing-checkpointNot covered by the manifest signature

    SECOND_MAC_SIGNATURE_AND_INVENTORY_VERIFICATION_PASS_WEBSITE_ACCEPTANCE_PENDING

    listed handoff checksums
    PASS
    listed handoff files
    10
    manifest signature
    PASS
    trusted comment signature
    PASS
    manifest pin
    PASS
    archive file inventory
    PASS_EXACT_125
    extracted file inventory
    PASS_EXACT_125
    candidate code executed
    false
    behavior suite rerun
    false

    Environment

    host from prompt
    Montrels-MacBook-Air
    account from prompt
    montrelhutto
    minisign
    0.12
    python
    3.9.6
    os version
    NOT_CAPTURED
    architecture
    Homebrew arm64 bottle shown in owner-supplied install log; no separate uname capture

    Evidence source: Owner-pasted Terminal output in this conversation; not externally attested execution or a complete raw session export.

    • Separate-Mac fresh-directory verification, not proof of a newly installed or uncompromised machine.
    • Handoff checksums checked listed entries only; no claim of exact outer-folder inventory.
    • Signature covers manifest and trusted comment; external metadata remains unsigned.
    • No behavioral score added. Existing independent review qualifications remain in force.

    verification

    EZA-001-R001-Post-Signing-Checkpoint-001.json

    EZA-001-R001-Post-Signing-Checkpoint-001.json · 4.6 KB · application/json

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    Later second-machine verification checkpoint. Recorded as an unsigned external record.

    SHA-256 / sha256Bytes hashed against declaration
    b32f5415415ad4591bf2d9beea873d3c911c9a15093c9a7585b08538ee25b270

    Independent review

    Unsigned record
    Verdict
    REQUIRED_ENFORCEMENT_AND_REPRODUCTION_GATES_PASS_WITH_EXPLICIT_WRAPPER_EXCEPTION
    All gates passed unqualified
    false

    Findings

    IR8-001
    CLOSED_FOR_RC9_ONLY
    IR7-001
    RC8_CLOSURE_PRESERVED_NO_RC9_REGRESSION_OBSERVED
    IR9-001
    Original wrapper FAIL preserved; narrow explicit operator exception admitted review execution only.
    Preserved gate failureFAIL_PRESERVED_WITH_EXPLICIT_NARROW_EXCEPTION

    Wrapper inventory

    Operator exception
    Kind
    explicit-operator-wrapper-exception/1
    Recorded
    2026-09-16T03:58:47.418250+00:00
    Original gate
    FAIL
    Scope
    Execution admission: AUTHORIZED_BY_NARROW_EXCEPTION. Signature or publication authorized: false.

    Authorized: proceed only if the sole discrepancy is the unlisted regular file `.DS_Store` outside both frozen candidate directories, and every inventoried wrapper file, probe, plan, and candidate file verifies exactly. Leave it untouched. Record its path, size, and SHA-256, preserve the original failed wrapper-inventory result, and document this explicit operator exception separately. Do not relabel the original gate as PASS, modify an inventory, or extend this exception to any other discrepancy. Continue the prescribed review and preserve all first-run results. Signing and publication remain unauthorized.

    Review process limits
    • Out-of-scope AGENTS.md filename search disclosed; no matches/content reported.
    • Full raw session export unavailable; early history reconstructed.
    • Comparison/source-map false flags and assessment patch-parser errors retained alongside corrections.
    • Local tool recordings do not authenticate every session event.

    Gate states now

    With the basis for each state

    Each state below is current, and names what it rests on. A gate settled by later evidence or by an owner decision, a gate blocked by a condition outside this release, and a gate simply not yet run are different things and are not merged. Owner decisions are recorded as owner decisions: they are not third-party certification.

    clean machine signed download verificationSatisfied by later evidence

    PASS on a second machine: manifest signature, trusted comment signature, manifest pin, and an exact 125-file inventory of both the archive and the extracted candidate.

    Post-signing checkpoint 001, run by the owner on a second Mac with Minisign 0.12 and Python 3.9.6. The evidence is owner-pasted terminal output rather than externally attested execution, and no candidate code was executed and no behaviour suite was re-run.

    Prepared record stated: NOT_RUN

    eziah dev wiring and acceptanceSatisfied by later evidence

    PASS on the deployed production origin: every declared artifact, including the archive at its stable canonical address, was downloaded anonymously and matched its expected byte count and SHA-256.

    An unauthenticated hosted-download run against https://eziah.dev delivered all 27 declared artifacts byte-exact — 15 against the signed manifest inventory, 12 against the release declaration alone — and the stable archive address returned HTTP 200 with no redirect and the pinned digest. This establishes delivery of these bytes by this property; it is not formal release acceptance and does not authenticate the signing key.

    Prepared record stated: NOT_RUN

    independent public key trust channelAdvanced by an owner statement

    OWNER STATEMENT PUBLISHED OFF-SITE: the signing public key and key id are published by the owner through his established LinkedIn account, separately from eziah.dev. This is an owner self-statement, not third-party certification of identity.

    Signing-key owner statement — Montrel Hutto, LinkedIn. The post text and a screenshot supplied by the owner state the same key (RWRS1+wI01bGz7h6vYSR4m9shqB2/q8FiIpbY8tSgDQnhNZ4qzp+0mSA) and key id (CFC656D308ECD752) as this release. Automated retrieval of the post by the reviewer was blocked, so the content was read from owner-supplied material rather than fetched independently. A reader can now obtain the key from a place the owner controls that is separate from this site; the account holder's identity is not certified by any third party here.

    Prepared record stated: NOT_PUBLISHED

    private key backup recoveryConfirmed by the owner

    OWNER-CONFIRMED COMPLETE: the owner reports signing-key backup is in place.

    Carried forward as owner-confirmed complete at the owner's statement. The confirmation is the owner's own; physical custody and a recovery drill were not independently observed here.

    Prepared record stated: NOT_CONFIRMED

    final owner publication approvalApproved by the owner

    OWNER-APPROVED FOR PUBLIC RELEASE AS EXPERIMENTAL: the owner approved EZA-001 R001 for public release, retaining its qualified review, the disclosed wrapper-inventory failure, the operator exception, and every stated limitation.

    Owner approval given in writing on 2026-09-16 (UTC), recorded here as the owner's own decision. The approval keeps the release at EXPERIMENTAL maturity and changes no review outcome, signature scope, or frozen artifact. It is not third-party certification and does not convert any qualified finding into an unqualified pass.

    Prepared record stated: PENDING

    publication and indexingAuthorised by the owner

    INDEXING ENABLED: the site is live at https://eziah.dev, pages are delivered with index, follow, robots.txt permits crawling and declares the sitemap, and https://eziah.dev/sitemap.xml lists the canonical public pages.

    The owner authorized production search indexing on 2026-09-16 (UTC). Indexing is enabled only for a production build through the build-time gate (VITE_ALLOW_INDEXING=true with the canonical origin https://eziah.dev); preview and development builds continue to emit noindex, nofollow, disallow crawling, and publish no sitemap. Indexing enabled means crawling is permitted and the pages are submittable; it is not evidence that any search engine has indexed them.

    Prepared record stated: NOT_PERFORMED

    Gate states at preparation

    Historical record, not current

    These are the states the frozen acceptance record declared when it was prepared. They are preserved unchanged as history and do not describe the present. Current states are above.

    clean machine signed download verification
    NOT_RUN
    eziah dev wiring and acceptance
    NOT_RUN
    independent public key trust channel
    NOT_PUBLISHED
    private key backup recovery
    NOT_CONFIRMED
    final owner publication approval
    PENDING
    publication and indexing
    NOT_PERFORMED

    Records published with this release

    Downloadable individually

    These files are served separately from the archive. The checksum file is transfer information; the acceptance, handoff, verification and checkpoint records are unsigned external records that the manifest signature does not cover.

    checksums

    SHA256SUMS.txt

    SHA256SUMS.txt · 952 B · text/plain

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    Transfer integrity information for the listed handoff files. It is not a signature over the external metadata.

    SHA-256 / sha256Bytes hashed against declaration
    b9485aca0fe2d6a691ac9a7c3c6c05ba4a8e922151e7de4b4b19b6f8418f163c

    Transfer checksums for the separately downloaded files.

    metadata

    RELEASE-ACCEPTANCE-PREPARED.json

    RELEASE-ACCEPTANCE-PREPARED.json · 10.2 KB · application/json

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    Prepared acceptance metadata. Unsigned: the manifest signature does not cover this record.

    SHA-256 / sha256Bytes hashed against declaration
    2f698cfa42acf5e1e062f997db73fed12d644e75e70d682e99c58cc8dc7863bd

    The unsigned external acceptance record, as prepared.

    verification

    HANDOFF-VALIDATION.json

    HANDOFF-VALIDATION.json · 376 B · application/json

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    Preparation-time validation record. Its PENDING fields describe its state at preparation, and are preserved unchanged.

    SHA-256 / sha256Bytes hashed against declaration
    73dfc04d9e9d90660d7a3690c6e483ae8b019ea2b00d8a57f4d481c201756077

    The recorded handoff validation result.

    verification

    SIGNATURE-VERIFICATION.json

    SIGNATURE-VERIFICATION.json · 2.2 KB · application/json

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    Recorded signature verification, including its negative controls and what it does not claim.

    SHA-256 / sha256Bytes hashed against declaration
    c65d1de87a0ebd46cf308e2cf1fdd5a9c79f3928f69514e3a0e6542702117172

    The recorded signature-verification result.

    verification

    EZA-001-R001-Post-Signing-Checkpoint-001.json

    EZA-001-R001-Post-Signing-Checkpoint-001.json · 4.6 KB · application/json

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    Later second-machine verification checkpoint. Recorded as an unsigned external record.

    SHA-256 / sha256Bytes hashed against declaration
    b32f5415415ad4591bf2d9beea873d3c911c9a15093c9a7585b08538ee25b270

    A dated verification event recorded after signing.

    verification

    Verification instructions VERIFY-PUBLICATION.md

    VERIFY-PUBLICATION.md · 8.4 KB · text/markdown

    Unsigned external record — not covered by the manifest signature

    Bytes hashed against declaration

    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 unsigned external material: the manifest signature does not cover it.

    Download

    The prepared verification recipe, published verbatim as supplied.

    SHA-256 / sha256Bytes hashed against declaration
    718a82a568be894186557e004fbe461b3c98176e31b5b19e8bd809d8524485d5

    The prepared read-only verification procedure.

    Inspection surfaces