Docs Operating Model

Internal docs are for durable knowledge, not every conversation.

Belongs Here

• Architecture decisions
• Runbooks
• Incident summaries
• Release process notes
• Private product strategy
• Integration plans
• Customer or operational context that is not public

Does Not Belong Here

• Secrets
• One-off chat transcripts
• Raw task discussion
• Stale implementation guesses
• Temporary plans that will not matter later

Shipping Rule

When a code change affects installation, APIs, runbooks, releases, or operator behavior, the code repository should either update local docs or open a pull request here.