Verification, handoffs, and device switching all assume you can find your project’s files. CRAFT’s project layout is what makes that assumption true — a standardized six-folder structure that turns “the project” into something legible to humans and provable to AI.
Last week we showed how CRAFT’s QA framework catches AI hallucinations at the source. This week: those gates only work if the files they reference can actually be found. Verification needs a structure to verify against.
The Problem with “Just Make Folders”
Most AI projects accrete. You start with a single chat, save a few outputs to Downloads, drop a PDF somewhere, paste an instructions document into a Google Doc. After a month, the project exists across six locations — none of them named anything you’d find on purpose.
This is fine for solo, one-shot work. It breaks the moment you need any of three things: a second device, a second collaborator, or a second AI session. Each one has to relearn where everything lives.
For Cowork specifically, the cost compounds. The AI assistant in your session can read files — but only files it can find. Every session that starts with “let me explain how this project is organized” is a session paying a tax on disorganization. Multiply that by twenty sessions across two devices and a small team, and you have a coordination problem masquerading as a productivity tool.
The Six-Folder Standard
CRAFT specifies a fixed project layout. Every CRAFT project has the same six folders in the same place:
Cookbooks, recipe definitions, framework specs. The reusable infrastructure shared across CRAFT projects.
The project’s own files: handoffs, lessons learned, configuration. This is where the project’s state lives.
Reusable templates and style references. The blueprints used to scaffold new files in the project.
Session artifacts and intermediate working files — the scratch space that doesn’t belong in the project record.
Research docs, analyses, extraction reports. The inputs that informed what the project became.
Cross-project XFER packets — inbound/, outbound/, accepted/. How knowledge moves between projects without ad hoc copy-paste.
A seventh folder, branding/, is optional — added when a project produces branded assets. The structure is documented in the CRAFT-FOLDER-STRUCTURE-SPEC, which defines the design principles, ten compliance rules, and a recipe-by-recipe impact map.
This is small. Six folders, one optional. The point isn’t the number — the point is that the number is the same across every CRAFT project. If you’ve worked with one, you can navigate any of them.
The Counterintuitive Insight
Here’s the part that surprised us during testing: the folder structure benefits humans more than AI.
Cowork’s Glob and Grep tools find files regardless of how they’re nested. From an AI tool’s perspective, “the LL file in project/” and “the LL file in random/path/notes/” are equally findable. The structure isn’t necessary for the AI to function.
What the structure does is make the project legible to the human who shares it with AI sessions. A new collaborator opening a CRAFT project knows immediately where to look. The handoff is in project/. The recipes are in framework/. The research that informed the build is in research/. The cross-project import that arrived last Tuesday is in transfers/inbound/accepted/.
This matters because the human is the bottleneck. The AI can scan a thousand files in seconds; the human cannot. The structure exists so the human can describe the project quickly, locate references quickly, and verify claims quickly. The AI is downstream of the human’s clarity.
The AI doesn’t need a layout to function. You do. The folders exist to make the project navigable in your head, not the model’s context window.
How the Structure Powers Everything Else
Every capability covered in this series depends on the layout.
Session continuity (Week 2) works because the handoff file has a known, predictable location: project/{PROJECT_ID}_AI-CHAT-HISTORY-v*.txt. RCP-CWK-001 (Session Initialization) reads it without asking where to look.
File safety (Week 3) works because every CRAFT project keeps modifiable files inside project/ and reference files inside framework/. Git checkpoints can target the right set without exclusion gymnastics.
Device switching (Week 4) works because the cloud-synced folder mirrors the same six folders on every machine. A laptop session opens to the same paths as the desktop session. The handoff finds itself.
Quality assurance (Week 5) works because Gate 1 — File-Pointability — requires a stable file location to point at. “The LL says X” is provable when the LL file lives where the spec says it lives. It’s a flag when the file is named differently or stored in a personal folder.
Strip out the standard layout and every other recipe still runs — but each one has to ask where things live before it can do its job. That’s the tax CRAFT removes.
The Evidence
The structure was tested against sixteen Cowork capability checks — file reads, glob patterns, grep searches, recipe scans, monorepo references — and all sixteen passed.
Nine CRAFT projects have been consolidated under the standard, covering more than five hundred files. Cross-project work — the XFER packet system that lets one project hand off knowledge to another — operates entirely on the assumption that transfers/inbound/ and transfers/outbound/ exist in the same place on both sides.
Projects that predate the spec can be detected via a has_folder_structure boolean. Recipes adapt their behavior rather than refusing to run. The standard is enforced going forward; existing work isn’t punished for arriving early.
Why This Matters
A working AI environment isn’t a single tool. It’s a stack — memory, verification, handoffs, device portability, audit trails. Each piece depends on the others, and all of them depend on knowing where things live.
You can build any of those pieces ad hoc. You can also build the foundation under all of them once, and let every subsequent piece inherit the assumption. CRAFT’s project structure is that foundation. It’s the part you stop thinking about — which is exactly the point.
This is Week 6 of our 8-week capability spotlight. Each week we go deep on one part of CRAFT — how it works, what problems it solves, and how to use it. Two weeks left.
