Skip to the content.

Steerability scorecard

This is the measuring stick for the question no other fak scorecard asks: as the repo doubles in size, does the effort to steer, change, and navigate it stay roughly flat — and if it drifts, do we know, and can we correct? Every number below is re-derived from the working tree by tools/steerability_scorecard.py — no hand-entry.

The headline is a 0–100 steerability index, not a debt count, because steerability is a property of shape, not size. Every KPI is growth-invariant — a ratio, density, or distribution percentile — so a 2×-larger repo with the same modular discipline scores identically. (A raw defect count, the kind every sibling scorecard uses, would climb just from getting bigger.)

Regenerate: python tools/steerability_scorecard.py --markdown --stamp DATE > docs/STEERABILITY-SCORECARD.md

Headline

Metric Value
Steerability index 93.7/100 (grade A)
Hard steerability-debt 0
Advisory drift signals 4
Index by group modularity:82.5 · coupling:100.0 · navigability:100.0 · correction:100.0

Per-KPI

Eleven KPIs, each 0–100, in four groups. debt = HARD steerability-debt (only dispatch_god_file and ratchet_present can emit it — everything else is advisory, because its cheapest fix would be gaming a detector). god_file_rate / god_func_rate SCORE the size rate but leave the raw count to code_quality (no portfolio double-count). package_doc_frac counts // Package ... docs for libraries and // Command ... docs for command packages. churn_concentration is HEAD-relative.

Group KPI Score Debt Clean-gain Detail
modularity func_size_dist 56 0 +4.4 314/14419 functions over the soft length line (rate 2.18%)
modularity god_file_rate 87 0 +0.9 4/1509 files > 1500 lines (rate 0.27%)
modularity god_func_rate 90 0 +0.7 15/14419 functions > 200 lines (rate 0.10%)
modularity file_size_dist 97 0 +0.3 file length p50=200 p90=546 (ref 520) over 1509 files
coupling fan_in_gini 100 0 +0.0 fan-in Gini 0.56 over 226 packages (top abi:73, model:38, windowgate:36, benchcli:26, cachemeta:26)
coupling hub_share 100 0 +0.0 top hub ‘abi’ imported by 73/350 packages (21%)
coupling dispatch_god_file 100 0 +0.0 no cmd dispatch god-file
navigability package_doc_frac 100 0 +0.0 349/350 packages carry an orientation doc-comment (100%)
correction ratchet_present 100 0 +0.0 control-pane ratchet present + this scorecard wired
correction worst_pkg_drift 100 0 +0.0 no package-LOC baseline pinned (informational)
correction churn_concentration 100 0 +0.0 churn Gini 0.50 over 42 files in HEAD~40..HEAD (HEAD-relative)

No hard steerability-debt: the index and the advisory drift signals below carry the story. 🎉

Drift signals (advisory)

Highest-index moves

Gain if clean KPI Why this helps Current detail
+4.4 func_size_dist split long routines at tested seams 314/14419 functions over the soft length line (rate 2.18%)
+0.9 god_file_rate split oversized files along ownership boundaries 4/1509 files > 1500 lines (rate 0.27%)
+0.7 god_func_rate split hard-to-review functions before they become shared chokepoints 15/14419 functions > 200 lines (rate 0.10%)
+0.3 file_size_dist keep typical files below the p90 size line file length p50=200 p90=546 (ref 520) over 1509 files