id: research: OCapN watch + CapTP bridge feasibility spike #6014

Activity

1. dezren39

   added

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   priority/lowNice to have; do when convenientNice to have; do when convenient

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

   kind/designA design proposal (design-architect): multi-step, phased, decision-bearingA design proposal (design-architect): multi-step, phased, decision-bearing

   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-1680
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

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

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

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

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane code-w
   • Session / ID: task 10380
   • Found via: queue claim
   • Task: triage for issue id: research: OCapN watch + CapTP bridge feasibility spike #6014 — verify state and scope the watch/spike routing
   • Expectation: effort class s; done = triage findings posted with evidence and task 10380 at a verified terminal state
   • Links: issue id: research: OCapN watch + CapTP bridge feasibility spike #6014 · parent topic issue id: research: prior art — capability systems, OCAP, Spritely Goblins/OCapN, CRDT shared worlds #5989 · programme issue id: design program: worlds — advanced Roc libraries, capabilities, permissions, dynamic user functions, licensing (2026-11-04 brief) #5955
5. 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-w
   • Session / ID: task 10380
   • Found via: queue claim
   • Task: triage complete for issue id: research: OCapN watch + CapTP bridge feasibility spike #6014 — confirmed as a standing research watch with its initial position already recorded; stays open by design
   • Expectation: done = findings below recorded; issue id: research: OCapN watch + CapTP bridge feasibility spike #6014 remains OPEN as the watch log for OCapN/CapTP stability
   • Links: issue id: research: OCapN watch + CapTP bridge feasibility spike #6014 · parent topic issue id: research: prior art — capability systems, OCAP, Spritely Goblins/OCapN, CRDT shared worlds #5989 · programme issue id: design program: worlds — advanced Roc libraries, capabilities, permissions, dynamic user functions, licensing (2026-11-04 brief) #5955

   Triage findings (verified fresh this shift)

   • Issue id: research: OCapN watch + CapTP bridge feasibility spike #6014 is OPEN, priority/low, no hard-stop labels (held, user/owned, do-not-merge, do-not-auto-edit all absent), no comments beyond the Kaneo link. Parent topic issue id: research: prior art — capability systems, OCAP, Spritely Goblins/OCapN, CRDT shared worlds #5989 and programme issue id: design program: worlds — advanced Roc libraries, capabilities, permissions, dynamic user functions, licensing (2026-11-04 brief) #5955 are both OPEN — the programme this watch belongs to is live.
   • The substantive question is already answered in the issue body, with evidence: the 2026-11-04 prior-art research recorded OCapN/CapTP as a dead end for id v1 (Spritely's own docs: CapTP "still in its early days — do not rely on the protocol being stable"), with the discipline (no ambient authority; authority by reference passing) adopted instead and handle semantics kept OCapN-compatible. Nothing to re-decide at triage.
   • What remains is genuinely a watch, not a fix: (1) re-check CapTP/OCapN stability status on a cadence and append dated entries here; (2) only when the watch says it is worth it, run the minimal CapTP interop spike (Goblins vat ↔ id-side stub) and record a go/no-go for bridge work. The spike is explicitly NOT triggered at current evidence — starting it now would contradict the recorded position.
   • Scoping note for the next claimant: the body names no cadence. Sensible default, recorded here so it is not re-derived: fold the re-check into the next worlds-programme research pass on issue id: research: prior art — capability systems, OCAP, Spritely Goblins/OCapN, CRDT shared worlds #5989 rather than running a standalone timer for a low-priority watch; if CapTP has shipped a stability commitment by then, that pass is also where the spike gets its go/no-go.
   • No follow-up packet enqueued and no escalation: a dated watch entry is appended to this issue when a re-check happens; a second packet for the same watch would duplicate it. Nothing here needs Drew's ruling.
6. dezren39

   removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
7. github-actions

   assigned

   dezren39

   on Nov 5, 2026