Optional HTTP access handoff v1

A standalone black-box handoff is prepared for the proposed optional HTTP profile. It includes a runner, shell encoders, the relevant profile documents, requirement status, a fixed binary vector and a SHA-256 manifest. It contains no Rust source, server runtime, operational credentials or private deployment configuration.

Archive: site/downloads/http-access-handoff-v1.zip

SHA-256: a069d66527cee83ca84a1beef9a64232405148b9a3deb55b385f73f332c2703c

Size: 17,158 bytes; ten files, including the manifest. Rebuilding with python3 scripts/build_http_access_handoff.py reproduces the digest.

Use

Extract into a new directory and read README.md. Python 3, jq, xxd, shell and Ed25519-capable OpenSSL are test prerequisites; the implementation under test can use any language. Generate short-lived test fixtures with run.py prepare, start a dedicated node using the supplied policy and binary_v1 format, and use run.py run against its URL. The archive's README contains exact commands.

The runtime need not implement a special testing API. The runner uses ordinary GET /core/admissions, POST /core/admissions and POST /core/query operations. Eleven checks cover expected IDs, retry, malformed/version/truncation/trailing refusals, forged signature, oversized input, subsequent valid submission and queries. Fixture generation and expected hashes do not consult the Rust reference.

Retention policy remains local: retained false is allowed. The controlled fixture must be discoverable if reported retained. Use a fresh isolated state directory; the suite writes claims and is not intended for shared services.

Evidence

The extracted package passed against the reference implementation from outside the repository, both initially and after the supervising harness killed/restarted the node. A fake server that accepted every submission failed the negative checks. Manifest contents matched every extracted file, and a second archive build matched the first digest. Results: docs/results/http-access-handoff-v1/.

The generic runner cannot observe a restart performed outside it. It reports that limitation even when invoked with the after-restart phase label. The reference harness separately records its observed process restart. Independent authorship, TLS/public deployment, comprehensive cryptographic malformed cases, sponsor conflicts, epoch transitions and sustained-load fairness are not established by these checks. Those remain separate suites and review gates.

Next assurance gate

An external implementer can now use the archive and return results, implementation source/version, launch commands, exact archive digest, process/reopen logs and any specification ambiguities. Disclose authorship and assistance. Passing the same-author reference is a harness check, not independent interoperability.

The existing strict-admission handoff archive remains frozen and separate. This new optional-profile artifact does not replace it or claim broader Core coverage.