Harness · Day Eight · Wednesday · 2026‑06‑24

Power hour.
All hands.
Build the coach.

Your peak is 9:30–10:30 · the whole team on one machine
Harness · A two‑week AI bootcamp
01 / 12
The morning read

First, the Rundown.

Quick read, mine the new terms — then we go straight into the build. Today's a build day, top to bottom.

Open today's Rundown  rundown.ai/articles
Classroom · brief
02 / 12
RECAP · YESTERDAY YOU SPLIT UP

Three of you went three ways —
and all three paid off.

The scholarship finder took longer than planned, but the detour was the value: we mapped every way to stand one up, then each of you chased a different thread. Let's bank it before we converge.

Classroom · recap
03 / 12
Scholarship finder · the differences ARE the lesson

Same goal. Four design choices.

Where it runs
Local on the Mac vs. remote on a VPS — with cron and launchd
Memory & hydration
Anthropic Routines + Cloudflare + GitHub for instructions & memory
Essay generation
With vs. without auto-generated essays
Profiles
One seeker vs. multiple plug-in profiles

We learned by differentiating — each approach has a caveat, and naming the caveat is the real engineering.

Classroom · recap
04 / 12
Late afternoon · everyone on their own track

Three tracks, and a real find.

Chris

Finder, deeper

Pushed the scholarship finder further — enhancements and options.

scholarship finder
Nicholas

Started the coach

Began the real-time coach — and found a brand-new way to let it watch. More on that shortly.

game coach
Xander

Broke in

Found the unauthenticated path — rogue account registration. Stood up evidence capture + docs, and captured his own testing methodology as he went.

app-sec · the prize
Classroom · recap
05 / 12
The boot camp's peak
9:30 – 10:30Power Hour

Your hardest work, at your peak.

One hour, highest intensity, the hardest problem on the table. It's a habit I keep myself: I stack my most demanding work on Wednesday morning — midweek, the weekend behind me and the next one not yet pulling, when my biorhythm is at its best.

  • Half of it is real. Half is a trick I play on myself to show up at full power — and it works.
  • Find your own peak, and aim your hardest work straight at it. That's the skill.
The power hour
06 / 12
TODAY · ALL HANDS ON DECK

Everyone builds the
same machine.

No more splitting up. Today the whole team converges on the one build we've pointed at since Day 2 — the real-time game coach. Power hour is for the hardest slice of it.

The game coach
07 / 12
Architecture · the same loop as yesterday

Observe → analyze → decide → speak.

Observehow it watches
Analyzelocal model reads it
DecideClaude on summaries
Speakvoice in your ear

The brain, the voice, and the cadence are settled. The open question — and the choice each of you makes — is the very first box: how does it watch the game?

The game coach
08 / 12
"Observe" · now three ways in

Three ways to let it watch.

Path A

Capture + vision

DXcam grabs your screen → a local model reads it. Works on any game — but fights VRAM and anti-cheat.

watch any game · hard
Path B

Own-game telemetry

Fork a game, add a WebSocket node that broadcasts state as JSON — your own GSI. No vision needed.

a game you build
Path C · NEW

Steam spectator

Let an AI watch from inside the game via Steam. Nicholas's find — details next.

Nicholas · Steam-only
The game coach
09 / 12
Path C · the Steam route · Nicholas

Invite the AI to watch the match.

Option 1

A Steam mod

A mod that exposes live game state for the coach to read — structured, no screen-scraping.

Option 2

AI as spectator

Give an AI worker its own Steam credentials, invite it to your game, and let it watch through the Steam platform overlay in spectator mode.

  • The trade: it only works for Steam games — an acceptable limit.
  • The upside: the coach watches from inside the match, and can run on a separate machine — off your gaming rig entirely.
The game coach
10 / 12
The plan · build in vertical slices · power hour = the hardest one

Pick a path. Get one slice working.

1Input working — pick A / B / C and get the game state flowing inpower hour
2One coaching line — state → Claude → a single piece of advicedecide
3Give it a voice — pipe that line to TTS → your headsetspeak
4The live loop — observe → analyze → decide → speak, hands-free (carries into tomorrow)loop

Power hour goal: getting input flowing is the hardest, fiddliest step — so we put it where you're sharpest.

The game coach
11 / 12
GO

Pick your path.
Spend your peak hour on the hard part.

Rundown's done. The architecture's settled. From 9:30 you're at full power — point it at getting the game state flowing, and by tonight the coach has its first words. Log your time in Harvest.

Harness · Day Eight
12 / 12