Local-loopback HTTP profile requirement map

Copy Markdown View Source

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.

RequirementsEvidenceStatus
CORE-compose-v1, CORE-profile-identity, HEADER-closed-set, HEADER-signed-identityproof-cases.json; five SDK corpus consumers; exact producer/assembly bytespopulated
CORE-cross-profile-reject, CORE-no-inference-fallbacklocal, standard, and unknown typ cases; separate public namespaces; architecture export/import lockspopulated
CLAIM-closed-required, CLAIM-grant-major, CLAIM-nonce-required, CLAIM-v1-bindingsmissing/wrong nonce, valid signed envelope, and complete legacy BAP1 corpuspopulated
URI-canonical, URI-http, URI-exact-hosts, URI-host-reject-list, URI-port, URI-path, URI-reject-list, URI-pre-normalized36 language-neutral URI cases run by all five implementationspopulated
URI-no-network-proxypure-library architecture gate plus URI implementations with no I/O importspopulated
API-complete, API-return-shape, API-no-signer, API-assembly-revalidate, API-symmetry, API-factsfive separately named public surfaces per implementation; corpus producer/assembly/decode/envelope checks; existing redacted fact-shape gatespopulated
CONFORMANCE-complete, CONFORMANCE-sdks, CONFORMANCE-no-driftcertified profile index plus Elixir/TypeScript/Python/Rust/Go consumers; unchanged complete 283-case BAP1 suite is a release blockerpopulated
CONFORMANCE-real-network, HOST-direct-target, HOST-one-profilemix local_loopback_http.verify: real 127.0.0.1 and ::1 HTTP listeners, fresh in-memory keys, direct listener/request target derivation, secret-free receiptpopulated
SECURITY-honest-scopenormative security section, README, and threat model state that loopback HTTP is neither TLS nor process isolationpopulated
IANA-templateexact active registry entry plus machine-readable and rendered RFC 6838 templates; filing remains externally gatedpopulated
HOST-replay-trustPublic verifier checks the required nonce but owns no state. BA-37 must prove reservation before effect in the adopting authority runtime.downstream gate
RELEASE-immutableRequires 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.