Floor Score · Growth
How Floor Score grew
Every feature, merged branch and decision record since the first productivity video tool in August 2025, grown into one tree. The seed is that tool. The tip is today.
- commits in git
- 41
- decision records
- 23
- branches merged
- 1
- feature commits
- 16
Reading the tree
Height is time, squeezed so the busy weeks stay readable. The thin lower trunk is the video tool that came before the app, with no git. The thick upper trunk starts at the first commit on 1 March 2026. Floor Score is small and built mostly on main, so most branches are single feature commits.
- Octahedron
- a merged branch or a feature commit
- Small pyramid
- a decision record (ADR)
- Ember
- the tip
Drawing the tree
The same story in words
Productivity video tool
A browser page reads the weekly productivity workbooks and records a video for the floor TVs.
Records and streaks
Small tables of all-time records, consistent performers and top pickers feed the video.
Rates per customer
Pick rates are set per customer, so a case on one account is not graded like a case on another.
History and name map
A running history file, a name map and a list of management teams. The decision records that start the app are written this month.
First commit
The app is committed: the RES engine with extended metrics.
Git begins
The first commit in the repository. Everything before it is known only from dated backup folders.
Today
Floor Score is in beta: the RES leaderboard, the TV slides and, since October 2026, a reviewed week sent from Relay.
What the tree leaves out
- Before 1 March 2026 there is no git. The lower trunk comes from file modified times in the old tool's folder, so its dates are approximate.
- Floor Score has 41 commits and one merged branch. Its other branches are feature commits picked by their message; fixes and docs are left out.
- Five decision records about the stack are marked as inherited and dated 1 January 2026, two months before the first commit.
- Floor Score has no releases or version numbers yet, so the trunk has no release rings.
- The tree shows no operator data: no names, photos, scores or headcounts.
- 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.