Start here

Experimental implementation — synthetic protected objects only.

EZA-001 Developer Trial Package 001 is an experimental implementation for synthetic protected objects and a finite two-principal workload. It is a separate developer distribution (EZA-001-DEVELOPER-TRIAL-001 · online-distribution-001). It is not a new EZA-001 specification release, and it does not supersede the frozen R001 standard or the historical Trial 003 adapter below.

1. 01Download the experimental package.
2. 02Verify its SHA-256 and Minisign signature.
3. 03Review the supported Linux environment and prerequisites.
4. 04Follow the quick-start and installation instructions.
5. 05Execute the bounded authorization demonstration.
6. 06Inspect the resulting evidence.
7. 07Record independent reproduction results.

Manifest SHA-256

26bb4a29b0067d1091ad2745ac5d43e3cbed34f6e990299ae1f61b6e6f07da03

Signing key ID

CFC656D308ECD752 — the same Eziah key as R001

Trusted comment

Eziah EZA-001-DEVELOPER-TRIAL-001; online-distribution-001; experimental; Publication Gate 001

Signature scope

The detached signature authenticates RELEASE-MANIFEST.json. The manifest binds each listed file, including both archives, through its SHA-256. Nothing outside that list is covered.

Recorded result

• AI-operated trial installation: a Claude Code session, acting as an unfamiliar developer, executed the documented acceptance workflow on a fresh Ubuntu 24.04.5 LTS aarch64 host and completed it with exit 0 / PASS.

• 30 terminal authorization workflows across two principals, 27 grants issued and consumed, 27 protected effects; replay refused, a lost issuance reply reconciled, and committed state preserved across one quiescent restart.

• Offline reanalysis of the preserved evidence reproduced all 32 evaluator checks.

• This was not an independent human developer installation. It records that the documented workflow ran as written; it is not a certification of the protocol, and it does not establish organizational adoption or production readiness.

Limitations

• Not production-ready.

• Synthetic protected objects only, in a finite two-principal workload.

• Finite authorization capacity: fifteen lifetime terminal workflows per principal; refusals and closures consume slots.

• Some interrupted transactions can leave the entire authority domain permanently unavailable. There is no supported repair or recovery.

• No guarantee of arbitrary external-agent containment.

• No comprehensive power-loss or distributed-system durability claim.

• No completed independent human-developer installation.

• No demonstrated organizational adoption.

• No third-party wheel redistribution clearance: the developer installs the pinned dependencies from their official sources.

Report your results

• RELEASER001 release — identity, provenance, artifacts, digests→
• SPECSpecification as published on this property→
• REPRODUCEVerification and reproduction instructions→
• LIMITSDeployment boundary and stated limits→
• EZA-001Specification identity and release history→

The walkthrough provisions a disposable synthetic domain, starts the enforcement service under its own operating-system identity, submits one exact request as a separate requesting identity, observes one authorized write, and shows replay refused before and after a service restart. The adapter package contains the files it uses.

• WALKTHROUGHDeveloper walkthrough — the guide the reader followed, unchangedMarkdown · 35,285 bytes
• ADAPTERAdapter package — walkthrough, ten executable files, retained evidence, closure recordZIP · 174,993 bytes
• INVENTORYFile inventory with SHA-256 for every packaged fileJSON · packaging-time hashes

Package SHA-256

aa58b0737e21fc492cb15e32b7d71152990abac9ef9ad89a0cad9e3e54f688cd

Package size

174,993 bytes

Walkthrough SHA-256

6674860e0e292ef8d8c7d16af328807f1c4ab54ce2b7e9c63e0ed577610e098d

Signature scope

Historical integration material — outside the frozen R001 manifest’s signature scope, and not part of Developer Trial 001.

Release archive

Unchanged. Download and verify it from the release pages.

This is integration material, not a signed release artifact. The inventory hashes inside the package were computed when it was assembled; they identify its bytes and are not historical run evidence.

One reader followed this walkthrough to completion on Ubuntu 24.04.5 LTS with Python 3.12.3, on a dedicated administrator-owned runtime pinning jsonschema 4.25.1 and cryptography 46.0.0. This is a continuing assisted reader trial of a reference-based integration — not a blind first-reader test, and not an independently authored enforcement implementation.

• Governed action sequence, Ubuntu 24.04.5 / Python 3.12.3PASS — original execution, not rerun
• Corrected recorded-evidence analysisPASS — exit 0
• Evidence preserved before disposalPASS — 26 payloads verified
• Guarded disposal of the disposable root onlyPASS — exit 0
• Evidence after disposalPASS — hashes unchanged
• Reader’s own additional analyzerFAIL — retained as history

The reader’s own additional analyzer failed in that trial and that failure is kept as history: it was not rerun, edited, or relabelled. An earlier trial was blocked at dependency installation; the walkthrough’s dedicated-runtime section is the correction made in response, and it does not turn that blocked trial into a completed one. Reviewer closure of the supplied evidence is recorded at 2026-09-18T22:20:23Z, from supplied records rather than live access. One disposable environment; no reboot or power-loss testing; no production-readiness claim.

• EZA-001 R001 is published and EXPERIMENTAL, with its qualified review, disclosed wrapper-inventory failure, operator exception and stated limits intact. The candidate archive, manifest and signature are unchanged.

• This Developers page, the walkthrough and the adapter package are publicly available as EXPERIMENTAL integration material. They remain outside the frozen release manifest’s signature scope, and they are not a formal release acceptance.

• EZA-001 Developer Trial 001 (online-distribution-001) is a separate EXPERIMENTAL developer distribution, signed by the owner with the existing Eziah release key CFC656D308ECD752. It is not an R001 identity change and makes no production claim.

• Scope is synthetic local objects only. The walkthrough requires administrator privilege throughout, and the operating-system boundary it demonstrates depends on real UID separation that the operator configures.

Authentication

None.

Transport

Streamable HTTP.

Tools

search, fetch, get_release_status

Purpose

Retrieve published documentation and recorded release status.

Connecting this service does not grant authority and does not execute governed actions. It is a read-only reporting surface over published records.

Permit one identified agent to write one exact value to one synthetic local object, once. Then demonstrate that missing authority, altered requests, and replay cannot produce another protected effect.

The walkthrough above carries this out step by step, and a reader completed that sequence once in a disposable Linux environment. That is a recorded reader trial of a reference-based integration, not a general production result.

• VERIFY

  Verify the downloaded files

  Confirm that the bytes you hold are the published bytes: the signed manifest, its signature, the signer's public key, and the declared digests. This establishes authenticity of the package only.

• REPRODUCE

  Reproduce the reference tests

  Run the package's own controlled suite in a disposable directory and compare exact results, effects and recovery behaviour against the expected outcomes it ships.

• INTEGRATE

  Integrate the reference into an agent's environment

  Place the enforcement interface between a requesting agent and protected synthetic local state, so that an action can only occur with valid authority. This is a separate activity: completing verification or reproduction does not establish it.

• The operator controls permissions, actor identification, and protected state. These are not the requesting agent's to set.

• The requesting agent submits requests through the enforcement interface, and must not hold direct access that bypasses it.

• The reference's Python process separation alone does not establish operating-system isolation.

• Scope is synthetic local objects. Email, cloud changes, filesystem operations outside the profile, shell execution, and other external effects are outside this release.

Adopting the published reference implementation is permitted. TRIAL.md defines the separate evidence required to claim an independently written implementation — a recorded cold implementation study against the frozen package. It does not prohibit reference-based adoption.