Staging Bay

Open 24/7 · Buckner DC

Relay · Growth

How Relay grew

Every feature, merged branch and decision record since the first Passdown App in July 2025, grown into one tree. The seed is that first app. The tip is today.

commits in git
164
decision records
33
branches merged
4
feature commits
73

Reading the tree

Height is time, squeezed so the busy weeks stay readable. The thin lower trunk is the passdown apps that came before Relay, with no git. The thick upper trunk starts at Relay's first commit on 24 February 2026. Relay is built on main with few merges, so most branches are 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

  1. Passdown App starts

    A shift-handoff app on the same vanilla JavaScript stack as the first Beacon.

  2. Next.js rewrite

    The passdown app is rebuilt on Next.js and Firebase, with a handoff form, a schedule, a startup screen, site setup and analytics pages.

  3. Moved to Firestore

    The handoff data moves to Firestore, with notes on its structure, usage and access rules, and a reworked employee roster.

  4. Restyled

    The app is restyled to the company style guide.

  5. Last build of the old app

    The last build on disk of the Next.js passdown app, two weeks before Relay starts.

  6. Relay begins

    Relay starts on React, Vite and Firebase: foundation, then a nine-step setup wizard, on the first day.

  7. Git begins

    The first commit in the repository. Everything before it is known only from dated backup folders.

  8. Today

    Relay is in build: the passdown, the schedule, the TV board and the weekly incentive feed to Floor Score.

What the tree leaves out

  • The apps before Relay had no git. Their dates come from folder and file modified times, so a step may be older than the date shown.
  • Relay was built straight on main. Its branches are feature commits picked by their message, plus the 4 real branches that were merged in October 2026. Fixes, docs and tooling commits are left out.
  • Relay's decision records carry no numbers or dates. They are numbered in file order and dated by the commit that last changed each heading, so many share the day the file was added.
  • Relay has no releases or version numbers yet, so the trunk has no release rings.
  • 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.