Project Folder Convention v2

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.

A typical scenario

Misael needs to build a new Elmwood ad set. Here's the path he takes through the file set.

  1. Opens CLAUDE.md first to confirm naming prefix (ELM_630_), HSAC rules, approval chain.
  2. Reads campaign.md Active Cycle paragraph to know what cycle we're in and what's already live.
  3. Goes to digital.md Ad Matrix to see the ad spec, then Bid Strategy & Budget Pacing for the build settings.
  4. Cross-references production.md only if a creative question comes up (capitalization, GST phrasing).
  5. Builds in Ads Manager / Markifact.
  6. Adds a Status Log entry to campaign.md when done.
  7. After 24 hours, campaign-monitor agent updates health.md and performance.md with the new spend data.

Why this flow works

That flow is why v2 split production.md and digital.md. In v1, the build spec was buried inside production.md alongside creative direction, status updates, and technical refs. Media had to skim past creative direction to find pixel IDs. v2 makes the build spec its own file so it can be deep and uncluttered.

The same pattern holds for AM scenarios. If Hilda (AM) needs to draft a client check-in:

  1. Opens campaign.md Status Log — last few dated entries are her briefing material.
  2. Reads health.md Active Flags — what's broken right now that the client should hear about (or that she needs to head off before they ask).
  3. Reads performance.md Last 30 Days — the numbers she'll quote.
  4. Checks CLAUDE.md Standing Rules if she's about to suggest something — make sure she's not violating a locked rule.

Or a PM scenario. Helena (PM) is briefing a new creative cycle:

  1. Opens CLAUDE.md Standing Rules to remember the durable creative direction (brand voice, HSAC, language scope).
  2. Opens the prior cycle's production.md (current root file, will snapshot on rollover) as a reference template.
  3. Writes the new production.md for the upcoming cycle. Snapshots the old one to Reference/History/Productions/{old-cycle-slug}/.
  4. Doesn't touch digital.md — that's Media's job once the brief is signed.

Each role has a primary file they live in. Each role appends to campaign.md Status Log when they take a meaningful action. Everything stays discoverable.