Achieve HTTP Conformance Methodology
Scope
The unit of assessment is one normative requirement in the V3 requirements ledger. The inventory has 211 stable IDs spanning RFC 9110, RFC 9111, RFC 9112, and RFC 9113. Each ID appears once in the register pages and retains its V2 traceability.
The assessed endpoint is Achieve 3.1.0 on Node.js 24.22.2. Node.js, llhttp, nghttp2, HPACK, OpenSSL, and application-authored behavior are distinguished in the responsibility and evidence fields. Delegation identifies the responsible layer; it does not by itself establish conformance or make an endpoint obligation inapplicable.
Normative language
Each register entry preserves the ledger's normative level, including MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY. Conditions and role limitations remain part of the requirement. The linked RFC Editor section is authoritative if a summary is ambiguous.
Classifications
- Conformant
- Sufficient implementation and verification evidence establishes the applicable obligation for the assessed endpoint and runtime.
- Nonconformant
- A specific violation of the applicable obligation is demonstrated.
- Unverified
- Available evidence does not establish either conformance or nonconformance. Absence of a failure is not treated as proof.
- Not applicable
- The obligation does not apply to Achieve's supported origin-server role or configuration.
- Optional not implemented
- An optional capability is absent and the RFC permits that absence.
Evidence rules
- Source inspection, existing automated tests, bounded raw-protocol probes, runtime documentation, and qualification artifacts are recorded separately.
- A finite set of successful cases is not generalized beyond the behavior it exercises.
- Wire observations take precedence over API assumptions when the requirement concerns protocol output or error scope.
- Historical Node.js 22 evidence is preserved to explain earlier results; current classifications use the qualified Node.js 24.22.2 baseline.
- Requirements owned by HTTP caches, clients, proxies, or servlet applications are not attributed to Achieve core unless the endpoint has the applicable role.
Qualification boundary
The final Linux qualification for Achieve 3.1.0 ran all 37 verifier suites successfully with no environmental skips and completed package installation/startup smoke testing. The bounded protocol artifact recorded six corrected observations, seven known limitations, and no unexpected failures. Those observations resolve only the specific requirements identified by the ledger; they are not treated as a blanket conformance result.
Traceability
The V2-to-V3 mapping, consolidation report, authoritative summary, batch reviews, and focused investigations are indexed on the evidence page.