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

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