Safety copy: Do not send illegal material, private personal data, passwords, or anything requiring secure legal handling.
What to send
Correction requests
Send the page URL, the sentence or link at issue, the durable source that supports the correction, and a short explanation of the requested change.
Broken-link reports
Send the route, the broken source link, and any archived or official replacement if one exists.
Source tips
Send public, lawful, durable source pointers such as court records, official reports, public filings, or clearly provenance-tracked archive material.
What not to send
- Do not send illegal material.
- Do not send private personal data or credentials.
- Do not send medical, legal-sensitive, or private identifying material unless it is already lawfully public and directly relevant.
- Do not send unsupported allegations, threat labels, or identity guesses.
How corrections are handled
A correction can downgrade, caveat, relabel, or clarify a page. The archive favors narrow, source-linked changes over broad narrative claims. If a source gap remains unresolved, it should stay visible as an open receipt slot rather than becoming a finding.
Latest correction · September 30, 2026: The Barak timeline had summarized EFTA00389664 as a June 5 noon Barak entry. Source OCR instead shows a June 3 4:00pm appointment with Ehud Barak and a June 4 noon lunch with Barak and Bob Kerrey. EFTA00404605 was also moved from an undated open slot to a Sep. 23–24, 2012 scheduling chain after its OCR was reopened. The receipt cards and dynamic details were updated to match.
Previous correction: Flight Log Count and Aircraft Reconciliation records the 2026-07-23 correction for Clinton and Maxwell passenger-row counts, N505LS aircraft-tail repair, and N474-family quarantine language.
What makes a correction actionable
The fastest correction packet includes four things: the exact public route, the sentence or source link that is wrong or incomplete, the replacement source, and the narrow change requested. For an archive dossier, include the EFTA identifier, page number, footer number, render filename, or PDF page reference if those are visible. For a methodology or policy page, point to the rule that is unclear and describe the reader risk created by the wording.
Source tips are handled differently from correction requests. A tip may create a review queue item, but it does not change a public claim until the source can be inspected, attributed, and placed into the right lane. If the tip is only a screenshot, copied text, or an unsourced assertion, it may be useful as a pointer but not as a citation. Durable sources include court dockets, official reports, public filings, agency pages, preserved source renders, and archive records with stable identifiers.
Possible review outcomes
- Correction: the page said something wrong and the text, title, description, link, or source note is changed.
- Clarification: the original sentence was defensible but too easy to overread, so a limit or example is added.
- Downgrade: a claim loses confidence and moves to a review lead or open receipt slot.
- Retirement: a weak route is removed from the sitemap or marked noindex while the underlying source remains accessible.
- No change: the challenged text is supported by the cited source, but the request may still be recorded for future review.
Public notes and preservation
Grok Archive Hub does not delete source evidence to make a correction look cleaner. When the problem is interpretation, the visible page should change. When the problem is a generated route, search treatment can change while the archive record or PDF remains available. When the problem is OCR debris, the fragment should not remain an indexable entity or topic page, but the source location that produced it should stay traceable if it matters to the audit trail.
Contact
Email: grokcloudflare@gmail.com