What reviewers need
- Clue or correction
- Country or category
- Source or evidence
- Caveats or false positives
- Optional contact
Contribute
Prepare a clue, correction, source note, or guide idea without creating an account. This MVP keeps contribution manual until a real community intake channel is approved.
No live submission inbox is configured yet
There is no connected form, mailbox, moderation queue, account, or database write path in this MVP. Use the checklist below to prepare a complete contribution for the eventual community channel.
Prepare a useful submission
A good contribution gives maintainers enough context to verify the clue and explain its limits to learners.
Submission checklist
Keep the note specific and source-aware. The goal is not volume; it is a clue or correction that can be reviewed and maintained.
- Clue or correction: Describe the exact clue, correction, or guide gap in one focused note.
- Country or category: Name the relevant country, region, clue category, guide, or comparison page.
- Source or evidence: Include official documentation, source links, example round context, or a clear reason the clue is reliable.
- Caveats or false positives: Explain where the clue fails, changes by coverage era, or should not be used alone.
- Optional contact: Add a handle or email only if you want follow-up questions from maintainers.
Manual submission template
Save this structure and send it through the approved community channel once one is configured. Until then, it is a preparation checklist, not a live form.
Clue or correction: Country or category: Source or evidence: Caveats or false positives: Optional contact:
What happens next
- Maintainers should verify sources before publishing factual claims.
- Community meta should stay labeled separately from verified facts.
- Coverage-sensitive notes should include review dates when available.
Scope boundaries
- No accounts or auth wall.
- No public write path or moderation queue yet.
- No commercial funnel, paid tier, or donation requirement.