Glossary and README

Three files, three jobs

AGENTS.md holds imperative operating rules. The glossary defines domain terms and exact metrics. The README orients a person to the project and where its pieces live. Mixing them turns all three into a document nobody can use.

Write Revenue as quantity * net_price on order_items, not a vague synonym for sales. Be exact about source grain: raw orders has 1,212 rows for 1,200 order IDs, and raw order_items has 2,895 rows for 2,880 distinct lines. A one-row-per-order statement belongs to the deduplicated staging asset, not the raw table.

Your task

Replace the Revenue TODO in docs/glossary.md. Add AOV, active customer, churn, category, net vs gross, and fiscal period. State both raw-table grains correctly and cite at least one asset file where a metric is computed.

Check your understanding

• A new rule says the agent must never run DELETE against generated data without asking first. Which file does that belong in, and why not the glossary?
• Why does the Revenue glossary entry need to name a column instead of describing a concept?
• Why is a stale AGENTS.md worse than a short one?

Do it with your agent

Say next lesson, update the glossary yourself, then say review my work. The agent should check all six terms, exact grain, a real citation, and that no TODO remains.