Staging Bay

Open 24/7 · Buckner DC

Meridian · Growth

How Meridian grew

Every merged branch, decision record, pull request and release since the SQF document library was sorted in January 2026, grown into one tree. The seed is that library. The tip is today.

commits in git
1,342
decision records
162
branches merged
123
releases
52

Reading the tree

Height is time, squeezed so the busy months stay readable. The thin lower trunk is the work before git; the thick upper trunk starts at the baseline commit on 14 May 2026. Each family of branches is one area of the app. Rings are releases.

Ring on the trunk
a release
Octahedron
a merged branch
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

  1. SQF document library

    The site's SQF documents are sorted into one folder per clause, 2.1 to 12.8, next to the Storage and Distribution code.

  2. Field scan and gap analysis

    A script scans every document for the fields a site fills in, and a workbook lists the documents still missing. Two backup copies are taken.

  3. Third backup

    A third dated copy of the library and scripts.

  4. The app takes shape

    Decision records from here describe a React app: free-roam navigation, shared module config and an agent harness for building it.

  5. Mock audit with Sebastian

    An AI auditor walks a site through a mock SQF audit, modelled on a certification body's audit prompts.

  6. Sanitation forms by QR

    Floor staff can file sanitation forms from a QR code without signing in.

  7. Baseline commit

    The app is committed to git as a baseline. The git era starts here.

  8. Git begins

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

  9. v1.0.0

    Baseline - SQF Edition 10, Storage and Distribution

  10. v2.0.0

    The app runs Edition 9, the edition the site is audited on

  11. v3.0.0

    Food Manufacturing code alongside Storage and Distribution

  12. v3.10.0

    New capability: the annual management review now draws in the period's objectives updates…

  13. v3.20.0

    Every site can now start Leader Standard Work from one default list with shift-time headi…

  14. v3.28.0

    A site can now verify sanitation sheets from a review task, the way floor forms are verif…

What the tree leaves out

  • Before 14 May 2026 there is no git. The lower trunk comes from dated folders, backup copies and the first fourteen decision records, so its dates are approximate.
  • Early decision records dated by month only (4 of them) sit on the first of that month.
  • Version numbers before 3.6.0 were assigned afterwards from the decision record (ADR-127). Those rings have no build or commit behind them.
  • Only unmerged branches with a commit in the last 14 days are drawn. 3 older unmerged branches and 22 agent worktree branches are left out.
  • Pull requests were only used in May and June 2026. The 17 still open are early drafts that were never closed.
  • 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.