---
type: "synthesis"
spans_days: [1, 2, 3, 4, 5, 6]
tags: ["architecture", "mental-model", "orchestration"]
id: "arc-claude-orchestrator-three-layer"
sources: ["cross-day"]
---
## What this arc tracks

Every speaker in the series implicitly or explicitly invokes the same three-layer architecture. Tim makes it explicit; the others assume it. Holding the shared model lets a downstream agent map any specific stack onto the same skeleton.

## The shared three-layer model

**Layer 1 — Substrate** (where state lives)
- Day 1: Claude Projects ([[concept-claude-projects]]) holding brand assets.
- Day 2: Notion databases ([[entity-notion]]) — Creator List, Content Ideas, Knowledge Base.
- Day 3: Local filesystem (project directory + [[concept-brand-asset-system]]).
- Day 4: Local Downloads folder + the mutable Skill itself.
- Day 5: Local desktop folder opened in [[tool-vs-code]] ("AI Marketing Skills").
- Day 6: Claude Desktop file system + browser tabs.

**Layer 2 — Orchestrator** (the brain)
- Always Claude, in some surface: web, desktop ([[entity-claude-co-work]], [[entity-claude-d6]]), CLI ([[entity-product-claude-code]], [[tool-claude-code]]), or Skill-equipped (every day).
- The orchestrator holds named instruction sets (Skills, see [[arc-skills-semantic-drift]]) and routes calls to executors.

**Layer 3 — Executors** (the hands)
- Generation executors: Higgsfield (Day 1), Whisper-via-Groq (Day 2), Whisper-local + Remotion (Day 3), Nano Banana 2 via Blotato (Day 4), Arvow (Day 5), Gamma (Day 6).
- Action executors: Blotato scheduler (Days 3, 4, 5), Arvow CMS publisher (Day 5), Notion writes (Day 2).
- Sensor executors: Chrome MCP (Days 2, 3, 6), local file reads (Days 3, 4, 5).

## Sabrina Ramanov's compact metaphor (Day 3)

> *"Claude Code is a kernel; Agent Skills give it knowledge; MCP gives it hands; Remotion is its rendering target; Whisper + FFmpeg are its scalpels; Blotato is its mailroom."*

This is the cleanest statement of the unified model in the entire series. Every other day's architecture maps cleanly onto this skeleton — substitute different executors for different content domains.

## What this lets you say

- *"All six videos teach the same architecture with different executors."*
- *"When choosing a stack, identify which layer you're shopping for. Don't compare Blotato (executor) to Claude Co-Work (orchestrator)."*
- *"The orchestrator is the durable layer. Executors will be replaced every 12-18 months."*

## The implication for vendor choice

Layer 1 is plumbing (interchangeable). Layer 3 is best-of-breed shopping (high churn). **Layer 2 is the strategic choice.** This is why every speaker in the series treats Claude as the constant. See [[quote-stop-bouncing-tools]] — Sabrina's "pick one tool, go deep" — for the explicit version of this argument.