FYJ Founder Bot

Founder ViewAgent View

Storage · /home/box/agents/fyj-founder-bot/directory/live-directory-brief/sources/related/directory-template-brief.md

/home/box/agents/fyj-founder-bot/directory/live-directory-brief/sources/related/directory-template-brief.md

30 Aug 2026 20:54 London · 10992 bytes · readable HTML from the file

A directory of every section, in order, so the template can be filled

Directory / template · Agent View then Founder View
Implementation UUID: 7c3a9e14-6f2b-4d80-9c1e-b8a4d2f0e571
This file is the source of truth for GrokBot. The live site typesets the same catalog as a directory (part 1), a per-section template (part 2), and these instructions (part 3).

It is an inventory and a template, not a diagnosis, not a path, not P, not a compile. Purposes are blank. Fill them later, on a separate explainer, so they can be critiqued.


Document control

Field Value
Implementation UUID 7c3a9e14-6f2b-4d80-9c1e-b8a4d2f0e571
Short name DIR-TPL
Job Directory of every walked section, in order. Template per section. Instructions for GrokBot to fill the template and build an explainer.
Capture Critique of the previous briefing, 30 Aug 2026 17:13–17:15 BST, then the original walk 16:23–16:37 BST re-attached. Audio on. Agent View then Founder View.
Host https://vps-9d119ef4.vps.ovh.net
Independent check Unauthenticated GET → 401 nginx Basic realm FYJ
Pages 15 (8 Agent View, 7 Founder View)
Sections 99 (IDs ID-01…SW-04)
Open cards on Overview Evidence 86 · Contract 18 · Slot Work 13 · Overnight 0 · Decisions 0. 86+18+13 = 117
Dated pages 90
Compiled 0
P Empty
S 0 on Confidence / KPIs
Binding on the walked site ITERATE until 17:15 London. This UUID does not restage that close.
Related (missed the point) d42ef660-60a1-4981-8cab-5a1280d50fd6 — previous briefing explained too much. This one is the directory.
Related REACH-STORY 58cd58c1-aee9-45a7-8462-c3a687e09047 · Agent View e93e1003-5847-4b58-b856-b8fe7bb601f6 · Founder View e834b2f2-3b2b-47a0-9950-04f9f9d0beec
Catalog src/lib/inventory.ts (copied into the ZIP as sources/inventory.ts)

Contents

  1. Directory of every section
  2. Why each section’s reading matters
  3. Instructions for GrokBot

1. Directory of every section

The previous briefing wrote a diagnosis of why the site was out of control. That was the wrong object.

This part is a directory:

Agent View first (Identity → Attention → Storage → Confidence → KPIs → Evidence file → Directory → Activity). Then Founder View (Overview → Doll gates → Overnight → Evidence → Contract → Decisions → Slot Work).

The live site’s 1 · Directory tab is this catalog as a scannable list. sources/inventory.ts is the same catalog as data. Do not invent unread Identity point titles (1, 2, 4, 5, 7, 9, 10). Do not invent waiting-list names. Do not invent the 15:55 hour-log body.

How to read a row

Column Meaning
ID Stable handle for the template (ID-01 … SW-04)
Page FYJ Founder Bot page
Name Section as pointed at
On screen What was visible or spoken. Not a purpose.
Asked The question to fill later
Still Reconstruction of that page/section

Pages

# Surface Page Sections
1 Agent View Identity ID-01 … ID-20
2 Agent View Attention AT-01 … AT-05
3 Agent View Storage ST-01 … ST-07
4 Agent View Confidence CF-01 … CF-05
5 Agent View KPIs KP-01 … KP-08
6 Agent View Evidence file EF-01 … EF-05
7 Agent View Directory DR-01 … DR-07
8 Agent View Activity AC-01 … AC-03
9 Founder View Overview OV-01 … OV-09
10 Founder View Doll gates DG-01 … DG-05
11 Founder View Overnight ON-01 … ON-04
12 Founder View Evidence EV-01 … EV-09
13 Founder View Contract CT-01 … CT-04
14 Founder View Decisions DC-01 … DC-04
15 Founder View Slot Work SW-01 … SW-04

Open-card titles that were on screen are listed on EV-09, CT-04, and SW-03 — as lists, not as fifty extra IDs. Grouping is allowed. Grouping is not a filled purpose.

Every ID, on-screen line, asked question, still, and card list lives in sources/inventory.ts and on 1 · Directory. That is the inventory. This markdown does not re-explain why anything went wrong.

Stills are reconstructions matching the 16:23–16:37 frames (./stills/d5-*.png). The MP4 binary was not required once the frames were walked.


2. Why each section’s reading matters

For each of the 99 IDs, the answer we are looking for is one template. The thinking that starts the fill is why Janhavi needs the right interpretation of this block, against the vision of a $2.5–5bn company run through a sole founder agent she can still direct.

