A shop OS you own

Fit gate

• If you are agency, advisory, or B2B, you want your own OS, and you have work (calls, jobs) that should compound, stay.
• If you are a local shop that only needs the calendar full, stop. Open Ugly ads that book the town, or Recover the job they turn down.
• If you will not write the first room down, stop. A chat will not be the platform next month.

The lock · you can do this today

You can stand the platform up as a folder tree and run room one by hand. No Codex. No API. No agent. You still get the result. APIs, scheduled jobs, and agents are later rungs. Paid installer is last.

• Name the platform. Create the folder tree on the desktop. Exact names below.
• Open room one. Export or copy the transcript from Fathom (or any notetaker). No API required to start. Fathom is intake. The folder is the platform.
• 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. Write the 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. Same names. Then an installer.

You = login / 2FA / pay when a tool needs it. The rest is the platform.

Tools in order

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

Fathom is a room's intake, not the platform. The folder is the platform. A model, Codex, or Grok Bot can walk the same folder later. A chat is not a tool on this list. A chat can run a skill. It does not hold the system of record. No Cal.com. No GHL sales calendar. Sales books stay on iClosed if they book sits. No funding.

Folder tree · the platform

Name the platform. The File uses shop-os/ so the names stay exact. Create this on the desktop today. Do not rename the rooms until a month has run.

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

This is the platform. Room one lives at rooms/calls/. Raw is immutable. You drop the transcript in. You never edit it. Enriched is one structured page per item. Knowledge is the living list. Every line has a source. Reports are the daily pulse and the monthly backlog. Prompts hold the one-shot VSL, deck, email, and content prompts. MEMORY.md gets a line only when a pattern repeats. AGENTS.md gets a line only when a rule actually changes.

Next rooms · map only

Do not build these today. They plug into the same tree later. Same rules: raw vs structured, source every claim, assets must move.

If the work is repo and ops folders for an agency, that is a sibling File: The agency in a folder. This File is the shop OS. That File is the agency OS.

Room one intake · no API

1. Open Fathom in the browser (or your notetaker). You: login / 2FA if it asks. Fathom is intake. It is not the platform.
2. Open the call you just ran.
3. Copy the transcript, or download the text export.
4. Save it as rooms/calls/raw/YYYY-MM-DD-company-person.md. Example: 2026-08-12-acme-jordan.md.
5. Do not edit that file after you save it. If you need a clean version, that is the structured page, not raw.

Any notetaker works the same way. Export or copy. Drop it in raw. The platform does not care which app recorded it. Human: the filename is the date plus the name, so you do not drop the same export twice. Bot later: track IDs in processed.json.

Room one · structured page

Every item gets a page the platform can reuse. Copy into rooms/calls/enriched/YYYY-MM-DD-company-person.md. Fill the brackets. Copy-paste exact phrases. Do not polish their English.

After you fill it, lift the exact quotes into the knowledge files they belong in: outcomes, criteria, winning language, stakeholders, risks, stages, next steps. One or two lines each. Do not rewrite the call into a novel.

Knowledge line format · objections

Append one line to knowledge/objections.md. Newest at the bottom. Never delete an old line. Never overwrite raw.

Theme is a short tag you reuse. That is how you see a repeat. Two lines with the same theme is a pattern. One line is a one-off. A one-off does not go in MEMORY.md.

Knowledge rooms · one line each, their words

MEMORY.md and AGENTS.md

• MEMORY.md: a line only when a pattern repeats (same theme on 2 or more calls). A one-off does not get promoted.
• AGENTS.md: operating rules. Only edit when a rule actually changes. Example first lines you can paste:

Daily pulse · 5 lines

Save as reports/daily/YYYY-MM-DD.md. Next morning is fine. If room one took no work, write "no item" and stop.

Monthly backlog · first of the month

