Founder Bot walkthrough → founder-agent brief

---
name: founder-bot-walk-brief
description: "Turn a FYJ Founder Bot phone walkthrough (Founder View, Agent View, or both, audio or silent) into a UUID and a three-part founder-agent briefing site — background, importance for Janhavi, instructions — with reconstructed stills and an iPhone-safe ZIP. Use when the user shares a Founder Bot recording, asks to research the walk, brief the founder agent, index page problems (Current picture, five headings, story versus stats, stale chrome), or repeat the live-gate / Agent View / reach-story compile task. Not for Gemini shares (use gemini-share-archive)."
type: workflow
lifecycle: active
user-invocable: true
metadata:
  author: Janhavi Ravi Iyengar
  short-description: Walkthrough to UUID plus 3-part briefing site and ZIP
---

# Founder Bot walkthrough → founder-agent brief

Turn a **phone walkthrough of FYJ Founder Bot** into one briefing: research every point on screen, write three parts, mint a UUID, typeset a site with sub-navigation for those parts, reconstruct stills, pack a ZIP.

Worked examples in this project:

- Founder View, 30 Aug 2026 13:35–13:39 — UUID `e834b2f2-3b2b-47a0-9950-04f9f9d0beec` — [public/live-gate-brief.md](../../../public/live-gate-brief.md)
- Agent View, 30 Aug 2026 14:07–14:11 — UUID `e93e1003-5847-4b58-b856-b8fe7bb601f6` — [public/agent-view-brief.md](../../../public/agent-view-brief.md)
- Founder View then Agent View critique, 30 Aug 2026 14:52–15:01 (audio on) — UUID `58cd58c1-aee9-45a7-8462-c3a687e09047` — [public/reach-story-brief.md](../../../public/reach-story-brief.md)

Read on demand: [references/brief-contract.md](references/brief-contract.md).

## 1. When to use

- User attaches or describes a phone recording of `vps-9d119ef4.vps.ovh.net` / FYJ Founder Bot (Founder View, Agent View, or both; audio or silent)
- User asks to research the walk, explain why it matters, and instruct the founder agent
- User asks to repeat “this task” (background / importance / instructions / UUID / site / stills / ZIP)
- User indexes problems with the page (Current picture, five headings, story vs stats, stale chrome)
- Slash: `/founder-bot-walk-brief`

Do **not** use for Gemini shares (that is `gemini-share-archive`), or for walks of other products.

## 2. Standing constraints (never break)

These are product rules, not style. A briefing that names a customer or moves P is wrong even if the site is beautiful.

1. Do not name a customer.
2. Do not move P. `p-evidence.md` stays empty unless the walk itself shows it filled — then report that as a fact, do not fill it.
3. Do not unpark, release, or install the first-customer cut (`63e813ea` when that id is on screen).
4. Do not treat a menu, scale mechanism, constraint, overlay, HTTPS/401, or “got stronger” as a compiled path.
5. Do not assemble. Do not hire the waiting list. Do not stand up the paper roster.
6. Do not invent counts, hashes, or card titles. If it was not on screen, it is missing, not guessed.
7. A model is not a customer. Third-party overlay is not accepted market/path language.
8. Strength is not a path. Peer toggle is a layer transfer, not P. Firing the clock is not taking the founder job.
9. Do not solve reach by naming a buyer. A first runnable hour that “cannot be walked without naming a buyer” stays uncompiled.
10. Do not treat “the car should have been moved to the market” or “maybe at five fifteen” as permission to unpark the first-customer cut.
11. “Released today (26 Aug 2026)” on a later calendar day is stale chrome, not a slot rewrite. Fix the adverb; do not rewrite the Current slot line.

## 3. Sequence of work

### 3.1 Capture

