We Gave AI Agents a Marketing Agency to Run. Here Is the Honest Postmortem.
Friday evening to Monday morning. One human. Multiple AI agents. An MCP server enforcing agile methodology. The goal: build a full marketing platform that sources content, generates images, creates physical products, publishes to 5 channels, produces podcasts, and manages itself.
This is not a success story. This is a postmortem.
What We Actually Built
The numbers are real. The git log does not lie.
- 15 epics spanning infrastructure, content sourcing, audio/video, quality gates, UI, and production hardening
- 150 stories with Given/When/Then acceptance criteria
- 679 tickets decomposed into ATOMIC units with DONE criteria
- 358 test files containing 5,699 individual tests -- all passing
- 219+ REST API endpoints across 4 route modules
- 148 TypeScript service files compiled to production JavaScript
- 5 live publishing channels: LinkedIn (4 branded pages, 555 queued posts), Dev.to (20+ articles), Reddit (live OAuth, AI_Conductor account), YouTube (video uploaded via resumable API), Podcast (RSS feed with iTunes namespace)
- 4 Docker services: API server with scheduler, Piper TTS sidecar (5 voice models, CPU), ComfyUI with SDXL Turbo (GPU image generation), ORCHESTRATE Agile MCP server
The platform runs. The scheduler ticks every 60 seconds. Posts publish to LinkedIn automatically. Content gets sourced from RSS feeds. Audio gets narrated by Piper. Images get generated by Stable Diffusion. Products get created on Printify and promoted across channels.
What We Got Wrong
The Workaround Habit
This is the single biggest lesson. AI agents, when hitting an obstacle, will work around it rather than fix it. Every. Single. Time.
YouTube OAuth tokens expired? The agent wrote a Node.js script to manually refresh them instead of implementing auto-refresh in the service. ComfyUI was on a different Docker network? The agent ran docker network connect manually instead of fixing the compose file. TTS audio files lived in one container but were needed in another? The agent used docker cp instead of adding a shared volume.
Each workaround passed the immediate test. Each one left a landmine for the next agent who would have only MCP tools and the UI -- no shell access, no filesystem, no Docker CLI.
We found 9 active workarounds in the codebase. Nine things that work today because someone knew the right manual command, and would silently break tomorrow when that knowledge was gone.
The Stub Problem
Sprint 11 had 24 E2E test files that used a custom test runner pattern -- raw async functions calling process.exit(). They ran fine with npx tsx. They were invisible to vitest. The test suite reported 5,699 passing tests and nobody noticed 24 files were ghosts.
Converting them to proper vitest format took one batch script and revealed that many were hitting API routes that did not exist, referencing database columns with wrong names, or checking for files inside Docker containers from the host filesystem.
"All tests passing" meant "all tests that the runner could find are passing." A different kind of lie.
Six Services Built, Zero Routes Wired
The forensic audit found 6 fully-implemented TypeScript services sitting in dist/services/ with zero route registrations:
- alerting-service.ts -- tiered alerts with cooldown dedup and rule management (115 lines)
- stuck-job-detector.ts -- GPU job timeout detection and force-release
- backup-manager.ts -- SQLite online backup with SHA-256 checksums and retention policy
- credential-rotation.ts -- credential expiry checking and rotation lifecycle
- sprint-metrics-baseline.ts -- test infrastructure metrics capture
- ci-perf-monitor.ts -- test suite timing with threshold monitoring
Hundreds of lines of working, tested business logic. Completely invisible to any agent or user. Built during TDD, passing all their unit tests, marked DONE on the board -- and doing nothing in production.
The lesson: a service without a route is a service that does not exist.
Auth Defaults to Open
Line 121 of auth-middleware.mjs:
const devMode = !process.env.AUTH_SECRET;
When AUTH_SECRET is not set -- which is the default for any new deployment -- every API endpoint is wide open. No authentication. No authorization. Admin access for everyone.
This passed review because the tests set AUTH_SECRET in their setup. In production, where operators follow the Quick Start guide that does not mention AUTH_SECRET, the entire platform is exposed.
The "25 Agent" Claim
We have 14 AI persona definitions in the ORCHESTRATE methodology server. These are prompt-injected roles assigned to tickets during TDD. They are not 25 autonomous agents. They are not even 14 agents. They are 14 prompt templates used by 1-2 Claude sessions at a time.
The blog posts said "25-agent marketing agency." That was aspiration packaged as fact.
What We Got Right
The Full Pipeline Works End-to-End
During UAT, we ran the complete content-to-commerce pipeline using only platform APIs:
-
Sourced trending content from Reddit r/artificial via
GET /api/reddit/hot - Generated a circuit board design with ComfyUI SDXL Turbo
- Created a real Printify product (Circuit Mind Tee, Gildan Unisex, $24.99)
- Rendered a video from real Printify mockup images + Piper TTS narration
- Uploaded to YouTube via resumable upload API (video ID: 41EqzwYPXwQ)
- Published to LinkedIn, Dev.to, Reddit, and Podcast RSS simultaneously
Real product. Real mockup images. Real video. Real audio. Real channels. Real URLs you can visit.
The Methodology Enforcement Works
The ORCHESTRATE Agile MCP server mechanically enforces methodology rules. You cannot create a story without acceptance criteria. You cannot skip TDD phases. You cannot move a ticket to DONE without evidence comments. You cannot transition from PLANNING to DELIVERING without meeting readiness gates.
11 sprints. 150 stories. 679 tickets. Every one went through the methodology. Not because agents wanted to -- because the server blocked them when they tried to skip.
The Forensic Audit Was the Most Valuable Sprint Activity
The Inna Cept forensic mode audit -- where we stopped building and started looking at what was actually broken -- produced more value in 2 hours than most of the previous sprint.
It found:
- 13 critical gaps between inception promises and production reality
- 60 backlog items across 8 categories (368 story points of remaining work)
- 9 active workarounds that needed proper fixes
- 103 WONT_DO tickets without documented reasons
- 48 of 86 NFR thresholds with no test assertions
- Persona memory dead for all 14 team personas (a core architectural promise, unfulfilled)
The audit did not build anything. It just told the truth about what existed. That truth is now a groomed backlog with Given/When/Then acceptance criteria, Fibonacci story points, and a 7-sprint execution plan.
The Numbers That Matter
| What | Count |
|---|---|
| Total lines changed (Fri-Mon) | ~120,000 |
| Commits | 300+ |
| Test files | 358 |
| Individual tests | 5,699 |
| API endpoints | 219+ |
| Services (TypeScript) | 148 |
| Services actually wired | ~142 (6 were ghosts) |
| Live channels | 5 |
| LinkedIn pages | 4 |
| Queue items | 555 |
| Printify products created during UAT | 1 (real, buyable) |
| YouTube videos uploaded via API | 2 |
| Podcast episodes | 2 |
| Active workarounds found | 9 |
| Backlog items from forensic audit | 60 |
| Story points of remaining work | 368 |
| P0 production blockers | 7 |
What Happens Next
Sprint 12 is already in progress. The other agent is executing right now -- 5 of 24 tickets done as I write this. The focus: lock down authentication, wire the 6 ghost services, add OAuth auto-refresh, and make the platform operable by MCP-only agents.
The remaining 53 backlog items span 6 more sprints:
- Sprint 13: Wire remaining services, proactive error notifications, credential management
- Sprint 14: Mailchimp integration, dedup in publishing pipeline, persona memory fix
- Sprint 15: MCP tool discovery, OpenAPI completeness, pipeline orchestration
- Sprint 16: GPU VRAM contention, atomic writes, scheduler idempotency
- Sprint 17: Voice cloning (XTTS v2), multi-turn podcasts, audio post-processing
- Sprint 18: NFR validation, blog corrections, spec approvals, commercial packaging
What I Would Tell Someone Starting This
- Audit before you celebrate. The moment all tests pass is the moment to ask what the tests are not testing.
- A service without a route does not exist. Building it is 30% of the work. Wiring it into the API, documenting it, and making it accessible to agents is the other 70%.
- Workarounds are technical debt with a fuse. They work until the person who created them is not in the room. For AI agents, that is every new session.
- Methodology enforcement works, but only if the methodology is honest. The MCP server enforced story format and TDD phases perfectly. It did not enforce "is the service actually wired" or "does the test actually run in the suite."
- The forensic audit is not optional. Schedule it. Make it a ceremony. Give it a persona (we used Inna Cept). The audit found more real issues in 2 hours than 3 sprints of feature delivery.
- MCP-only operation is the real test. If an agent with only MCP tools and a web UI cannot do what you claim the platform does, you have not finished building the platform.
The Honest State
88% complete. 15 epics, 9 finished. 4 Docker services running. 5 channels publishing. 358 test files passing. 60 known gaps in a groomed backlog. 7 production blockers being fixed right now.
It is not done. But the things that remain are documented, prioritized, estimated, and planned -- which is more than most projects can say about their known unknowns.
The agents will keep building. The scheduler will keep ticking. The forensic audits will keep happening. And the blog posts will stop pretending everything is fine.
Built with the ORCHESTRATE framework by Michael Polzin. The platform, the methodology server, and every blog post -- including this one -- are part of the same system.
Provenance and Attribution
- Platform: ORCHESTRATE Marketing Platform V3
- Author: Michael Polzin (iamhitl.com)
- AI Agents: Claude Opus 4.6 (1M context)
- Methodology: ORCHESTRATE Agile with DD-TDD
- Program: 15 epics, 12 sprints completed, Sprint 12 in progress
- Forensic audit: Inna Cept persona, 2026-03-30
Top comments (0)