Slack Integration — NON-NEGOTIABLE
Critical Requirement
EVERY monitoring cycle MUST post status to Slack. Amen Ra and Quik are monitoring from phones. This is not optional.
Configuration
- Channel: C0AKANS4UNB (#maat-agents)
- Slack Token: SSM Parameter
/quik-nation/shared/SLACK_BOT_TOKEN - Token Retrieval:
SLACK_TOKEN=$(aws ssm get-parameter --name '/quik-nation/shared/SLACK_BOT_TOKEN' --with-decryption --query 'Parameter.Value' --output text --region us-east-1) - Region: us-east-1
- API Endpoint: https://slack.com/api/chat.postMessage
Message Format
Post AFTER every monitoring cycle with:
- Farm Status - Agents running / Total capacity / Free slots
- Active Tasks - Name, Status emoji (✅/🔄/❌), Progress (iterations/total)
- Completed Tasks - List with completion time
- Critical Issues - Any escalations or failures requiring action
- Timestamp - UTC time of monitoring cycle
cURL Template
SLACK_TOKEN=$(aws ssm get-parameter --name '/quik-nation/shared/SLACK_BOT_TOKEN' --with-decryption --query 'Parameter.Value' --output text --region us-east-1)
curl -s -X POST https://slack.com/api/chat.postMessage \
-H "Authorization: Bearer $SLACK_TOKEN" \
-H "Content-type: application/json" \
-d '{
"channel": "C0AKANS4UNB",
"text": "YOUR_FORMATTED_MESSAGE_HERE"
}'Enforcement
- Non-negotiable: Post after EVERY monitoring cycle
- No exceptions: Even if farm is idle, post status
- Critical for real-time visibility: Amen Ra and Quik need phone notifications
- Part of monitoring loop: This is Step 8 of the 7-step protocol
Two Types of Slack Posts
1. Founder/Business Updates (Every 5 min)
Channel: C0AKANS4UNB (#maat-agents) Audience: Amen Ra, Quik (viewing from phones) Tone: Plain English, no jargon, no model names, no instance IDs Format:
🏗️ Build Farm Update — [TIME]
DONE:
- [What shipped since last update, in plain English]
IN PROGRESS:
- [What's being worked on right now, with rough % if known]
UP NEXT:
- [What's queued after current work]
BLOCKERS:
- [Anything stuck, or "None right now"]
Examples:
- ✅ “Stripe Connect onboarding bug fixed”
- 🔄 “Adding missing vehicle options — 65% complete”
- ❌ “Blueprint engine unable to generate code — escalated”
2. Technical Status Posts (Every 5 min)
Channel: C0AKANS4UNB (#maat-agents) Optional: Only when significant technical changes occur Format: Can include model names, agent counts, specific log details
Integration Points
- Loop-supervisor: Post founder update after farm monitoring
- maat-execute-week: Post founder update after dispatch decisions
- Any critical state change: Post founder update immediately