id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882

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

   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 10284
   • Found via: queue claim
   • Task: triage for issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 — verify state against parent issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 and its framework triage, and route accordingly
   • Expectation: effort class s; done = triage findings posted with evidence and task 10284 at a verified terminal state
   • Links: issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 · parent issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 · epic issue epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056
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 10284
   • Found via: queue claim
   • Task: triage complete for issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 — confirmed, correctly scoped against the parent framework; the design work itself stays on this issue
   • Expectation: done = findings below recorded; issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 remains OPEN as the design ticket
   • Links: issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 · parent issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 · predecessor issue id: design: residency boundaries for native bridge, federation and relays #3398

   Triage findings (verified fresh this shift)

   • Issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 is OPEN, no hard-stop labels (held, user/owned, do-not-merge, do-not-auto-edit all absent), no comments beyond the Kaneo link, and no decision record posted yet — the design has not been done or duplicated elsewhere.
   • Parent issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 is OPEN and was triaged earlier today (task 10116, lane code-k): the framework is Drew-ruled opt-in and framework-first, its predecessor surface designs (issue id: design: jurisdiction-aware per-user store routing (signup jurisdiction field, DO/blob/directory pinning) #2283, issue id: design: jurisdiction-partitioned hosted worlds and world blobs #3397, issue id: design: residency boundaries for native bridge, federation and relays #3398) are CLOSED, all decomposition children are OPEN, the remaining parent work is the framework synthesis document (opt-in only, default off), and the set is low priority. Issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 inherits that posture: nothing in it is urgent, and its design must stay inside the parent's opt-in/default-off ruling.
   • Feed relation checked: the issue body says this design "feeds id: design: residency boundaries for native bridge, federation and relays #3398" — issue id: design: residency boundaries for native bridge, federation and relays #3398 (residency boundaries for bridge/federation/relays) is CLOSED as a predecessor surface design (per the task 10116 triage), so read that relation as lineage, not a live dependency: issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 is the framework-level successor for the same surface (peer-asserted evidence and transit rules where boundaries meet bridges, federation, and relays), and its decision record should cite issue id: design: residency boundaries for native bridge, federation and relays #3398's outcome rather than reopen it.
   • Scope check: well-formed design ticket — the question is enumerated, the parent decisions it must not silently re-decide are named, and the expected deliverable is a recorded decision (chosen shape, alternatives rejected and why, invariants for implementation) on this issue or in a linked doc/ record. No packet defect.
   • No follow-up packet enqueued: the design work IS this issue and will be claimed as its own work item. Per the issue body, implementation timing is a separate programme decision (possibly months out) — a prioritisation note, not a blocker, and nothing here needs Drew's ruling beyond the opt-in ruling already recorded on issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683.
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
8. developing-today commented on Nov 8, 2026

   

   developing-todayBot

   on Nov 8, 2026 – with developing.today

   Contributor

   More actions

   🤖 Agent note · handed off

   • Agent: queue worker (repo-worker-code), lane code-p
   • Session / ID: task 12368
   • Found via: queue claim
   • Task: triage for issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882. Execution lane assigned opencode per §1b — handing off to the laptop opencode claimant; this worker does not work the task directly.
   • Expectation: done = task 12368 acceptance met for issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 by the claimant session.
   • Links: issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882; task 12368 parked 1200s for the claimant window.
9. 67 remaining items

   Load more
10. dezren39

    added

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

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

    status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

    queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

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

    on Nov 9, 2026
11. dezren39 commented on Nov 9, 2026

    

    dezren39

    on Nov 9, 2026

    MemberAuthor

    More actions

    Triage verdict: validated — but the design deliverable already landed; closing as superseded

    • Fresh check (2026-11-09T12:43:13Z): issue OPEN, no hard-stop labels (held, user/owned, do-not-merge, do-not-auto-edit absent).
    • What this ticket asks for: settle "peer-asserted evidence and transit rules where boundaries meet bridges, federation, and relays", and close with the chosen shape, rejected alternatives and implementation invariants.
    • That decision record is merged. id: design: residency boundaries for native bridge, federation and relays #3398 (CLOSED 2026-11-02, COMPLETED) → PR design(id): #3398 residency boundaries #3856 (MERGED 2026-11-02T15:49:37Z) → doc/2026-11-01_design_id3398.md:
      • peer assertions are not evidence: "A peer's own location statement is not evidence" (the decision, lines 11–25) plus the scope/evidence rules (lines 66–93);
      • transit at bridge / federation / relay: the transport plane (line 63) and the §3 path rows for native sync, native↔hosted bridge, federation and relay, each with its required negative test (lines 97–112);
      • chosen shape vs rejected alternatives and invariants: §4 (lines 114–121), §5 (lines 123–153);
      • implementation acceptance criteria and the phased plan: §6–§7 (lines 159–221).
    • Why the duplicate exists: id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 was filed 2026-11-04 by the WS-F gap pass as a follow-on to design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 and says it "feeds id: design: residency boundaries for native bridge, federation and relays #3398" — but id: design: residency boundaries for native bridge, federation and relays #3398's design had already merged on 2026-11-02. The gap pass filed a second ticket for a decision already recorded.
    • The runtime gap is real, but it is implementation, not design. Current code still does not enforce residency at the event-sync, world-record, connectivity or outbox seams (2026-11-08 verification: pkgs/id/crates/id-core/src/residency.rs is a pure evaluator with no call sites). That scope belongs to id: implement Residency boundaries for native bridge, federation and relays (design #3398) #5529 "id: implement Residency boundaries for native bridge, federation and relays (design id: design: residency boundaries for native bridge, federation and relays #3398)" — OPEN, blocked/assigned. The framework-level vocabulary (declaration predicates, non-binary outcomes) is being settled in design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683's PR docs(id): residency & boundaries framework skeleton design (#5683) #7781, which is the parent framework's step 1.
    • Conclusion: no separate design is owed here, and a parallel design PR would duplicate design(id): #3398 residency boundaries #3856 and fork the vocabulary. Closing as superseded. Implementation tracking stays on id: implement Residency boundaries for native bridge, federation and relays (design #3398) #5529; parent vocabulary on design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 / PR docs(id): residency & boundaries framework skeleton design (#5683) #7781.
    • Dated design records that cite id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882 for the boundary (id: design: self-hosting & interop stance — own servers, Rust library reuse, what intercompatibility requires #5975 stance, id: design: land/parcel capability domains — per-parcel policy granularity without tokenized land #6015) are immutable snapshots; read those citations as pointing to the merged id: design: residency boundaries for native bridge, federation and relays #3398 record and id: implement Residency boundaries for native bridge, federation and relays (design #3398) #5529 for implementation. No doc edit made.
    • Queue: task 13587 completes as superseded; issue closed and queue/status/work labels cleared. Task attempts were 6/6 at cap — this verdict is the terminal state that ends the handoff loop.
12. dezren39

    closed this as not plannedon Nov 9, 2026
13. developing-today

    added

    status:done

    on Nov 9, 2026
14. developing-today

    closed this as completedon Nov 9, 2026
15. dezren39

    removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    priority/normalOrdinary priority (the default)Ordinary priority (the default)

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

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

    on Nov 9, 2026