Knowledge Base Rules

1. Markdown and Git are authoritative; rendered sites and indexes are derived.
2. Search before creating a page. Prefer updating the established canonical page.
3. Create a new page for a substantial topic with an independent lifecycle or when an existing page has become difficult to navigate.
4. Record intent, authority boundaries, constraints, failure behavior, and non-obvious relationships—not facts trivially visible in one source file.
5. Label verified behavior, decisions, hypotheses, experiments, deprecated material, and history accurately.
6. Keep research separate from accepted architecture. Promote it only after verification or an explicit decision.
7. Preserve important decisions with lightweight ADRs.
8. Prefer links over duplicated explanations. Resolve contradictions instead of maintaining competing active descriptions.
9. Do not paste raw chat transcripts. Distill durable knowledge and retain only necessary evidence.
10. Never commit credentials, tokens, private player identifiers, or sensitive log content.
11. Update relevant KB pages with implementation changes whenever practical. Cross-repository changes may use paired commits or pull requests.
12. Reorganize incrementally with git mv, updating links and known source references in the same change.