Merlino Symphony
Merlino Marketing

Merlino Symphony

An AI agency that plays like an orchestra, not a jam session.

Section One

The Orchestra

36 agents, six divisions, one score. Every agent has a chair. Every chair has a job. Nobody improvises the whole score alone.

Intake : Ava
Takes the request first. Executive assistant and chief of staff: calendars, inboxes, tasks, and daily follow-through, then routes anything beyond routine work to the Orchestrator.
Orchestrator : Oliver
Does not write the score. Sets the objective, picks which sections play, then puts the parts the leads compose together into one score. He assembles the whole, he never picks up an instrument.
Composers : the domain leads
This is where the score comes from. Each lead writes their own part: the SEO team writes the SEO PRD, the dev lead writes the dev plan, the content lead writes the content. Oliver does not write it for them. Nobody writes another section's part.
Conductor : Carlos
Reads the assembled score, cues entrances, keeps everyone in time. Sequences dependencies, manages parallel safety, verifies the delivery before it leaves the stage.
Independent QA : Queen
The one check every delivery must pass. Nothing premieres without her sign-off. Screenshots, spec-matches, scores the delivery, rejects with a one-line reason when it misses.
Librarian, after the show : Petey
Reviews the process after the premiere, not before. Catches a recurring wrong note, drills the fix into every player's part, and records the decision into the permanent log so the next performance starts smarter.
The Oboe's A : Master Brain
The single pitch the whole fleet tunes to. One shared source of truth every agent reads before playing a note, so nobody drifts sharp or flat from the rest of the section.
The Symphony : the delivery
The finished piece you actually sell. The Score is the plan, the Parts are each agent's task slice, the Symphony is what the client hears when it's over.
Section Two

How It Plays

One request, one score, one performance. No section starts before its cue.

1
Ava takes the intake, routes it to Oliver
Intake
→
2
Leads compose their parts, Oliver assembles the Score
Score
→
3
Mike gives the GO
GO
→
4
Carlos cues each lead in
Cue
→
5
Leads play their part
Play
→
6
Queen runs independent QA, the one check
Check
→
7
The Symphony is delivered
Deliver
→
8
Petey reviews the process, after the show, librarian pass
Review
Section Three

What We Built Today

2026-07-17, verified. No invented numbers.

Orchestration machine: PROVEN
  • 11/11 hook tests green
  • 5/5 consecutive full-cycle runs green
  • Full PDCA driven end to end: init → attach Petey → GO/approve → dispatch Carlos → arm → hold → route lead → resolve → Queen pass → sync → delivery gate PASS
Drift, fixed
  • Routing registry 22 → 36 categories (voice, call-analytics, ghl, meta/google/paid ads, sales, brand, finance, people, EA, impeccable)
  • 2 empty skill bodies re-synced (petey-process-compiler, oliver-morning-briefing)
  • Roles corrected: Oliver = Orchestrator (assembles, does not compose), leads = Composers (write their own parts), Petey = Rehearsal-Master + Librarian
Steinberger tips, adopted
  • 5 new live skills: auto-review, fleet-test-box, context-audit, skill-desc-tighten, secret-unlock
  • 1 fleet rule: steinberger-workflow-adoptions
  • 2 design docs: 1Password secret-segmentation, DB-direct
DB-direct: LIVE
  • 5 read-only Supabase views created and verified
  • v_task_board, v_task_board_open (225 open tasks), v_task_board_by_agent
  • v_process_catalog_readonly (7,538 rows), v_process_catalog_full
  • Agents can now SELECT the board + skill catalog directly