Smaller than it was
On 27 September the gym's movement library lost 4,724 lines and gained one field. What came out was a theory of how movements relate. What replaced it was a trainer writing the relation down.
3 min readMicroGym · Library stage
Every other part of the platform reads the library. A workout is a list of movements from it, a session runs those movements against the members in the room, and the assessment engine decides which members should do something else. So the library is less a list than a vocabulary, and on this platform the vocabulary had grown a theory. Each movement belonged to a body area and a set of target areas, each gym could define its own of both, and a table of suggested substitutions said what to do instead of each movement. Around them sat a service meant to infer the rest: read a member's assessment, work out what they should not do, and propose what they should.
What came out
On 27 September 2026 one commit removed body areas, target areas, the substitution editor, the links between movements and assessments, and the screens that managed them: 4,724 lines out, 142 in. What went in was one table and one column. Each gym gets a list of movement patterns, seeded with eight (squat, hinge, push, pull, lunge, carry, rotation, mobility), and a movement may name one. The migration is additive. The old columns stay and nothing reads them, so undoing the change means putting screens back, not recovering data.
Why one field was enough
Body areas existed to answer a question the platform had stopped asking: given that this member has a sore shoulder, which movements are like this one? By September the answer lived somewhere else. A trainer attaches a rule to a movement: when a member answers this assessment question this way, swap to that movement, or keep the movement and use a named variation. The rule is written by the person who knows the member and the gym, on the movement's own form, and it is applied when a session's roster is built. Production holds 32 of them. Once the swap was a sentence a trainer wrote, the taxonomy that was meant to let software infer it had no job left except labelling, and a label needs one field. Of the 80 movements in production, 55 have no pattern yet, and nothing depends on it.
What the cut missed
The commit deleted the screens and hooks. It did not delete the service underneath them. The last 901 of its 1,541 lines hold eight exported functions that nothing outside the file calls. Seven never were: they arrived on 29 June 2025 in a commit called New assessment system wip and stayed when the system went another way. The eighth fed a member's strength tab until 24 July 2026, when point-in-time assessments were replaced. One of the seven is the fallback for a movement with no written substitution: if the member's level is one or two, offer three easier alternatives. The query behind it takes any three movements from the gym other than the original, in no order, with nothing that measures easier. It never ran, which is the only good thing about it.
The old substitution table is in the same state. It holds 36 rows. Since September no screen can add one. The only code that still writes to it copies rows when a movement is duplicated, and the only code that reads it is either unreachable or a log line before a delete.
Why it belongs on this page
Dead code is not harmless because it does not run. It is a description of the system that nobody checks. The next person to open that file, or the next model asked how substitutions work, reads a fallback that hands a beginner three random movements, and nothing in the file says it is fiction. The September commit was right about what to remove, and it stopped at the edge of what the screens could show. What remains is a deletion of about nine hundred lines and one table, and it is written down.