Independent implementer package v1

The strict admission exercise is ready to hand to another implementer. The archive is outputs/implementer-handoff-v1.zip: 24 files, 62,484 bytes, SHA-256 a78fb96fc5e9036adaec01c4a5379bdbb86e5c85accfcb4cd14c2a650883bf88. It has not been sent to anyone or published by preparing it.

Contents and use

The package contains the Core contracts, strict authentication/admission/epoch contracts, fixed signed fixtures, expected vectors, standard-library Python runner, file manifest and an implementation-evidence template. It excludes the reference runtime, adapters and fixture generators. Historical references in the broader contracts remain pointers to the repository; the archive README identifies the four operations/suite groups in scope.

An implementer extracts it, runs python3 VERIFY.py, implements a JSON-lines adapter with explicit strict acceptance, then runs the four README commands. Targets are 12 codec vectors, 14 claim vectors, eight admission traces and four epoch traces. Complete IMPLEMENTATION.json and return raw reports, source/build instructions and ambiguities. Disclose assistance and any reference code consulted. The manifest checks file integrity relative to the archive, not publisher identity.

Validation

The package was extracted into a fresh temporary directory and all four suites passed against the existing same-author Rust reference. Changing one fixture was detected by the manifest. Two builds produced byte-identical archives. Evidence is retained in docs/results/implementer-handoff-v1/. Rebuild with scripts/build_implementer_bundle.py --output NEW_ARCHIVE.zip; changed source contracts require a new archive/version and evidence, not replacement of this one.

This validation establishes package usability, not independent implementation or full Core conformance. An external author/team still needs to perform the exercise. No reviewer was contacted. Hostile discovery progress targets remain failed; this package tests bounded local protocol rules, not discovery usefulness or scale.

Work while external assurance remains open

Keep this package fixed for comparison. Record implementation discrepancies against its digest and explicit suite/profile before changing contracts. Independent semantic validation and wider distributed fault testing remain separate roadmap items. Repeating these tests under another assistant or computer does not close the independent-author gate.