Default-value scorecard - keep value features fully enabled
Auto-generated by the internal/defaultvaluescore Build over the live tree. Do not hand-edit; re-run the tool.
Grade D - score 66.7 - default_value_debt 1 - 15 value-flag(s) across 2 surface(s), 10 gated OFF; 1 score surface(s)
The law: a value feature ships ENABLED. Every cost/cache/amplification value-flag is default-on (or gated OFF with a documented reason); no exit-summary line folds kernel.Counters that are structurally 0 on the Decide-only fak guard -- claude proxy; and no score surface defaults its headline to a modeled (“planned”) number instead of observed telemetry. This is the recurring guard for epic #1089 so a value feature can never silently regrow not-fully-enabled.
| KPI | score | detail |
|---|---|---|
| value_flag_default_on | 100 | 15/15 value-flags default-on or gated-with-reason |
| no_vacuous_counter_fold | 100 | 1/1 kernel.Counters exit-folds are proxy-aware |
| observed_not_modeled_default | 0 | 0/1 score surfaces default to an OBSERVED headline |
Work list (HARD)
- score.go: score surface defaults its headline source to “planned” (modeled), upgraded to observed only when live telemetry is present – the default report is a modeled number (C_MODELED_NOT_OBSERVED)