1. Walk every frame. Founder View and Agent View are peer surfaces — record which one this walk used.
2. Inventory: clock, battery, host, login, five headings / Agent View tabs, meters, hashes, hour-log rows, waiting list, score/KPI lines, evidence cards, directory live vs paper.
3. Independent check of the host: unauthenticated GET. 401 = login gate. Dead link = failed publish. 500 = failure.
4. If the MP4 binary is not on disk, reconstruct stills from the frames. Caption them as reconstructions. Do not invent screenshots of screens that were not walked.

### 3.2 Mint the UUID

New UUID per walk. Do not reuse the previous capture’s UUID. Record the previous capture as **related**.

### 3.3 Write the markdown (source of truth)

Follow [references/brief-contract.md](references/brief-contract.md). Required:

1. Title = the live-door English from this walk (not a slogan).
2. Document control table.
3. Contents with slugs matching `slugifyHeading`.
4. **§1 Background** — geography, timeline, what was on screen, what is not a compiled candidate.
5. **§2 Importance for Janhavi** — destination $2.5–5bn, cost of empty P, hours compounding on the wrong object, what failure looks like.
6. **§3 Instructions for the founder agent** — do-not list, compile definition, sequence, candidate template, validation, reply-once, close conditions.
7. Provenance.

### 3.4 Typeset the site

- One homepage. Part pills **1 · Background / 2 · Importance / 3 · Instructions**, each with its own sub-nav.
- Show only the current part’s markdown (document control with part 1; provenance with part 3).
- Meters from this walk (do not copy 109/41/13 from a different walk).
- Copy UUID. Download ZIP uses fetch + blob / iOS `navigator.share({files})` — never `<a href=".zip">`.
- Editorial tokens: paper `#F4F0E8` / ink `#1A1D23` / steel. Fraunces + Source Sans 3. No gold/purple chrome on the briefing site.
- Related previous capture as a markdown link, not a second competing homepage unless the user asks for both.

### 3.5 Stills

Reconstruct phone chrome matching the walked surface (Founder View cream/black headings, or Agent View dark storage / cream evidence / ITERATE ledger). 390×844 @2x. Place stills in the markdown next to the section they prove.

### 3.6 ZIP

Offline `index.html` + `sources/` (markdown, stills, provenance.json, related captures). Nitro `Content-Disposition: attachment` + `application/octet-stream`. Pack on `prebuild`/`build`.

### 3.7 Verify

`npm run typecheck`, `npm run build`, `node scripts/browser-smoke.mjs` on dev and on the built preview with `--baseline`. Click parts 1/2/3. Inspect desktop and mobile screenshots. Leave the dev server up.

## 4. How to validate

- Every count, hash, and card title on screen appears in §1. Missing integers are not invented.
- §3 do-not list includes assemble / waiting list / slot-rewrite when those were on this walk.
- Compile template includes who / why / how / next when Agent View stated they were missing.
- UUID is unique. Related UUID is cited, not overwritten.
- ZIP downloads on iPhone without previewing.
- No customer name. P untouched. Cut still parked.

## 5. What to return

1. The live briefing site (three parts, stills, ZIP).
2. UUID, short name, live-door English, binding action if present.
3. One-paragraph note of what this walk added versus the previous capture.

Do not dump frame-by-frame OCR to the user; the brief is the record.

## Common issues

| Problem | Fix |
|---|---|
| iPhone previews the ZIP | Never navigate to `.zip`. Fetch bytes; share files on iOS; else octet-stream blob + attachment header |
| Hydration mismatch on stills | Lift `img` out of `<p>` before wrapping `<figure>` |
| Reused UUID | Mint a new UUID per walk; cite the previous as related |
| Copied meters from another walk | 85/89/0 compiled are the 14:52 walk; 87 / S 0 are Agent View 14:07; do not copy across |
| Treated “got stronger” as a path | Strength is context or constraint. Compile needs who / why / how / next |
| Named a buyer to walk reach | Reach stays the blocker. A name is a customer |
| Unparked because “car should have moved to market” | Parked cut is a milestone, not a live Open gate. 17:15 only |
| Assembled the waiting list | Binding action is ITERATE. Paper roster is not staff |