portfolio-watchlisted
Install: claude install-skill Kemetra/Seshat-BI
# portfolio-watch
Portfolio Watch answers one recurring question: *since we last looked, what changed,
what still needs a human, and what is the one next thing to do per scope?* It is the
baseline-diffable, multi-dimension EXTENSION of the point-in-time `retail-control-room`
roll-up (F012) -- same read-only, aggregate-never-re-derive posture, plus a persisted
snapshot and the drift/semantic-drift/dashboard-intent-divergence dimensions the control
room does not fold in.
## Scope wall (read first)
- **Aggregates, never re-derives.** Every finding is sourced from a shipped surface's
already-committed output (`drift.py`/`drift_semantics.py`, `metric_drift.py`,
`semantic_audit.py`/`report_intent.py`, `readiness_projection.py`/`readiness_classify.py`,
`approval_inbox.py`, `review_integration.py`/`review_pack_export.py`). It runs NO new
check and calls NONE of those surfaces' own comparators itself -- it reads what they
already recorded and cites the path.
- **No new gate / rule / approval mechanism.** This is a Tier-5 read/summarize/derive
companion (roadmap binding rule), not another governance engine. `seshat check`'s rule
inventory and exit behavior are unchanged by this skill's existence.
- **No score, ever.** Only the four readiness spine statuses, the shipped categorical
finding enums (relayed verbatim), and measured magnitudes (counts/rates/deltas) traced
to a committed source appear anywhere. A health/confidence/priority/quality number is
never emitte