The WAR Room Protocol.
A documented protocol for high-stakes product strategy: a synthetic 100-panelist bench, 100 rounds of structured argument, a three-question stress test, a kill list, and a Sacred Accident discipline that catches the things the room learns about itself while running.
Why this exists
Most product decisions are made by a single founder under deadline pressure, with the loudest voice in the room winning by default. Most strategy documents are written by one person trying to sound like twenty. Both shapes lose to the same failure mode: the strategy is shaped by the available people in the room, not the right people.
The WAR Room is the operator’s response. Every high-stakes decision at SongForgeAI is argued by a synthetic panel of 50–100 named experts — real people in their actual disciplines, drawn from across the relevant industries, with at least one panelist specifically positioned to attack the operator’s instinct. The room runs 100 rounds of structured argument, builds a kill list as it goes, and ends with a final verdict.
The protocol is documented here so others can run it. The artifacts are committed publicly so the operator’s decisions are auditable from the outside. The license is the same one the Lyric Scoring Standard ships under: CC BY 4.0.
The protocol
How a WAR Room runs.
1. Compose the panel
The bench is weighted toward people who actually do the work being argued about. A wedding-vertical room over-indexes on wedding planners, officiants, and venue GMs — not technologists. A scoring-rubric room over-indexes on songwriters, poets, and editors — not ML researchers. At least one group is adversarial by charter: their job is to attack every proposal until it survives.
2. The three-question stress test
Every proposal must pass three questions, set in Round 0 by the room’s discipline-keeper. Failure on any one sends the proposal to the kill list, not the shortlist:
- Could a competitor copy this in 90 days? If yes, it’s a feature, not a moat. Tighten the proposal until the answer is no.
- Would a million users genuinely use it? If the proposal is beautiful but addresses a hundred-person market, name that — and either kill it or move it to a different revenue line.
- Is the operator the right party to ship it? Some game-changers belong to a partner, a label, a foundation. The room isn’t here to staff the roadmap by force.
3. Run 100 rounds
Each round has a topic, an argument, a rebuttal, and a synthesis. The standard sequence: Rounds 1–10 read the brief; 11–30 size the market and viability; 31–60 work through implementation tradeoffs; 61–80 stress-test pricing and operational ceilings; 81–90 cover go-to-market; 91–100 synthesize and surface the Sacred Accident. Some rooms compress; none extend. 100 is the discipline.
4. The kill list is mandatory
Every WAR Room ends with a written kill list: the proposals the room considered and refused. The kill list is a first-class artifact — documented with the same care as the verdict. Future rooms reference the kill list to avoid re-litigating settled refusals. Some kills are permanent (voice-cloning the deceased, NFT memorial certificates, “in the style of [famous artist]” in buyer UI); others are deferred.
The Sacred Accident discipline
What the room learns about itself.
Around Round 90, a properly run WAR Room often surfaces a finding that wasn’t in the brief and isn’t on the kill list — a permanent operational principle the room learned by running. We call these Sacred Accidents. They get numbered, named, and logged.
Sacred Accident #13, from the Memorial + Wedding room, is a representative example: “A memorial song trapped behind a login outlives nothing.” The room arrived at it after R88 (an argument about how to gate downloads) and R94 (an argument about whether memorials should be indexable). It became the brand promise of the entire vertical — export-by-default, share-by-default, heirloom-by-default.
The discipline: a Sacred Accident must be unsought (not the room’s charter), load-bearing (operationally consequential), and surfaced by the room, not by the operator. They are logged at /sacred-accidents and committed as canonical artifacts.
Published WAR Rooms
Every room is committed publicly.
The audit trail is the protocol. Each room’s transcript — the panel composition, the 100 rounds, the kill list, the verdict, the Sacred Accident if one surfaced — lives in the public repo. Anyone can audit the operator’s strategic reasoning from the outside.
Topic Sovereignty
The principle that the user owns the topic; the system varies the treatment. Established why we refuse to silently mutate a user’s song idea across a batch.
docs/WAR-ROOM-TOPIC-SOVEREIGNTY.md → GitHub
Model Abstraction
Whether to migrate from a single-provider Claude path to a provider-agnostic abstraction. The verdict shaped the buildArtistBriefViaProvider migration.
docs/WAR-ROOM-MODEL-ABSTRACTION-2026-05-17.md → GitHub
Perspective UX Audit
The 8-voice Crucible UX. Argued every legibility, ordering, and verdict-rhythm decision before the redesign shipped.
docs/WAR-ROOM-PERSPECTIVE-UX-AUDIT.md → GitHub
Duet V2 — World Class
The two-voice contribution-ledger system. Argued the bench through co-author rights, voice attribution, and copyright posture.
docs/WAR-ROOM-DUET-V2-WORLD-CLASS.md → GitHub
Artist Brief Perspective
The structured 15-field brief that powers the Persona Forge. Argued every field, every cap, every redaction rule.
docs/WAR-ROOM-ARTIST-BRIEF-PERSPECTIVE.md → GitHub
Fifty-creative monetization
Fifty-panelist room: which monetization paths to test, which to kill. The kill list from this room still governs the operator’s ship decisions.
docs/WAR-ROOM-2026-05-16-FIFTY.md → GitHub
100 Creative Minds review
The largest WAR Room run to date. 100 panelists, 100 rounds, 17 survivor proposals, 22-item kill list, Sacred Accident #12 surfaced.
docs/WAR-ROOM-100-CREATIVES-2026-05-18.md → GitHub
Memorial + Wedding vertical
Bench rating 91/100. Verdict: build it carefully. Sacred Accident #13 (“a memorial song trapped behind a login outlives nothing”) was the room’s most important finding.
docs/WAR-ROOM-MEMORIAL-WEDDING-2026-05-18.md → GitHub
License · CC BY 4.0
Fork it. Use it. Cite it.
The WAR Room Protocol v1.0 is licensed under Creative Commons Attribution 4.0 International. You can adopt it, modify it, and run your own rooms under it. Required attribution: a link back to this page and a citation in the artifacts you generate (“Following the SongForgeAI WAR Room Protocol”).
The protocol is deliberately model-agnostic. Some rooms have run on Claude alone; some have mixed Claude and GPT; one ran on a literal whiteboard. The discipline is the panel, the three questions, the rounds, and the kill list — not the tool.