CONTRIBUTIONS / CONTROLLED BETA
The public site is read-only. The correction path is still open.
Public write access is paused until contributor identity, moderation, abuse controls, and decision attribution are ready. Corrections remain free and are reviewed on evidence, not affiliation.
Prepare the correction
Include the stable OGS Tracker record id, the exact claim that needs correction, the proposed replacement, a source URL or document citation, and the date you checked that source. If you are reporting a new station or link, name both endpoints as precisely as the evidence allows.
Send it to the data desk
Contact the maintainer through the established Evan Grey LinkedIn profile ↗ and begin the message with “OGS Tracker correction.” If you represent an operator, say so and use an account or follow-up address that can establish the relationship.
Do not send confidential, export-controlled, security-sensitive, personal, or restricted operational information.
What happens next
The evidence is staged as a proposed Claim. It does not overwrite release 0.8. Identity and duplicate checks run first; then the proposal is accepted, rejected, or returned for clarification. Accepted changes enter a draft projection and must pass release validation before publication.
Operator corrections
Operator input is valuable but does not bypass the source standard. Direct confirmation is identified as operator-supplied, published evidence governs conflicts, and no payment changes a record’s contents, status, or placement.