reporting-architecturelisted

# Reporting Architecture One metric, one definition, one owner. An undefined metric is not a measurement, it is a position in an argument. ## When to use - Two dashboards report different numbers for the same thing - Board or investor reporting needs building - Dashboard count is growing and trust is falling - Somebody proposes buying BI to solve a disagreement ## Inputs - Needs from user: every report currently in use, the metrics on each, who reads them, and the two reports that disagree - Reads: `workspace/reports/attribution-model.md`, `workspace/reports/lifecycle.md` ## Workflow ### 1. Run the definition test first Ask three people to define one important metric independently, in writing. Do this before building anything. Three different answers, which is the usual result, means the problem is definitional. No tool fixes that. A warehouse lets the same three definitions disagree faster and at higher resolution. ### 2. Build the metrics dictionary One row per metric. This is the artifact the whole skill exists to produce. ``` Metric | Definition (one sentence) | Formula | Source system | Object counted | Date field used | Filters and exclusions | Owner | Refresh cadence ``` The four columns that resolve almost every real disagreement: **object counted, date field used, filters, exclusions**. When two numbers differ, one of those four differs, and finding which one is the entire investigation. **Every metric has one named owner.** The owner arbitrates when a nu