● Reckoneerhow it works
Reckoneer / Stage 11
Stage 11BuildOperator + Auto

Staging

After the operator approves in Stage 10, the dev branch is merged to the staging branch on GitHub. The Shopify GitHub integration picks up this push and automatically syncs the theme files to a designated staging theme in the store's theme library.

The staging theme is still unpublished — customers cannot see it. But it represents the final, approved state of the build. The operator does a final review on the staging theme (using its own preview URL) before publishing.

This staging step exists as a buffer between approval and go-live: an additional safety check using the exact code that will go live, as opposed to the developer's build environment.

Terms
Staging theme

A separate unpublished theme in the store's theme library, synced automatically from the GitHub staging branch via the Shopify GitHub integration. Represents the final pre-production state of the build.

AnalogyA dress rehearsal on the actual stage, in full costume, with a live audience of one (the operator). Not a practice run in a rehearsal room — the real venue, the real show, one last check before opening night.
OriginStage: from Old French 'estage' (a floor, a level). Staging: in theatre, preparing for a performance. In deployment: a near-production environment for final validation.
Shopify GitHub integration

A native Shopify feature that connects a GitHub repository to a store. When code is pushed to a mapped branch, Shopify automatically syncs the theme files. No manual upload required.

AnalogyA live wire between the repository and the store. Touch the wire on the GitHub side (push code) and the current flows immediately to the Shopify side (theme updates).
OriginIntegration: from Latin 'integrare' (to make whole). A connection that makes two separate systems work as one.
Branch merge

The Git operation of combining changes from one branch into another. In the Reckoneer pipeline: dev → staging (after Stage 10 approval) and staging → main (after final staging review).

AnalogyMerging two lanes of traffic into one. The vehicles from the dev lane (new code) join the staging lane (production-bound code), then both flow into the main lane (live).
OriginMerge: from Latin 'mergere' (to dip, to plunge, to combine). In version control: combining the history of two branches into one.