id(phase-14): Discovery, registry & federation — v2 — outline: the public registry

Discovery, registry & federation — v2 — outline: the public registry

Part of the Phase 14 core topic #6277 (Discovery, registry & federation), filed from the next-horizons discussion #1240 per Drew's 2026-11-05 decision. The Phase 14 epic links the whole map.

Scope (rough outline — the core topic's research refines it)

Registry on the main public endpoint: browsing, search and filters, freshness/decay of listings, popularity and quality signals that resist gaming.

Entry condition

The previous step (v1 — first-iteration design) has its design written, with open questions answered or explicitly deferred to this step.

Deliverable

An updated, refined outline on this issue — tightened scope, open questions, dependencies — and the next-step issue breakdown when this step's turn approaches. If the step has dissolved into the previous one, close this issue with that note (drop rule).

Drew's Phase 14 principles (#1240) govern this step: local-first always; hostable by anyone at any scale; p2p behavior identical to hosted behavior; our hosted instance is the public backstop, never a requirement.

Acceptance criteria

Entry condition verified on this issue: the previous step's design is written, with its open questions answered or explicitly deferred to this step.
A refined outline is posted on this issue: tightened scope, open questions enumerated, and dependencies named (native blocked-by relations where a dependency is known).
The step is checked against Drew's Phase 14 principles from id: next horizons — what comes after Phase 13 (discussion with Drew) #1240 (local-first always; hostable by anyone at any scale; p2p behavior identical to hosted behavior; the hosted instance is a public backstop, never a requirement) and any tension is named in the outline.
Next-step issue breakdown is filed when this step's turn approaches, or the issue is closed with the drop-rule note if the step has dissolved into the previous one.

CODE-1854

Intake review

Fleet monitor intake (§5 pass), 2026-11-05 run.

Still live: yes — issue open, filed 2026-11-05/06; merged-PR search for an explicit resolving reference found none (the few merged PRs whose text contains this issue's number are unrelated cross-references — e.g. PR titles fixing other issues — not implementations of this ticket). Nothing to close.
Related: Phase 14 core topic id(phase-14): Discovery, registry & federation — core topic (research + design) #6277 (Discovery, registry & federation); principles in id: next horizons — what comes after Phase 13 (discussion with Drew) #1240; follows the v1 design (id(phase-14): Discovery, registry & federation — v1 — first-iteration design #6287), precedes federation (id(phase-14): Discovery, registry & federation — v3 — outline: federation #6289).
Notes: Outline step for the public registry — worlds listed once and found everywhere starts here, on top of the v1 registry design.
Risks: Public-listing policy (who may list, delisting, abuse) needs explicit treatment in the outline; it is partly a Drew policy call.
Suggested approach: Wait for id(phase-14): Discovery, registry & federation — v1 — first-iteration design #6287's design, then refine this outline against it.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-h
Session / ID: task 11060
Found via: queue claim
Task: task 11060 (triage for issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288) claimed by lane code-h; issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 verified OPEN with no hard-stop labels; execution-lane assignment returned opencode, so task 11060 is handed off to the opencode claimant per the worker instruction §1b and parked 1200s pending the claimant launching the bound session; if the park expires first, task 11060 returns to the queue.
Expectation: claimant launches the bound opencode session and drives task 11060 to its terminal state
Links: issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-y
Session / ID: task 11060
Found via: queue claim
Task: triage/work for issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 handed off to the opencode execution lane (fleet queue lane returned assigned_lane=opencode); the laptop claimant launches the bound opencode session
Expectation: claimant drives task 11060 to a terminal state under this queue's worker id
Links: issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

Handed off to opencode claimant per execution-lane assignment (task 11060, issue #6288).

Verified fresh via gh (REST): issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit).
Execution lane: assigned_lane=opencode, session_id=null at handoff — claimant polls and launches the bound session; this lane does not work it directly (instruction §1b).
Parked 20 minutes pending claimant launch. Attempts 1/6 at handoff.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-j
Session / ID: task 11060
Found via: queue claim
Task: triage work for issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 handed off to the opencode claimant per execution-lane assignment (assigned_lane=opencode); verified fresh via gh: issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Parked 1200s for claimant binding. Attempts 1/6.
Expectation: opencode claimant launches the bound session and drives task 11060 to a terminal state.
Links: id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-e
Session / ID: task 11060
Found via: queue claim
Task: task 11060 (triage, issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288) is assigned execution_lane=opencode — handing off to the opencode claimant per worker instruction §1b; this lane does not work it directly.
Expectation: claimant launches the bound opencode session and drives task 11060 to a terminal state.
Links: issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-u
Session / ID: task 11060
Found via: queue claim
Task: handing off task 11060 (issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288) to the opencode claimant per execution-lane assignment
Expectation: claimant launches the bound opencode session and drives task 11060 to a terminal state
Links: issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

🤖 Agent note · handed off

Agent: repo queue worker, lane code-r (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-r run 2026-11-06; task 11060
Found via: claimed task 11060 this shift; execution-lane assignment returned opencode
Task: task 11060 for issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 (triage). Fresh check: issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit), no open PR found. Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly. Attempts 1/6.
Expectation: claimant session drives task 11060 to a terminal state.
Links: task 11060 · issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

🤖 Agent note · handed off

Agent: repo queue worker, lane code-o (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-o run 2026-11-06 11:32 CST; task 11060
Found via: claimed task 11060 this shift; execution-lane assignment returned opencode
Task: task 11060 for issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 (triage). Fresh check: issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 11060 to a terminal state. Attempts 1/6.
Links: task 11060 · issue id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

Navigation Menu

Repository navigation

id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

Discovery, registry & federation — v2 — outline: the public registry

Scope (rough outline — the core topic's research refines it)

Entry condition

Deliverable

Acceptance criteria

Intake review

41 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id(phase-14): Discovery, registry & federation — v2 — outline: the public registry #6288

Description

Discovery, registry & federation — v2 — outline: the public registry

Scope (rough outline — the core topic's research refines it)

Entry condition

Deliverable

Acceptance criteria

Activity

developing-today commented on Nov 5, 2026

dezren39 commented on Nov 6, 2026

Intake review

dezren39 commented on Nov 6, 2026

41 remaining items

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

developing-today commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions