Explaining a Project

Explanation renders what a project is and does into prose a non-author can follow.

Architecture

• explain-architecture-faithful: An architecture explanation MUST be faithful to the code and design docs — translate technical detail into prose without inventing structure the project does not have.

Capabilities

• explain-capabilities-grounded: Capability claims MUST be grounded in what the project actually does (README, docs, commits), not aspirational roadmap.
• explain-translate-for-reader: Technical detail SHOULD be translated to the reader's level without losing accuracy.