New · Intake Model · v1.3
Drop everything in Inbox/. Claude routes it.
The convention now has a default intake path. Drop files into Inbox/ and /inbox-process(in progress) routes them to the right canonical destination overnight. Direct drops to known destinations are still allowed as a fast path.
Default path
Drop in Inbox/ → Claude routes nightly
Fast path
Direct drop if you know the destination
Forbidden
Files dropped at project root
Status: /inbox-process not yet built — manual routing until it ships. New Reference/ and Deliverables/ chapters document the model in detail.
Every active client project folder follows the same v2 file set: six persistent root files (plus per-cycle copy-meta.md, copy-google.md, preview.html when a cycle is active), five bins. This guide explains what each file is for, who owns it, what goes in it, and shows real reference implementations (Marcon Elmwood; Rennie Pier West as of 2026-05-24). Use it when onboarding new team members, or when you're staring at one of these files and asking "what am I supposed to put here?"
File set at a glance
| File | Owner | Bloats | Purpose |
|---|---|---|---|
CLAUDE.md | AM | No | Project identity + Standing Rules & Preferences |
campaign.md | AM + Media | Yes (Status Log appends) | Playbook + cycle history + operational status log |
production.md | PM | Per cycle | Creative brief — PM to Design / Creative team |
digital.md | Media Specialist | Per cycle | Build spec — account IDs, ad matrix, targeting, bid strategy, QA |
health.md | Ad Ops (agent) | No (overwritten) | Active flags, alerts, drift detection |
performance.md | Media (agent) | No (overwritten) | Latest benchmarks, trends, historical context |
Two of these are agent-maintained (health.md, performance.md). Four are human-curated. All six are stamped with convention_version: 2026-05-12 in their frontmatter so we can spot stale files at audit time.
The five-bin layout
Around the root files, every project folder has the same five bins:
Inbox/— undigested briefs, raw uploads, handover materialReference/— durable analyses, brand voice, contracts, prior-agency materialsDeliverables/— generated copy sheets, reports, exports, ad-preview boardsLogs/— daily auto-monitor output (Jonathan's stack)_junk/— never delete, archive by dated subfolder
The root holds only canonical context files. If a file isn't one of the six persistent files (or the three per-cycle files), it belongs in a bin.
Chapters
01CLAUDE.md
Project identity plus locked rules and preferences. The first file any agent or team member reads when they land in a project folder. Curated by the Account Man
campaign.md
The strategic playbook plus an append-only operational status log. Where the AM and Media team co-own the project's running story.
production.md
Creative brief only. PM-to-Design handoff for the current cycle. No build specs, no status updates, no technical references. All of that moved out in v2.
digital.md
The Media Specialist's bible for the current cycle. Account IDs, pixel, ad matrix, targeting spec, bid strategy, budget pacing, UTM convention, QA checklist, bu
health.md
Agent-maintained campaign health monitor. Active flags, alerts, drift detection. What's broken right now. Owned by `campaign-director` / `campaign-monitor` agen
performance.md
Agent-maintained performance ledger. Latest benchmarks, historical context, trends. The numbers behind whatever `health.md` is flagging. BQ-driven where possibl
Reference/
New chapter. The inputs library. Six subfolders (brand, creative-specs, creative-sources, ooh-proposals, leads, History) plus root singletons. Pier West is the canonical reference implementation.
Deliverables/
New chapter. The outputs library. Four zones: current cycle bundles, Reports/, _archive/ (NOT _junk/), and root singletons. Skill-write exemption + _archive vs _junk distinction documented.
How they work together
A worked example. Misael needs to build a new Elmwood ad set. Here's the path he takes through the file set.
What this replaces
The v1 to v2 delta. What changed, why it changed, what's gone.
What's new
See the changelog for what's changed in each version.