Tyre Swing OS

The little robots that run the back office

A one-page picture of the agent system Jackie operates: two walled-off worlds, the families of agents, and how a change flows from your laptop to the cloud.

1

Two walled-off worlds

You operate the Tyre Swing one. You never touch Matt's.

Tyre Swing OS

Jackie operates this · repo tyreswing-os

  • The ~24 store agents
  • Ramp Champ · Kids Car Sales · Eco Off Grid
  • Your logins, growing over time
the wall

matthew-os

Matt only · private

  • Matt's personal agents
  • Property, wealth, personal admin
  • Not your concern — ever
2

The families of agents

One agent, one job, running on a schedule so a person doesn't have to.

Daily Dashboards

Yesterday's revenue, orders, costs & profit written into each store's sheet every morning.

Freight

Works out shipping on every paid order and posts the quote straight onto Shopify.

Spam Rescue

Finds real customers Gmail wrongly dumped in spam, before they're lost for good.

Payments

Matches bank-transfer payments to the right order and lines them up for Judy.

Ads

Watches ad spend and performance and suggests moves — you approve, it never auto-runs.

Product Hygiene

Flags messy or drifted product listings across the three catalogues each week.

SEO & Stock

Tracks Google rankings and warns when a top seller is about to run out of stock.

Daily Digests

Rolls the day up into one clean email so nobody stitches numbers together by hand.

3

How a change flows

You work in the first two boxes. The cloud follows on its own.

Your PC
Edit
Talk to Claude Code in the folder. It makes the change; you review.
→push
GitHub
Master copy + backup
The safe, shared source of truth. Nothing lives only on your laptop.
→auto
Railway
Runs it, 24/7
The cloud updates itself the moment GitHub changes. You never log in here.
Push to GitHub and Railway auto-deploys — no publish button, no server to log into.  ·  Watch it all on the Control Tower → Dashboard tab: green = fine.
4

The four copies

Not four versions — four copies of one master. GitHub is the master; the rest follow it.

Matt's Mac

His copy, for when he works on it. A desk, not a different version.

Your PC

Your copy, where you and your Claude make changes. Your working desk.

GitHub — the master

The one master copy, and the backup. When anyone says "the code", they mean this. It's always right.

Railway — runs it 24/7

Clones the master and does the actual work around the clock. No laptop has to be on.

Think of GitHub as the original in a filing cabinet, and the others as photocopies kept in sync with it. There's no "which version is right?" — GitHub is. If a copy falls behind, it just gets refreshed. Nothing is lost.
5

Push and pull, without the jargon

You never type either one. Here's all they mean.

Pull
Grab the latest first
Brings your copy up to date with anything Matt changed, before you start.
 
Push
Save it back to the master
Sends your change to GitHub — and Railway auto-deploys it from there.
When you ask your Claude to change something, it pulls the latest, makes the change, then pushes it back — as one smooth motion. The only habit: let Claude handle it, and try not to edit the exact same file as Matt at the exact same moment (rare — and Claude sorts out any clash for you).