Sync

Sync — One Navi. All the screens. (The Sync Update, v0.3.0e Build 1)

The badge round above is the deliberate ceremony; Sync is the everyday gesture it grew into. Sync sits in the menu's Apex | Utilities group. It opens no page: one tap pops a small card and runs the whole round — pull, converge, push — so a conversation started at the desk is waiting on the phone over DHD, and the other way around. The card says only the essentials: the state (Syncing…, Synced, Can't reach — held, Needs your eyes), what moved, the route actually used — the Mesh whenever a paired machine's road is lit (named on the card, Mesh — ), the backup repo otherwise — and at most one action, Retry. A success lingers five seconds and dismisses itself; a held or Needs your eyes card stays until you deal with it. Pulls also happen on their own: at app start, when a DHD session starts, when a window opens (the seat notes itself to the bridge, which refreshes the room for it — the desk was the one seat that never announced itself before this build), and on Mesh contact. Publishing stays the button's act. There is no polling daemon.

What rides is the whole living her, anchored to your GitHub account — the set's manifest names the account, and a set from a different account is refused by name at the door, on both transports, before anything is applied: different accounts are different people's work. The set: the chat store; Case Files whole; the ChipDeck as one unit — chips with their install record, RAG packs with theirs, and the cards that tie machines together (your own pairing card and one per paired peer, re-drawn fresh each round, and a gateway card for every fedinet you keep; a gateway card landing on a machine that doesn't keep that fedinet yet admits it — admission and introduction only, never trust); your operator picture and badge; her memory entries; and her Soul and her memory book. The Operator Badge keeps its crown jobs — recovery root, the acts that need the ceremony — but it is not the sync key anymore; the account is. Settings stay with the badge backup, as ever.

Convergence is the badge round's, widened: per chat, the newest copy wins; a pair that genuinely diverged parks both copies — the later one as a dated sibling — and only then does the card say Needs your eyes, naming the chat or case. Her two documents converge per document and are never silently overwritten: a side untouched since the last sync takes the other side's text; both changed, the newer text wins and the losing text is parked beside the document as a named .from-sync- conflict copy for your eyes. Memory entries union — they are append-shaped, and nothing un-remembers. Your picture and badge are single values: the latest change wins. Deletions travel as tombstones: delete a chat, a case, or a note on one machine and the deletion itself syncs, so the other machine's older copy cannot resurrect it — while a copy genuinely edited after the deletion counts as newer work and survives. One exception is absolute: the main chat cannot be deleted — not from the Chats tab, not through sync; /clear or /cls empties it. The one law that does not bend: backups already taken are snapshots and are never reached into — a tombstone governs live machines, not history. Failures are named in the usual discipline: offline is held and retried at the next trigger, a spent rate limit is named with its wait, a refused credential is named as auth, a foreign account is named as the account it belongs to.