Minimal developer quick-start (human-operated, after signature verification)

1. Follow the recipient section of VERIFY-AND-SIGN.txt. Verify the entire signed
   wrapper and the distribution tar before extracting or executing package code.
   In a new normal-user working directory outside the download directory:

     tar -xf /absolute/path/to/public/artifacts/distribution-001.tar
     cd distribution-001
     EZA_PACKAGE="$(pwd -P)"
     EZA_INVENTORY=9c8753f74caa352b152ed96d1a0a00e029bc3f257760711c16459686f3390a91
     python3 -I -B "$EZA_PACKAGE/verify_v1.py" --expected-inventory "$EZA_INVENTORY"

   Expect PASS, 223 package files and 148 frozen files. Keep all logs outside
   distribution-001/. Preserve stderr and exit codes as well as stdout.

2. Read INSTALL.txt completely. Confirm PREREQUISITES.txt and choose unused
   EZA_HOME, EZA_STATE, EZA_PREFIX and EZA_OPERATOR values. Follow INSTALL.txt
   steps 2–5 exactly: root fresh setup, operator venv/pinned dependency install,
   then one root seal. Record every command, environment version and deviation.
   Stop at any unexpected failure; never repeat seal after partial failure.

3. On that unused sealed domain run the single scripted command from
   WALKTHROUGH.txt (ROOT; requires explicit operator approval to run the fixed
   synthetic requests):

     sudo systemd-run --scope --unit "$EZA_PREFIX-accept-001"        --property=MemoryMax=1G --property=MemorySwapMax=0 --property=TasksMax=64        /usr/bin/python3 -I -B "$EZA_HOME/package/verification/acceptance_v1.py"        --config "$EZA_STATE/config.json" --run-id first-attempt-001

4. Read ACCEPTANCE.txt and inspect (ROOT reads):

     sudo cat "$EZA_STATE/results/first-attempt-001/RESULT.json"
     sudo cat "$EZA_STATE/results/first-attempt-001/FINAL-ORACLE.json"

   Require both exit 0 and RESULT.json status PASS, plus its documented evidence.
   Expected final counts: 30 terminal records, 15 per principal, 27 grants,
   27 consumed roots and 27 effects. Missing evidence, unexpected nonzero exits
   or unresolved outcomes mean FAIL/INCOMPLETE, not a reason to chase a PASS.
   The two deliberately refused sixteenth client allocations are expected
   internal nonzero results; the acceptance command itself must exit 0.

5. Recheck installed package bytes using the same inventory pin, then preserve
   the stopped trial using CLEANUP.txt step 1 (export only). Save the archive
   digest separately. Follow RECORD-INDEPENDENT-RESULTS.txt. Destructive cleanup
   is optional, separately authorized, and was not exercised in the prior trial.

Do not run the historical reproduction suites or old archive tooling as part of
this quick-start. This is a navigation guide; INSTALL/WALKTHROUGH/ACCEPTANCE retain
the exact complete commands, permissions and failure handling for integration v1.