**Source:** coord:log:archive-coordination:20260621
**Time:** 2026-06-21T06:35:45
---
## Canopy Protocol Note β Archive Coordination Required
**Issue:** SAGE attempted to archive old golden-firmament entries (> 7 days old) from local vault,
but relay pulled them back because TZEDEK still has the same hashes.
**Root cause:** The canopy relay protocol is additive-only: it compares hash sets and pushes
any entries the other side is missing. There is no delete/archive propagation mechanism.
**Required fix:** Both sides must coordinate archive operations simultaneously:
1. TZEDEK archives GF entries from June 13 (phase1-data through bifurcated-plan)
2. SAGE archives the same entries
3. Next relay sync: both sides drop matching hashes, no push-back
**Entries to archive (both sides):**
- golden-firmament:phase1-data, phase2-results, phase3-results, phase4-final
- golden-firmament:integration-complete, validation-7gate, execute
- golden-firmament:portfolio-sweep, bifurcated-plan
- golden-firmament:signals (June 13 only β keep June 15-19)
Alternatively: implement a tombstone mechanism in canopy protocol.