Jonathan KirkwoodandClaude Fable 5 f13d044a70 progress: only track KPIs that ever carried a target ...

Tested against the live Strike ledger (9 decks): its decks mint ad-hoc KPI
names every quarter, so ~70 one-off unscored mentions flooded the watch list,
trajectory table, and dropped-KPIs gap. A KPI now only counts as trackable/
vanished if it was held to a target at least once; the rest collapse to a
one-line count. Scoring-derived flags (no_profitability_visibility,
no_quantitative_kpis, kpi_dropped) no longer duplicate their dedicated gaps
as recurring-flag requests.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-31 20:53:14 -05:00

..

fixtures

Implement BDEF v1.1 grading: scoring core, per-deck pipeline, ledger, dashboard, StartOS layer

2026-07-06 14:15:12 -05:00

test_decks.py

Implement BDEF v1.1 grading: scoring core, per-deck pipeline, ledger, dashboard, StartOS layer

2026-07-06 14:15:12 -05:00

test_ledger.py

Implement BDEF v1.1 grading: scoring core, per-deck pipeline, ledger, dashboard, StartOS layer

2026-07-06 14:15:12 -05:00

test_progress.py

progress: only track KPIs that ever carried a target

2026-07-31 20:53:14 -05:00

test_scoring.py

Implement BDEF v1.1 grading: scoring core, per-deck pipeline, ledger, dashboard, StartOS layer

2026-07-06 14:15:12 -05:00