Editorial policy

1. Sources first

We prioritize identifiable first-party announcements, official documentation, release notes, technical papers and reputable reporting. A public event must retain at least one source link, and the source remains the factual reference for the underlying claim.

2. Publication bar

Before an event is publicly indexable, it should have:

• a clear, specific title;
• an original summary of at least 140 non-whitespace characters that explains the actual development;
• a separate “Why it matters” explanation of at least 90 non-whitespace characters;
• source attribution and relevant entity connections; and
• no obvious interface text, placeholder copy or unsupported generic language.

The summary and context must add different information. Records that fail this bar remain private, are sent for editorial review or are improved before publication. They are not added to the public sitemap merely because they exist in the database.

3. Automation and AI assistance

Automation helps discover sources, remove duplicates, cluster related items and prepare structured drafts. It does not make a weak source record valuable by itself. Publication remains subject to the editorial quality gate, and editors can revise the summary and context before approval.

4. Corrections and feedback

If you find a factual error, broken attribution or a missing source, please contact us with the event URL and the correction. We review the report, update the record when appropriate and preserve the source trail.

Community feedback is currently handled by email rather than an open comment box. This keeps corrections attributable and moderated while the public service is still establishing its review workflow.