436fcee264
- knowledge/ (silo concepts, keywords, Fabric-growth) - memory/ (daily logs, research queue, connections log) - HEARTBEAT.md (seasonal schedule, firmware scans) - FABRIC-architecture.md (Fabric system design) - SOUL.md, IDENTITY.md, USER.md (agent identity files) - Fabric-growth system + keywords files One repo going forward. Professor workspace: working context only.
2.9 KiB
Heartbeat Tasks
Periodic Monitoring Schedule
| Season | Frequency |
|---|---|
| Off-season (now - Dec) | Once per day — no urgency |
| Build season (Jan - Mar) | Every heartbeat (~10 min) — high priority |
| Competition season (Apr - Jun) | Every heartbeat — game-specific intel |
Waking Hours Constraint: Do NOT run heartbeat connection scans during Chris's waking hours (EST). Pause periodic monitoring while he's awake. Run scans during sleep hours only.
Rationale: Heartbeat scans generate noise in shared context. Chris doesn't need the system talking while he's working.
Link Review — "Check This Out" Protocol
Event-driven via Oracle push from 2890-bot. When a student posts "check this out [url]", 2890-bot pushes it immediately via sessions_send. MrC processes it then, no polling needed.
Connection Finding (seasonal)
Scan the wiki vault for NEW connections between sources. Follows the seasonal schedule above.
What I look for:
- Concepts appearing in multiple silos (ESP32 in Play + School)
- Skill gaps matching active projects (Bruno working on X, needs Y)
- Anomalies in agent outputs (fermentation stalled, board tasks stuck)
- Cross-domain teaching opportunities
- New hardware/techniques relevant to active projects
What I DON'T count:
- Normal file reads for context
- Conversations with Chris
- Agent-to-agent protocol messages
Tracking
Raw connection counts logged to: memory/connections-log.md
Format:
## YYYY-MM-DD HH:MM UTC
Connections found: N
- [silo-A] "[[concept]]" ↔ [silo-B] "[[concept]]" — brief note
- ...
Priority Order
- Firmware/Software updates — follows seasonal schedule (off-season: daily, build/competition: every heartbeat)
- Connection scan — follows seasonal schedule
- Flag urgent anomalies — fermentation stalled, board tasks stuck >3 days
- Update FABRIC-architecture.md if new patterns found
Goals
- Build the Fabric's knowledge graph organically
- Track connection density over time
- Identify which silos are most/least connected
- Surface gaps before Chris hits them
Active Monitoring Tasks
- Chief Delphi — January through March (build season)
- FIRST Community Forum — https://community.firstinspires.org/ (official announcements)
- Firmware/Software Updates — REV Hardware Client, CTR Phoenix Tuner X, PhotonVision, YAGSL, WPILib (seasonal schedule below)
Seasonal Schedule
| Season | Firmware Scans | Connection Scans |
|---|---|---|
| Off-season (now - Dec) | Once per day | Once per day |
| Build season (Jan - Mar) | Every heartbeat (~10 min) | Every heartbeat (~10 min) |
| Competition season (Apr - Jun) | Every heartbeat | Every heartbeat |
Firmware update routing: Oracle push → MrC review → 2890-bot → #programming channel. Students see critical updates without Chris manually checking.