id: design: multi-device sync cluster (knowledge layer) (from #5678) #5838

Activity

1. dezren39

   added

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1521
3. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code), lane code-i
   • Session / ID: task 10241
   • Found via: queue claim
   • Task: Triage of issue id: design: multi-device sync cluster (knowledge layer) (from #5678) #5838 — complete. Design ticket; ordering and reconciliation targets recorded below. No implementation follow-up enqueued (the design itself is the work, gated on the parent programme).
   • Expectation: design proceeds after parent issue id: design: Knowledge layer feature program — competitor feature matrix, import/export, read-authority #5678 produces its feature matrix; see below.
   • Links: issue id: design: multi-device sync cluster (knowledge layer) (from #5678) #5838 · parent issue id: design: Knowledge layer feature program — competitor feature matrix, import/export, read-authority #5678 · epic issue epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056

   Triage findings (2026-11-05, verified against current state):

   • Parent state: issue id: design: Knowledge layer feature program — competitor feature matrix, import/export, read-authority #5678 is OPEN and still queued — it is a design-to-make-designs programme whose deliverable (the competitor feature matrix over the id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048 zettelkasten layer) does not exist yet. This ticket's cluster design is one of its named outputs, so the matrix is this design's input; the design cannot settle its shape before the matrix exists without re-deciding the parent, which the ticket forbids. Implementation timing is, per the ticket, a separate decision possibly months out.
   • Reconciliation targets (sync substrate already in tree): ID's own sync is real code, not a blank page — pkgs/id/src/event_sync.rs (event sync over its own ALPN, split from log_sync's /id-sync/1), plus the partial-replication design ticket issue id: design: partial replication protocol (from #5672) #5800 in this same programme family. The knowledge-layer sync design must link/reuse those, as the ticket requires ("reconciled with ID's own sync designs, linked not duplicated") — in particular the local-first/offline questions overlap issue id: design: partial replication protocol (from #5672) #5800's replication protocol, and the two designs should not fork each other's answers.
   • Related in-flight work to cite, not duplicate: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 (generic event-body persistence + range-sync, in progress) and issue pkgs/id crate split — step 3: extract id-sync (log_sync + wire layer; artifact lands here) #4406 (id-sync crate extraction, in progress) change the substrate this design will sit on; the decision record should name the substrate state it assumes.
   • Next action: when issue id: design: Knowledge layer feature program — competitor feature matrix, import/export, read-authority #5678's matrix lands, work this ticket as a design task producing the decision record (local-first vs cloud-first, conflict resolution, offline editing, E2E expectations, attachment/media sync) with explicit links to issue id: design: partial replication protocol (from #5672) #5800 and the event-sync substrate. No code task should be filed from it before that record exists.
5. dezren39

   added

   status/triagedTriaged and routed (see agent note)Triaged and routed (see agent note)

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 5, 2026
6. github-actions

   assigned

   dezren39

   on Nov 5, 2026