Coherence Daddy · Advisory Board

Six advisors. One verdict. Zero hedging.

Run any question, idea, or decision through a structured council that fetches real data, debates it from six angles, peer-reviews itself anonymously, and gives you a Chairman's verdict with kill criteria.

11 slides · ~5 min read Claude Code · MCP · Anthropic API ~$1–3 per council run
Why a council, not a chatbot

One AI gives you one perspective.

Ask GPT or Claude "should I do X?" and you get a balanced, hedged answer that mostly reflects the model's training average. Useful, but not what you need before a real decision.

The council fixes three failure modes of single-model advice:

  • Single perspective: six advisors with deliberately conflicting thinking styles produce tension you can use.
  • Hallucinated facts: a recon agent fetches real data first, so advisors aren't inventing market state.
  • Sycophancy: advisors review each other anonymously, so they evaluate the argument, not the source.
The council's job is not to agree. It's to give you a clear answer that survived contact with five other smart objections.
Slide 03 / The six advisors

Six thinking styles. Three natural tensions.

01 / Downside

The Contrarian

Looks for the fatal flaw. Names the failure mode in the first 30 days. Tests per-unit economics.

02 / Reframe

The First Principles Thinker

Asks "what are we really solving?" Strips assumptions. Forces a reframe even if the original survives.

03 / Upside

The Expansionist

Names the 10x version. Finds the adjacent market. Maps the long-term moat.

04 / Buyer

The Customer

Pretends to be the actual end buyer. Surfaces curse-of-knowledge jargon. Names what would stop a sale.

05 / Tempo

The Executor

"OK, but what do you do Monday morning?" The smallest test. The kill date. The distribution mechanic.

06 / Reality

The Operator

Legal entity, liability, refunds, taxes, KYC, regulatory exposure. The parts a strategy memo never mentions.

Tensions: Contrarian vs Expansionist (downside vs upside) — First Principles vs Executor (rethink vs ship) — Customer + Operator hold the room honest.

Slide 04 / The reality check

Recon before the council deploys.

Most strategy questions depend on current external reality — competitor pricing, regulatory rules, platform behavior. Single-LLM advice often hallucinates these confidently.

Before any advisor sees the question, the facilitator dispatches a recon agent that fetches real data via WebFetch and returns a ≤500-word ground-truth packet — every claim cited with a URL.

RECON PACKET
- Stripe per-transaction fee: 2.9% + $0.30 (stripe.com/pricing)
- LLC filing in Delaware: $90 state fee + registered agent
- Competing tool X charges $49/mo (saw landing page X.com)
- Reddit thread, 2026-03: "this category is saturated"
  (reddit.com/r/X/comments/abc123)
If recon contradicts the user's premise
The framed question is rewritten before the council deploys. Don't make six advisors solve the wrong problem.
Slide 05 / Each advisor has mandatory checks

Generic answers don't ship.

Each advisor is given an explicit checklist they must address. This is what stops "the Contrarian" from giving a vague pessimism take and forces them to actually identify the load-bearing assumption.

Example — The Operator's mandatory checks:

  • Legal entity & liability: who is the legal principal, whose name is on the contracts, what's the personal exposure?
  • Regulatory exposure: licenses, tax filings, GDPR/CCPA, platform ToS, industry rules?
  • Unit economics: what does each transaction cost after fees, refunds, support time, taxes?
  • Customer-service shape: what happens with refunds, chargebacks, an angry customer who demands a phone call?
  • Failure-mode containment: what's the kill switch and the worst single-incident loss?

If an advisor genuinely has nothing to add on a check (e.g., no legal dimension), they say so explicitly rather than padding.

Slide 06 / Anonymous peer review

Each advisor reviews the others — blind.

Once all six advisor responses are in, they're anonymized A through F (random map) and re-dispatched to six fresh reviewer agents. Each reviewer answers five questions:

  1. Which response is the strongest? Why?
  2. Which has the biggest blind spot? Name the specific thing it's missing.
  3. What did all six miss? (mandatory — even if you have to dig)
  4. Which response, if followed alone, would lead to the worst outcome?
  5. What evidence would change your answer to #1?
Question 5 is the load-bearing one
It forces the reviewer to name the falsification condition for their own pick — which makes the eventual recommendation honest about what it depends on.

Anonymization removes positional bias. Reviewers evaluate the argument, not the brand.

Slide 07 / The Chairman's verdict

One synthesis. Seven sections. No hedging.

The Chairman gets everything: question, recon packet, six advisor responses (de-anonymized), six peer reviews. The verdict follows a fixed structure:

SectionWhat it forces
Where the council agreesHigh-confidence convergence signals
Where the council clashesReal disagreements, not papered over
Blind spots peer review caughtInsights that emerged in round two
What the council got wrongMandatory: Chairman must disagree on at least one thing
RecommendationWhat to do, why over alternatives, kill criteria, falsification trigger
The one thing to do firstSingle concrete next action — not a list of ten
What to verify before actingPre-action recon to protect against stale reality

The Chairman can — and should — disagree with the majority if the minority case is stronger. The job is the right answer, not the popular one.

Slide 08 / Three output files

Every session produces three artifacts.

council-report-[timestamp].html

A clean briefing document. Framed question, Chairman's verdict prominent, alignment table, recon packet with URLs, collapsible advisor responses, peer review highlights. Opens immediately after generation.

council-transcript-[timestamp].md

Full record. Original question, framed question, recon, all six responses, all six peer reviews with anonymization map revealed, Chairman synthesis. The artifact a future agent can re-enter the conversation from.

council-followups-[timestamp].md

Pre-action checklist + post-action checkpoints + re-council triggers. This is the file that turns a one-shot council into a continuous decision tool.

Why three?
The HTML is for humans. The transcript is for replay. The follow-ups file is what makes the next session possible without re-doing the work.
Slide 09 / Install

One install. Then invoke per question.

Claude Code
/plugin marketplace add Coherence-Daddy/advisory-board
/plugin install advisory-board@advisory-board
/reload-plugins

Then any agent can invoke the council via the Skill tool, or you can prefix any question with:

Claude Code
Use advisory-board to council this:

I'm thinking of [decision]. Audience [profile]. Constraints [budget, time].
What's the best move?
Download .md

The skill loads on demand — its body doesn't bloat your session context until you invoke it.

Slide 10 / When not to council

Knowing when to skip is part of the skill.

A council is overkill for a lot of questions. The facilitator is trained to not deploy the machinery when:

  • You've already counciled this topic recently and the new question is narrow and specific within the prior verdict's scope. Just answer using the prior verdict as context.
  • The question is about executing a prior recommendation. Drop into normal assistant mode, not council mode.
  • The question is purely factual or mechanical. "How does Stripe webhook signing work?" doesn't need six advisors.

A council is the right tool when:

  • The decision is consequential, multi-dimensional, or has significant downside.
  • You suspect you have blind spots or you're emotionally invested in one answer.
  • External reality (markets, regulations, platforms) materially affects the answer.
Cost reality check
A council run is roughly 12 LLM calls plus recon. Real money. Don't council "what should I name my variable."
Episode 01 · Done

One real decision is all it takes.

Pick something you've been chewing on for more than a week — a pricing change, a launch decision, a partnership offer, a pivot. Something with real downside. Run it through the council. Worst case: 10 minutes and confirmation. Best case: the council catches the one thing that would have killed the plan.