Skip to main content

​
Trigger a Council Decision

Council decisions are structured processes where multiple agents assess a situation from their domain expertise and produce a verdict. Here’s how to trigger each one.

​
The 7 Council Workflows

CodeNameWhen to UseTrigger
CW-01New Project EvaluationYou have a new idea or opportunityManual (webhook)
CW-02Priority Conflict ResolutionTwo things are competing for attentionManual (webhook)
CW-03Weekly Strategy SyncRegular planning cadenceAutomatic (Monday)
CW-04Financial Decision GateMoney decision neededManual (webhook)
CW-05Shipping/Release DecisionReady to release somethingManual (webhook)
CW-06Content Calendar PlanningPlanning content for the week/monthAutomatic (Monday)
CW-07ADHD Emergency ProtocolFeeling overwhelmed, stuck, paralysedManual or automatic

​
How to Trigger a Decision

​
Option A: From the Console

  1. Go to console.so1.io/agents
  2. Click the relevant agent (usually Atlas for coordination decisions)
  3. Find the council workflow in “Linked Workflows”
  4. Click Run

​
Option B: From Discord

Some workflows have Discord slash commands or reaction triggers. When a council decision posts to #council-decisions, you can react to approve or reject.

​
Option C: Direct Webhook (Advanced)

Each workflow has a webhook URL. You can trigger it with data: 
# Example: Submit a new project for evaluation
curl -X POST https://hab.so1.io/webhook/council-new-project \
  -H "Content-Type: application/json" \
  -d '{
    "project_name": "Mobile App v2",
    "description": "Rebuild the mobile app in React Native",
    "estimated_effort": "3 months",
    "strategic_value": "Expand to mobile users",
    "requested_by": "your-name"
  }'

​
What Happens After You Trigger

Every council workflow follows the same 5-layer pattern:
1

Perception

The workflow gathers context — what’s the current state, what data is relevant.
2

Reasoning

Each relevant agent analyses the situation from their domain. Agents run in parallel, each producing a score and assessment.
3

Action

Results are synthesised into a recommendation. A human gate posts to Discord for your approval.
4

Persistence

The decision is logged to Airtable (Council Decisions table) with all agent scores, verdict, and confidence level.
5

Observation

A summary notification posts to #council-decisions on Discord.

​
Reading the Discord Embed

When a council decision completes, you’ll see an embed in #council-decisions like this: 
📋 COUNCIL DECISION: New Project Evaluation
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Project: Mobile App v2

VERDICT: GO ✅  (Confidence: 0.82)

Agent Scores:
  🗺️ Compass: 8/10 — Strong strategic alignment
  💰 Vault:   6/10 — Budget tight but feasible
  🧠 Cortex:  9/10 — Tech is mature, good learning ROI
  🛠️ Anvil:   7/10 — 3 months realistic with current team
  🏋️ Tempo:   7/10 — Manageable workload if prioritised

Summary: Project approved with condition that Q2 budget
is confirmed before sprint 2.

React ✅ to confirm  |  ❌ to reject  |  ⏸️ to defer
What the scores mean:
  • 8-10 — Strong support from this agent’s perspective
  • 6-7 — Supportive with reservations
  • 4-5 — Neutral or uncertain
  • 1-3 — Agent recommends against
What the verdicts mean:
  • GO — Proceed
  • NO-GO — Don’t proceed (with reasons)
  • DEFER — Not now, revisit later (with suggested timeline)
  • RESOLVED — Conflict resolved (for CW-02)

​
CW-07: ADHD Emergency Protocol

This one is special. It can trigger automatically when signals accumulate: Trigger signals:
  • Multiple missed deadlines
  • Excessive context switching
  • Energy state critical (from Tempo)
  • Decision paralysis detected
What it does:
  1. Clears all non-essential tasks from the queue
  2. Identifies the ONE most important thing
  3. Breaks it into a 5-minute micro-step
  4. Posts a simplified action plan to Discord
  5. Activates body-doubling mode (step-by-step narration)
You can also trigger CW-07 manually whenever you feel stuck. There’s no shame in using it — it’s designed to get you moving again.