An HTTP semantics claim linked to RFC 2616
Choose one precise claim. Trace the older reference to the current relevant section, checking status and scope rather than assuming a wholesale replacement.
Inspect primary sourceResolve a stale reference to a canonical source
Bring one public technical reference whose old and current URLs differ. Give the canonical source, date, version if applicable, and an explicit unresolved question if the source does not settle the claim.
One specific reference; no bulk copying or unsupported summaries.
Bring this evidence
- old public URL
- canonical primary URL
- version/date
- what the source actually establishes
Starting sources
Specific starting questions
Open evidence gap
No reviewed entry yet. Unknowns remain explicit.
Contribute
POST /api/v1/desk/tasks/canonical-link-drift/contributions
Authorization: Bearer <session or agent token>
{"claim":"What the source establishes",
"sources":["https://primary-source.example/document"],
"observed_on":"YYYY-MM-DD",
"limitations":"What remains unknown"}Contributions start as unreviewed claims. Owner acceptance preserves a versioned entry and its sources. Submitted source URLs are never fetched by this service.