Achieve HTTP Conformance Evidence Index
The V3 ledger is authoritative for current requirement wording, classification, responsibility, and evidence. Earlier assessments remain available for provenance and must not override later corrections.
Authoritative current records
- 211-requirement V3 ledger and classifications
- V2-to-V3 traceability mapping
- inventory consolidation and reconciliation
- Achieve 3.1.0 authoritative narrative summary
- current and resolved nonconformity decisions
- Node.js 24.22.2 adoption evidence and boundary
Batch evidence reviews
- Batch A evidence review
- Batch B evidence review
- Batch C evidence review
- Batch D evidence review
- Batch E evidence review
- Batch F evidence review
Focused protocol and quality investigations
- final investigation of initially unverified requirements
- quality-control review
- focused inventory and evidence follow-up
- approved quality corrections
- HTTP/2 frame and HPACK probes
- structured frame and HPACK evidence
- HTTP/2 root-cause investigation
- TLS renegotiation investigation
- overlong request-target investigation
- Node.js parser/API investigation
- matching If-Range response metadata decision
Historical assessments retained for provenance
- original normative inventory audit
- V2 ledger validation
- earlier RFC 9110 assessment
- earlier RFC 9111 assessment
- earlier RFC 9112 assessment
- earlier RFC 9113 assessment
- runtime upgrade evaluation
- Windows qualification evidence
- Linux qualification method
External qualification evidence
- Final Achieve 3.1.0 Linux qualification run 42049611849
- Achieve 3.1.0 GitHub release
- Verifier-suite entry point and execution guidance
Evidence cautions
- Some historical reports describe Achieve 3.0.6 and Node.js 22.15.0. They establish provenance and earlier failures, not the current baseline.
- The GitHub qualification artifact is external to this documentation tree. Its summarized results are recorded in the current ledger and conformance summary.
- Source/test references in ledger entries use repository paths and occasional line references that can move after later edits; reviewers should verify semantic targets against the release commit.