Funday Archive Vault
Lifecycle: PUBLISHED KEEP / HISTORICAL archive — these records are intentionally published and may appear in Quartz search. They are evidence and context, not current operational SSOT.
Start with current documentation
Use the live domain spine before consulting historical material:
Preserved historical compilations
These large 2026-06-25 compilations are intentional KEEP artifacts. They preserve distinct snapshots and are not duplicate-deletion candidates.
| Collection | Historical scope |
|---|---|
| Architecture | Architecture, infrastructure, and integration records |
| Bug history | Incident, defect, and remediation history |
| Checklists | Completed and superseded operational checklists |
| Handovers | Session and agent handoff records |
| Plans | Historical implementation and cleanup plans |
| Other | Remaining preserved source material |
Curated historical categories
- Architecture snapshots
- Bug-history case files
- Game records
- Archived Ompcord project research
- Reference snapshots
- Archived report assets (
reports/*.yaml) - Archive provenance
- Wall of Fame
- Hermes report — 2026-07-04
Reading and maintenance rules
- Treat dates, commands, paths, architecture, and status claims as historical unless a current spine page independently confirms them.
- Keep contradictory snapshots when they document different periods; add a current canonical pointer rather than erasing evidence.
- Never hand-edit generated Quartz output.
- Validate content locally with the repository link audit or a non-publishing Quartz build. Use the Frontend Deployment runbook only when production publication is actually required.