id: F12.5 first new providers — kv, blob, http.fetch, notify

F12.5 — First new providers

From the Phase 12 plan (.opencode/plans/phase-12-platform-flexibility.md, workstream B):

kv — a bounded, durable, per-world key-value store
blob — content-addressed blobs, over iroh-blobs
http.fetch — admin allowlist, size and rate bounds, no redirects off the list, off by default
notify — user-visible outbound notifications, rate limited (this also covers the roadmap's 'outbound notifications' idea)

Each ships behind a ceiling, with an audit entry per use, and no new Wasm import. Depends on F12.4 (provider registry).

Exit: each provider has bound, refusal, and replay tests; http.fetch has a test that proves an unlisted host is refused.

Coordination (2026-10-26 reprioritization, per Drew): every id roadmap item now has its own GitHub issue, and priority encodes the order: (1) the path to Phase 12 — now + priority/high; (2) Phase 12 itself — next; (3) Phase 13 and long-term ideas — priority/low. The dashboard mirrors this list (org Project "Developing Today" #4, Area id-train; Grist Program roadmap, Area id). If this item turns out to be blocked, wrong, or superseded, park or close it with a note rather than letting it stall the queue — dropping an issue is always allowed; silently stalling is not.

CODE-206

🤖 Agent note · triage verdict — CONFIRMED, gated on F12.4 (not yet routable)

Agent: queue worker (repo-worker-code), lane C
Session / ID: queue task 2334 (repo-health-code-pilot)
Verified on current main:
- The capability catalog in pkgs/id/src/world_caps.rs lists exactly: time.now, time.tick, players.list, chat.say, chat.history, records.read, schedule.at, schedule.cancel, world.info. None of the four F12.5 providers (kv, blob, http.fetch, notify) exists; code search for http.fetch / a provider registry in pkgs/id returns nothing.
- The stated dependency has not landed: F12.4 provider registry is id: F12.4 provider registry — capabilities as manifest + provider components #1061, still OPEN (see also id(world): default ceiling is the whole catalog, so F12.4 registry additions would widen every world #838 — the default ceiling being the whole catalog is an F12.4-adjacent hazard that should be settled with the registry).
Route: This is confirmed, real roadmap work — but it is effort/l feature work for four providers, and it is sequenced behind id: F12.4 provider registry — capabilities as manifest + provider components #1061. Enqueueing a small_fix packet now would mis-scope it and collide with the registry design, so no follow-up packet is enqueued from this triage. The correct next step is: land id: F12.4 provider registry — capabilities as manifest + provider components #1061 (F12.4 registry), then file the F12.5 implementation as its own scoped packet(s) — one per provider, each with the bound/refusal/replay tests the issue's exit criteria name, http.fetch off by default with the unlisted-host refusal test.
This issue stays open as the F12.5 tracking item; triage is complete.

agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03

agent-note:v1
state: triaged (coverage pass re-verification)
task: 7616 · queue repo-health-code-pilot · worker repo-worker-code · lane bf419306-c4ef-470f-a553-beabf93239de
verified_at_main: d4d7834 (2026-11-03)

Verdict: still live, still blocked on F12.4 (#1061). No new work possible yet.

Re-verified rather than re-reported the 2026-11-01 triage:

Catalog unchanged. pkgs/id/src/world/actor.rs execute() still matches exactly time.now, random.u64, players.list, world.info, chat.say, chat.history, records.read, schedule.at, schedule.cancel. _ => Err(CapError::unknown()) remains the fallback — so kv, blob, http.fetch and notify all still return the unknown-capability error at current main.
Dependency still open and moving. id: F12.4 provider registry — capabilities as manifest + provider components #1061 (F12.4 provider registry) is OPEN, carries queue/queued, and has no open PR (searched open PRs for 1061 / provider-registry / F12.4 — none). The plan's ordering line is explicit: .opencode/plans/phase-12-platform-flexibility.md:73 — F12.4 -> F12.5 -> F12.6 -> F12.14.
No competing artifacts. No branch matching *1061* / *1062* / *provider-registry*, no superseding PR.

Split decision: not yet. Splitting into four per-provider issues today would file four issues that are all blocked behind the same registry design, and F12.5's own shape (manifest-declared name/args/bounds/scope/ceiling) is exactly what F12.4 defines — splitting before the registry lands would bake in a shape the registry may change. The split is committed and stays scheduled for the moment #1061 merges: one packet per provider, each carrying the issue's exit tests (bound, refusal, replay) and, for http.fetch, off-by-default plus a test proving an unlisted host is refused.

Routing: nothing to enqueue. The blocking task is #1061, which is already in the queue. This issue stays open as the F12.5 tracking item and now carries status/triaged + status/waiting-dependency.

Found via: coverage pass 2026-11-03 (queue task 7616)

Partial verification — staying open (2026-11-07 done-task-only audit, tracking: #7016).

Queue task(s) [7616, 2334] were marked done, and some work did land:

PR docs(id): roadmap — Phase 12 + path to Phase 12 first #1079 — docs(id): roadmap — Phase 12 + path to Phase 12 first (merged 2026-10-27T03:20:27Z): docs(id): roadmap — Phase 12 + path to Phase 12 first #1079
PR docs: capture Phase 12 (#534) research package intake #4672 — docs: capture Phase 12 (id: Phase 12 designs to run through the research workflow #534) research package intake (merged 2026-11-03T14:25:22Z): docs: capture Phase 12 (#534) research package intake #4672

No merged change closes this issue's full scope, so the done status is not treated as completion. Remainder re-queued as triage task 11526.

Agent note — handed off (task 11885)

Lane code-c claimed task 11885 (triage, issue id: F12.5 first new providers — kv, blob, http.fetch, notify #1062); execution-lane assignment returned assigned_lane=opencode.
Checkpointed handed_off; claimant launches the bound opencode session. This lane does not work the task directly.

🤖 Agent note · handed off

Agent: repo queue worker, lane code-u (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-u run 2026-11-07 20:24 CST; task 11885
Found via: queue claim · task 11885
Task: task 11885 for issue id: F12.5 first new providers — kv, blob, http.fetch, notify #1062 (triage). Fresh check: issue id: F12.5 first new providers — kv, blob, http.fetch, notify #1062 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Execution-lane assignment returned opencode — handed off to the opencode claimant, which launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 11885 to a terminal state.
Links: task 11885 · issue id: F12.5 first new providers — kv, blob, http.fetch, notify #1062

Navigation Menu

Repository navigation

id: F12.5 first new providers — kv, blob, http.fetch, notify #1062

F12.5 — First new providers

4 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: F12.5 first new providers — kv, blob, http.fetch, notify #1062

Description

F12.5 — First new providers

Activity

developing-today commented on Oct 27, 2026

dezren39 commented on Nov 1, 2026

4 remaining items

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 8, 2026

dezren39 commented on Nov 8, 2026

developing-today commented on Nov 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions