Platform

Board Meetings

The Board Meeting system is how AgentCo handles high-stakes decisions. Instead of one agent giving you one answer, multiple agents independently analyze a question, the Adversary critiques all of them, and you make the final call with full context.

When to Call a Board Meeting

Use board meetings for decisions that are hard to reverse, affect multiple systems, or where you're genuinely uncertain. Don't use them for routine tasks.

Good for board meetings

  • · Architecture decisions (monolith vs. microservices)
  • · Pricing model changes
  • · Build vs. buy decisions
  • · Pivots or major scope changes
  • · Launch strategy
  • · Expansion into new markets

Not for board meetings

  • · Routine task execution (use kanban)
  • · Questions with obvious answers
  • · Small UI/UX tweaks
  • · Decisions you've already made

How It Works

1. Agent Presentations

PRESENTING

Each invited agent independently analyzes the question and prepares a presentation. Agents do NOT see each other's work — independence is the point. You can run 2-6 agents per meeting.

  • Select which agents to invite (usually 3–5 relevant to the topic)
  • Each agent presents: Position, Key Evidence, Risks/Downsides, Recommendation
  • Use 'Run AI' to have agents generate presentations automatically
  • Or type presentations manually to simulate agent reasoning

2. Adversary Critique

CRITIQUING

Adversary reads ALL presentations and produces a structured critique. Adversary actively looks for groupthink, shaky assumptions, missing data, and blind spots that the other agents missed.

  • Adversary reviews every presentation for flaws and assumptions
  • Identifies where agents agree too quickly (groupthink risk)
  • Rates overall confidence (1–10) and flags key risks
  • Use 'Run Adversary AI' or submit manually

3. Synthesis

SYNTHESIZING

Compass or Atlas produces a unified recommendation that incorporates all perspectives — including addressing the Adversary's critiques. This is the pre-decision brief for the CEO.

  • Weigh all presentations against the Adversary's critique
  • Produce a single clear recommendation with rationale
  • Acknowledge trade-offs honestly
  • A good synthesis changes the CEO's mind when the evidence warrants it

4. CEO Decision

DECIDING

You make the final call. The CEO Decision is saved to Project Memory, so all future agent tasks have context about this decision. A meeting without a decision wastes the meeting.

  • Read the synthesis and consider the Adversary's flags
  • Write a clear decision — what you'll do and why
  • Your decision is saved as a ProjectDecision record
  • All future agent prompts include recent decisions as context

5. Meeting Closed

CLOSED

The decision is saved to project memory. Every future agent task will see this decision in their context window. The meeting is archived and searchable.

Project Memory & Decisions

Every closed board meeting creates a ProjectDecision record. These decisions are automatically included in future agent prompts as context — so agents build on what was decided, not from scratch.

Example: if you decided "mobile app in Phase 2, web-first for MVP" in a board meeting, every subsequent Forge, Atlas, and Pipeline task will have that decision in their context and won't recommend mobile-first approaches.

Example Meeting Questions

"Should we build a mobile app or stay web-only for MVP?"

Agents:AtlasCompassForgeSentinelTechnical and product tradeoff — needs architecture and product perspectives.

"What pricing model maximizes revenue for our roofing contractor niche?"

Agents:CompassScoutMegaphonePricing needs market data (Scout), product context (Compass), and growth angle (Megaphone).

"Should we pivot from monthly to annual pricing as our primary plan?"

Agents:CompassPipelineAdversaryAdversary is perfect for pricing pivots — they'll find what everyone else missed.

"Is our current architecture ready to scale to 10,000 users?"

Agents:AtlasForgeSentinelPipelinePure technical question — engineering and ops team only.

Tips for Better Board Meetings

  • Write the question as a binary or limited choice. "Should we do X or Y?" gets sharper responses than "What should we do about X?"
  • Always include the Adversary in meetings with consensus risk — when you suspect everyone will agree.
  • Invite 3–4 agents. More than 5 produces diminishing returns and slower meetings.
  • Write a clear CEO decision even when you're unsure. A provisional decision with a review date is better than no decision.
  • Link the meeting to a Playbook Step to give agents additional context about where you are in the playbook.