EZA-001 Developer Trial Package 001 — experimental public developer evaluation
Publication Gate 001 / online-distribution-001 / integration v1

The preceding Publication Gate 001 staging snapshot was signed by the release
owner, and its Minisign signature was verified with Eziah key CFC656D308ECD752.
This final documentation correction requires a fresh signature on the revised
RELEASE-MANIFEST.json. Recipients must verify the signature for the exact manifest
received before trusting or executing the package. The release materials are
prepared for eziah.dev publication; deployment remains separately authorized.

This package lets a developer install a small local authority experiment on a
fresh disposable Linux host and inspect whether exact synthetic actions are
permitted once, refused, or reconciled after an issuance reply is lost.
It operates only on synthetic protected objects in a finite two-principal workload.
Some interrupted transactions can leave the entire authority domain permanently
unavailable. There is no supported repair, migration or recovery of that domain.

Read in this order:
1. VERIFY-AND-SIGN.txt: establish publisher trust and verify all delivered bytes.
2. RELEASE-NOTES.txt and GUARANTEES-AND-LIMITATIONS.txt: understand the scope.
3. PREREQUISITES.txt and QUICK-START.txt: run one fresh, disposable evaluation.
4. RECORD-INDEPENDENT-RESULTS.txt: preserve and report what actually happened.
5. FRESH-LINUX-EVIDENCE.txt and LICENSE-AND-PROVENANCE.txt: evidence and terms.

The archive artifacts/distribution-001.tar is the exact transfer archive from
the successful AI-operated fresh-Linux trial. It extracts to distribution-001/.
The evidence archive contains all 1,606 original evidence files. Treat its state
copies as inert evidence, never as an installation, backup or recovery image.

Chronology matters: the sealed distribution's README, ACCEPTANCE, provenance
and audit records describe packaging time, before Linux execution. Those bytes
are unchanged. The later evidence summary adds one AI-operated Linux PASS; it
does not rewrite historical records or upgrade the frozen candidate's identity.
The inherited R001 NOTICE/SIGNING/VERIFY documents refer to their original scope.
Use this wrapper's signature procedure for this separate developer distribution.

An AI-operated installation, an independent human installation, and actual
organizational adoption are three different milestones. Only the first is
supported by the included Linux evidence. No production readiness is claimed.