One folder, three ways in: the phone, Cowork, and Claude Code. The folder lives on the Mac and syncs through iCloud. Each level of the folder carries its own CLAUDE.md, so any agent that walks in gets the right rules for where it's standing.
Systems — who talks to whom
Folders — the nested CLAUDE.md notes
CLAUDE.md files nest like Russian dolls. The outer one sets the RichOS rules, the middle one sets the bench rules, and the inner one holds the project detail. The further in you go, the more specific the note.Who reads which note
| Note | Scope | Claude Code (started in ! Printing) | Cowork session |
|---|---|---|---|
iCloud root CLAUDE.md | RichOS-wide rules · ~21 KB | Loaded automatically (parent folder) | Loaded at session start (connected folder) |
! Printing/CLAUDE.md | Printer, defaults, folder rules, project index | Loaded automatically | Read when the work touches the bench |
project-a/CLAUDE.md | One project: files, v1 print, risks, next steps | Loaded when working inside project-a/ | Read when the work touches the project |
abstract.html · handoff | The story and the geometry | Read when a note points to them | Read when a note points to them |
House rules
- Short notes, long binders. A
CLAUDE.mdpoints to the detail. It never copies it. - Edit only your own section. Cowork and Claude Code share these files. Add to the logs, and don't rewrite someone else's lines.
- Confidential stays in the project folder. The bench note gets a one-line project index and nothing more.
- New project = a folder, an
abstract.html,sources/, its ownCLAUDE.md, and one row in the bench table. - Phone access needs the Mac awake. If a phone session can't see your files, the Mac is asleep.
Updated 19 Sep 2026 · Source of truth: ! Printing/CLAUDE.md and each project's CLAUDE.md. This map shows the pattern; the notes hold the facts.