EZA-001 Developer Trial Package 001 — Experimental Developer Implementation

This experimental developer distribution packages the frozen
EZA-001-P3-CONTINUITY-001 implementation with integration v1, hash-pinned online
dependency installation, a bounded walkthrough, acceptance checks, and evidence
export instructions. The existing package identity EZA-001-DEVELOPER-TRIAL-001,
packaging revision online-distribution-001, and frozen identity are retained.
Publication Gate 001 is a publication wrapper, not a new protocol release or R002.

An independent AI-operated evaluation installed the unchanged package on a fresh
Ubuntu 24.04.5 LTS aarch64 host and completed its documented acceptance. It
observed 30 terminal workflows across two principals, 27 grants, and 27 protected
effects, including refusal cases, replay denial, lost issuance reply reconciliation,
and one quiescent restart. Offline reanalysis reproduced all 32 evaluator checks.
This is evidence from one finite synthetic trial, not independent human adoption.

The implementation supports only synthetic local protected objects, two principal
UIDs and their two delegate UIDs, and fifteen lifetime terminal workflows per
principal. Refusals and explicit closures consume slots. Some interrupted
transactions can make the entire authority domain permanently unavailable.
There is no supported domain repair, replenishment, reconstruction or migration.
Do not put production credentials or real external actions into this experiment.

The intended next evaluation is an unfamiliar human developer following the
published instructions and preserving successful, failed or incomplete results.
Installation requires a disposable reference Linux environment, administrative
access, and online acquisition of the nine pinned dependencies. No dependency
wheels, installed runtimes or native executable libraries are bundled.

The release owner signed the preceding Publication Gate 001 wrapper, and its
Minisign signature was verified with Eziah key CFC656D308ECD752. This corrected
wrapper requires a fresh signature on its revised RELEASE-MANIFEST.json;
recipients must verify the exact received manifest against an independently
authenticated Eziah public key. Neither the superseded staging signature nor
the original R001 signature authenticates this corrected wrapper. Authentication
does not establish correctness, runtime authority, production suitability or
organizational use.