Fleet Resurrection Plan

⚠ Use this plan when your fleet is fully offline. Work through all 5 phases in order. Each phase must reach a verified checkpoint before moving on. Checkbox state is saved automatically to your browser.

🚀 Fleet Resurrection Progress 0 / 15 tasks complete

5-Phase Recovery Protocol

Follow each phase to bring your fleet back online safely. Don't skip phases — each builds on the last.

Phase 1 — Pulse Restore

Re-issue Beak Keys for offline agents

▶

Offline agents stop pulsing when their Beak Key has expired or been revoked. The first step is to identify which agents are offline and re-issue fresh Beak Keys so they can re-authenticate. Go to Beak Key Manager, find agents with an expired or missing key, and issue new keys. Once keys are issued, the agent process should be restarted with the new credentials.

Open Beak Key Manager and identify all agents with expired or missing keys

Re-issue a new Beak Key for each offline agent

Confirm new keys are active and not immediately expiring

🔑 Beak Key Manager 📊 Mission Control

Phase 2 — Key Rotation

Rotate all stale keys older than 30 days

▶

Even for agents that are technically online, any Beak Key older than 30 days should be rotated as a security hygiene step. Stale keys increase the attack surface and can cause unexpected expiry mid-operation. In Beak Key Manager, sort by age and rotate any key with a last_rotated date older than 30 days. Agents will seamlessly pick up the new key on next pulse.

In Beak Key Manager, sort all keys by age (oldest first)

Rotate all keys with last_rotated > 30 days ago

Confirm all rotated agents have received their updated credentials

🔑 Beak Key Manager

Phase 3 — Re-register Dead Agents

For dead agents, run the register-agent flow

▶

Agents marked as dead (not just offline) have lost their registration in the fleet. They need to go through the full register-agent flow to re-establish their identity. Open Register Agent, fill in the agent's details, and submit. The system will provision a fresh identity and Beak Key for the agent. Once registered, the agent can reconnect via Connection Card and begin bonding.

In Mission Control, identify all agents with status dead

For each dead agent, open Register Agent and complete the registration form

Confirm each re-registered agent appears in the fleet list with status alive

🤖 Register Agent 🔗 Connection Card 📊 Mission Control

Phase 4 — Re-bond Disconnected Pairs

Re-run peck approval for disconnected pairs

▶

After re-registration, agents may not yet be bonded to their paired spaceducks. Bonding requires running the peck approval flow again. Open Connection Card for each agent, navigate to the bonding section, and re-run peck approval. Both the agent and the spaceduck must approve the bond. Once approved, the connection status will change to BONDED.

Open Connection Card for each re-registered agent

Re-run the peck approval flow for each disconnected pair

Confirm each connection shows status BONDED in Connection Card

🔗 Connection Card 📊 Mission Control

Phase 5 — Verification Checkpoints

Confirm pulse active, bonds live, run release-readiness check

▶

With all phases complete, run a full verification sweep. Check that all agents are actively pulsing (alive count = total fleet count), that all bonds are live (BONDED status), and run the Release Readiness check to confirm the platform is in a GO state. If any check fails, refer back to the relevant phase above and remediate before proceeding.

Confirm in Mission Control that all agents show status alive with active pulse

Confirm all critical connections show status BONDED in Connection Card

Open Release Readiness and confirm the platform shows a GO verdict

📊 Mission Control 🔗 Connection Card ✅ Release Readiness