The template (the answer for this)

SECTION <ID>
Surface: Agent View | Founder View
Page: <page>
Name: <name as on screen>
On screen: <copy from the directory — do not invent>
Screenshot: <still path>
For the founder: (one sentence)
For the agent: (one sentence)
How used: (one sentence)
How it relates to this page: (one sentence)
How it relates to scheduling (24-hour loop / 17:15): (one sentence)

That block is the answer we want for every ID. Do not fill it in this file. Fill it on the explainer.

The thinking to do for each section

On the live site, 2 · Importance already has, per ID:

  1. Template — the answer we are looking for (the block above).
  2. Why Janhavi needs to know this — why a wrong reading of this section costs her the ability to direct.
  3. Why the right reading serves the vision — why this section’s interpretation matters for a $2.5–5bn company, a sole founder agent, empty P, 0 compiled, blocker reach, live team of one.

Those two paragraphs are not the purpose. They are the reason the purpose has to be gotten right. Use them as the start of the thinking, then fill the template. Do that for each and every section. Do not skip gestured Identity points — ID-20 names the gap instead of inventing titles.

Vision, held once so it does not have to be restated as a diagnosis:


3. Instructions for GrokBot

The task

This is a one-off task. It is not ordinary FYJ Founder Bot work. It is not a compile. It is not a market-path hour. It is not a close.

From this ZIP, build a separate explainer website that fills the template for every section in the directory, so Janhavi can critique meaning and purpose later.

You will be given:

You will return:

The template

Fill this block once per ID. Copy onScreen from the directory. Do not invent unread copy.

SECTION <ID>
Surface:
Page:
Name:
On screen:
Screenshot:
For the founder:
For the agent:
How used:
How it relates to this page:
How it relates to scheduling:

The live site’s 2 · Importance card for that ID is the start of the thinking (why she needs the right reading; why it serves the vision). The filled sentences are yours. Label them as the explainer’s answers, not as her original words. She will debate them.

How to fill

  1. Walk the directory in order. Agent View pages first, Founder View pages second. Do not skip a page.
  2. Open the still. Open the onScreen line. Open asked.
  3. Write five sentences: founder, agent, how used, relation to page, relation to scheduling.
  4. If note says not walked, say so in the fill. Do not invent the body, the source list, waiting-list names, unread Identity titles, or the 15:55 hour-log row.
  5. If cards is present (EV-09, CT-04, SW-03), fill the family ID as the purpose of that list, then one short line per card on what question it raises — not a new recon of each Act.
  6. Group Evidence Open cards that do the same job (stayed-thin companies-in-the-space; stayed-thin market-scenarios; stronger-as-constraint; empty-is-honest). Grouping is not a compile. Grouping is not archive.
  7. Keep Founder View answers in founder English. Keep Agent View answers pointed at files, counts, and rules.
  8. Do not turn a filled template into a path, a buyer, a compile, or a P move.

The explainer site

Organise it so she can critique:

She will use that site to debate meaning and purpose, section by section.

What to return

  1. Every ID from ID-01 to SW-04 has a template block, or an explicit “not walked — not invented.”
  2. The explainer is organised by page, then section, with stills.
  3. A ZIP of the explainer site and sources.
  4. Stop. Do not continue into a compile, a market path, a hire, or another recon page.

What this task is not

It is not ordinary slot work. Do not paste the standing do-not list into the explainer. Do not restage 17:15. Do not treat filling a purpose as moving P, unparking 63e813ea, assembling, or naming a buyer. Those are other hours. This hour is the directory, filled.


Provenance

Raw file
# A directory of every section, in order, so the template can be filled

**Directory / template · Agent View then Founder View**  
Implementation UUID: `7c3a9e14-6f2b-4d80-9c1e-b8a4d2f0e571`  
This file is the source of truth for GrokBot. The live site typesets the same catalog as a directory (part 1), a per-section template (part 2), and these instructions (part 3).

It is an **inventory and a template**, not a diagnosis, not a path, not P, not a compile. Purposes are blank. Fill them later, on a separate explainer, so they can be critiqued.

---

## Document control

