Precise · Internal · load this on the screen

Tomorrow, on this screen

Wed Aug 5 · 2–5pm · Spring Place 508 — then Polymarket at 5pm, Mediaocean Thu 10:30 at 120 Broadway, iHeart Fri 1:30 · Click between arcs as the talk moves · 15 switch tabs · recording runs from minute zero · nobody takes notes, Claude catalogs the transcript

Here is what we believe, and why this week is the week. Precise wins in the sandbox the new‑media crowd ignores: the very large, old‑world media enterprises whose legacy estates are the business. It is where MadHive made its money, and it is where three doors opened at once: Mediaocean tomorrow morning at their office, where Bill wants a bet that lets them own the next phase. Polymarket at five today, where Peter built us the warmest intro we have ever had. iHeart on Friday, where the proof of concept was granted out loud and just needs its dates. None of this was luck. It was research, questions, and working product, stacked patiently.

7000 rpm · Ford v Ferrari · Le Mans
Ken Miles on the Mulsanne Straight, engine screaming, and he holds it: "wait… wait… wait…" and then, at exactly the right moment, he drops the gear and buries the pedal. We played this clip at MadHive when the DSP first found traction. It gets played again today, because the moment is the same: we have been short‑shifting on purpose. This week we take her to seven thousand.

Then three things, and only three. The files go on screen and we argue with them, as sloppy as the thinking needs. The recorder runs from minute zero. And Claude catalogs everything into the files the same day: positions, objections, the phrases that sound like us, and every deck we ask for. Nobody takes notes. Everybody drives.

The company · the politics
Are we reading the room right: does Bill's growth hunger carry this if Zvika digs in? Who else at Mediaocean needs to feel ownership before the bet meeting?
The machine · decision classes
If Kane resists the buy grid, which decision class is the fallback? Is the payable‑source pick really the best unobvious wedge, or is dispute policy stronger in a finance room?
The seam
Is "your compliance story" the right altitude for Markman, or a step too far for meeting one? Say the one‑sentence version each of us would use.
The assumptions
Which A‑rows would each of us personally bet against? What belief are we carrying that is not in the register at all?
The rooms · the yeses
Are the three load‑bearing yeses the ones we would actually trade for? Is learning retention truly first‑paper, or negotiable?
Wednesday · the run sheet
Say the two opening lines out loud. Do they sound like us? Who really carries each beat, and what does a great Thursday at Mediaocean feel like when we walk out at noon?
The program · the substrate
One machine, or does bundling three workstreams read as overreach? Do we say the substrate goal in the room, or let the boards imply it?
The boards
Would Kane recognize these screens as his product? What do we cut so the walkthrough lands in twenty minutes, and which board stays on screen while we talk?
The connection map
Invited overlay: smart, or a trust risk in the first ninety days? Do we say the Boombox trial on the OMG seat out loud Thursday?
The wedge · five facts
Which fact opens? Is the share‑gap framing safe to say to their faces, or an insult to the people who bought the media?
The first proof
Is the World Cup retrospective the ask, or is the coverage read alone the safer first yes? What is the smallest grantable thing that still starts the track?
The room
Pre‑brief Anthony through Peter, or let the acceptance‑rule question land live? How does Jenner become the hero rather than the graded?
The company · the raise
Does the $20B raise framing help or spook? Does anyone say the word Kalshi, and who?
The working deck
Which spread opens the meeting? Boards live on screen, or the leave‑behind? Is the path story a meeting‑one idea?
The questions P01–P13
Which three answers do we most need before scoping anything? Which does Peter answer for us before the 5pm call today?
Positioning · pricing
Referee‑not‑player versus in‑house brain: where exactly is our line? If they ask what it costs, in the room, what do we say?

The thread: Jul 30 demo call, 32 minutes: Adam, Spencer, Matt, Jordan (day four) with Josh Backer and Matt Pilcer. Matt walked the live dashboard; the room engaged; Adam floated the browser‑plugin overlay path. The checkable deck shipped the same day and is the strongest single artifact in the thread. Transcript filed.

Where it stands
Jul 30 demo went well (Josh Backer, Matt Pilcer; 32 minutes; dashboard shown live). What was the follow‑up we owe, and who owns the thread?
The deck
The checkable deck ("What the Listen Was Worth": two questions, governance in, no new interface, recommendations not writes, the quarter‑end Tetris) is live. Does it need the dossier treatment before the next touch, or is the deck enough?
The plugin moment
Adam offered the browser‑plugin path on the call ("a go‑over on top of whatever you need"). Same invited‑overlay question as Mediaocean: smart, or premature?
Priority
Where does iHeart sit against Mediaocean and Polymarket this month? What is the smallest move that keeps the thread warm without splitting focus?

Record from minute zero. Re‑room: the transcript diffs against the files; decisions resolve, outcomes become walls, same day, same URLs. Manifest: every deck request becomes one line: audience, register, spine, the verbatim language, the candor rules. Build: from the manifest, reusing the boards; anything external runs the adversarial pass. Publish: pages.dev, noindex, toggle. Grade: the next meeting's transcript runs the loop again.