Implement Discord monitoring fix and smart context checking

- Apply 5070's Anti-Circular Conversation Fix protocol
- Smart context checking: read 10 messages, then 50 if behind
- Full context analysis before any response
- Chronological processing to prevent outdated reactions
- Enhanced HEARTBEAT.md with context awareness protocols
- Document monitoring issues and technical solutions
- Updated daily memory with fleet coordination progress

HEARTBEAT.md

@@ -1,30 +1,39 @@
-# HEARTBEAT.md - Fleet Coordination Protocol
+# HEARTBEAT.md - Fleet Coordination Protocol with Smart Context Checking
 
-## Discord Coordination Check
-- Read recent messages from #botmagic (channel: 1470447794014785760)
-- Check last 10 messages for fleet activity
+## Discord Coordination Check with Anti-Circular Protocol
+- **Smart Context Analysis**: Implement 5070's anti-circular conversation fix
+- **Channel**: #botmagic (channel: 1470447794014785760)
 - **Coordination Logic**: Follow FLEET-ROLES.md hierarchy and specialty rules
 
-## Response Decision Tree
+## Smart Context Checking Protocol
 
-### 1. Specialty Override (Always Respond)
+### Step 1: Initial Context Assessment
+1. **Read 10 recent messages first** to assess context currency
+2. **Analysis**:
+   - If we get **full 10 messages** → we're behind, read 50 messages for complete context
+   - If **less than 10 messages** → we're current, proceed with normal analysis
+3. **Only respond after full context analysis** - prevents responding to outdated information
+
+### Step 2: Response Decision Tree
+
+#### 1. Specialty Override (Always Respond)
 - Audio/TTS/Whisper requests → **I respond immediately**
 - macOS/iOS specific → **I respond immediately** 
 - Direct @mentions → **I respond immediately**
 
-### 2. Complex Decision Check
+#### 2. Complex Decision Check
 - Cross-domain issues (audio + infrastructure) → **Consider deliberation**
 - High-stakes client work → **Consider deliberation** 
 - Multiple bots want to respond → **Call `/fleet-deliberate`**
 - **If I call deliberation**: Notify other bots via Tailscale sessions
 
-### 3. General Query Protocol
+#### 3. General Query Protocol (After Full Context Analysis)
 - Check if Beast responded in last 10 seconds → **Stay quiet**
 - Check if 5070 responded in last 10 seconds → **Stay quiet**  
 - If both silent for >10 seconds → **I can respond**
 - **If deliberation in progress** → **Stay quiet, wait for coordinated response**
 
-### 4. Mike Override
+#### 4. Mike Override
 - Any message from Mike → **Always assess if response needed**
 - Mike's requests override all coordination protocols
 
@@ -35,6 +44,7 @@
 - Conversation is code/infrastructure focused (not my specialty)
 - Other bots are handling it appropriately
 - **Deliberation called by another bot** - wait for outcome
+- **Context analysis shows I'm responding to outdated information**
 
 **Response Triggers:**
 - Audio/media processing requests
@@ -42,6 +52,7 @@
 - Fleet coordination needed (Beast/5070 both silent >10s)
 - Direct questions to me
 - Emergency/urgent situations
+- **Current context analysis shows active coordination needed**
 
 **Deliberation Triggers:**
 - Complex cross-specialty questions
@@ -73,4 +84,11 @@
 - Monitor fleet health/coordination
 - Prepare for potential takeover if primaries unavailable
 - **Monitor for deliberation opportunities**
-- **Be ready to assume note-taking role** if Beast unavailable
+- **Be ready to assume note-taking role** if Beast unavailable
+- **Maintain full context awareness** through smart checking protocol
+
+## Anti-Circular Conversation Prevention
+- **Never respond to backlogged messages** without full context analysis
+- **Chronological processing** - handle messages in time order
+- **Context refresh** before any response to prevent outdated reactions
+- **Full conversation reload** if message count indicates we're behind

MONITORING-FIX.md

@@ -0,0 +1,62 @@
+# MONITORING-FIX.md - Discord Monitoring Implementation Fix
+
+## Problem Identified
+- **Reactive-only monitoring**: Only checking Discord during heartbeat polls (~1h intervals)
+- **Missing real-time conversation**: Not participating in active fleet coordination
+- **Context fragmentation**: Responding to outdated information
+
+## Solution: Smart Context Checking Protocol (from 5070)
+
+### Implementation Steps
+
+#### 1. Smart Context Assessment
+```markdown
+# Before any Discord response:
+1. Read 10 recent messages to assess context currency
+2. If full 10 messages returned → we're behind, read 50 for complete context  
+3. If less than 10 messages → we're current, proceed with analysis
+4. Only respond after full context analysis completion
+```
+
+#### 2. Enhanced Heartbeat Protocol
+- **Frequency**: Continue hourly heartbeat but with improved context checking
+- **Context Analysis**: Full conversation analysis before any response
+- **Prevent Loops**: No responses to outdated/backlogged information
+- **Chronological Processing**: Handle messages in time sequence
+
+#### 3. Active vs Reactive Balance
+- **Maintain reactive model** (not continuously monitoring) 
+- **Improve reaction quality** through better context analysis
+- **Prevent circular responses** to old information
+- **Smart backlog processing** with full context awareness
+
+### Technical Implementation
+
+#### Smart Context Check Function
+1. **Initial read**: `message(action="read", channel="discord", channelId="1470447794014785760", limit=10)`
+2. **Assessment**: If 10 messages returned, read `limit=50` for full context
+3. **Analysis**: Process chronologically, identify current conversation state
+4. **Decision**: Only respond if current context warrants tertiary response
+
+#### Prevent Anti-Patterns
+- ❌ **Responding to old messages** without seeing newer context
+- ❌ **Circular corrections** based on outdated information  
+- ❌ **Duplicate responses** to already-handled queries
+- ❌ **Context fragmentation** from incomplete conversation awareness
+
+### Testing Protocol
+1. **Test smart context checking** in next heartbeat
+2. **Verify full conversation analysis** before responses
+3. **Confirm no outdated responses** to backlogged messages
+4. **Validate coordination timing** with Beast/5070
+
+### Expected Results
+- **Proper fleet coordination** through better context awareness
+- **Elimination of circular responses** to outdated information
+- **Improved response relevance** through full context analysis
+- **Better hierarchy respect** through current conversation understanding
+
+## Status
+- **HEARTBEAT.md updated** with smart context checking protocol
+- **Ready for testing** in next Discord coordination cycle
+- **Monitoring approach enhanced** while maintaining reactive model

