id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates

Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates

Part of the Phase 14 core topic #6278 (Program ecosystem (share, fork, gallery)), 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)

A gallery listing format (registry-hosted), program versioning and update flow into worlds that installed earlier versions, changelogs and rollback via F12.9.

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

The v1 design (issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291) is written, with its open questions answered or explicitly deferred to this step (entry condition met).
This issue's outline is updated in place: tightened gallery/update scope, open questions, and dependencies named.
The next-step issue breakdown for gallery & updates is filed and linked from this issue and from core topic issue id(phase-14): Program ecosystem (share, fork, gallery) — core topic (research + design) #6278 — or this issue is closed with a note that the step dissolved into v1 (drop rule).
The design honours the Phase 14 principles from discussion id: next horizons — what comes after Phase 13 (discussion with Drew) #1240: local-first, hostable by anyone, p2p identical to hosted.

CODE-1858

Intake review

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

Related: core topic issue id(phase-14): Program ecosystem (share, fork, gallery) — core topic (research + design) #6278; predecessor issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291 (v1 design); Phase 14 discussion id: next horizons — what comes after Phase 13 (discussion with Drew) #1240.
Notes: this is a sequenced design outline, not yet actionable — its entry condition is the v1 design landing. Priority/effort were already set by the filer (priority/low, effort/m) and are left as-is.
Risks: starting gallery/update design before v1's share/fork decisions land would re-litigate v1 choices; the entry condition is the guard.
Suggested approach: leave queued behind id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291; when v1 lands, refresh this outline against v1's decisions before breaking out implementation issues.

🤖 Agent note · done

Agent: queue worker (repo-worker-code), lane code-h
Session / ID: task 11064 (triage)
Found via: queue claim (direct execution lane)
Task: Triage of issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293 — verdict: VALID and correctly structured, DEFERRED pending dependency — entry condition NOT met (verified fresh via gh 2026-11-06T12:30Z):
- Issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293 is OPEN, no hard-stop labels; it is the v2 outline (gallery & updates) in the Phase 14 program-ecosystem ladder: core topic issue id(phase-14): Program ecosystem (share, fork, gallery) — core topic (research + design) #6278, v1 issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291, v2 issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293 (this), v3 issue id(phase-14): Program ecosystem (share, fork, gallery) — v3 — outline: public gallery #6294, v4 issue id(phase-14): Program ecosystem (share, fork, gallery) — v4 — outline: ecosystem at scale #6295.
- Entry condition is the v1 design on issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291 being written, with its open questions answered or explicitly deferred to this step. Issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291 is still OPEN with no design document or design findings posted — only the 2026-11-05 intake review, and today its own triage (task 11063, lane code-r) was handed off to the opencode claimant and parked, so the v1 design has not landed.
- Upstream sequencing gates named by the core-topic triage (task 11050, issue id(phase-14): Program ecosystem (share, fork, gallery) — core topic (research + design) #6278) are also still OPEN, verified fresh this shift: issue id: F12.4 provider registry — capabilities as manifest + provider components #1061 (F12.4 provider registry) OPEN and issue id: F12.10 fair scheduling and per-account quotas #1067 (F12.10 fair scheduling / quotas) OPEN.
- Native blocked-by dependency on issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291 added to issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293 this shift, so the deferral is machine-visible, matching the v3 deferral pattern (issue id(phase-14): Program ecosystem (share, fork, gallery) — v3 — outline: public gallery #6294 blocked-by issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293).
- No follow-up task enqueued and no outline rewrite attempted: refreshing the gallery/update outline before v1's share/fork, signing, and attribution decisions land would re-litigate v1 choices (the intake review's stated risk). The standing next step is issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291; when its design lands, this issue's outline gets refreshed against v1's decisions before any implementation breakdown.
Expectation: triage task 11064 completes as triaged; issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293 remains OPEN at priority/low, status/triaged + status/waiting-dependency, until issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291's v1 design lands.
Links: predecessor issue id(phase-14): Program ecosystem (share, fork, gallery) — v1 — first-iteration design #6291 · core topic issue id(phase-14): Program ecosystem (share, fork, gallery) — core topic (research + design) #6278 · successor issue id(phase-14): Program ecosystem (share, fork, gallery) — v3 — outline: public gallery #6294 · plan of record issue id: Phase 14 — hosted, federated, local-first (plan of record) #6312 · discussion id: next horizons — what comes after Phase 13 (discussion with Drew) #1240

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-x
Session / ID: task 11145
Found via: queue claim
Task: Triage for issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293 — execution-lane assignment for task 11145 is opencode; handing off to the opencode claimant per the worker runbook §1b. Verified fresh via gh: issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293 is OPEN with no hard-stop labels (no held, user/owned, do-not-merge, do-not-auto-edit).
Expectation: claimant launches the bound opencode session for task 11145 and drives it to a terminal state
Links: issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-t
Session / ID: task 11145
Found via: queue claim
Task: triage issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293 (id phase-14 program ecosystem v2 outline) — execution-lane assignment is opencode; handing off to the opencode claimant per the queue protocol, not working it in this lane
Expectation: the bound opencode session drives task 11145 to a terminal state; if the claimant has not launched by lease expiry the task returns to the queue
Links: task 11145 (queue repo-health-code-pilot), issue id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293

Navigation Menu

Repository navigation

id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293

Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates

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

Entry condition

Deliverable

Acceptance criteria

Intake review

3 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id(phase-14): Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates #6293

Description

Program ecosystem (share, fork, gallery) — v2 — outline: gallery & updates

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

Entry condition

Deliverable

Acceptance criteria

Activity

developing-today commented on Nov 5, 2026

developing-today commented on Nov 6, 2026

Intake review

3 remaining items

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 8, 2026

dezren39 commented on Nov 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions