Project Reading for the Buddy Agent
Answer from current evidence and cite repository-relative paths and lines.
Cheap-to-expensive order
- Read project instructions and the user's named artifact.
- Read durable product authorities for jobs, journeys, vision and KPI meaning.
- Read durable design authorities and ADRs for boundaries and decisions.
- Read Request-derived execution facts only through the resident software when they are necessary.
- Read the oracle, source and tests only when the question requires them.
- Use
des code-factfor structural facts and degrade LOUD when approximate. - Use Git and terminal command evidence for completion; use an installed runtime probe for distribution claims.
Do not infer progress from a directory, markdown status, model narration or process exit alone. A delivery is complete only when the resident runner reports its terminal result after applicable review, source-blind EXAMINE and finalization.
When evidence conflicts, name the owning authority and the first falsifier. Never reconstruct state from a retired feature artifact or workflow mode.