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 stills and an iPhone-safe ZIP. When the founder says reconstructions are not accurate, crawl the live host and screenshot every page and section. Use when she asks to traverse every founder/agent page, build a live directory, or generate an explainer she can query and steer. 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, capture stills (live crawl when she says reconstructions are not accurate), 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)
- Agent View then Founder View inventory, 30 Aug 2026 16:23–16:37 (audio on) — UUID `d42ef660-60a1-4981-8cab-5a1280d50fd6` — [public/cohesion-inventory-brief.md](../../../public/cohesion-inventory-brief.md)
- Directory / template (critique of that briefing, then the same walk re-attached), 30 Aug 2026 17:13 then 16:23–16:37 — UUID `7c3a9e14-6f2b-4d80-9c1e-b8a4d2f0e571` — [public/directory-template-brief.md](../../../public/directory-template-brief.md)
- Live crawl of every founder and agent page, 30 Aug 2026 ~20:04 — UUID `c9e2b7a1-4f58-4d3c-91ae-7b6d0e8f2453` — [public/live-directory-brief.md](../../../public/live-directory-brief.md). Original screenshots, not reconstructions.

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, cohesion, section purpose)
- User asks to screenshot every section and list what it is for, for the founder and for the agent
- User says the last briefing missed the point: background should be a directory, importance a per-section template, instructions a one-off explainer task
- User says reconstructions are not accurate, or asks to traverse every founder page and every agent page from the live host and screenshot each section
- 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.
12. Do not invent section purposes as the founder’s original words when the walk is an inventory. List the sections. Fill purposes only as the founder-agent job, labelled as such.
13. Do not treat REACH-STORY surface paint as finished cohesion. Paint is not purpose. Concatenated stats are not a statistical view. Addressed-and-still-open is not closed.
14. Do not copy meters across walks. Live crawl 30 Aug evening: 0 compiled / 122 open (0+89+19+0+14) / 93 dated / S 0. 0/117/90/S 0 are the 16:23 inventory. 0/85/89/S 0 are the 14:52 walk. 87 / S 0 are Agent View 14:07.
15. If the founder says the last briefing missed the point: §1 is a directory (what it is, what page, screenshot), not a diagnosis. §2 is the template plus why the reading matters for Janhavi, per section. §3 is the one-off task to fill that template on an explainer — not the standing do-not list.
16. If she says the directory is not accurate: crawl the live host. Screenshot every page and every named section. Do not reuse reconstructed stills. Independent check may now be 200 (shareable until the first-customer gate); 401 is a failed publish while contract 06657cd0 is live. §2 is why every surface must have meaning for the $2.5–5bn goal. §3 is an explainer with Janhavi / agent / query / steer — not reconstructions.

## 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. 200 readable = shareable until the first-customer gate. 401 = login gate or failed publish while contract 06657cd0 is live. Dead link = failed publish. 500 = failure.
4. If she asked to traverse the live site: crawl every Founder View page and every Agent View page. Screenshot chrome, each named section, each Identity point, each doll-gate bucket, open and archive lists. Caption stills as original captures.
5. If the MP4 binary is not on disk and she did not ask for a live crawl, 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. **If the walk is a directory job:** list every section in walk order (ID, page, name, on screen, asked, still). Do not explain why anything went wrong.
5. **§2 Importance for Janhavi** — destination $2.5–5bn, cost of empty P, hours compounding on the wrong object, what failure looks like. **If the walk is a directory job:** for each section, the template (the answer we are looking for) plus why she needs the right reading, plus why that reading serves the vision.
6. **§3 Instructions for the founder agent** — do-not list, compile definition, sequence, candidate template, validation, reply-once, close conditions. **If she asked for a one-off explainer task:** how to fill the template for every ID and build an explainer she can critique. Do not paste the standing do-not list into that task.
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

Prefer original captures of the live host (390×844 @2x) when she asks for accuracy. Reconstruct phone chrome only when the host cannot be crawled and an MP4/frame exists. Place stills next to the section they prove. Do not mix reconstructed stills into a live-crawl UUID.

### 3.6 ZIP

Offline `index.html` + `sources/` (markdown, stills, provenance.json, related captures). Nitro `Content-Disposition: attachment` + `application/octet-stream`. Pack on `prebuild`/`build`. **The ZIP must be under 25 MB.** Crop tall full-page lists (top + bottom + omission bar) rather than shipping 95k-px screenshots. Never fall back to unbounded `element.screenshot()`.

### 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 | 0/117/90/S 0 are the 16:23 inventory; 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 |
| Invented section purposes during an inventory walk | List IDs first. Fill founder/agent purpose only as the founder-agent job |
| Treated REACH-STORY paint as cohesion | Story card + Market tabs + adverb fix are paint. Concatenated stats and 117 open cards are the live issue |
| Wrote a diagnosis when she asked for a directory | Background = inventory in walk order. Importance = template + why the reading matters, per section. Instructions = one-off explainer fill. Do not explain what went wrong. |
| ZIP over 25 MB | Crop tall lists (top + bottom). Do not ship unbounded element screenshots. Pack fails if the archive is ≥ 25 MB. |