Absorbed — absorbed into methodology-22-ROUNDTABLE-SYNTHESIS.md, per Arch’s B3 synthesis
ruling (2026-09-01, docs/internal/architecture/reviews/2026-08-architectural-review/), which
found this pattern and m-22 to be genuine unflagged redundancy — both EFFECTIVE, describing
overlapping multi-perspective leadership-alignment coordination. Arch ruled the shape (one
absorbs the other) and delegated the pick to Docs+CIO jointly; picked m-22 as canonical because it
carries substantially more unique content (3 dated, evidenced case studies, a synthesis template,
a “why this works” analysis, and its own failure-mode catalog) — moving m-22’s content into this
file would have been the larger migration. This pattern’s own unique content (the Anti-Patterns
table and the Pattern-029 differentiation) was folded into m-22 as part of the same motion, not
lost. Pattern content preserved below for historical reference.
| Original status (pre-absorption): Emerging | Proven in MUX Track V1 (January 19, 2026) |
Complex, cross-cutting work often requires input from multiple advisor domains before execution can begin. Traditional approaches have limitations:
The Leadership Caucus addresses the need for synchronous multi-advisor alignment before complex work begins, complementing async coordination patterns.
Core Concept: A facilitated, synchronous discussion where multiple advisors contribute domain perspectives to a cross-cutting decision, with the PM as facilitator capturing decisions as they emerge.
Key Elements:
How It Works:
Use a Leadership Caucus when:
| Role | Presence | Purpose |
|---|---|---|
| PM | Required (facilitator) | Frame question, capture decisions, resolve disputes |
| Relevant advisors | 2+ recommended | Contribute domain perspective |
| Lead Dev | If implementation follows | Confirm implementation path |
Note: Full advisor complement is optional—invite those relevant to the decision.
1. FRAME - PM states the question and provides context
2. CONTRIBUTE - Each advisor shares perspective from their domain
3. CAPTURE - PM documents decisions explicitly as they emerge
4. RESOLVE - Disagreements addressed in session (not deferred)
5. CONFIRM - Lead Dev acknowledges implementation path
| Anti-Pattern | Why It’s Wrong | Correction |
|---|---|---|
| Caucus for single-domain decisions | Overkill; wastes advisor time | Use direct consultation or mailbox |
| Skipping caucus for cross-cutting work | Creates alignment debt; execution slows | Call the caucus upfront |
| No facilitator | Discussion meanders, decisions unclear | PM always facilitates |
| Deferring disagreements | Kicks the can; alignment incomplete | Resolve in session |
| Full advisor complement always | Not all decisions need everyone | Invite only relevant advisors |
| Design by committee | Advisors contribute, they don’t vote | PM facilitates and decides |
MUX Track V1 (January 19, 2026):
docs/omnibus-logs/2026-01-19-omnibus-log.mdIdentified by HOSR during Jan 16-22 workstream review as “Leadership Cascade,” renamed to “Leadership Caucus” by PM to emphasize iterative deliberation over sequential handoff.
| Pattern | Purpose | Timing | Participants |
|---|---|---|---|
| Audit Cascade (049) | Verify work at phase boundaries | After work | Single agent audits |
| Mailbox System | Async cross-role communication | Any time | 1:1 or 1:many |
| Leadership Caucus (059) | Sync multi-advisor alignment | Before complex work | PM + multiple advisors |
Pattern-059 and Pattern-029: Multi-Agent Coordination both involve multiple agents but serve different purposes:
| Dimension | Pattern-059 (Leadership Caucus) | Pattern-029 (Multi-Agent Coordination) |
|---|---|---|
| Domain | Leadership alignment | Technical execution |
| Purpose | Align on cross-cutting decisions before work begins | Coordinate parallel implementation work |
| Participants | Advisory agents (CXO, Architect, PPM) + PM | Coding agents (Backend, Frontend, Analyst) |
| Timing | Before execution | During execution |
| Output | Decisions, assignments, implementation direction | Code, tests, validated changes |
| Coordination | Facilitated discussion, real-time decision capture | Cross-validation, handoffs, parallel phases |
In practice: A Leadership Caucus (059) produces the decision and assignment that triggers a Multi-Agent Coordination (029) deployment. They are sequential, not competing — one decides what and how; the other executes.
mailboxes/exec/read/memo-cio-leadership-caucus-response-2026-01-26.mdmailboxes/cio/read/memo-cio-leadership-caucus-2026-01-26.mdPattern created: January 26, 2026 Origin: MUX Track V1 coordination success Formalized per CIO recommendation