Save as reports/monthly/YYYY-MM.md. Rank the knowledge list. Then pick #1 and ship one asset. The report is the backlog. It is not the result. The asset is the result. The platform is not a graveyard.

Asset update rule

Top objection becomes one of: a VSL prompt, a deck slide, a case study, a sales email, or a content piece. Pick one. Write it from the template. Save it in prompts/ or wherever the live asset lives, and log the path.

Every recurring pattern must ship an asset. A list that sits there is a graveyard. The platform is not done until an asset moved.

processed.json · do not duplicate raw

Human path: the filename is the date plus the name. Look in rooms/calls/raw/ before you save. If 2026-08-12-acme-jordan.md is already there, do not drop it again.

Bot path: keep a small index so a nightly pull does not write the same meeting twice.

{
  "raw_files": ["2026-08-12-acme-jordan.md"],
  "meeting_ids": []
}

Bot may add meeting IDs when the API is on. Human can ignore this file. Never use it as a reason to edit raw.

Keys, later · security in plain words

• If you later use keys, put them in a file named .env at the root of the platform folder (shop-os/).
• Add .env to .gitignore so it never goes to GitHub.
• Never paste keys into a chat. Never paste keys into a File on this site. Never put a key in MEMORY.md, AGENTS.md, or an enrich page.
• Only process calls you are allowed to send to a model. If the buyer did not agree, or your shop does not allow it, keep that transcript in raw and enrich it by hand. Do not send it out.

A .env is a small local file that holds secrets. Your computer reads it. A chat should never see it. You do not need this file to run the month by hand.

Later rung · API, .env, scheduled tasks

Do this after the platform and room one have run by hand. Same folder. Same names. The human path stays the source of truth. First rungs are stand up the platform and run room one. Later: Fathom API, a model API, a .env, nightly and monthly scheduled tasks, then an installer.

1. You: Fathom login / 2FA. Open User Settings, then API Access. Generate a key. Put it in .env as FATHOM_API_KEY. Do not paste the key into a chat.
2. Same for the model you want to use. MODEL_API_KEY in the same .env.
3. Fathom lists meetings at https://api.fathom.ai/external/v1/meetings with header X-Api-Key. Pull new calls. Write new files into rooms/calls/raw/ only if the meeting ID is not in processed.json. Never overwrite a raw file that is already there.
4. Schedule the nightly prompt (below) in Codex, Grok Bot, or Claude. Same for the first-of-month prompt.

Numbered run

1. Name the platform. You: create the folders on the desktop from the exact names. That is the shop OS. Bot later: scaffold. Do not live in a ChatGPT project as the system of record.
   You create the foldersBot later scaffolds
2. Open room one. You: open Fathom or any notetaker, export or copy, save in rooms/calls/raw/ as date-plus-name. Raw never gets edited. Fathom is intake. Later: API key in a .env.
   You download or copyBot later API key, .env
3. Write the structured page from the template on this page. You: fill it. Copy-paste exact phrases. Bot later: structured output into the same fields.
   You fill the templateBot later structured output
4. Fill the knowledge rooms. You: paste date | call | stage | exact quote | theme. Every line has a source. Bot later: merge. Never overwrite raw. Never delete old lines.
   You paste the lineBot later merge, never overwrite raw
5. Daily pulse, or next morning. You: five lines if room one took work. Bot later: nightly scheduled task. Same outline.
   You 5 linesBot later nightly scheduled task
6. Monthly backlog. You: rank, pick #1, write the email or slide or VSL from the template. Bot later: first-of-month job writes the prompt pack. The platform is not a graveyard. An asset must move.
   You pick #1 and write the assetBot later first-of-month job
7. File log. Room one items in, knowledge added, assets updated. MEMORY only on a repeat. AGENTS only when a rule changes. Later rooms plug into the same tree.
   You keep the log todayBot later writes the row

File log columns

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

Done rule

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. iClosed remains the sales book if they book sits.
• 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 you are allowed to.