retail-governlisted

# retail-govern Seshat BI's conventions are enforced by a static checker, `seshat check`. This skill teaches you to **run it, read its findings, and map each rule id to the file and fix it points at**. The authoritative catalog is the glossary's "Static check rules" section, which mirrors the checker's live rule registry; the rules manifest is the machine-readable inventory. (An older 23-rule governance-layer design doc is a historical record, NOT the current count -- do not cite it for the catalog.) ## Scope boundary (read this first) This skill is **invoke-and-interpret only**. It does **not** orchestrate a Power BI build, does **not** call `pbi-cli` or Power BI Desktop, and does **not** auto-fix or self-heal violations. Those are deferred D-layer work (spec §9). Here you run the checker, explain a finding, and tell the user (or the `powerbi-analyst` agent) the single place to change — then stop. ## Run the checker From the repo root: ``` seshat check ``` It parses the committed TMDL / PBIR / SQL / git text — **no Power BI Desktop, no `pbi-cli`, no network** — and exits non-zero if any `error`-severity finding exists. `warning` and `info` findings are printed but do not fail the build. Severity is layer-aware (see the recorded severity-posture inventory for the observed per-rule posture), so treat that record — not a hardcoded list here — as the source of truth for which ids warn vs error. (`G2` emits an `info` "no PBIP project present" when the repo has no model yet