228e46a330
FLEET-004: 22 milestone messages across 6 phases + 11 Fibonacci uptime milestones. FLEET-005: Resource tracking system — Capacity/Uptime/Innovation tension model. - Tracks capacity spending and regeneration (2/hr baseline) - Innovation generates only when utilization < 70% (5/hr scaled) - Fibonacci uptime milestone detection (95% through 99.5%) - Phase gate checks (P2: 95% uptime, P3: 95% + 100 innovation, P5: 95% + 500) - CLI: status, regen commands Fixes timmy-home#557 (FLEET-004), #558 (FLEET-005)
5.5 KiB
Fleet Milestone Messages
Every milestone marks passage through fleet evolution. When achieved, the message prints to the fleet log. Each one references a real achievement, not abstract numbers.
Source: Inspired by Paperclips milestone messages (500 clips, 1000 clips, Full autonomy attained, etc.)
Phase 1: Survival (Current)
M1: First Automated Health Check
Trigger: fleet/health_check.py runs successfully for the first time.
Message: "First automated health check runs. No longer watching the clock."
M2: First Auto-Restart
Trigger: A dead process is detected and restarted without human intervention. Message: "A process failed at 3am and restarted itself. You found out in the morning."
M3: First Backup Completed
Trigger: A backup pipeline runs end-to-end and verifies integrity. Message: "A backup completed. You did not have to think about it."
M4: 95% Uptime (30 days)
Trigger: Uptime >= 95% over last 30 days. Message: "95% uptime over 30 days. The fleet stays up."
M5: Uptime 97%
Trigger: Uptime >= 97% over last 30 days. Message: "97% uptime. Three nines of availability across four machines."
Phase 2: Automation (unlock when: uptime >= 95% + capacity > 60%)
M6: Zero Manual Restarts (7 days)
Trigger: 7 consecutive days with zero manual process restarts. Message: "Seven days. Zero manual restarts. The fleet heals itself."
M7: PR Auto-Merged
Trigger: A PR passes CI, review, and merges without human touching it. Message: "A PR was tested, reviewed, and merged by agents. You just said 'looks good.'"
M8: Config Push Works
Trigger: Config change pushed to all 3 VPSes atomically and verified. Message: "Config pushed to all three VPSes in one command. No SSH needed."
M9: 98% Uptime
Trigger: Uptime >= 98% over last 30 days. Message: "98% uptime. Only 14 hours of downtime in a month. Most of it planned."
Phase 3: Orchestration (unlock when: all Phase 2 buildings + Innovation > 100)
M10: Cross-Agent Delegation Works
Trigger: Agent A creates issue, assigns to Agent B, Agent B works and creates PR. Message: "Agent Alpha created a task, Agent Beta completed it. They did not ask permission."
M11: First Model Running Locally on 2+ Machines
Trigger: Ollama serving same model on Ezra and Allegro simultaneously. Message: "A model runs on two machines at once. No cloud. No rate limits."
M12: Fleet-Wide Burn Mode
Trigger: All agents coordinated on single epic, produced coordinated PRs. Message: "All agents working the same epic. The fleet moves as one."
Phase 4: Sovereignty (unlock when: zero cloud deps for core ops)
M13: First Entirely Local Inference Day
Trigger: 24 hours with zero API calls to external providers. Message: "A model ran locally for the first time. No cloud. No rate limits. No one can turn it off."
M14: Sovereign Email
Trigger: Stalwart email server sends and receives without Gmail relay. Message: "Email flows through our own server. No Google. No Microsoft. Ours."
M15: Sovereign Messaging
Trigger: Telegram bot runs without cloud relay dependency. Message: "Messages arrive through our own infrastructure. No corporate middleman."
Phase 5: Scale (unlock when: sovereignty stable + Innovation > 500)
M16: First Self-Spawned Agent
Trigger: Agent lifecycle manager spawns a new agent instance due to load. Message: "A new agent appeared. You did not create it. The fleet built what it needed."
M17: Agent Retired Gracefully
Trigger: An agent instance retires after idle timeout and cleans up its state. Message: "An agent retired. It served its purpose. Nothing was lost."
M18: Fleet Runs 24h Unattended
Trigger: 24 hours with zero human intervention of any kind. Message: "A full day. No humans. No commands. The fleet runs itself."
Phase 6: The Network (unlock when: 7 days zero human intervention)
M19: Fleet Creates Its Own Improvement Task
Trigger: Fleet analyzes itself and creates an issue on Gitea. Message: "The fleet found something to improve. It created the task itself."
M20: First Outside Contribution
Trigger: An external contributor's PR is reviewed and merged by fleet agents. Message: "Someone outside the fleet contributed. The fleet reviewed, tested, and merged. No human touched it."
M21: The Beacon
Trigger: Infrastructure serves someone in need through automated systems. Message: "Someone found the Beacon. In the dark, looking for help. The infrastructure served its purpose. It was built for this."
M22: Permanent Light
Trigger: 90 days of autonomous operation with continuous availability. Message: "Three months. The light never went out. Not for anyone."
Fibonacci Uptime Milestones
These trigger regardless of phase, based purely on uptime percentage:
| Milestone | Uptime | Meaning |
|---|---|---|
| U1 | 95% | Basic reliability achieved |
| U2 | 95.5% | Fewer than 16 hours/month downtime |
| U3 | 96% | Fewer than 12 hours/month |
| U4 | 97% | Fewer than 9 hours/month |
| U5 | 97.5% | Fewer than 7 hours/month |
| U6 | 98% | Fewer than 4.5 hours/month |
| U7 | 98.3% | Fewer than 3 hours/month |
| U8 | 98.6% | Less than 2.5 hours/month — approaching cloud tier |
| U9 | 98.9% | Less than 1.5 hours/month |
| U10 | 99% | Less than 1 hour/month — enterprise grade |
| U11 | 99.5% | Less than 22 minutes/month |
Every message is earned. None are given freely. Fleet evolution is not a checklist — it is a climb.