Concepts
Use concept pages to explain the durable mental models readers need across workflows. Keep procedures in guides, exact option listings in reference, and implementation architecture in contributing.
What belongs here
Section titled “What belongs here”- Terms readers must understand across multiple workflows.
- Relationships among user-visible parts and data.
- Behavioral guarantees, lifecycle rules, and constraints.
- Explanations of observable behavior that are true for the documented stable release.
Do not use Concepts as a home for source-module tours, internal contracts, or maintainer-only architecture. Put that material in Contributing. Do not publish plans, investigations, meeting notes, or speculative designs.