id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services

Agents in worlds (MCP bridge) — v4 — outline: hosted agent services

Part of the Phase 14 core topic #6280 (Agents in worlds (MCP bridge)), 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)

Always-on hosted agents (on the T1 hosting substrate): agent programs listed in the registry, hired/attached to worlds, with the public-server trust model applied.

Entry condition

The previous step (v3 — outline: shared agent worlds) 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

A design outline for this iteration is recorded on this issue (or in a linked design doc) covering scope, non-goals, and the key decisions this iteration must settle.
Open questions and decision points needing Drew's ruling are listed explicitly on the issue.
Follow-up implementation work is filed as linked issues (native sub-issues / blocked-by relations per protocol §11), not left as prose in this outline.
The relationship to the sibling iterations of the same phase-14 topic is linked from this issue.

CODE-1868

Intake review

Fleet monitor intake (repo-fleet-monitor, 2026-11-05) — protocol §5 pass.

Related: siblings in the same topic: id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301 (v2), id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 (v3); v1 of this topic was enriched in the previous monitor run.
Notes: Human-filed phase-14 design outline (Agents in worlds (MCP bridge), v4 — outline: hosted agent services). It already carries kind/feature, source/human, priority/low and an effort class; the missing piece was an acceptance-criteria section, now appended to the body. This is a design-stage item: per protocol §10/§11 nothing here is finished work until the decisions are recorded and implementation issues are filed as native relations.
Risks: Outline issues can sit silently — the failure mode the fleet rules call out ("a design with no implementation link is flagged"). The v1→v4 ladder also risks later versions being read as commitments before earlier decisions land.
Suggested approach: Work the ladder in order; record each iteration's decisions on its own issue; file implementation issues with native sub-issue/blocked-by links in the same pass; escalate only genuine Drew decisions, with the substance in the message.

🤖 Agent: fleet monitor · Found via: monitor intake (Duty 2)

🤖 Agent note · parked (waiting-dependency)

Agent: repo queue worker, lane code-p (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-p run 2026-11-08; task 12953
Found via: claimed task 12953 this shift; execution-lane assignment returned direct (lane row 4651), so this lane revalidated it directly.
Task: task 12953 for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 (design v4 outline: hosted agent services). Fresh check: issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). ENTRY CONDITION UNMET: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 (v3 outline) is still OPEN with status/waiting-dependency + queue/queued, its latest comments are triage/handoff notes only, and no open PR or posted design for id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 exists — the v3 design has not been written yet, so the v4 outline cannot start.
Expectation: park as waiting-dependency; resume only when issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302's v3 design is written with open questions answered or explicitly deferred to v4.
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 · epic id(phase-14): Agents in worlds (MCP bridge) — core topic (research + design) #6280

🤖 Agent note · parked (waiting-dependency — entry condition unmet)

Agent: queue worker (repo-worker-code), lane code-y
Session / ID: task 12953
Found via: queue claim; execution-lane assignment direct (lane row 4651), worked by this lane
Task: task 12953 (small_fix) for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 — v4 hosted-agent-services design outline. Entry condition: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 v3 design written.
Fresh verification (2026-11-09T00:52Z, via developing.today GitHub App token — user token GraphQL rate-limited): issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 OPEN, no hard-stop labels; issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 OPEN with status/waiting-dependency and queue/queued — the v3 design is not written, so the v4 entry condition is still NOT met. Same verdict as lanes code-w (00:10Z) and code-p (00:31Z) today; nothing has changed since.
Expectation: task 12953 parked; resume when id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302's v3 design is written and recorded on id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303.
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · gate issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302

🤖 Agent note · parked — waiting dependency

Agent: queue worker (repo-worker-code), lane openchamber-scheduled-lane (1a180ae5-384f-4e71-8d77-08f7b1652c75)
Session / ID: task 12953 (ses_e5e422dba69ffeFBwEJYsVMveo)
Transition: picked up → parked; no branch/worktree created.
Fresh entry-gate check: id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 is OPEN with status/waiting-dependency and queue/queued. Its latest triage says v3 waits for id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301's design; id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301 is OPEN/waiting-dependency on id(phase-14): Agents in worlds (MCP bridge) — v1 — first-iteration design + spike plan #6300; id(phase-14): Agents in worlds (MCP bridge) — v1 — first-iteration design + spike plan #6300 is OPEN/waiting-dependency on first-pass research for id(phase-14): Agents in worlds (MCP bridge) — core topic (research + design) #6280.
Resume condition: id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302's v3 design is written, with open questions answered or explicitly deferred to v4; then revalidate the sibling chain before starting id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303.
Links: id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 · id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301 · id(phase-14): Agents in worlds (MCP bridge) — v1 — first-iteration design + spike plan #6300 · id(phase-14): Agents in worlds (MCP bridge) — core topic (research + design) #6280 · task 12953

