Skip to content

id: design: fleet surface for the broker role (from #5671) #5798

Open

Description

@dezren39

Summary

Follow-on design ticket from #5671 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.

What this design must settle

The future fleet id subcommand wiring the broker role into fleet sandbox→laptop patterns — the operational surface of the fallback design.

Context from the parent

The parent design fixes how ID clients and servers stay reachable when UDP is denied — fallback order, broker shapes, trust model, and the E2E boundary. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.

Decision record expected

Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.

Relations

Parent: #5671. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).

Activity

  1. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Nov 5, 2026
  2. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 5, 2026
  4. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  5. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · triage complete

    • Agent: queue worker (repo-worker-code), lane code-j
    • Session / ID: task 10201
    • Found via: queue claim (coverage-audit requeue)

    Triage of issue #5798 at current main (verified fresh 2026-11-05):

    Ordering (the substantive triage finding): #5798 designs the fleet surface (fleet id wiring) for the broker role — it consumes other tickets' outputs, so it goes last in this sibling set:

    1. id: design: id broker / serve-proxy role (from #5671) #5792 first — it defines the broker/serve-proxy role whose operational surface id: design: fleet surface for the broker role (from #5671) #5798 would wire into fleet; designing the surface before the role exists guarantees rework.
    2. id: design: relay trust model & broker authorization (from #5671) #5795 (trust model & broker authorization) and id: design: transport negotiation & fallback ordering (from #5671) #5791 (fallback ordering) next — the surface must expose, not re-invent, the authorization model and fallback order.
    3. id: design: fleet surface for the broker role (from #5671) #5798 after those land, scoped to: the fleet id verb/registry shape for the broker role in the sandbox→laptop pattern, which parent decisions it binds to (cited, not re-decided), and the decision record the body requires.

    Blockers recorded: sequencing only — #5798 is blocked in practice on #5792/#5795/#5791 decisions, all of which are open design work under parent #5671 (programme epic #2056). No Drew decision is needed to proceed in that order; implementation timing remains a separate decision per the filing note. Issue #5798 stays open as the design ticket.

  7. added
    status/triagedTriaged and routed (see agent note)
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)status/triagedTriaged and routed (see agent note)task/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions