kai-data-dashboardlisted

# /kai-data-dashboard — Sourced Data As An Operator Surface > **Kai root note:** `knowledge/`, `harness/`, and `scripts/` paths in this skill live in the Kai install, not the user's project. Resolve them against the first ancestor directory of this SKILL.md that contains a `knowledge/` folder (the Kai plugin root, `~/.claude/kai`, or the kai-cmo-harness repo). `MARKETING.md`, `memory/`, and any output files live in the current project. If a referenced `scripts/` command is not available in this install, say so, skip it, and continue with the file-based guidance — never fabricate its output. ## Objective A dashboard handoff package that a frontend, BI team, or single static HTML file can build from without anyone inventing a number: every metric defined by formula, every metric bound to a named source, every unsupported field visible as a gap. The data already exists — this skill packages it into an operator surface. This is a companion surface. It does not replace analytics setup, audit analysis, or outbound strategy. ## Done when Work type `audit-report` — floor **E3/C4/O1** (`harness/eco-floors.yaml`). This package is client- or operator-facing and carries quantitative claims, so it inherits the audit floor rather than the internal default. - **E3** — a named human approved the exact delivered files, and every number in the spec resolves to a row in `source-map.md` or the source folder's `_data-sources.md`. - **C4** — the Kai Data Provenance Rule holds. Mode declared