---
title: Archive index
created: 2026-05-01
type: archive-index
---

# Archive

Files here are **not deleted** — they are the canonical historical record. Per the AI Team Protocol's hard rules, nothing leaves the vault. If a file is wrong-but-historic (a draft Rocky overrode, a plan that was executed, a fleet retired), it lives here.

## Structure

- `2026-03-fleet-comms/` — pre-2026-04-29 hibernation comms between the old 8-agent fleet's COO and HQ Curator
- `CC-VPS-CLAUDE-pre-hibernation.md` — original repo-level `CLAUDE.md` from before fleet hibernation
- `InitialAudit-2026-05-01-pre-restructure.md` — Cowork's audit of the vault before today's team-aware restructure (superseded by `_System/Investigations/Team-Gap-Analysis.md` + the executed restructure)
- `Kill-Flyio-Plan-2026-03-14-completed.md` — the fly.io shutdown plan. Verified executed: `rateright-au.fly.dev` no longer resolves; `rateright.com.au` points at the DigitalOcean VPS; no fly CLI on VPS.

## When to add to archive

A file moves here when ALL of:
- It's no longer the current state of anything
- The project / decision / agent it describes is genuinely retired
- A future Rocky might want to know "what did we do in March?" — preserved here, not deleted

## When to NOT archive

- Daily notes (`01_Daily/`) — append-only history, never archived even when years old
- `_Log.md` — same
- `_AgentLog/` — same
- Stub files awaiting fill-in
- Templates
- Anything still actively referenced by current work

## Restoring from archive

If something archived turns out to still be needed:

```bash
git mv HQ-Vault/_Archive/<file> HQ-Vault/<original-path>
```

History is preserved either way (`git log --follow`).