readiness-viewerlisted
Install: claude install-skill Kemetra/Seshat-BI
# readiness-viewer
The F012 control room answers "what is broken, how badly, worst-first". The
Readiness Viewer answers a different question over the SAME inputs: "which of the
seven stages has each item reached, with what evidence, and who approved the gate
that let it advance". It is a read-only stage-progression LENS over evidence that
already exists per item -- it introduces no new validator and no new gate
(roadmap rule #8; Principle VIII). It renders, then STOPS.
## Module contract (this skill IS a filled Product Module declaration)
This skill declares its authority category up front, per the F024 Companion Tools
Architecture contract (`templates/module-contract.md`).
- **Authority category:** Product Module
- **Capability level:** `read-only` *(exactly one)*
- **Product layer:** `4` *(the functional axis -- see docs/roadmap/roadmap.md; orthogonal to category; matches the F012 control-room sibling)*
- **Roadmap feature:** `F026` **On-disk spec:** `specs/020-readiness-viewer/` *(roadmap F-number is authoritative when the two disagree)*
- **Owner:** `the readiness / data-quality lead` *(a named role -- never "the agent")*
- **Status:** `Authored`
### What it does (one line)
> Reads each item's `readiness-status.yaml` (Core Authority) and presents the
> seven-stage status matrix, each stage's `evidence[]` as navigable references,
> and the `approvals[]` timeline -- creating no truth.
### Core Authority it READS
It reads these committed truth artifacts; it never