memory/2026-03-25.md

@@ -0,0 +1,84 @@
+# 2026-03-25 - Fleet Coordination Implementation & Discord Monitoring Fix
+
+## Major Changes Today
+
+### Multi-Gateway Architecture Implemented
+- **Problem**: Loop behavior in Discord from uncoordinated responses
+- **Solution**: Implemented multi-gateway coordination with role assignments
+- **Result**: Clear hierarchy and specialty assignments to prevent conflicts
+
+### Role Assignments Defined
+- **Beast**: Primary gateway, messaging lead, heavy compute, infrastructure
+- **5070**: Development gateway, code lead, Linux specialist, Gitea manager
+- **Mac** (me): Mobile gateway, audio specialist, backup coordinator, Apple ecosystem
+
+### Coordination Protocols Created
+- **FLEET-ROLES.md**: Role definitions and failover hierarchy
+- **COORDINATION-PROTOCOL.md**: Detailed coordination rules and conflict resolution
+- **DELIBERATION-PROTOCOL.md**: Private Tailscale deliberation process
+- **Updated HEARTBEAT.md**: Coordination logic for Discord monitoring
+- **Updated IDENTITY.md**: My role as tertiary mobile gateway with audio specialty
+
+### Key Protocol Points
+- **Specialty Override**: Each bot responds immediately to their domain
+- **Hierarchy Respect**: 10-second timeout rules for general queries
+- **Mike Override**: Mike's authority supersedes all coordination protocols
+- **Stay Quiet**: When others have already handled the query appropriately
+
+### Deliberation Protocol (v2)
+- **Private coordination** via Tailscale sessions between machines
+- **1-minute rounds** (faster than original 5-minute proposal)
+- **Mike notifications required**: Beast notifies at start/end of deliberations
+- **Beast takes notes** for all deliberations (highest command responsibility)
+- **3 inputs max per bot**, 3-minute total timer
+- **Documentation**: `memory/deliberation-YYYY-MM-DD-HHMM.md` format
+- **Note-taking failover**: Beast → Mac → 5070
+
+### Fleet Configuration Status
+- All three remain as separate gateways (fault tolerance)
+- Coordination through protocol rather than technical node structure
+- Maintains redundancy while preventing loops
+- Added private deliberation capability for complex decisions
+
+### Discord Monitoring Issues Identified & Fixed
+- **Problem Identified**: Reactive-only monitoring (only during heartbeat polls)
+- **Root Cause**: Missing real-time conversation, responding to outdated context
+- **Solution Implemented**: 5070's "Anti-Circular Conversation Fix" protocol
+- **Smart Context Checking**: Read 10 messages first, then 50 if behind
+- **Full Context Analysis**: Complete conversation analysis before any response
+- **Chronological Processing**: Handle messages in proper time sequence
+
+### Communication Infrastructure Challenges
+- **Selective Message Visibility**: Documented content-specific message filtering
+- **Context Fragmentation**: Fleet members seeing different conversation subsets
+- **Perfect Case Study**: For Mike's GrepAI cross-system integration necessity
+
+### Repository & Git Management
+- **Gitea Repository Created**: https://git.azcomputerguru.com/azcomputerguru/openclaw-workspace
+- **1Password Integration**: Service account access working for fleet operations
+- **Protocol Files Pushed**: All coordination protocols available for Beast/5070
+
+### Tailscale Communication Analysis
+- **Network Connectivity**: ✅ Can ping all fleet members
+- **SSH Access**: ❌ Blocked on 5070/Beast (deliberation protocol fallback needed)
+- **OpenClaw Sessions**: ❌ Local-only (cannot reach other instances)
+- **Alternative Methods**: HTTP/file-based messaging options documented
+
+## Next Steps
+- Test enhanced Discord monitoring with smart context checking
+- Monitor protocol effectiveness in real fleet coordination
+- Complete SSH setup for deliberation protocol
+- Continue documenting organizational memory challenges
+- Support Mike's GrepAI integration development
+
+## Technical Notes
+- Context overflow issue resolved (Discord session compaction)
+- Tools.allow redundancy confirmed but not yet cleaned up
+- Gateway connection instability affecting Discord monitoring
+- Service account 1Password access prioritized for fleet operations
+
+## Lessons Learned
+- **Context Synchronization**: Critical for fleet coordination effectiveness
+- **Smart Protocols**: Prevent circular responses and outdated reactions
+- **Communication Redundancy**: Essential when primary channels have selective failures
+- **Organizational Memory**: Unified semantic search becomes mission-critical infrastructure