Dual-Rail

One session. Two rails. You oversee, review, QC, orchestrate. The wait is not a hole to fill with another app. It is the other job — the one you were originally good at.

← Productivity · AI Agents · Ecommerce / GTM · AI-native GTM · Distribution engineer · Named threads · Operator vs engineer

Why this page

Personal SOP. Summer 2025 through now was programmer-mode: one Pomodoro, one deep-work task, five-minute break, repeat. That was correct when you were the compiler.

It is wrong now. Agents hold the 30 minutes. You start, wait, QC, next prompt. The wait felt like failure, so you opened another build. Urgent products ran out. GTM stayed “later.” GTM was the original skill.

Friends: there is no programmer role vs marketing role. One seat. That sentence already lives on this site as operator, distribution engineer, builders and sellers, five roles. What was missing: how you sit. Dual-rail is the sitting.

One-sentence TL;DR

Same calendar block, two rails (dev threads + GTM / Bernie). When a thread is waiting, default to the other rail. Do not invent a product to fill silence. QC is the job on both. Pomodoro can keep the timer. It does not get to keep “one task type per tomato.”

What actually changed

	Old (Pomodoro deep work)	Now (dual-rail)
Who compiles	You. Stack in RAM for 25–30 min.	The agent. You hold the dashboard.
Context switch cost	High. Reloading a codebase hurt. Left/right split made sense as a schedule.	Low. The thread remembers. Reloading “did Bernie send it?” is cheap.
Idle	Break. Or guilt.	The other rail, unless a thread is blocked on you.
Symptom of starving GTM	Empty marketing calendar you never opened.	Running out of urgent things to build while five threads still run.
Your job	Do the work.	Oversee, review, QC, orchestrate. Same verb on code and on outreach.

Left-brain / right-brain was a load-cost story, not a soul story. Builder and seller are still different jobs (Drucker still holds). They are no longer different days or different identities.

The two rails

	Dev rail	GTM rail
Who holds the thread	Grok Build / Codex / Cursor / named sessions (/grokthreads)	Bernie.agent, CRM, one outreach loop, recap from Granola
While they run	Do not start a fourth product.	Queue, draft, enrich — no send until you QC.
When they ping	Read the diff. Next instruction or kill.	Approve, rewrite, or kill. Same fence as Require Approval.
Done looks like	Shipped or parked with a note the next sitting can resume.	A human heard from. A lead moved. A loop closed (quarterback).

GTM is not “content someday.” It is the always-on system on /gtm and the CBS plan on /gtmcbs: avatar, enrich, outreach, report. Bernie is that thread, not a marketing day on Friday.

The rule (master this)

Open both rails when the session starts. Dev dashboard (named threads) + GTM dashboard (Bernie / CRM / today’s list). If GTM isn’t open, you will fill waits with builds.
Default wait-action is the other rail. Compile running → GTM QC. Bernie drafting → glance at the diff that just finished. Not Twitter. Not a new repo.
A thread blocked on you beats the other rail. That’s the interrupt. Handle it, then return. Don’t batch “I’ll review all the agents at 4.” They stall; you invent work.
Do not start a build to fill silence. If both rails are waiting on the world (email, deploy, a human), that is the five-minute break. Body still needs it.
QC is the same muscle. Diff: did it do what I asked, any send/spend/publish? Outreach: is the avatar right, is the claim true, would I send this? Same skepticism as Jev shadow mode — don’t flip “active” on day one of a new loop.
One outcome per named thread. Stolen from Grok threads. “Fix checkout” is a thread. “GTM: CBS follow-ups” is a thread. “Play with a new framework” is how the urgent list dies.

A sitting (90 minutes, not six tomatoes of only code)

Timer on if the body wants it. Session is the unit, not the tomato type.
Write two lines at the top: Dev: ___ / GTM: ___. If you can’t name the GTM line, that’s the starvation.
Unblock whatever pinged overnight. Then start at most one new dev thread if something is actually urgent to ship.
Every wait: Bernie / CRM / one follow-up / one avatar note (/customeravatar).
End of block: park threads with resume notes. GTM: what moved. Not “I was busy.”

Granola after a call is GTM rail, not a third mode (/granola): enhance, skim, then either recap email or first slides. Still QC.

What this is not

Not ADHD multitasking. Six tabs and no QC. Dual-rail is two dashboards and a default.
Not “I’m a full-stack marketer now.” You are an operator who already knew GTM and spent a year as the compiler. The agents took the compile. Take the other rail back.
Not melting roles in the company. Boris’s five still describe how a team ships. You personally are sitting Grower + Builder in one block because the staff is agents.
Not skipping Require Approval because GTM “has to move fast.” Fast is queued drafts. Send is still a human gate (gym hack).

How this maps here

Page	Its job	Dual-rail uses it as
/gtm · /gtmcbs	Always-on GTM system	The GTM rail’s loop, not a separate week
/distributionengineer	Distribution is the scarce skill	Why the wait goes to GTM, not a fourth app
operator vs engineer	Conductor, not model-trainer	The seat you already occupy
/grokthreads · /tmux	Named, resumable work	How the dev rail doesn’t live in your RAM
/emailquarterback	Inbox → work → close	GTM rail’s close-the-loop standard
/customeravatar	Who it’s for	A GTM wait-action that isn’t “new feature”
/chiefofstaff · /grokbotceo	One inbox, specialists	You are the inbox. Rails are the specialists.

What we keep vs skip

Keep: timer for the body; two named rails; wait = other rail; interrupt if blocked on you; QC on diffs and on outreach; Bernie as GTM thread; park with resume notes.
Verify: whether Bernie’s CRM is actually the GTM dashboard (if it isn’t, the rail will collapse back to Slack); whether “urgent build” is a real user or a silence-filler.
Skip: one-task-type tomatoes; a new repo because Codex is compiling; “marketing day”; calling this multitasking; sending without approval; pretending GTM is left-brain-optional.

Related on this site

AI-native GTM · CBS GTM plan
Distribution engineer — why build-only is the old hierarchy
Builders, sellers, measurers
Five roles · Operator vs engineer
Named threads · Loops
Proactive · Agency
Granola — call ends, GTM rail has the note