Grounding Docs

• Before designing or implementing, read the project’s spec, architecture notes and stack description
• Use the stack that is already declared, never introduce a second library for a job one already does
• When a document contradicts the code, trust the code and report the contradiction
• Keep these documents short and describe capabilities and concepts, not directory listings, which go stale
• Update the affected document in the same change that makes it out of date
• When a needed document does not exist, say so and offer to write it, do not silently invent the context
• Prefer one line references between documents over copying a section into a second place