docs: refresh fleet figures from the #91 ledger; correct #92 and #94 scope - #96
Merged
Merged
Conversation
…scope The fleet program's substrate (#91) is built: the one-shot 2026-08-03 import census is now an append-only ledger in gitignored misc/data/ (full commit pins + restore helper, per-dependent baseline suite results, an AST census, a generated zero-usage report, one immutable record per scan). Only the doc-side figures are committable — the ledger and its data are gitignored — so this commit replaces every stale number and the two roadmap entries whose scope the scan changed: - 89 direct dependents, not 85 (121 transitive, of 217 registry packages). - Import != subclass, now measurable: 29 dependents actually subclass a core class across 141 classes; 3 more import one and never subclass it. - #94: 82 of 148 exports have zero fleet usage, but only 58 have been public over a year — that cohort is the candidate pool. The other 24 are the recently shipped content/autoviv/path_*_writeback surface. - #92 reframed: the successor spelling is already live (wrap_kvs accepts key/value_encoder/_decoder as aliases onto the X_of_Y four) and the fleet is already split across both — 34 pkgs/132 sites vs 9 pkgs/28 sites, 5 packages using both. Meanwhile kv_wrap's directional kwargs have no named fleet uses and key_codec/value_codec have none at all. Two live spellings to converge, not three peers to reconcile. Refs #91, #92, #94
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc-side landing of the #91 fleet usage ledger. The ledger itself and all its data live in gitignored
misc/data/, so only the figures and the two roadmap entries whose scope the fresh scan changed are committable here. Full record: #91 comment.What changed
Stale figures replaced (2026-08-03 → 2026-08-21 scan):
__init__exportsNew, because the regex scan couldn't measure it: import ≠ subclass. 29 dependents actually subclass
Store/KvReader/KvPersister/Collectionacross 141 classes; 3 more import one and never subclass it.wrap_kvsis called by 40 packages across 112 call sites, 29 of them as a class decorator.#94's candidate pool is 58, not 82. The other 24 zero-usage exports shipped within the last year (the
contentmodule,autoviv,path_*_writeback,PathContext,FirstArgIsMapping,unravel_key) — nothing has had time to adopt them, so their absence of usage is not evidence about them. The report generates that split.#92 reframed. The successor spelling isn't prospective:
dol/trans.pyalready acceptskey_encoder/key_decoder/value_encoder/value_decoderas aliases onto the fourX_of_Ynames, and the fleet is already split across both — 34 pkgs / 132 sites onX_of_Yvs 9 pkgs / 28 sites on encoder-decoder, 5 packages using both. Meanwhilekv_wrap's directional kwargs have no named fleet uses andkey_codec/value_codechave zero call sites. Two live spellings to converge, not three peers to reconcile.Verification
Collectionsubclasses, and submodule star imports scored against the wrong surface), both now frozen as regression tests alongside the tool.dol/is touched by this PR.Refs #91, #92, #94