PINAVOX · after the X1 goes live

How It Runs

Where you work, where the machines work, and where everything is actually saved.

The short answer

Your Mac stays your workshop. The X1 is the shop that never closes.

Nothing about how you work today gets taken away. You still open VS Code, you still talk to Claude Code exactly as you are right now, your vault still lives on this Mac and still opens in Obsidian. Local files stay local.

What changes is only this: things can now happen when you are not at the Mac. That is the entire upgrade. The X1 is not a replacement for anything — it is the part of the system that stays awake.

01 · The whole system

WHERE YOU TOUCH IT Mac · VS Code deep work, exactly as today Phone · Slack capture + dispatch, anywhere Any device · claude.ai ask the brains directly DM → APEX MCP connector straight to a brain WHAT DOES THE WORK THE MAC Claude Code · full skills vault on disk · Obsidian client calls · video rig awake when you are THE X1 APEX · answers Slack logged-in browser · both inboxes team's shared exit IP awake always you reach the X1 from the Mac or phone (Tailscale) they never sync files to each other — see below WHERE EVERYTHING IS SAVED Git repos vault, notes, playbooks, code a full copy on EACH machine GitHub is the meeting point The brains Stefan · PINAVOX · per client live state, drafts, planner Cloudflare — always reachable Drive · Notion · Sheets documents people open team ops, trackers unchanged Both machines read and write the same three places. That is what makes them interchangeable — not a sync tool between them. The old setup failed because it tried to keep two machines in sync directly. This one never does.
Fig 1. Three ways in, two machines that do work, one shared place for everything that matters. The Mac and the X1 never copy files to each other — they both talk to the same repos and brains, which is why either can pick up where the other left off.

02 · Your direct questions

You askedAnswer
Do I still work here, in VS Code?Yes, unchanged. This is still where deep work happens — writing, building, client artefacts, long sessions with full skills and context. The X1 adds nothing to and takes nothing from this.
Is nothing local on the Mac anymore?Wrong the other way round. Your whole vault stays on the Mac as real files — that is what Obsidian opens. The X1 gets its own copy of the same repo. Two full copies, both real, both local to their machine.
So how do they stay in step?Through GitHub, not through each other. A session pulls before it works and pushes when it is done. No background sync daemon anywhere — that is precisely what broke last time and it is gone by design.
What is actually new?Work that continues while the Mac is closed: Slack answered, browsing done from a real logged-in browser, both mailboxes reachable, the team sharing one IP, scheduled jobs running.

03 · Where a piece of content lives

1 · Idea phone, car, meeting 2 · Captured Slack → idea bank 3 · Drafted brain, by number every version kept 4 · Reviewed Google Doc you approve 5 · Published LinkedIn, blog link on the board 6 · what worked feeds back — the tracker writes performance into the brain so the next hook is chosen from evidence, not memory Steps 1, 2 and 6 keep running while you sleep. Steps 3 and 4 are where you and your taste come in.
Fig 2. The answer to "where is the content saved": the text lives in the brain, versioned by content number, from first draft onward. Google Docs stay the review surface. The board holds status and published links. Nothing lives in a chat window.
The rule that prevents the old chaos: one home per kind of thing. Knowledge and notes in the repo. Live status and drafts in the brain. Documents people read in Drive. Nothing is stored in two places, so nothing can disagree with itself.

04 · Which brain answers

Three separate brains, and you never pick manually — the surface you are on decides, and it is enforced by which keys that session holds, not by remembering to say the right thing.

Where you areBrainHolds
Slack DM with APEXStefan privateTaxes, legal, family, personal admin, life logistics
#stefan-ops · content workPINAVOXContent, leads, sales, playbooks, client work
A client's own ClaudeThat client'sOnly their content. Physically separate database
claude.ai on your phoneWhichever Project you openedOne connector per Project, so the Project is the switch

A company question asked in the private brain simply cannot reach company data, and the reverse is equally true. Not a policy — the session literally has no key for the other side.

05 · A week, concretely

Tuesday · 07:40 · in the car

An idea arrives

You dictate it into Slack. Three seconds, no session, no waiting. It is safe the instant you hit send.

Later: the idea is filed in the bank with the rest. In the morning brief you see it again, reply in that thread — days later if you want, the conversation is still there — and it becomes a draft.

Tuesday · 09:00 · at the desk

Content session

VS Code, Claude Code, exactly like today. The writing rules, the stencils, the scene bank from your own calls — all loaded. You write, the draft is saved into the brain by number, the review doc lands in Drive.

Unchanged from today. This is the part that already worked.

Wednesday · 11:00 · client meeting

The board is on screen

Questions get typed as they are said. Priorities set live. A question becomes a numbered piece in front of everyone. The client sees their own system moving.

Afterwards: the same board is what their team works in all week, from their own logins.

Thursday · 15:30 · between calls

Dispatch something

"Find flights and hotels for Kelowna, downtown but not seven nights of downtown prices." You close the laptop and go to the next call.

The X1 does the work in a real browser on your own line, and posts the comparison back into that Slack thread. You reply to dig deeper.

Sunday · 03:30 · everyone asleep

The quiet shift

The nightly pass reads what happened, distils the real lessons, and writes them into the brain with sources. The tracker pulls last week's numbers.

Monday morning the brain is smarter than it was on Friday, without anyone having logged anything by hand.

06 · What actually changes

TodayAfter the X1
Deep workMac, VS Code, Claude CodeIdentical
Your vaultLocal files, ObsidianIdentical
Idea from the roadSent, then often lostFiled, resurfaced, continued in the same thread
Asking for work while awayOnly if the Mac is openAny time. The X1 is awake
Personal + work email togetherOne account at a timeBoth, in one place
Team on LinkedInThree countries, one accountOne shared IP, your own line
Cost of all this—Roughly nothing. Hardware you own, subscriptions you have
The one honest limit. The X1 is a laptop in a room, not a datacenter. It has a battery for outages, unlocks itself after a power cut, restarts its own services, and pings if it disappears — but if it truly dies, the fix is hands on the machine. That is why no client ever depends on it: client work runs on Cloudflare, where there is nothing of yours to fail.