Coach demo build status

Snapshot · 7 September 2026, 15:55 Medellin Links: Lane dispatch · Coaching method · Discovery research · These rules

The coach talks, joins a call, uses your cloned voice and speaks only facts from the person's pack. One thing blocks a demo you can show: the words never reach the screen while the voice is speaking.

9done
5building
2blocked
3needs Yair
Six lanes
Drag sideways when the row overflows
1  Transcript on screen coach-slice3 blocked0%
0 of 4 · Terra high · critical path
1.1 blocked The coach's words never arrive

A real greeting sent only "turn ended" and no sentences, while the voice log shows two sentences spoken. Three replay tests pass and could not catch it.

!
1.2 later The person's words never arrive either

The new desktop page is refused by the service that mints its speech key. One allowlist entry.

1.3 later Interrupt it three times without breaking
1.4 later Check against the old bug list
2  How the coach coaches coach-method 50%
2 of 4 · Terra medium
2.1 done Method written the way you dictated it

Invite instead of a pitch. Quick coaching history. No style asking. Two doors, naming negative habits.

2.2 done Beats and prompt wired
2.3 building Prove it with the real model, not a test

Checks 12 of 12 on paper, 0 of 10 live. It hunted for the key in the wrong place. Unblocked with the keychain path.

2.4 later Fold in the discovery questions
3  What the coach knows about someone coach-packs needs Yair20%
1 of 5 · Luna low
3.1 done Three chats turned into packs

Alejandro 11 facts, Ziad 9, Mariana 7. All three mint and end cleanly.

3.2 building Get the people files out of the shared repo

My error put them there. The repo inherits team access, so six accounts could read them.

3.3 later Strip the private things

A job offer someone was weighing, a detox, illness, an earthquake. None of it belongs in a coach's mouth.

3.4 later Mariana's portfolio in, properly

The colour direction is there but chopped mid-sentence. Being reassembled into real recommendations.

3.5 needs Yair You read and correct the three drafts Y
4  Finding what someone wants coach-discovery 50%
2 of 4 · Terra high
4.1 done A seven question sequence, cited and attacked

A second model tried to break it. Three objections folded in, one rejected with a reason.

4.2 done Your own calls found, after a wrong answer

254 documents, 148 per-call extractions, 15 first sessions. About 25 of your own questions pulled with file and line.

4.3 building Rebuild it on how you actually open a call

Breathing and what feels positive. Permission to be direct. Reflect back before advising. What stopped you solving it alone. The 40 years version and the it-became-easy version. Commitment out of ten, then the gap.

4.4 later Correct the published line that got it wrong
5  This page, but live coach-board needs Yair0%
0 of 1 · Luna medium
5.1 needs Yair Copy the content system board and feed it from the bus

Same numbered blocks, accordions and size sliders as the board you approved in August. Then this page updates itself instead of being hand written. One paste starts it.

Y
6  Coming back to a session coach-persistence 0%
0 of 1 · waits for lane 1
6.1 waiting Save everything, let them pick it up later

Your requirement. The demo shows the start; the real feedback is what happens when they return and go deeper.

What this page is, and how the lanes work
  1. Six Claude and Codex sessions work the coach demo in parallel. Each is a lane with its own ordered items.
  2. They report to one conductor on the session bus. You are not in the relay any more.
  3. An item is only green when a real signal proved it: a test run, a log line, an HTTP code. Never a session saying so.
  4. This snapshot is hand written from the bus. Lane 5 replaces it with a version that updates itself.

Only you can do these

  1. Sit through one call and listen. Greeting, interruption, the plan walk.
  2. Read the three pack drafts once the private things are out, and correct them.
  3. Try it on a laptop with the screen shared, so we know the speakers do not eat your words.

No open decisions

The privacy call, the portfolio call and the no-styles call are all made and dispatched. Nothing is waiting on you to choose.

1.1 The coach's words never arrive

A real greeting sent only "turn ended" and no sentences, while the voice log shows two sentences spoken. Three replay tests pass and could not catch it. A frame by frame log and a fixture that reproduces it were demanded rather than a blind patch. This is the whole demo.

1.2 The person's words never arrive either

The new desktop page is refused by the service that mints its speech key, so their half of the transcript is dead too. Small fix, one allowlist entry, unproven until a real request returns a good code.

Read this before you trust anything green

Every pass so far is green on a text run or a test. Nobody has heard this thing. The coaching beats check 12 of 12 on paper and 0 of 10 live. Until you sit through one call, treat all of it as written rather than working.

LaneCodeTestsLive runHeard by a humanPushed
1 Transcript on screenyesyesfailsnoyes
2 How the coach coachesyesyesnonoyes
3 What the coach knowsyesyesyesnoyes
4 Finding what they wantn/an/an/anoyes
5 This page, but livenonononono
6 Coming back to a sessionnonononono

What the columns mean

Code means it is written. Tests means a test file exercises it. Live run means it ran against the real model or a real call. Heard by a human means you or someone else actually listened. Pushed means it is on the repository, not only on the box.