Orba · Growth
How Orba grew
Every feature wave and decision record since Orba's first commit in April 2026, grown into one tree. The seed is the first commit. The tip is today.
- commits in git
- 104
- decision records
- 23
- feature commits
- 38
Reading the tree
Height is time, squeezed so the busy days stay readable. Orba was built in two bursts: eleven waves of features in three days in April 2026, then a rebuild of the data model after the move off Supabase in late August. Each family of branches is one area of the warehouse.
- Octahedron
- a feature commit
- Small pyramid
- a decision record (ADR)
- Ember
- the tip
Drawing the tree
The same story in words
Wave 1, 10 Apr 2026
The first commit: foundation, design tokens, a routing shell and the database schema for a small warehouse system with RF and desktop screens.
Today
Orba is in build on Cloud SQL and Firebase: inbound, inventory on the handling unit, and the RF screens.
What the tree leaves out
- Orba has never merged a branch. Its branches are feature commits picked by their message (the waves and feat: commits); fixes, docs and clean-ups are left out.
- The tree is drawn from the migration/firebase-cloudsql branch, where all work since August 2026 lives. Its old master branch stopped on 12 April 2026.
- All 23 decision records were written from 28 August 2026, during and after the re-platform. None covers the April build.
- Orba 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.
- 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.