Yardzip · Growth
How Yardzip grew
Every feature and decision record since Yardzip's first commit in May 2026, grown into one tree. The seed is the first commit. The tip is today.
- commits in git
- 318
- decision records
- 39
- feature commits
- 134
Reading the tree
Height is time, squeezed so the busy weeks stay readable. Yardzip is a ground-up rebuild of an older yard system, built on main, so its branches are feature commits. Each family of branches is one part of the yard.
- Octahedron
- a feature commit
- Small pyramid
- a decision record (ADR)
- Hexagon
- a pull request
- Icosahedron
- a branch that was never merged
- Ember
- the tip, and any branch being built now
Drawing the tree
The same story in words
Yardzip, 5 May 2026
The first commit: a Next.js scaffold and the Firebase setup for dev, test and production, plus notes on the bugs found in the older yard system.
Today
Yardzip is in build: the gate, the dock schedule, detention, alerts and a 3D view of the yard.
What the tree leaves out
- Yardzip has no merge commits on main; the four pull requests merged in October 2026 landed as plain commits. Its branches are its feat: commits. Fixes, docs, tests and refactors are left out.
- The older yard system it replaces was kept only as reference code. It is not John's work and is not drawn.
- Load planning and document storage were built in May 2026 and then cut from scope on 27 July 2026. Their feature commits are still on the tree.
- Yardzip has no releases or version numbers yet, so the trunk has no release rings.
- There is no pre-git era: the seed sits on the first commit. 4 agent worktree branches are left out of the unmerged branches.
- Branches and decisions are sorted into families by keyword, so some sit on the wrong limb. Sign-in and access-control items keep their number and date but their wording is withheld.