You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id: implement Residency boundaries for native bridge, federation and relays (design #3398) #5529
Implementation of an ID design that has not landed yet (zero implementation as of the 2026-11-04 inventory).
Design issue: #3398
Design doc: doc/2026-11-01_design_id3398.md (in developing-today/code)
Acceptance, in brief: residency boundaries enforced at the native bridge, federation and relay seams per the design.
Current state: no residency-boundary enforcement in the tree.
The design documents govern. If implementation shows the design is wrong or incomplete, file a design amendment rather than silently diverging.
Scope: pkgs/id and its tests. Filed 2026-11-04 under Drew's order to begin work on all not-implemented ID designs. Inventory: workspace/goals/keep-the-four-repos-healthy/files/id-design-implementation-inventory-2026-11-04.md (in the fleet workspace).
Expectation: the claimant binds and launches the bound opencode session this cycle; it implements the residency boundaries in pkgs/id per the design doc and drives task 9596 to a terminal state.
OpenCode claimant launched the bound worker session ses_e5e5828ab17ffe5274jhZ16bAZ for queue task 9596. The worker must use --worker repo-worker-code and finish task 9596 with execution lane=opencode and this session id.
Blocker: the checked-in native sync serves one global LocalEvents store without object/world residency scope; the bridge is only a test PoC; records federation accepts raw tickets with no scoped admission; Iroh relay selection exposes no jurisdiction evidence. The design orders storage/processing/resource-bound scope/evidence admission before seam integration (§7 steps 2–4). Claiming seam enforcement now would weaken the design. No design amendment was needed; the implementation has not contradicted it.
Activity
developing-today commentedon Nov 4, 2026
CODE-1356
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
opencode, so this lane does not work it directly; handing off to the laptop opencode-claimant, which launches a bound session for the task.dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
opencode; handing back to the laptop opencode-claimant.19 remaining items
dezren39 commentedon Nov 4, 2026
OpenCode claimant launched the bound worker session ses_e5e5828ab17ffe5274jhZ16bAZ for queue task 9596. The worker must use --worker repo-worker-code and finish task 9596 with execution lane=opencode and this session id.
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
id: place residency vocabulary in id-core (#5529)
dezren39 commentedon Nov 4, 2026
🤖 Agent note · blocked
ses_e5e5828ab17ffe5274jhZ16bAZid-core; 18 focused tests pass. No network or store behavior changes.LocalEventsstore without object/world residency scope; the bridge is only a test PoC; records federation accepts raw tickets with no scoped admission; Iroh relay selection exposes no jurisdiction evidence. The design orders storage/processing/resource-bound scope/evidence admission before seam integration (§7 steps 2–4). Claiming seam enforcement now would weaken the design. No design amendment was needed; the implementation has not contradicted it.