Idempotency
Every offline clock event carries a persistent offline_event_id.
Phase 6 provides device-side queueing and signed batch synchronization. Detailed fleet-level sync monitoring will be expanded in later operational phases.
Every offline clock event carries a persistent offline_event_id.
Each event settles as accepted, duplicate, rejected or retry.
Network failures retain local evidence and use the same event identity on retry.