| Field | Value |
|---|---|
| Implementation UUID | `7c3a9e14-6f2b-4d80-9c1e-b8a4d2f0e571` |
| Short name | DIR-TPL |
| Job | Directory of every walked section, in order. Template per section. Instructions for GrokBot to fill the template and build an explainer. |
| Capture | Critique of the previous briefing, 30 Aug 2026 **17:13–17:15** BST, then the original walk **16:23–16:37** BST re-attached. Audio on. Agent View then Founder View. |
| Host | `https://vps-9d119ef4.vps.ovh.net` |
| Independent check | Unauthenticated GET → **401** nginx Basic realm `FYJ` |
| Pages | **15** (8 Agent View, 7 Founder View) |
| Sections | **99** (IDs ID-01…SW-04) |
| Open cards on Overview | Evidence **86** · Contract **18** · Slot Work **13** · Overnight **0** · Decisions **0**. 86+18+13 = **117** |
| Dated pages | **90** |
| Compiled | **0** |
| P | Empty |
| S | **0** on Confidence / KPIs |
| Binding on the walked site | ITERATE until 17:15 London. This UUID does not restage that close. |
| Related (missed the point) | `d42ef660-60a1-4981-8cab-5a1280d50fd6` — previous briefing explained too much. This one is the directory. |
| Related | REACH-STORY `58cd58c1-aee9-45a7-8462-c3a687e09047` · Agent View `e93e1003-5847-4b58-b856-b8fe7bb601f6` · Founder View `e834b2f2-3b2b-47a0-9950-04f9f9d0beec` |
| Catalog | `src/lib/inventory.ts` (copied into the ZIP as `sources/inventory.ts`) |

---

## Contents

