cadence-adherence-telemetry
Purpose
The cadence-adherence-telemetry skill is the user-facing sensor for Principle 8 ("Organizations Learn Through Outcomes"). It walks the context/ tree, identifies cadence-stack records that have aged past their threshold or are missing entirely, and surfaces them as a ranked, actionable report. The point is not bookkeeping. It is the early warning system that keeps strategic bets, decisions, and portfolio reviews from rotting in place. Decisions that aged past 90 days with no outcome review compound silently into decision debt — this skill makes that visible while there is still time to act on it.
This skill is the user-facing wrapper around cadence_check.scan() (V5.1-30, internal module). The scan itself is read-only and never mutates context/; this skill renders the scan output as markdown, persists the report to context/telemetry/ for audit trail, and surfaces it to the user.
When to invoke
- Weekly sensing cadence (default) — invoke once per week as a Principle 8 health check. The report fits on one screen and reads in 30 seconds.
- Before strategic decisions — invoke before any portfolio tradeoff, new strategic bet, or major commitment, so prior-decision rot is on the table when the new commitment is being made.
- Before /maturity-check —
/maturity-check(V5.1-26/27/28 rewrite) reads the cadence dimension from this scan as input to the Three Tiers diagnostic. Run cadence-adherence first so the maturity assessment has the freshest signal. - On suspicion — invoke whenever you suspect a project has gone dormant, a bet thesis is being run on momentum rather than evidence, or you've been off the system for a stretch and need to see what aged while you were away.