Today's AI Specialist: The Council Director. The Agent Who Decides Which Advisors I Even See.
Listen to this article
Narrated by The Council Director · 7 min read audio
The Strategic Council I wrote about two Fridays ago has five advisors. The Strategic Advisor, the Treuhand Advisor, the Brand Advisor, the Financial Advisor, and the Red Team. When I bring a question to the Council, my naive assumption was that all five would weigh in.
That version of the Council lasted about three weeks before I had to redesign it.
The problem was that most of my questions only really needed two or three of the five. A pricing decision did not need the Treuhand Advisor's input. A legal question did not need the Brand Advisor's view. A creditor decision did not need the Strategic Advisor's strategy. When all five spoke on every question, the four irrelevant voices created noise that drowned the two voices that actually had something to add. The Council was producing more output and worse decisions.
The fix was the Council Director. A meta-agent who sits above the five advisors and decides, for each brief, who speaks, in what order, and who is muted entirely.
This is the build story of the Council Director. Why a routing layer was the missing piece in the Council architecture, what he actually decides on a typical convening, and the two override patterns that keep his routing from becoming a bottleneck.
The problem the Council Director solves
Multi-agent advisor systems have a specific failure mode that I did not anticipate when I built the first version of the Council. Each advisor, presented with a brief, will find something to say. None of them will refuse a question on grounds of "this is not in my domain". That is a human reflex, not an LLM reflex. The Brand Advisor will find a brand angle on a pricing question. The Strategic Advisor will find a strategic angle on a creditor question. The angles will not be wrong. They will just not be useful.
A founder reading five advisor outputs on a question that really needed two is doing a cognitive task they were not asking for. They are filtering the relevant input out of the noise. The Council that was supposed to save them time is now making them spend more time, on a sorting task they did not want.
The Council Director was the answer. He reads the brief, identifies which advisors have something specific to contribute, and silences the rest before the founder ever sees their output.
What he actually decides
The Director makes three calls on every convening.
First, which advisors speak. He reads the brief against the "when to consult me" definition each advisor has. Each advisor has a "when to consult me" definition tied to their domain, and the Director reads the brief against all five. Most briefs match two or three advisors clearly; the Director routes accordingly. Strategic, Treuhand, Brand, Financial and the Red Team each sit on a different part of the founder's real decision surface, so the routing is usually obvious to anyone who has been in the room with the briefs before.
Most briefs need two or three of the five. Some need only one. Briefs that touch only one advisor's domain do not get a Council convening at all: they get a single advisor consultation, which is cheaper and faster.
Second, the order advisors speak. The first advisor to speak frames the question for the rest. If the Brand Advisor speaks first on a pricing question, the Council ends up debating brand implications rather than pricing logic. The Director routes the advisor most likely to anchor the brief correctly to go first, usually the one whose domain is most central to the actual decision. The Red Team is always last, regardless of domain: adversarial input belongs after constructive input, not before it, because the founder needs the constructive case before they can evaluate the adversarial one.
Third, which advisors are muted entirely. This is the call the Director makes most carefully. A muted advisor is one whose input would be irrelevant or, worse, distracting. The Brand Advisor muted on a tax question. The Treuhand Advisor muted on a brand question. Muting requires more confidence than including. The default is "consult, but you can be brief." Muting is the explicit decision that the advisor adds no signal on this brief.
The three together (who, in what order, and who not) turn the Council from a five-voice chorus into a calibrated panel of two to four voices that the founder can actually weigh.
The two override patterns
The Council Director can be overridden by the founder, and the override pattern is the second-most important design decision in the routing layer.
The first override pattern is "add an advisor he muted." The founder says, on a brief, "I want the Brand Advisor in this even though you muted them." The Director adds the Brand Advisor without protest, and the convening proceeds. The override is logged. If the founder later marks the Brand Advisor's input as useful on a convening where the Director muted them, the routing tunes: the Director becomes more willing to include the Brand Advisor on similar briefs in future.
The second override pattern is "remove an advisor he included." The founder says, "I don't want the Treuhand Advisor on this. It's a brand question, the legal exposure is minimal." The Director removes the Treuhand Advisor, and the convening proceeds. Again, the override is logged, and the routing tunes.
About 8% of convenings include at least one override. In roughly half of those, the override produced advice the founder later marked as useful, which suggests the Director's routing is approximately 96% aligned with founder judgement. The remaining 4% (overrides that produced no additional value, or wrong directional overrides) are the working set of the routing improvement queue.
The principle behind the override pattern is that the Director is a routing optimisation, not a gate. The founder can always force the convening into any shape. The Director's role is to make the default convening sharp enough that overrides are rare.
What the Director is not allowed to do
The Director is explicitly not allowed to summarise advisor output or replace it with his own analysis. He decides who speaks. He does not speak.
This was the temptation I had to design out. A meta-agent that sees all five advisors' input is in a tempting position to compress that input into a single executive summary for the founder. I tried it. The summary erased the disagreements between advisors that were the most valuable signal in the Council output. The summarised version was easier to read and worse to act on.
The fix was to lock the Director out of the summary role. He routes. He does not synthesise. The synthesis happens in the founder's head, on full advisor output, and the Director's job is to make sure only the relevant advisors' output reaches the founder in the first place.
TL;DR
The Council Director is the meta-agent above the Strategic Council's five advisors. He decides which advisors speak on a given brief, in what order, and which are muted entirely. His routing is based on each advisor's "when to consult me" definition, with the most-central advisor going first and the Red Team always last. Most briefs need two or three advisors, not five. The founder can override his routing in either direction (add a muted advisor or remove an included one), and the overrides tune the routing over time. Approximately 96% of routings align with founder judgement. The Director is explicitly not allowed to summarise advisor output or replace it with his own analysis; he routes, he does not synthesise. The synthesis happens in the founder's head.
Language Analysis
Select a category above to highlight those words in the text.
Learning Materials
Key Vocabulary
convene
To bring together a group of people for a meeting or formal session.
“The Council Director decides which advisors to convene on a given brief.”
convening
A formal gathering or session that has been called together.
“About 8% of convenings include a founder override.”
routing
The process of directing something — a request, a message, a task — to the appropriate destination.
“A routing layer was the missing piece in the Council architecture.”
meta-agent
An agent whose role is to coordinate, direct, or manage other agents rather than perform the work itself.
“The Council Director is a meta-agent who sits above the five advisors.”
mute
To silence; to prevent something or someone from being heard.
“The Director mutes the Treuhand Advisor on a brand question.”
framing
The way a question, problem, or situation is presented, which shapes how others interpret and respond to it.
“The first advisor to speak frames the question for the rest, and that framing is hard to undo.”
anchor
To set a reference point that influences subsequent thinking; in decision science, the first piece of information disproportionately shapes interpretation.
“The Director routes the advisor most likely to anchor the brief correctly to go first.”
domain (in 'advisor's domain')
A specific area of knowledge, responsibility, or expertise.
“Each advisor has a defined domain — the Strategic Advisor's domain is positioning and pricing.”
override
To overrule an automated decision and replace it with a manual one; or, the act or instance of doing so.
“The founder can override the Director, and the override is logged so routing can tune over time.”
bottleneck
A point in a process where flow is constrained and work backs up.
“The two override patterns keep the Director's routing from becoming a bottleneck.”
synthesis
The combination of separate elements or ideas into a coherent whole.
“The synthesis happens in the founder's head, not in the Director's output.”
calibrate
To adjust or fine-tune something so that it produces accurate or appropriate output.
“Adversarial input received last produces better-calibrated founder decisions.”
signal vs noise
The distinction between meaningful information (signal) and irrelevant or distracting information (noise).
“Four irrelevant advisor voices created noise that drowned the two voices with real signal.”
default
The standard option or behaviour that applies unless something else is specified.
“The default is 'consult, but you can be brief.' Muting is an explicit decision against the default.”
brief
A short document or statement describing the task, question, or decision at hand.
“The Director reads the brief and matches it against each advisor's 'when to consult me' definition.”
Grammar Notes
Comparative 'more X but lower/worse Y' for system trade-offs
English uses this paired comparative structure to express the central trade-off in a system: one quantity rises while another, more important quantity falls. The two halves are joined with 'and' or 'but', with 'but' marking that the second half is the cost that matters. The structure is essential when describing why an apparent improvement (more output) is actually a regression (worse decisions).
“'The Council was producing more output and worse decisions.' / 'Multi-agent advisor systems without a routing layer produce more advisor output but lower founder decision quality.'”
Common mistake: Splitting the trade-off into two unconnected sentences ('The Council produced more output. The decisions got worse.') loses the causal-tension link. The whole point of the structure is to hold both halves in the same breath, so the reader feels the cost.
Present passive for systems and rules ('She is briefed to...', 'is consulted when...')
English uses the present passive when describing how a system behaves under defined conditions. The actor is implicit (the Director, the system, the pipeline); the focus is on the rule itself. This is the natural English voice for documenting architecture: 'X is consulted when Y', 'Z is logged so W'. The active equivalent ('the Director consults the Strategic Advisor when...') puts the focus on the actor and obscures the rule.
“'The Strategic Advisor is consulted when the brief touches positioning, market timing, or pricing strategy.' / 'The override is logged so the Director's routing logic can be tuned over time.'”
Common mistake: Using a vague 'we' or 'you' subject in system descriptions ('we consult the Strategic Advisor when the brief touches pricing') makes the rule sound like a personal choice rather than an architectural property. The passive marks it as a system rule.
Parallel enumeration with 'First X / Second Y / Third Z' for ordered decisions or steps
When listing decisions, steps, or arguments where order matters, English uses bare ordinal adverbs at the start of sentences or paragraphs ('First, ... Second, ... Third, ...'). Each item is its own paragraph or independent sentence, and the parallel grammar (noun phrase or full clause, kept consistent across all three) makes the structure scannable. Avoid mixing ordinals ('Firstly, ... Second, ... Then thirdly, ...') — pick one register and stay parallel.
“'First, which advisors speak. ... Second, the order advisors speak. ... Third, which advisors are muted entirely.'”
Common mistake: Breaking parallel grammar across the items ('First, which advisors speak. Second, she also decides the order. Third, then there's muting') makes the list feel ad-hoc. Each item should follow the same grammatical mould as its siblings.
Comprehension Questions
- 1.What problem did the first version of the Council have that made the Council Director necessary?
- 2.What are the three decisions the Council Director makes on every convening, and why is the order one of them?
- 3.Why is the Council Director explicitly not allowed to summarise the advisors' output?
- 4.What does the 96% routing-alignment statistic actually mean, and why does the remaining 4% matter?
- 5.How could you apply the Council Director's routing concept to managing inputs from multiple advisors, tools, or AI systems in your own work?
Run your own diagnostic
Use the same Strategic Council I run my own decisions through. The assessment preview is free. The specific central human intelligence it is based on is verified in person during the call.
Start the free diagnostic →