This map traces every normative REQ-LLH1-* requirement in
spec/bap-local-loopback-http-v1.md to executable
evidence or an explicit downstream/release gate. The certified profile corpus is revision 1 at
priv/conformance/application-profiles/local-loopback-http/v1.
Strict Ed25519 verification (erratum 2):
the profile's signature and key checks follow the strict rule of
spec/bap-v1.md § 14.1. Its requirements keep their
contract-major ids (REQ1-SIGNING-ed25519-canonical-point,
REQ1-SIGNING-ed25519-small-order-reject, REQ1-SIGNING-ed25519-scalar-range,
REQ1-SIGNING-ed25519-cofactorless, REQ1-KEY-ed25519-acceptable) and are traced in the
requirement map. Their cases for this profile are the 31 cases of the
loopback family in the additive strict-Ed25519 corpus (priv/conformance/strict-ed25519, index
SHA-256 732117dfe1881b553998126a9524a95bfb1171257e388d5430a0a099f2287cb9). This profile's own
corpus, index, and verdicts are unchanged.
Producer canonicality (erratum 3): this profile's assembler refuses a signature that fails the
keyless part of rule S1 (R canonical and not of small order, S < L) and emits accepted bytes
unchanged, through the one Ed25519 assembly call site every assembler shares. Its cases are the
4 assemble-loopback-* cases of the ed25519-assemble family in the additive
producer-canonicality corpus (priv/conformance/producer-canonicality, index SHA-256
99ee6fbbf32758b03d4630647f721d8d4e349f0628d860493d667fe6e762c601): S = L, identity R, and R with y = p refused, S = L - 1 emitted byte for byte.
RED PROOF: mutation ed25519-assembly-gate-removed reddens the family test. This profile's own
corpus, index, and verdicts are unchanged.
| Requirements | Evidence | Status |
|---|---|---|
CORE-compose-v1, CORE-profile-identity, HEADER-closed-set, HEADER-signed-identity | proof-cases.json; five SDK corpus consumers; exact producer/assembly bytes | populated |
CORE-cross-profile-reject, CORE-no-inference-fallback | local, standard, and unknown typ cases; separate public namespaces; architecture export/import locks | populated |
CLAIM-closed-required, CLAIM-grant-major, CLAIM-nonce-required, CLAIM-v1-bindings | missing/wrong nonce, valid signed envelope, and complete legacy BAP1 corpus | populated |
URI-canonical, URI-http, URI-exact-hosts, URI-host-reject-list, URI-port, URI-path, URI-reject-list, URI-pre-normalized | 36 language-neutral URI cases run by all five implementations | populated |
URI-no-network-proxy | pure-library architecture gate plus URI implementations with no I/O imports | populated |
API-complete, API-return-shape, API-no-signer, API-assembly-revalidate, API-symmetry, API-facts | five separately named public surfaces per implementation; corpus producer/assembly/decode/envelope checks; existing redacted fact-shape gates | populated |
CONFORMANCE-complete, CONFORMANCE-sdks, CONFORMANCE-no-drift | certified profile index plus Elixir/TypeScript/Python/Rust/Go consumers; unchanged complete 283-case BAP1 suite is a release blocker | populated |
CONFORMANCE-real-network, HOST-direct-target, HOST-one-profile | mix local_loopback_http.verify: real 127.0.0.1 and ::1 HTTP listeners, fresh in-memory keys, direct listener/request target derivation, secret-free receipt | populated |
SECURITY-honest-scope | normative security section, README, and threat model state that loopback HTTP is neither TLS nor process isolation | populated |
IANA-template | exact active registry entry plus machine-readable and rendered RFC 6838 templates; filing remains externally gated | populated |
HOST-replay-trust | Public verifier checks the required nonce but owns no state. BA-37 must prove reservation before effect in the adopting authority runtime. | downstream gate |
RELEASE-immutable | Requires the exact reviewed package and corpus identity to be published before BA-37 adopts it. Publication is not authorized by design approval. | release gate |
“Populated” means the repository contains executable evidence for the public-library obligation. It does not claim live replay reservation, revocation, trust selection, or a business effect; those remain downstream authority-host responsibilities.