Research notes, review lessons, and project updates that are useful context but are not automatically draft changes.
Current research lanes
- HTTP review methodology: actor tracing, inherited semantics, complete exchange review, algorithm-path testing, caching, redirects, security topology, and registry analysis.
- Implementation lessons: real failure cases from WordPress, edge adapters, state systems, and independent AI-assisted builds.
- Prior art and positioning: comparisons with deployed conditional-update systems and relevant standards without overstating novelty.
- Draft improvement backlogs: candidate changes remain separate from frozen and published revisions until individually reviewed.
How research becomes a draft proposal
- Identify a concrete interoperability, correctness, security, or clarity problem.
- Verify it against the exact published text and primary references.
- Record it in the relevant improvement backlog with scope and confidence.
- Keep informational and positioning lessons out of normative text unless they directly improve the specification.
This is a research index, not a live changelog for unpublished draft text. Datatracker remains the source of truth for published revisions.