Scott Reimers
1df00eebf8
Design doc: Protocol v4 spec — header-driven sync, tiered engagement, multi-upstream
New section documenting the planned v0.4.0 protocol revision:
- ManifestPush as primary post notification (CDN tree = notification system)
- Slim PullSyncRequest: per-author timestamps replace full post ID lists
- Self Last Encounter: per-author sync tracking (implements v0.2.0 design intent)
- Tiered engagement checks: 5min (<72h) / 1hr (3-14d) / 4hr (14-30d) / 24hr (>30d)
- Multi-upstream: 3 max per post with fallback chain and BlobDeleteNotice unregistration
- Auto-prefetch followed authors <90d from header discovery
- Encrypted-but-not-for-us CDN caching with natural decay
- Serial engagement polling (one peer, authoritative response)
- Header-driven post discovery flow (7 steps)
- Migration path: backward-compatible via ALPN, v3 fallback for mixed networks
- DB schema additions: last_engagement_ms, last_check_ms, last_sync_ms
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>