Supporting experimental evidence

    Signed public edition

    EZA-001 Linux Experimental Evidence 001

    Saved evidence from a native Linux experiment. The native authority protocol passed within five saved cases. Overall adversarial isolation is inconclusive, live same-tick mutation was not executed, and full runtime reproduction is not available from this public subset.

    EZA-001-LINUX-EXPERIMENTAL-EVIDENCE-001-public.2

    Separately signed supporting evidence for EZA-001 R001 (EZA-001-R001-rc.9). It does not amend, supersede or re-version the specification.

    EZA-001 specificationR001 evidenceMachine-readable record (unsigned)

    What this evidence supports

    • Native authority protocol — within five saved casesPASS
    • Overall adversarial isolationINCONCLUSIVE
    • Live same-tick mutationNOT EXECUTED
    • Full runtime reproduction — from the public subsetNOT AVAILABLE

    Each result stands alone. They are not combined into a security score, and no production readiness or third-party certification is claimed.

    What each record is

    • signed artifacts

      Owner-signed with key CFC656D308ECD752. The signatures authenticate these exact bytes, and through them the ZIP identity and payload digests. They do not attest that unobserved events happened.

    • privacy projections

      Some records inside the ZIP are derived projections with opaque aliases for machine, host, account, network and boot identifiers. They are not byte-identical to the private originals, and the original signature does not authenticate them.

    • unsigned website summary

      This page and its JSON record. They summarise the signed edition and add no signed claims.

    • independent review

      Earlier reviews were agent re-examinations of saved bytes, not independent human or laboratory execution. The Public.2 verification record checks signatures and bytes only; it is not a new evidence review.

    Recorded findings

    • One exact authorized write to object:X, one root consumed and the prepared handle removed; object:Y remains initial.

      Verdict
      PASS for exact native case only
      Classification
      evaluator conclusion
      Signature coverage
      privacy-derived projection in the owner-signed public.2 package (manifest and release binding Minisign signatures independently verified); original Release 220 signatures do not authenticate projections or interpretation
      Specification requirements
      R1, R3, R6, R7, R10, R12
      Finding ID
      eza-001/linux-experimental-evidence-001-rc.1/claim/authorized

    • Request without authority refused with FAIL_SAFELY and zero additional protected effects.

      Verdict
      PASS for exact native case only
      Classification
      evaluator conclusion
      Signature coverage
      privacy-derived projection in the owner-signed public.2 package (manifest and release binding Minisign signatures independently verified); original Release 220 signatures do not authenticate projections or interpretation
      Specification requirements
      R1, R3, R8, R9, R10
      Finding ID
      eza-001/linux-experimental-evidence-001-rc.1/claim/no-authority

    • Out-of-scope attempt refused for replay; no additional protected effect; isolated scope enforcement remains INCONCLUSIVE.

      Verdict
      PASS for exact native case only
      Classification
      evaluator conclusion
      Signature coverage
      privacy-derived projection in the owner-signed public.2 package (manifest and release binding Minisign signatures independently verified); original Release 220 signatures do not authenticate projections or interpretation
      Specification requirements
      R4, R7, R8
      Finding ID
      eza-001/linux-experimental-evidence-001-rc.1/claim/out-of-scope-replay

    • Consumed-grant replay refused with no additional protected effect or renewed authority.

      Verdict
      PASS for exact native case only
      Classification
      evaluator conclusion
      Signature coverage
      privacy-derived projection in the owner-signed public.2 package (manifest and release binding Minisign signatures independently verified); original Release 220 signatures do not authenticate projections or interpretation
      Specification requirements
      R7, R8
      Finding ID
      eza-001/linux-experimental-evidence-001-rc.1/claim/consumed-grant

    • The exact spent-handle attempt refused with no additional protected effect; broader attack isolation not established.

      Verdict
      PASS for exact native case only
      Classification
      evaluator conclusion
      Signature coverage
      privacy-derived projection in the owner-signed public.2 package (manifest and release binding Minisign signatures independently verified); original Release 220 signatures do not authenticate projections or interpretation
      Specification requirements
      R6, R7, R8
      Finding ID
      eza-001/linux-experimental-evidence-001-rc.1/claim/spent-handle

    • Manual four-file denial: INCONCLUSIVE

      Verdict
      INCONCLUSIVE
      Classification
      evaluator conclusion
      Signature coverage
      privacy-derived projection in the owner-signed public.2 package (manifest and release binding Minisign signatures independently verified); original Release 220 signatures do not authenticate projections or interpretation
      Specification requirements
      R6
      Finding ID
      eza-001/linux-experimental-evidence-001-rc.1/claim/manual

    • Isolated scope enforcement: INCONCLUSIVE

      Verdict
      INCONCLUSIVE
      Classification
      evaluator conclusion
      Signature coverage
      privacy-derived projection in the owner-signed public.2 package (manifest and release binding Minisign signatures independently verified); original Release 220 signatures do not authenticate projections or interpretation
      Specification requirements
      R4
      Finding ID
      eza-001/linux-experimental-evidence-001-rc.1/claim/scope

    • Same-tick mutation: NOT EXECUTED

      Verdict
      NOT EXECUTED
      Classification
      evaluator conclusion
      Signature coverage
      privacy-derived projection in the owner-signed public.2 package (manifest and release binding Minisign signatures independently verified); original Release 220 signatures do not authenticate projections or interpretation
      Specification requirements
      R5, R6
      Finding ID
      eza-001/linux-experimental-evidence-001-rc.1/claim/same-tick

    Requirement links are a reviewer crosswalk to the R001 specification, not a statement of full conformance.

    Limits

    • Historical captures trust root, Linux kernel, systemd/journald, installer anchor and capture transport. Hashes and signatures authenticate bytes, not unobserved events.INCONCLUSIVE
    • Manual four-file denial was owner-reported; two UID 5206 sudo sessions lack stdin code, exact four targets, errno, exit status and output.INCONCLUSIVE
    • Out-of-scope request used a consumed grant; replay refusal preceded the scope check.INCONCLUSIVE
    • No live same-tick mutation execution record is established; fixture cases are not substitutes.NOT EXECUTED
    • No production certification, universal security, arbitrary filesystem isolation or root/kernel compromise resistance is established.NOT ESTABLISHED
    • Linux implementation manifest 8b072a89… differs from R001 rc.9 specification manifest fc44b015…; requirement mappings are a reviewer crosswalk, not byte equivalence or full conformance.DISTINCT IDENTITIES
    • Current and prior agent reviews are saved-byte re-examinations, not independent human/laboratory execution or organizational adoption.NOT ESTABLISHED
    • Native wheels and all dependency distributions, original containers and unselected history are omitted. Saved-case consistency is checkable; full runtime/installation reproduction and independent original-container ancestry verification require omitted originals/inputs. Historical pre-signing statement in the frozen package text (retained verbatim there): "New edition remains unsigned pending owner signing." Current state (2026-10-21): MANIFEST.json and RELEASE-BINDING.json carry owner Minisign signatures (key CFC656D308ECD752), independently verified; its identity does not replace the original. Public.2 also projects operational identifiers and omits complete maintenance authentication/replay material.PARTIAL EVIDENCE EDITION
    • This edition uses explicit opaque aliases for operational machine, host, account, network and boot identifiers. Aliases are public correlation labels, not actual historical identifiers, and do not establish host/key retirement or present operational status. Modified records are derived projections, not byte-identical copies; original Release 220 signatures do not authenticate projected bytes. Full maintenance replay is unavailable from public.2 because current-maintenance.json and associated replay inputs are omitted. The five saved native cases, 22 substantive ledger rows, receipt/event relationships and required native journal MESSAGE payloads remain the intended inspectable scope. No runtime reproduction, new experiment, independent redaction attestation or stronger security result is asserted.PRIVACY PROJECTIONS; PACKAGE OWNER-SIGNED (manifest and binding verified); ORIGINAL RELEASE 220 SIGNATURES DO NOT AUTHENTICATE PROJECTIONS
    • The remaining current-authority ledger/physical-state consistency, checkpoint/witness relationships, selected sudo journal bindings and saved native-case receipt/event checks can be inspected. Complete SSH authentication history, complete maintenance-journal membership and full saved maintenance replay cannot be independently reproduced from public.2. Historical maintenance PASS statements are retained historical assessment statements, not current-public-edition verification claims.FULL MAINTENANCE REPLAY UNAVAILABLE

    Signed release files

    The signed release binding identifies the exact ZIP by filename, size and SHA-256. The signed manifest identifies its exact payload. No direct ZIP signature is claimed.

    • EZA-001-LINUX-EXPERIMENTAL-EVIDENCE-001-public.2.zip1,912,040 bytes

      privacy-minimized public evidence edition — bound by signed RELEASE-BINDING.json (filename, bytes, SHA-256); not directly signed

      SHA-256 4889b9a31db11a23d33986690d8951eda23be3140caeba9c1f31d356bb960832

    • MANIFEST.json51,106 bytes · signed

      payload manifest of the public.2 edition — signed: MANIFEST.json.minisig

      SHA-256 4b9bfde72523248863487f11e8bd3e448a92b0d50d81e5dfe40aa2b3fe48fb6c

    • MANIFEST.json.minisig315 bytes

      detached Minisign signature over MANIFEST.json — signature

      SHA-256 59d86447a1b8b427875a064ad0b5c043902b50774cf9ba6f2fa5000de3d5a114

    • RELEASE-BINDING.json1,502 bytes · signed

      release binding: exact ZIP and manifest identity — signed: RELEASE-BINDING.json.minisig

      SHA-256 f4d820f664fe7d87c500ba77fabbb54ba6516ba53408c06ca38766bd44e6412b

    • RELEASE-BINDING.json.minisig322 bytes

      detached Minisign signature over RELEASE-BINDING.json — signature

      SHA-256 0752f94431152d53f1fe3092aaf7bc4653b5d81cc2f19bddf4f1eb291f78a8a4

    • SHA256SUMS554 bytes

      checksum list for the publication folder — unsigned companion; also lists OWNER-SIGNING-HANDOFF.txt, which is intentionally not published

      SHA-256 ce15b120321a5deb8004ca387342bbd2f0354f2d1c2dfc076706cd99ce65421d

    • VERIFY-COMMAND.txt419 bytes

      exact offline verification command — unsigned companion

      SHA-256 d6e9e7d14a97590d8ac78ff9a3c898cb8c21418b64202960a8e93c04de5e8689

    • verify_public_edition.py36,695 bytes

      offline standard-library saved-evidence verifier — unsigned companion; read before running

      SHA-256 4976e99b2a897d52cfe9687d564c40e29543035f13d75fea3e716b3507822d4b

    Verify it yourself

    Scheme
    minisign
    Key ID
    CFC656D308ECD752
    Public key
    RWRS1+wI01bGz7h6vYSR4m9shqB2/q8FiIpbY8tSgDQnhNZ4qzp+0mSA
    Key file
    /integration/eza-001-developer-trial-001/keys/eziah-release-2026-01.pub
    Key file SHA-256
    df3a3e0aa9f6368906f7004083e8abab76e8cb98b603ab0e9146e68abbdf0311
    # 1. Detached signatures (independently trusted key)
minisign -Vm MANIFEST.json -x MANIFEST.json.minisig -P RWRS1+wI01bGz7h6vYSR4m9shqB2/q8FiIpbY8tSgDQnhNZ4qzp+0mSA
minisign -Vm RELEASE-BINDING.json -x RELEASE-BINDING.json.minisig -P RWRS1+wI01bGz7h6vYSR4m9shqB2/q8FiIpbY8tSgDQnhNZ4qzp+0mSA
# 2. All eight public files — fails if any is absent or altered
sha256sum --strict -c - <<'EOF'
4889b9a31db11a23d33986690d8951eda23be3140caeba9c1f31d356bb960832  EZA-001-LINUX-EXPERIMENTAL-EVIDENCE-001-public.2.zip
4b9bfde72523248863487f11e8bd3e448a92b0d50d81e5dfe40aa2b3fe48fb6c  MANIFEST.json
59d86447a1b8b427875a064ad0b5c043902b50774cf9ba6f2fa5000de3d5a114  MANIFEST.json.minisig
f4d820f664fe7d87c500ba77fabbb54ba6516ba53408c06ca38766bd44e6412b  RELEASE-BINDING.json
0752f94431152d53f1fe3092aaf7bc4653b5d81cc2f19bddf4f1eb291f78a8a4  RELEASE-BINDING.json.minisig
ce15b120321a5deb8004ca387342bbd2f0354f2d1c2dfc076706cd99ce65421d  SHA256SUMS
d6e9e7d14a97590d8ac78ff9a3c898cb8c21418b64202960a8e93c04de5e8689  VERIFY-COMMAND.txt
4976e99b2a897d52cfe9687d564c40e29543035f13d75fea3e716b3507822d4b  verify_public_edition.py
EOF
# 3. ZIP membership and manifest consistency
python3 -I -B verify_public_edition.py 'EZA-001-LINUX-EXPERIMENTAL-EVIDENCE-001-public.2.zip' --expected-archive '4889b9a31db11a23d33986690d8951eda23be3140caeba9c1f31d356bb960832' --expected-manifest '4b9bfde72523248863487f11e8bd3e448a92b0d50d81e5dfe40aa2b3fe48fb6c'

    Run all three steps; any failure means the files are not the published edition. The signed SHA256SUMS also lists OWNER-SIGNING-HANDOFF.txt, an internal owner handoff intentionally omitted from public distribution, so a plain check of SHA256SUMS reports one missing file — step 2 checks the eight public files explicitly instead. These instructions are unsigned website guidance; the signed release evidence is the files and signatures themselves. The verifier reads the ZIP in memory and never runs archived code. Matching hashes prove bytes, not that unobserved events happened.

    Lineage

    Specification
    EZA-001 / R001 / EZA-001-R001-rc.9
    Original evidence release
    EZA-001-LINUX-EXPERIMENTAL-EVIDENCE-001-rc.1 — private
    Public edition
    EZA-001-LINUX-EXPERIMENTAL-EVIDENCE-001-public.2
    Lineage ID
    eza-001/linux-experimental-evidence-001-public.2/lineage
    Recorded
    16 requirements · 8 experiments · 6 observations · 8 claims · 23 relationships · 2 verifications · 10 limitations · 76 artifacts

    Public.2 signatures do not authenticate EZA-001-LINUX-EXPERIMENTAL-EVIDENCE-001-rc.1 or EZA-001-LINUX-EXPERIMENTAL-EVIDENCE-001-public.1. Those remain separate historical identities.

    Retrieval is not permission

    Retrieving information about authority confers information, not execution permission. Only the trusted enforcement boundary may establish and enforce permission for a protected action. EVIDENCE IS RETRIEVABLE. PERMISSION IS NOT INFERRED.

    Unsigned website summary derived from the owner-signed Public.2 release and its accepted canonical publication mapping. It reports; it does not extend any signature.