Explanation documentation provides context, rationale, and trade-off analysis.
Use this section to explain why vstack is designed the way it is, including:
- architectural choices
- product and workflow principles
- boundaries and non-goals
Explanation pages should help readers build mental models, not complete tasks.
Use Explanation pages for user-level understanding:
- mental models for core concepts
- why a concept exists and when to use it
- how concepts relate at a high level
Keep focus on concept understanding over implementation details.
Do not put internal engineering details here, such as:
- architecture decisions, component internals, or system decomposition
- implementation design, module structure, or generation mechanics
- product planning, roadmap details, or requirement tracking
For internal details, use: