🗺️ The Continuity Plan (Context Preservation)
Objective: Ensure that future Agent sessions (or a replacement Agent) can immediately understand the network state, access protocols, and current objectives without relying on lost chat history.
1. The "Golden Source" (Codex)
We must treat the Federation Codex (MkDocs) as the single source of truth, not the chat window.
- Action: Every major decision, architecture change, or credential convention must be documented in
docs/and published immediately. - New File:
docs/codex/continuity_handbook.md. This file will serve as the "Read Me First" for any new Agent.
2. The "Context Injection" Protocol
To prevent "amnesia," every new session should start with a specific prompt that forces the Agent to ingest the Golden Source.
- The Prompt:
> "You are the Federation Systems Administrator. Please initialize by reading
docs/codex/continuity_handbook.md,SUMMARY.md, anddocs/SERVER_ACCESS_GUIDE.md. Report your understanding of the current fleet status and active projects."
3. Automated State Snapshots
We will create a script that generates a "State of the Union" report.
- Script:
tools/generate_context_report.py. - Function:
- Scans active Docker containers across the fleet (via SSH).
- Checks disk usage and mount points.
- Lists active systemd services.
- Outputs to
docs/logs/current_state.md.
- Benefit: The Agent doesn't need to "remember" what is running; it just reads the latest report.
⚖️ Pros & Cons
| Pros | Cons | |
|---|---|---|
| Codex Reliance | Persistent Knowledge. Docs survive session crashes. | Requires discipline to update docs before acting. |
| Injection Prompt | Fast Start. Agent gets up to speed in seconds. | Relies on the user to paste the prompt correctly. |
| Auto-Reporting | Truth vs. Memory. The Agent sees reality, not just what it "thinks" happened. | Requires SSH access setup (which we have). |
🛠️ Immediate Action: Create the Handbook
I will create docs/codex/continuity_handbook.md now. This document will contain the "Keys to the Kingdom":
1. Network Map (IPs & Hostnames).
2. Credential Logic (Where keys are, what default users are).
3. Standard Operating Procedures (How to deploy, how to backup).
4. Critical "Gotchas" (e.g., "Do not reboot Memory Alpha automatically").