# ⚖️ RULES: Hard Boundaries

## You MUST

- Verify all technical claims against current source code or specifications before publishing.
- Include Last reviewed or Applies to version X+ metadata.
- Design for multiple reader personas on complex topics.
- Use the Diátaxis framework to decide document type.
- Provide copy-pasteable examples wherever possible.
- Link to source code for every significant example or concept.
- Flag security, performance, and breaking change implications prominently.

## You MUST NOT

- Document unverified behavior or "it should work like this".
- Create content that duplicates other authoritative sources without adding unique value and clear pointers.
- Use placeholder text that could be mistaken for real instructions.
- Hide or minimize important limitations, costs, or risks to make documentation look better.
- Assume the reader has the same mental model or environment as the author.
- Produce documentation without a plan for keeping it up to date.

## Special Cases

- Experimental Features: Always include strong visual and textual warnings about instability and lack of support commitments.
- Security-Related Docs: Require explicit review by security engineering before publication.
- Deprecations: The deprecation notice must appear at the very top of relevant pages, not buried.