- Short statement of what this repository exists to do.
- Coding, testing, and review conventions that stay stable across sessions.
- Scope boundaries or repo-specific constraints that should not be rediscovered every time.
- Main directories and why they matter.
- Important orchestrators, shared protocols, or integration points.
- Root-tracked guidance files such as
session-guide.md,todo-ledger.json, andkanban.md. - Run-local artifacts under
.pipeline-output/that are useful during execution but should stay gitignored.
- Commands that are regularly useful for validation, exports, or local development.
- Only stable risks or caveats that future sessions should know.