Skip to content

Where things live

The demo project, Cauldron Roasters, shows the layout. In it, a consultancy writes a competitor brief for a coffee roaster.

On its own. The renamed workspace is the whole project:

Cauldron-Roasters/
├── 1-Inputs/
│ ├── Sources/ market-note.pdf, kickoff-notes.docx
│ ├── Admin/ Cauldron-SOW.pdf, contract.pdf
│ ├── Templates/ branded-deck.potx, report.dotx
│ └── Examples/ last-year-brief.pptx
├── 2-Drafts/ competitor-brief/, versioned
├── 3-Knowledge/ a page per ingested source
├── 4-Trackers/ tasks.md, timeline.md
├── 5-System/ config, status, decisions
├── _update/ new release zips, when updating
└── .familiar/ … the agent's own files

Inside an existing project folder. The workspace sits one level down, beside files the agent never sees. Open the agent in Cauldron-Roasters-familiar/, not in Cauldron-Roasters/:

Cauldron-Roasters/
├── Finance/ invoices, budget.xlsx
├── Deliverables/ final decks you copied out
└── Cauldron-Roasters-familiar/ the workspace, laid out as above

Name the workspace after the project, with -familiar at the end. Many editors and agents show the folder name when a session starts. With several projects open, you can then tell them apart before the first reply.

Folder What is in it Who writes it
1-Inputs/ Sources/, Admin/, Templates/, Examples/. Add or rename subfolders as you like. Keep the name Templates/. You. The agent only reads it.
2-Drafts/ Generated documents and decks, in versions. _draft-index.md lists the current ones. The agent. You copy finished work out.
3-Knowledge/ One page per ingested source, an index, a source register, and saved full-text extractions. The agent.
4-Trackers/ tasks.md (open items and what blocks them) and timeline.md (milestones and dates). The agent, when you ask. You can edit them too.
5-System/ Configuration and context, Memory/ (status snapshot and activity log), Handoffs/, Decisions/, user-preferences.md. The agent.
.familiar/ The rules, route table and helper scripts. Do not edit them. The release.

Every fact has one home. Files that change often carry a revision marker. Before a later session writes to one, it compares the marker, so it does not overwrite newer work.