You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Measure which chapters, terms, ADRs and codes pay their way #342
Which parts of the specification and the decision record pay their way, measured rather than guessed?
For every spec/v1 chapter and section, every CONTEXT.md term, every ADR (all four registers) and every E_ code, record:
inbound references (from other chapters, ADRs, CONTEXT.md, issues);
use in the worked examples and the oracle files under spec/v1/examples/;
use in src/ and in emf/, and whether either implementation exercises it;
test or fixture coverage (the behaviour ledger, the rule ledger, lint:codes' PENDING list);
size and churn (lines, commits touching it since 2026-08-31);
whether any Application in the live estate needs it (join with the live-estate ticket once it lands).
Also measure what the parity contract costs: the share of pull requests since emf/ landed that edited both implementations, the CI minutes of the emf job and the mutation shards, and the lines under emf/.
The output is a cited table in docs/research/, sorted so the cheapest-to-cut items rise to the top. It recommends nothing; the cut list is a later decision.
Measured at origin/main4c12851; the cited tables are in docs/research/what-pays-its-way.md on branch research/what-pays-its-way (no pull request yet). The gist:
Spec: 10,489 lines in 261 ##/### sections. 68 sections (35 of 162 at ##) have no inbound anchor link from anywhere. The ten Diagram sources sections hold 1,070 lines (10.2%), and the open-items sections hold 380. 107 of the ## sections (5,846 lines) are linked from no file in src/, test/ or emf/. Chapters 15 and 50 are the least reached (6 and 9 files linking in, none of them code).
ADRs: 98 records, 8,666 lines. The median record is linked from 12 files in the model register and from 2 in the architecture and EMF registers. Three (0059, 0072, 0077) are linked from nothing but their register. 59 are named by no code, test, script or workflow.
Terms: all 95 are used somewhere. 17 appear in no code (Stable Address, Infrastructure Intent, Fence, Move method and others), and 9 delivery and composition words appear in src/ only.
Parity: since emf/ landed, 38 of 106 non-bot merged pull requests (36%) changed both implementations, which is 54% of those that changed either one. emf/ took 20,317 changed lines, against 17,237 for src/, and is 17,678 lines in total.
CI, last 30 runs: the emf job has a median of 11.6 min and used 11.4% of runner-minutes, plus 2.0% for CodeQL java-kotlin. The six mutation shards used 79.8%, and the slowest shard (median 19.0 min) is the wall-clock floor.
Resolved: the measurement is in docs/research/what-pays-its-way.md on branch research/what-pays-its-way. The gist is in the comment above. Whether a live Application needs each item joins from the live-estate inventory (#343).
Activity
ExtraToast commentedon Oct 9, 2026
Measured at
origin/main4c12851; the cited tables are indocs/research/what-pays-its-way.mdon branchresearch/what-pays-its-way(no pull request yet). The gist:##/###sections. 68 sections (35 of 162 at##) have no inbound anchor link from anywhere. The tenDiagram sourcessections hold 1,070 lines (10.2%), and the open-items sections hold 380. 107 of the##sections (5,846 lines) are linked from no file insrc/,test/oremf/. Chapters 15 and 50 are the least reached (6 and 9 files linking in, none of them code).src/and 57 inemf/, and 52 have a refusal oracle.src/only.emf/landed, 38 of 106 non-bot merged pull requests (36%) changed both implementations, which is 54% of those that changed either one.emf/took 20,317 changed lines, against 17,237 forsrc/, and is 17,678 lines in total.emfjob has a median of 11.6 min and used 11.4% of runner-minutes, plus 2.0% for CodeQLjava-kotlin. The six mutation shards used 79.8%, and the slowest shard (median 19.0 min) is the wall-clock floor.ExtraToast commentedon Oct 9, 2026
Resolved: the measurement is in docs/research/what-pays-its-way.md on branch
research/what-pays-its-way. The gist is in the comment above. Whether a live Application needs each item joins from the live-estate inventory (#343).