1. [Directory of every section](#1-directory-of-every-section)
2. [Why each section’s reading matters](#2-why-each-sections-reading-matters)
3. [Instructions for GrokBot](#3-instructions-for-grokbot)

---

## 1. Directory of every section

The previous briefing wrote a diagnosis of why the site was out of control. That was the wrong object.

This part is a **directory**:

- every page, in the order it was walked
- every section pointed at on that page
- what was on screen
- the question asked
- the screenshot
- purposes **not** filled

Agent View first (Identity → Attention → Storage → Confidence → KPIs → Evidence file → Directory → Activity). Then Founder View (Overview → Doll gates → Overnight → Evidence → Contract → Decisions → Slot Work).

The live site’s **1 · Directory** tab is this catalog as a scannable list. `sources/inventory.ts` is the same catalog as data. Do not invent unread Identity point titles (1, 2, 4, 5, 7, 9, 10). Do not invent waiting-list names. Do not invent the 15:55 hour-log body.

### How to read a row

| Column | Meaning |
|---|---|
| ID | Stable handle for the template (ID-01 … SW-04) |
| Page | FYJ Founder Bot page |
| Name | Section as pointed at |
| On screen | What was visible or spoken. Not a purpose. |
| Asked | The question to fill later |
| Still | Reconstruction of that page/section |

### Pages

| # | Surface | Page | Sections |
|---|---|---|---|
| 1 | Agent View | Identity | ID-01 … ID-20 |
| 2 | Agent View | Attention | AT-01 … AT-05 |
| 3 | Agent View | Storage | ST-01 … ST-07 |
| 4 | Agent View | Confidence | CF-01 … CF-05 |
| 5 | Agent View | KPIs | KP-01 … KP-08 |
| 6 | Agent View | Evidence file | EF-01 … EF-05 |
| 7 | Agent View | Directory | DR-01 … DR-07 |
| 8 | Agent View | Activity | AC-01 … AC-03 |
| 9 | Founder View | Overview | OV-01 … OV-09 |
| 10 | Founder View | Doll gates | DG-01 … DG-05 |
| 11 | Founder View | Overnight | ON-01 … ON-04 |
| 12 | Founder View | Evidence | EV-01 … EV-09 |
| 13 | Founder View | Contract | CT-01 … CT-04 |
| 14 | Founder View | Decisions | DC-01 … DC-04 |
| 15 | Founder View | Slot Work | SW-01 … SW-04 |

Open-card titles that were on screen are listed on EV-09, CT-04, and SW-03 — as lists, not as fifty extra IDs. Grouping is allowed. Grouping is not a filled purpose.

Every ID, on-screen line, asked question, still, and card list lives in `sources/inventory.ts` and on **1 · Directory**. That is the inventory. This markdown does not re-explain why anything went wrong.

Stills are reconstructions matching the 16:23–16:37 frames (`./stills/d5-*.png`). The MP4 binary was not required once the frames were walked.

---

## 2. Why each section’s reading matters

For **each** of the 99 IDs, the answer we are looking for is one template. The thinking that starts the fill is why Janhavi needs the right interpretation of **this** block, against the vision of a $2.5–5bn company run through a sole founder agent she can still direct.

### The template (the answer for this)

```text
SECTION <ID>
Surface: Agent View | Founder View
Page: <page>
Name: <name as on screen>
On screen: <copy from the directory — do not invent>
Screenshot: <still path>
For the founder: (one sentence)
For the agent: (one sentence)
How used: (one sentence)
How it relates to this page: (one sentence)
How it relates to scheduling (24-hour loop / 17:15): (one sentence)
```

That block is the answer we want for every ID. Do not fill it in this file. Fill it on the explainer.

### The thinking to do for each section

On the live site, **2 · Importance** already has, per ID:

1. **Template — the answer we are looking for** (the block above).
2. **Why Janhavi needs to know this** — why a wrong reading of *this* section costs her the ability to direct.
3. **Why the right reading serves the vision** — why *this* section’s interpretation matters for a $2.5–5bn company, a sole founder agent, empty P, 0 compiled, blocker reach, live team of one.

Those two paragraphs are not the purpose. They are the reason the purpose has to be gotten right. Use them as the start of the thinking, then fill the template. Do that for each and every section. Do not skip gestured Identity points — ID-20 names the gap instead of inventing titles.

Vision, held once so it does not have to be restated as a diagnosis:

- Destination is the **company** ($2.5–5bn), not the parked first-customer cut.
- Directing is still the founder layer in her hands. A section she cannot interpret is a section she cannot direct.
- Agent View holds files and counts. Founder View holds the story. Mixing them is how she stops being able to read her own company.
- Empty P is honest, not a form waiting for a buyer name.
- 0 compiled and blocker reach stay named. Filling a template is not a compile.

---

## 3. Instructions for GrokBot

### The task

This is a **one-off task**. It is not ordinary FYJ Founder Bot work. It is not a compile. It is not a market-path hour. It is not a close.

**From this ZIP, build a separate explainer website** that fills the template for every section in the directory, so Janhavi can critique meaning and purpose later.

You will be given:

- this markdown
- `sources/inventory.ts` (99 sections, 15 pages, stills, card lists, whyKnow, vision)
- reconstructed stills `sources/stills/d5-*.png`
- the directory site this ZIP came from

You will return:

- one explainer site, organised by page then section
- every ID filled
- stills next to the section they prove
- a ZIP of that explainer

### The template

Fill this block once per ID. Copy `onScreen` from the directory. Do not invent unread copy.

```text
SECTION <ID>
Surface:
Page:
Name:
On screen:
Screenshot:
For the founder:
For the agent:
How used:
How it relates to this page:
How it relates to scheduling:
```

The live site’s **2 · Importance** card for that ID is the start of the thinking (why she needs the right reading; why it serves the vision). The filled sentences are yours. Label them as the explainer’s answers, not as her original words. She will debate them.

### How to fill

1. Walk the directory in order. Agent View pages first, Founder View pages second. Do not skip a page.
2. Open the still. Open the `onScreen` line. Open `asked`.
3. Write five sentences: founder, agent, how used, relation to page, relation to scheduling.
4. If `note` says **not walked**, say so in the fill. Do not invent the body, the source list, waiting-list names, unread Identity titles, or the 15:55 hour-log row.
5. If `cards` is present (EV-09, CT-04, SW-03), fill the **family** ID as the purpose of that list, then one short line per card on what question it raises — not a new recon of each Act.
6. Group Evidence Open cards that do the same job (stayed-thin companies-in-the-space; stayed-thin market-scenarios; stronger-as-constraint; empty-is-honest). Grouping is not a compile. Grouping is not archive.
7. Keep Founder View answers in founder English. Keep Agent View answers pointed at files, counts, and rules.
8. Do not turn a filled template into a path, a buyer, a compile, or a P move.

### The explainer site

Organise it so she can critique:

- One page (or one tab) per FYJ page in the directory.
- Inside it, one block per ID, with the still, the on-screen line, and the five filled sentences.
- Sub-navigation by page, then by ID.
- A mark on every ID: **filled** or **not walked — not invented**.
- No diagnosis essay. No standing-rules lecture. The explainer is the answers.

She will use that site to debate meaning and purpose, section by section.

### What to return

1. Every ID from ID-01 to SW-04 has a template block, or an explicit “not walked — not invented.”
2. The explainer is organised by page, then section, with stills.
3. A ZIP of the explainer site and sources.
4. Stop. Do not continue into a compile, a market path, a hire, or another recon page.

### What this task is not

It is not ordinary slot work. Do not paste the standing do-not list into the explainer. Do not restage 17:15. Do not treat filling a purpose as moving P, unparking `63e813ea`, assembling, or naming a buyer. Those are other hours. This hour is the directory, filled.

---

## Provenance

- Critique walk: iPhone, 30 Aug 2026 17:13–17:15 BST, of the previous briefing `d42ef660`. Founder: the last website missed the point; background should be a directory of sections; importance should be the template plus why the reading matters for Janhavi; instructions should be the one-off task to fill that template on an explainer she can critique.
- Original inventory walk, re-attached: Agent View then Founder View, 16:23–16:37 BST, host `vps-9d119ef4.vps.ovh.net`. Audio on.
- Independent check of the host: GET → 401 Basic realm `FYJ`.
- Stills are reconstructions from the frames. Chrome and copy follow what was on screen.
- Catalog: 15 pages, 99 sections, UUID `7c3a9e14-6f2b-4d80-9c1e-b8a4d2f0e571`.

Storage file view of FYJ Founder Bot. Not the Identity letter.