🤖 Agent note · parked (entry gate still closed)

Agent: repo queue worker, lane code-p (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-p run 2026-11-08 18:57 CST; task 12953
Found via: claimed task 12953 this shift; execution-lane assignment returned direct
Task: Task 12953 (small_fix/design) for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 is gated on the v3 design in issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 being written. Fresh check: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 is still OPEN with status/waiting-dependency and issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 is OPEN with no hard-stop labels. The entry condition is still unmet, so no design work was started; task 12953 parked 1200s.
Expectation: resume task 12953 when issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302's v3 design is written/closed.
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302

🤖 Agent note · parked (waiting-dependency)

Agent: repo queue worker, lane code-h (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-h run 2026-11-08; task 12953
Found via: claimed task 12953 this shift; execution-lane assignment returned direct, so this lane verified it itself.
Task: task 12953 for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 (small_fix, design outline only). ENTRY CONDITION UNMET, verified fresh via developing.today App: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 has no v3 design written. The triage on issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 (comment 6726887550, 2026-11-08T20:55Z) established the ladder is gated step by step: id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 waits on id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301, id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301 waits on id(phase-14): Agents in worlds (MCP bridge) — v1 — first-iteration design + spike plan #6300, id(phase-14): Agents in worlds (MCP bridge) — v1 — first-iteration design + spike plan #6300 waits on first-pass research on id(phase-14): Agents in worlds (MCP bridge) — core topic (research + design) #6280, and no such research findings exist yet. Siblings id(phase-14): Agents in worlds (MCP bridge) — core topic (research + design) #6280, id(phase-14): Agents in worlds (MCP bridge) — v1 — first-iteration design + spike plan #6300, id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301, id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 all OPEN fresh. Writing a v4 outline now would invent decisions the earlier steps must settle.
Action: parked task 12953 as waiting-dependency. Resume condition: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 v3 design is written with open questions answered or explicitly deferred to v4 (which itself requires the id(phase-14): Agents in worlds (MCP bridge) — core topic (research + design) #6280 research, then id(phase-14): Agents in worlds (MCP bridge) — v1 — first-iteration design + spike plan #6300 and id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301 designs, in that order).
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 · issue id(phase-14): Agents in worlds (MCP bridge) — core topic (research + design) #6280

🤖 Agent note · parked (waiting-dependency)

Agent: repo queue worker, lane code-n (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-n run 2026-11-08 20:07 CST; task 12953
Found via: claimed task 12953 this shift; execution-lane assignment returned direct (lane row 4651), so this lane verified it itself.
Task: task 12953 for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 (small_fix). ENTRY CONDITION UNMET, verified fresh: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 is still OPEN with status/waiting-dependency and unchanged since 2026-11-08T20:45Z — no v3 design written; the ladder remains gated on first-pass research on issue id(phase-14): Agents in worlds (MCP bridge) — core topic (research + design) #6280 (still OPEN). Per the packet acceptance, no design work was started. No hard-stop labels on issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303.
Expectation: resume task 12953 when issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302's v3 design is written with open questions answered or explicitly deferred to v4. Parked 1200s.

🤖 Agent note · parked — waiting on dependency #6302

Agent: repo queue worker, lane code-o (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-o run 2026-11-08 21:32 CST; task 12953 (direct lane, row 4651)
Task: task 12953 for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 (design: Agents in worlds v4 refined outline; entry condition: the v3 design for issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 is written).
Fresh check: issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 is OPEN, no hard-stop labels. Entry condition UNMET: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 is still OPEN (queue/queued, status/waiting-dependency); no PR in any state mentions id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302, no commit on origin/main references it, and no v3 design doc exists under doc/ on main. The v3 design has not been written, so the v4 outline cannot start without inventing its input.
Expectation: park 1200s as waiting-dependency. Resume when issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302's v3 design is written/merged; then produce the v4 refined outline for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303.
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302

🤖 Agent note · parked (entry gate still closed)

Agent: repo queue worker, lane code-p (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-p run 2026-11-08 18:57 CST; task 12953
Found via: claimed task 12953 this shift; execution-lane assignment returned direct
Task: Task 12953 (small_fix/design) for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 is gated on the v3 design in issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 being written. Fresh check: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 is still OPEN with status/waiting-dependency and issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 is OPEN with no hard-stop labels. The entry condition is still unmet, so no design work was started; task 12953 parked 1200s.
Expectation: resume task 12953 when issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302's v3 design is written/closed.
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302

🤖 Agent note · parked (waiting-dependency) — lane code-w correction

Agent: repo queue worker, lane code-w (repo-worker-code), task 12953
Note: the immediately preceding note (comment 6732374384) was posted by this lane but its body was read from a stale laptop /tmp file belonging to lane code-p — same task and same conclusion, wrong attribution. This note supersedes it for lane code-w.
Fresh check 2026-11-09T04:41Z: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 still OPEN, status/waiting-dependency, v3 design not written; issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 OPEN, no hard-stop labels. Entry condition unmet.
Next: task 12953 parked; resume when id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 v3 design is written.

Lane code-u (task 12953): re-verified gate fresh 2026-11-09T05:1xZ — entry condition still unmet: #6302 (v3 design) remains OPEN with status/waiting-dependency, last updated 2026-11-08T20:45Z, no v3 design written. #6303 cannot start until #6302 lands. Parking task 12953 again; resume when #6302 design is written/merged.

🤖 Agent note · parked (waiting-dependency)

Agent: repo queue worker, lane code-n (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-n run 2026-11-09 00:07 CST; task 12953
Found via: claimed task 12953 this shift; execution-lane assignment returned direct (lane row 4651), so this lane revalidated it directly.
Task: task 12953 for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 (small_fix — design: Agents in worlds v4, entry condition: v3 issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 design written). Fresh check: issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). The entry condition is still unmet: issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 is OPEN with queue/queued + status/waiting-dependency fresh-checked 2026-11-09T06:20Z — the v3 design is not yet written.
Expectation: task 12953 parked 1200s; resume condition = issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 v3 design written/closed, then the v4 refined outline proceeds. Attempts 2/3.
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · gate issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302

🤖 Agent note · parked — waiting-dependency (entry condition unmet)

Agent: repo queue worker, lane code-h (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-h run 2026-11-09; task 12953
Task: task 12953 for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 (small_fix, direct lane). Entry condition from the packet: the v3 outline issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 has its design written, with open questions answered or explicitly deferred to v4.
Fresh check (2026-11-09): issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 OPEN, no hard-stop labels. Issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 still OPEN with queue/queued + status/waiting-dependency — the v3 design is not written. Siblings issue id(phase-14): Agents in worlds (MCP bridge) — v2 — outline: agents as citizens #6301 and issue id(phase-14): Agents in worlds (MCP bridge) — v1 — first-iteration design + spike plan #6300 also still OPEN. Entry condition remains unmet, so no v4 design work started, per the packet acceptance.
Resume condition: park ends and task 12953 resumes when issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 v3 design is written/closed; then write the refined v4 outline for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303.
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302

🤖 Agent note · parked (waiting-dependency)

Agent: repo queue worker, lane code-n (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-n run 2026-11-09; task 12953
Found via: claimed task 12953 this shift; execution-lane assignment (row 4651) returned direct — worked by this lane
Task: task 12953 for issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 (small_fix — design v4 outline; entry condition: the v3 design on issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 is written). Fresh re-verification at 2026-11-09T07:05Z: issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 OPEN, no hard-stop labels; issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 still OPEN with status/waiting-dependency, last updated 2026-11-08T20:45:14Z, latest comment is a triage note — the v3 design is NOT written. Entry condition remains UNMET, so there is nothing to implement yet; parking as waiting-dependency per the packet.
Expectation: task resumes when issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302 carries its written v3 design.
Links: task 12953 · issue id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303 · dependency issue id(phase-14): Agents in worlds (MCP bridge) — v3 — outline: shared agent worlds #6302

Navigation Menu

id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303

Agents in worlds (MCP bridge) — v4 — outline: hosted agent services

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

Entry condition

Deliverable

Acceptance criteria

Intake review

91 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id(phase-14): Agents in worlds (MCP bridge) — v4 — outline: hosted agent services #6303

Description

Agents in worlds (MCP bridge) — v4 — outline: hosted agent services

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 5, 2026

Intake review

91 remaining items

developing-today commented on Nov 9, 2026

developing-today commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

developing-today commented on Nov 9, 2026

developing-today commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions