# Banner Studio — Claude Code Briefing Bundle

This bundle contains everything needed to begin building the agentic HTML5 banner production platform with Claude Code, plus an executive summary for non-engineering audiences.

## What's in here

**For Claude Code (drop these in the project root):**

- `CLAUDE.md` — Read on every session. Locked decisions, conventions, what not to do. The operational source of truth.
- `PROJECT_STRUCTURE.md` — Monorepo layout, package by package, file by file. Use as the scaffolding target.
- `PHASE_1_BRIEF.md` — Step-by-step prompts for the first week of work. Foundation phase, no UI yet.
- `BUILD_SEQUENCE.md` — All 14 phases with exit criteria. Expand each phase into Claude Code prompts as you reach it.
- `ARCHITECTURE.md` — The full architecture spec (the document you authored). Source of truth for data shapes, algorithms, and rationale.
- `RESEARCH.md` — Research backing the locked decisions. Reference for the "why" behind stack and pattern choices.

**For leadership and stakeholder decks:**

- `EXECUTIVE_SUMMARY.md` — Plain-prose briefing. The PPT source document. Sections map naturally to slides.

## How to start

1. Create the project repo. Copy `CLAUDE.md`, `PROJECT_STRUCTURE.md`, `PHASE_1_BRIEF.md`, `BUILD_SEQUENCE.md`, `ARCHITECTURE.md`, and `RESEARCH.md` into the root.
2. Open Claude Code in that directory.
3. First prompt:

   > Read `CLAUDE.md`, then `PHASE_1_BRIEF.md`. We are at Step 1.1. Begin.

4. Work through Phase 1 step by step. Do not skip the unit tests on the layout engine. Do not skip Step 1.9 (the type-safety proof) — it confirms the contract chain works before you build anything substantial on top of it.

5. At Phase 1 exit, tag `v0.1.0-foundation` and start Phase 2.

## A note on the documents

`CLAUDE.md` is intentionally opinionated. It states what is locked, what is forbidden, and where to look for the why. This is the right shape for a Claude Code briefing — it tells the model what decisions have already been made so it doesn't waste context re-deriving them, and it tells it where to look when a deeper question comes up.

`PHASE_1_BRIEF.md` is the only phase with literal prompts pre-written. As you complete Phase 1 and start Phase 2, expand that phase's summary in `BUILD_SEQUENCE.md` into a similar step-by-step brief. The first phase needed prompts because zero-state is the hardest moment; later phases can lean on the patterns established in Phase 1.

`EXECUTIVE_SUMMARY.md` is written to be read by people who will never touch the code. It's the document that gets adapted into a 10-slide deck or a one-pager for a stakeholder conversation. Sections are sized to map to slides without further editing.