Home / Articles / The minimum code below / Versions / v1.2.0
The minimum code below: what changed in v1.2.0
From v1.1.0 (2026-10-18, de821285d) to v1.2.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 52 unchanged. About 0 words added and 116 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot mq-layers.webp | images/ | Top down, one question at every layer: what is the minimum code below this that the layer above needs? From a user story, through the workflow, modules and functions, to the dependencies, the language runtime and the operating system. Projected from the top, derived from the code; derived and not projected is code nobody asked for. | architecture
22 unchanged paragraphs, under In short {#in-short}, Bottom up, and where it stops {#bottom-up}, Top down: the minimum code below {#top-down}…
!shot mq-measured.webp | images/ | One use case, measured.measured: sgit 0.21.0 and its dependencies,dependencies runbefore underand coverageafter for a CI-style use case, then run again from a tree holdingkeeping only the files that ran: 1,500 files down to 428, Python source from 4.72 MB to 1.98 MB, compiled code unchanged at 14.78 MB. Inside the kept files 38% of the statements ran; commands outside the use case failed; coverage missed a compiled module the tests caught.ran. | comparison
14 unchanged paragraphs, under What the measurement also showed {#limits-measured}, It did not scale before, and now it can {#scale}, Who does what today {#landscape}
!shot mq-landscape.webp | images/ | Three ways to get to less code.code: Bottombottom up and hardened, as Chainguard does; runtime minimisation, as SlimToolkit and RapidFort do; and top down by use case, proposed here, which starts from what the application is for and ties every remaining line to a reason.case. | comparison
14 unchanged paragraphs, under The business model: certify what is left {#certify}, What this does not claim {#limits}, Where this comes from {#sources}