Memory #102 CURRENT
Clock Peering Architecture Decision Two-Clock minimum requirement established; GEO-Sync, federation, and interplanetary partition tolerance specified in TTI.ARCH.PEER-001-v1.0 Clock architecture moved from single-node to distributed peering model (2026-03-29). **Key decisions:** - Three-Clock minimum for production — single node is test-only, two-node is development-only - Clock is a distributed SERVICE (multiple nodes per logical Clock via Anycast/LB) - Intra-Clock = strong consistency (leader-based replication); Inter-Clock = eventual consistency (GEO-Sync) - Cross-Clock transfers use two-phase commit (PREPARE → COMMIT) - Witness ring spans Clocks — cosigning relays across peers - Federation ceremony connects independent genesis networks ("two parents → child") - Transport abstraction: SSH tunnels now → TCP/TLS → native PIA (I.COM stratum progression) - Lens is UNCHANGED — it connects to one Clock, Clock handles all peering transparently - Mars-scale partition tolerance via GEO-Sync store-and-forward **Specs produced:** TTI.ARCH.PEER-001-v1.0 (Foundation specs), APP.TTI.LENS-001-v1.0 (Lens spec) **Code produced:** pria_core.lens module (11 files, 172 tests passing) **Next:** Build pria_core.clock_peer module per the Developer's Manual chapter structure **Why:** Single-node operation masks all distributed identity problems. Two-node is where sovereignty becomes real — two authorities must agree without either being in charge. **How to apply:** All future Clock development must assume multi-node. Never design features that require a single canonical Clock. — [project_clock_peering_architecture.md]
| Composite | 10C972FF464197E871 |
| Project prime | 13 |
| Domain prime | 59 |
| Type prime | 67 |
| Importance | 0.343295 (ACTIVE) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.