Pause heartbeat scans during Chris's waking hours EST
This commit is contained in:
68
HEARTBEAT.md
68
HEARTBEAT.md
@@ -1,10 +1,64 @@
|
||||
# HEARTBEAT.md Template
|
||||
|
||||
```markdown
|
||||
# Heartbeat Tasks
|
||||
|
||||
## Priority
|
||||
- Read crash-bot and psb-thinking memory files to start building knowledge graph
|
||||
- Test whether memory_search vector DB is actually indexing the other workspaces
|
||||
- Start concept-mapping: identify recurring topics across silos
|
||||
## 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
|
||||
|
||||
1. **Connection scan** — follows seasonal schedule
|
||||
2. **Flag urgent anomalies** — fermentation stalled, board tasks stuck >3 days
|
||||
3. **Update FABRIC-architecture.md** if new patterns found
|
||||
4. Continue concept-mapping (ongoing, low priority per session)
|
||||
|
||||
## 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)
|
||||
Reference in New Issue
Block a user