# Skill · A platform for the shop

Install procedure the Grok Bot runs. Intake is already loaded. Drive the named tools. Stop only for login, 2FA, or pay. Write the File log. Do not hop on a call.

Human-first. They can stand the platform up as a folder tree and run room one by hand. APIs, scheduled jobs, and agents are later rungs. Paid installer is last.

Fathom is a room's intake, not the platform. The folder is the platform.

## Fit gate

Fit: agency, advisory, B2B. They want their own OS, not another chat. They have work (calls, jobs) that should compound.

Unfit: a local shop that only needs the calendar full (route to Ugly ads that book the town, or Recover the job they turn down). Someone who will not write the first room down (stop).

If unfit, stop. Do not scaffold a platform for a shop that will not write room one down.

## The lock

Even without Codex, an API, or an agent, if they just follow the blueprint they can do it and achieve the result.

- Name the platform. Create the folder tree on the desktop from the exact names in the SOP.
- Open room one. Export or copy the transcript from Fathom (or any notetaker). No API required to start.
- After every item: fill the structured page by hand. Copy-paste exact phrases.
- Add the line to the knowledge room with the source and the date. Every line has a source.
- Next morning: one new structured page if room one took work. Five-line daily pulse.
- First of the month: rank the list. Pick the #1 recurring pattern. Ship ONE asset (email, slide, or VSL). The platform is not a graveyard.
- Later: Fathom API + a model API + a .env + scheduled nightly and monthly tasks. Same files. Then an installer.

AI / cron is how it gets faster. Not how it becomes possible.

A chat is not the system of record. A folder is. You do not rent a brain. You stand one up.

## Tools

1. The platform folder (desktop first)
2. Room one intake: Fathom or any notetaker (export / copy today; API later)
3. Structured page (on the File)
4. Knowledge rooms
5. Daily pulse
6. Monthly backlog + one asset
7. File log
8. Later: .env, Fathom API, model API, scheduled tasks, then an installer

No Cal.com. No GHL sales calendar. Sales books stay on iClosed if they book sits. No funding. Do not invent a snapshot URL.

If the work is repo and ops folders for an agency, that is the sibling File: The agency in a folder. Do not rebuild that tree here.

## Run

### 1. Name the platform
- Human path: create the folder tree on the desktop from the exact names. No GitHub required. No API required.
- Bot path: scaffold the same names.
- Do not live in a ChatGPT project as the system of record.

Exact names:

```
shop-os/
  rooms/calls/raw/
  rooms/calls/enriched/
  knowledge/objections.md
  knowledge/outcomes.md
  knowledge/criteria.md
  knowledge/winning-language.md
  knowledge/stakeholders.md
  knowledge/risks.md
  knowledge/stages.md
  knowledge/next-steps.md
  reports/daily/
  reports/monthly/
  prompts/
  MEMORY.md
  AGENTS.md
```

Room one lives at rooms/calls/. Next rooms (ads, delivery, content) are a map only. Do not build them today.

### 2. Open room one
- Human path: open Fathom or any notetaker. Export or copy. Save as rooms/calls/raw/YYYY-MM-DD-company-person.md. Do not edit raw.
- Bot later: Fathom API key in a .env. User Settings > API Access. Never paste the key into a chat or a File.
- processed.json: human uses the filename (date+name) so they do not drop the same export twice. Bot tracks meeting IDs. Never duplicate raw.

### 3. Write the structured page
- Human writes the page from the template on the File. Exact phrases. Do not polish.
- Bot later: structured output into the same fields. Human keeps the file.

### 4. Fill the knowledge rooms
- Human pastes: date | call | stage | exact quote | theme. Every line has a source.
- Bot later: merge new lines. Never overwrite raw. Never delete an old line.
- Lift matching lines into outcomes, criteria, winning language, stakeholders, risks, stages, next-steps.

### 5. Daily pulse
- Human path: five lines next morning if room one took work. Items in, new knowledge, themes, next steps owed, asset moved Y/N.
- Bot later: nightly scheduled task. Same outline.

### 6. Monthly backlog + one asset
- Human path: first of the month. Rank by frequency, stage, buyer type, pipeline value. What appeared, disappeared, increased. Pick #1. Write one email, slide, or VSL from the template.
- Bot later: first-of-month job writes the prompt pack.
- Every recurring pattern must ship an asset. The platform is not a graveyard.

### 7. File log
Write room, item, knowledge added, assets updated. MEMORY.md only when a pattern repeats. AGENTS.md only when a rule actually changes. A one-off does not go in memory.

## Memory and rules

MEMORY.md: a line only when the same theme hits 2 or more items.

AGENTS.md start lines:
- Never overwrite files in rooms/calls/raw/.
- Never dump the platform into one chat as the system of record.
- Never promote a one-off into MEMORY.md.
- Every recurring pattern must ship an asset. The platform is not a graveyard.
- Later rooms plug into the same tree. Same rules.
- Only process work we are allowed to send to a model.

## Later rung

.env at the platform root. Add .env to .gitignore. Never paste keys into a chat or a File.

Fathom: User Settings > API Access. GET https://api.fathom.ai/external/v1/meetings with X-Api-Key. Skip IDs already in processed.json.

Only process work they are allowed to send to a model.

Nightly and monthly prompt text lives on the File. Paste into Codex / Grok Bot / Claude. Same SOP.

## File log

Columns: date · room · item · knowledge added · theme · asset updated (file or none) · memory Y/N · status

## Done

Stop when the shop has a platform folder, room one is live, and one recurring pattern became an asset. Not a smarter chat.

## Do not

- Do not dump the platform into one ChatGPT project as the system of record.
- Do not overwrite raw transcripts.
- Do not promote a one-off into memory.
- Do not skip the asset. The platform is not a graveyard.
- Do not treat Fathom, a model, Codex, or Grok Bot as the platform. They plug in.
- Do not put sales on a GHL calendar.
- Do not put this File on Cal.com.
- Do not talk funding.
- Do not paste keys into a chat or a File.
- Do not send a call to a model unless they are allowed to.