Voice pass proposals — /journey ("The Same Desk")

One table per stage. Protected lines untouched. Char delta noted where it approaches the ±15% choreography budget. Nothing has been applied.

Antitheses kept (2, per spec): "It isn't a tech career. It's about to cause one." and "The same job, and a completely different job."

Wobbles introduced (3 total): the weekend, the CTO ask, the finale.

Stage 01 · The bedroom

The switch — fact line
Before Every early decision from here is the same decision: this is interesting → pour hours into it.
After Most early decisions from here work the same way: this is interesting → pour hours into it.
Why "is the same decision" is epigram polish; the LinkedIn source states it flat ("Most of my early decisions were simply…"). −4 chars.

The first invoice — prose
Before Somebody pays you for this. That changes what it is. It stops being a thing you do instead of sleep and becomes a livelihood - a permission slip nobody at school ever handed you. By January 2012 you're blogging advice at other developers: say yes to everything, hire yourself. You've been taking both pieces of it for a while.
After Somebody pays you for this. That changes what it is - it stops being the thing you do instead of sleep. Nobody at school ever mentioned this as an option. By January 2012 you're blogging advice at other developers: say yes to everything, hire yourself. You've been taking your own advice for a while.
Why Kills the transformation-antithesis and the permission-slip metaphor (the protected fact line already lands the beat). "Nobody at school ever mentioned this as an option" keeps the school contrast as a flat literal statement. −7% chars.

Stage 02 · The workshop

The shelf — prose
Before Filtergram (Fast Company writes it up, October 2019). Shades. Ekko (sold, 2020). Somna. Closeloop, ContentCaddy, PlaySync. Most of them die. That isn't the tragedy it sounds like: every one taught something the next one used. The shelf isn't a trophy case. It's a syllabus.
After Filtergram (Fast Company writes it up, October 2019). Shades. Ekko (sold, 2020). Somna. Closeloop, ContentCaddy, PlaySync. Most of them die. Fine. Every one taught something the next one used, and you'd have built them anyway.
Why Two stacked antitheses → one flat "Fine." (house rhythm) plus the literal statement that was already doing the work. "you'd have built them anyway" is the honest, slightly self-directed truth from the LinkedIn Venn framing. −13% chars — flagging: at budget edge; happy to pad with a beat of product texture if the column height matters here.

The weekend — prose (wobble 1 of 3)
Before You build a fake API in a weekend so front-end developers have something to test against. You name it ReqRes. You have no idea what you've just started, which is true of everything on this desk, but this one especially.
After You build a fake API in a weekend so front-end developers have something to test against. You name it ReqRes. You have no idea what you've just started - though to be fair, you could say that about everything on this desk.
Why The ending currently steps up ("but this one especially"); the self-qualification steps down and adds the first wobble. ±0% chars.

Stage 03 · The boardroom

Rest — prose (wobble 2 of 3)
Before You ask for it precisely because it'll force you into a growth you can't back out of. The desk gets bigger and less yours. For the first time, the thing you're building is mostly made of people.
After You ask for it because it'll force you into a growth you can't back out of. That's the theory, anyway. The desk gets bigger and less yours. For the first time, the thing you're building is mostly made of people.
Why "precisely" is the copywriter's certainty; "That's the theory, anyway." is the hedge the moment deserves - he didn't know if he could do it, per the book. +1% chars.

First seat — no change proposed

"and quiet, solid proof that the system is real" stays: book-derived, sits after the protected deflation, and reads as relief rather than swell. (Listed in audit as question #18 - flag if you disagree.)

Second seat — prose
Before …the weekend a DNS change took the whole API down while your alerts were switched off - a mistake you only make once, and write about forever.
After …the weekend a DNS change took the whole API down while your alerts were switched off - a mistake you only make once. The fix was better alerting, and it took an afternoon.
Why "write about forever" auditions for a pull-quote and steps up. The book's actual epilogue to that story is mundane: the fix was simple alerting config. Flat, concrete, slightly embarrassing - the house move. +4% chars.

The notes — prose
Before So you start writing down everything nobody told you - not the polished conference-talk version, the 4am version, the mortified version, the version with your own name in the blame column. The whiteboard fills up.
After So you start writing down everything nobody told you - the 4am version, the version with your own name in the blame column. The whiteboard fills up.
Why Quadruple anaphora → two items (the book uses two). "The whiteboard fills up." stays as the flat landing. −14% chars — at budget edge, flagging.

Stage 04 · The farm office

Rest — prose
Before The desk faces a window now. You consult from here - tech lead on a government data platform, of all the places a wired panel was heading - and you're building again too, because you never actually stop. It took twenty years to learn that the desk was never the point; the window is.
After The desk faces a window now. You consult from here - tech lead on a government data platform, of all the places a wired panel was heading - and you're building again too, because you never actually stop. Twenty years to get a desk with a view. The commute's better, anyway.
Why Kills the triple tell (antithesis + metaphor narration + crescendo). The replacement is literal, wry, and steps down. −2% chars.

Still running — prose
Before ReqRes, the fake API from that 2015 weekend, is still running. It outlived products you loved more, companies that paid you more, and every roadmap it was never on.
After ReqRes, the fake API from that 2015 weekend, is still running. It outlived products you loved more and companies that paid you more. It was never on a roadmap. It just runs.
Why The ascending triad was auditioning; breaking the third limb into two flat sentences ends the beat stepping down. "It just runs." echoes the card title without announcing it. +5% chars.

The book — prose
Before The printed book standing on the desk is The First CTO: The Job Nobody Explains. It is the whiteboard from the boardroom, finished - every note nobody gave you, handed backwards to whoever sits down next.
After The printed book standing on the desk is The First CTO: The Job Nobody Explains. It's the whiteboard from the boardroom, typed up and finished - everything you needed someone to tell you in week one, in one place.
Why Keeps the cross-beat callback (grounded, not symbolic), contracts "It is", and replaces the "handed backwards" crescendo with the book's own plain claim ("what I would have wanted to hear during week one"). ±0% chars.

Finale — prose (wobble 3 of 3)
Before Most things you build will die. The point was never that they wouldn't. Somewhere back there a switch flicked on at your dad's company, and it never went off - it's still the same spark, and the same livelihood, carrying you through to this day. The point - the only point this room has been making - is that you kept the light on.
After Most things you build will die. You've made your peace with that - well, mostly. The switch that flicked on at your dad's company in 2009 never went off, and the livelihood it started is the one still paying for this desk. That's it. That's the story.
Why The spec's named target. Kills the opening antithesis, the spark/livelihood swell, and the symbolism narration - the dimming room and lit window carry the ending visually. Keeps the livelihood as a flat fact (it's Ben's own LinkedIn claim, minus the cadence). "That's it. That's the story." lands on the house rhythm's flat step-down. −22% chars — over budget, flagged: the finale drives the dim scrub timing, so either accept a slightly earlier trigger or I can re-tune the scrub thresholds (two constants in journey.js) when applying.

Open questions (unchanged pending your call)

  1. "nobody is teaching you now. The internet is." (the switch) - antithesis-shaped, but it's your own construction from the original beat spec. I've left it. Kill it if it reads as machine to you.
  2. "and quiet, solid proof that the system is real" (first seat) - kept as book voice. Cut to end on the protected "just relief" if you want the harder stop.
  3. "You ship things. Constantly." (workshop rest) - protected-adjacent house rhythm; untouched, confirming intentionally.