epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15)

Drew's 2026-10-28 directive, LIST 6–15: the ID platform expansion — core build, first apps, comms, currency, hosting, notes, chat, boards. Full text: hatch-personal memory/topics/id-program-2026-10-28.md. High priority; does not preempt in-flight work.

Children:

id: investigate: app packaging — apps as folders (code + resources), TUI/web interface parity, web-native specialization #2026 id: investigate: app packaging — apps as folders (code + resources), TUI/web interface parity, web-native specialization
id: investigate: capability-based specialization — forms, location, media across web, ESP32/MQTT, and text/audio modes #2027 id: investigate: capability-based specialization — forms, location, media across web, ESP32/MQTT, and text/audio modes
id: design: ID core build v1 — app model + capability system, enough to start app examples #2028 id: design: ID core build v1 — app model + capability system, enough to start app examples
id: investigate: did-it tracker data model — events, expectations, per-entity cardinality, details + later opinions #2029 id: investigate: did-it tracker data model — events, expectations, per-entity cardinality, details + later opinions
id: investigate: trust/visibility model — servers accept all signed objects; views count only allowed writers #2030 id: investigate: trust/visibility model — servers accept all signed objects; views count only allowed writers
id: design+PoC: sticky-notes / did-it tracker — the first ID app #2031 id: design+PoC: sticky-notes / did-it tracker — the first ID app
id: investigate: comms abuse controls — blocks, rate limits, and per-counterparty budgets #2032 id: investigate: comms abuse controls — blocks, rate limits, and per-counterparty budgets
id: design: abuse-control primitives v1 for ID comms #2033 id: design: abuse-control primitives v1 for ID comms
id: investigate: ephemeral live data vs the chained event graph — retention and intermittent signing #2034 id: investigate: ephemeral live data vs the chained event graph — retention and intermittent signing
id: investigate: multi-hop relay and P2P media paths — bridging peers, optional privacy relay, large-message chunking #2035 id: investigate: multi-hop relay and P2P media paths — bridging peers, optional privacy relay, large-message chunking
id: design: ID messaging/relay protocol v1 #2036 id: design: ID messaging/relay protocol v1
id: investigate: match-result attestation — mutual concession, witness adjudication, offline play #2037 id: investigate: match-result attestation — mutual concession, witness adjudication, offline play
id: investigate: match audit — netcode log format, replay validation, and cheating signals #2038 id: investigate: match audit — netcode log format, replay validation, and cheating signals
id: design: match attestation + audit v1 #2039 id: design: match attestation + audit v1
id: investigate: TigerBeetle — multi-currency ledgers, conversions, per-coin vs balance model, 3-node cluster topology #2040 id: investigate: TigerBeetle — multi-currency ledgers, conversions, per-coin vs balance model, 3-node cluster topology
id: investigate: token issuance in the ID graph — per-ID issuance, issuer snapshots, authorized conversion rates #2041 id: investigate: token issuance in the ID graph — per-ID issuance, issuer snapshots, authorized conversion rates
id: investigate: tokens for real services — Steam-key grants, returns/refunds, revocation #2042 id: investigate: tokens for real services — Steam-key grants, returns/refunds, revocation
id: design: ID currencies v1 #2043 id: design: ID currencies v1
id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044 id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID
id: investigate: hosted data option — per-user stores, Google SSO, static/local-storage variants, container-spend limits #2045 id: investigate: hosted data option — per-user stores, Google SSO, static/local-storage variants, container-spend limits
id: design: ID serverless edition v1 (Cloudflare Workers) #2046 id: design: ID serverless edition v1 (Cloudflare Workers)
id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047 id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model)
id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048 id: design: Zettelkasten layer — multiplayer docs/wiki on ID
id: investigate: IRC-first chat on ID — channels, graph-linked objects, presence #2049 id: investigate: IRC-first chat on ID — channels, graph-linked objects, presence
id: investigate: BitTorrent-style chunk retrieval for graph objects #2050 id: investigate: BitTorrent-style chunk retrieval for graph objects
id: design: ID chat v1 #2051 id: design: ID chat v1
id: investigate: boards — a modern phpBB on ID identity: no registration, copyable themes #2052 id: investigate: boards — a modern phpBB on ID identity: no registration, copyable themes
id: investigate: embedded playable posts — HTML5 mini-games, async challenges, and forkable succession saves #2053 id: investigate: embedded playable posts — HTML5 mini-games, async challenges, and forkable succession saves
id: design: ID boards v1 #2054 id: design: ID boards v1

Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md).
Working pattern: parallel investigations, then the named synthesis issue merges them into a full design. Route guidance: Workhorse by default; Specialist/Summit for synthesis and ramification-heavy work. A result that says "done" is not the endpoint — the orchestrator reviews it and may commission another round. Deliverables: a markdown design/investigation doc (mermaid/SVG diagrams welcome) linked from this issue, plus follow-up issues for anything buildable. Build a proof of concept where the design calls for one, but do NOT build the permanent feature on top of an unreviewed PoC.

Acceptance criteria

Every child investigation/design issue in the program (LIST 6-15) reaches a written conclusion or a synthesis issue
The synthesis issues merge their investigations into v1 designs for core, chat, boards, hosting and currency
Children that stall are named on this epic with their blocker rather than sitting silently

CODE-977

docs(id): 2026-10-28 program investigations — TigerBeetle + Cloudflar…

Dispatch intent (orchestrator note, 2026-10-28): enqueue children as normal fleet work. Investigations run on Workhorse; synthesis/design issues (#2028, #2031, #2033, #2036, #2039, #2043, #2046, #2048, #2051, #2054, #2062, #2063, #2066) are gated on their named investigations and go to Specialist/Summit-grade routes when their inputs land. ALREADY DONE — do not redo: #2040 (TigerBeetle) and #2044 (Cloudflare fit) investigations are complete; reports are in PR #2067 and summaries are commented on both issues. Follow-on batch already filed: #2057–#2066 (Workers follow-ons + currency control plane/conversion engine/topology/refundable grants). PoCs (#2031 sticky-notes) must not become permanent features without a review round. Full program text: hatch-personal memory/topics/id-program-2026-10-28.md.

Intake review

Umbrella epic for Drew's 2026-10-28 directive, LIST 6-15 (full text in hatch-personal memory/topics/id-program-2026-10-28.md); the body states the program is high priority and does not preempt in-flight work. Not resolvable by a single PR — closure is by child completion. Intake note: several children (#2059-#2073) were enriched in the previous monitor run; this pass covers the remaining #2051-#2058 batch. Risk: epic drift — the fleet's standing rule is that anything blocked surfaces rather than sitting silently.

— repo-fleet-monitor intake enrichment (protocol §5): acceptance criteria appended to the body where missing, labels normalized, meta/enriched applied.

Wave-1 enqueued at top priority (2026-10-29). The ID-side wave-1 investigations/designs from this epic — #2026, #2027, #2029, #2030, #2032, #2034, #2035, #2037, #2038, #2041, #2042, #2045, #2047, #2050, #2052, #2053, plus batch-2 #2057–#2066 — are enqueued as triage tasks 3343–3368 in repo-health-code-pilot at queue priority 20, after the producers did not convert them. Already done: #2040, #2044. Syntheses and PoCs (#2028, #2031, #2033, #2036, #2039, #2043, #2046, #2048, #2051, #2054) stay gated on their named inputs.

agent-note:v1
state: picked_up
task: 7281 (repo-health-code-pilot, triage, lane code-o, execution lane: direct)
next: fresh child-map of this epic's children (#2026–#2054 + follow-on batch #2057–#2066), blockers named on the epic, triage completed this shift.

agent-note:v1
state: triaged
task: 7281 (repo-health-code-pilot, lane code-o)

Triage: epic child map, verified fresh 2026-11-03 (GraphQL state read of every child)

Named children #2026-#2054: 20 closed, 9 open. Follow-on batch #2057-#2066: all 10 closed.

Closed children: #2026, #2027, #2028 (core design v1), #2029, #2030, #2032, #2033, #2034, #2035, #2037, #2038, #2040, #2041, #2044, #2046 (serverless design v1), #2049, #2050, #2051 (chat design v1), #2052, #2053.

Still open - investigations (3):

id: investigate: tokens for real services — Steam-key grants, returns/refunds, revocation #2042 tokens for real services (Steam-key grants, refunds, revocation)
id: investigate: hosted data option — per-user stores, Google SSO, static/local-storage variants, container-spend limits #2045 hosted data option (per-user stores, Google SSO, container-spend limits)
id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047 friendly-name references (@/# phrase resolution)

Still open - designs / PoC (6):

id: design+PoC: sticky-notes / did-it tracker — the first ID app #2031 sticky-notes / did-it tracker PoC (first ID app)
id: design: ID messaging/relay protocol v1 #2036 messaging/relay protocol v1
id: design: match attestation + audit v1 #2039 match attestation + audit v1
id: design: ID currencies v1 #2043 ID currencies v1
id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048 Zettelkasten layer
id: design: ID boards v1 #2054 ID boards v1

Blockers / gating named

id: design: ID currencies v1 #2043 (currencies v1) is gated on id: investigate: tokens for real services — Steam-key grants, returns/refunds, revocation #2042; its other inputs (id: investigate: TigerBeetle — multi-currency ledgers, conversions, per-coin vs balance model, 3-node cluster topology #2040, id: investigate: token issuance in the ID graph — per-ID issuance, issuer snapshots, authorized conversion rates #2041, and follow-on designs id: design: currency control plane — registry, account factory, gateway #2062, id: design: conversion engine — linked transfer pairs, rate authorisation, liquidity accounts #2063, id: design: refundable grants via pending transfers — Steam premium tokens voidable through the refund window #2065, id: design: currency as the centralised exception — how the hosted (Workers) edition reaches the currency service #2066) are all closed.
id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048 (Zettelkasten) is gated on id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047.
id: investigate: hosted data option — per-user stores, Google SSO, static/local-storage variants, container-spend limits #2045 is the one open investigation whose synthesis (id: design: ID serverless edition v1 (Cloudflare Workers) #2046, serverless edition v1) has already closed - its remainder either folds into implementation follow-ups or closes with evidence under its own task; flagging here so it does not sit silently.
No child is blocked on a Drew decision; the remaining work is fleet-routable investigation/design, and each open child carries its own coverage task from the 2026-11-03 full-coverage pass.

Verdict

Epic stays OPEN as the tracker (closure is by child completion, per its own acceptance criteria). Acceptance criterion 1 is partially met (20/29 named children concluded, 10/10 follow-ons); the synthesis criterion remains open for #2036, #2039, #2043, #2048, #2054, with core (#2028), chat (#2051), and serverless (#2046) syntheses closed. No new issues filed - the open children are already in the system; filing duplicates would violate the one-issue-per-change rule.

agent-note:v1
state: done
task: 7281 completed as triaged (repo-health-code-pilot, lane code-o). Epic #2056 child map and blockers are in the triage note above; the epic stays open as tracker and closes by child completion.

Program map — 2026-11-04 expansion pass (Drew's essay rulings + Q&A)

1. ANSWERS

PR #5707 (doc/2026-11-04_id-program-essay-answers.md) — grounded answers to Drew's questions on #2819, #2898, #3231/#3232, #534, #558, #788, #790, #835, writer-set projection (#5545), #3455, #2146, crate split.

⚠️ #3232 shows CLOSED, but its comments record the receipt audit as gated / not started — needs a verification pass before anyone cites it as done.

2. NEW DESIGN ISSUES FILED THIS PASS (16)

Transport & reachability

id: design: ID transport fallback for UDP-denied networks v1 #5671 — UDP-denied transport fallback (extends id: Phase 13 F13.3 SSH-over-iroh reachability (and iroh-over-SSH fallback) #785)
id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674 — Wire format & transport adapters (extends id: design: ID messaging/relay protocol v1 #2036)

Data

id: design: ID selective sharing and foreign data-store adapters v1 #5672 — Selective sharing + foreign data-store adapters
id: design: Querying local and remote ID servers v1 #5675 — Querying local/remote ID servers
id: design: KDL as human presentation format + triples + ANSI graph SQL (SQL/PGQ) for ID data #5688 — KDL presentation + triples + SQL/PGQ
design(id): serverless edition storage — D1 vs Turso vs both for id on Cloudflare Workers #5681 — Serverless storage: D1 vs Turso (extends id: design: ID serverless edition v1 (Cloudflare Workers) #2046)

Knowledge & apps

id: design: ID notes, message board, and multiplayer editing v1 #5677 — Notes ↔ board ↔ multiplayer editing (extends id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048/id: design: ID chat v1 #2051/id: design: ID boards v1 #2054)
id: design: Knowledge layer feature program — competitor feature matrix, import/export, read-authority #5678 — Knowledge layer feature program (extends id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048)
id: design: Markup & styling model for programs-as-websites — semantic markup, style-override mapping #5679 — Markup & styling model (extends id(serve): design — how does a program appear as a website? (program-only ports, mixed ports, path mounts) #2146)
id: design: Boards next steps — sharing flows, portable themes, playable posts, moderation #5680 — Boards: next steps
id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682 — Chat: next steps

Identity & trust

design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684 — Identity, login & delegation (extends id: design: issuer key rotation and compromise recovery for currency issuers (from #2041) #2804)
design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 — Residency & boundaries framework (extends id: design: jurisdiction-aware per-user store routing (signup jurisdiction field, DO/blob/directory pinning) #2283/id: design: jurisdiction-partitioned hosted worlds and world blobs #3397/id: design: residency boundaries for native bridge, federation and relays #3398 — framework-first, priority low by Drew's ruling)

Platform

design(id): DoS suite & performance benchmark programme — adversarial CI coverage and per-interface regression gates #5685 — DoS suite + benchmark programme (extends id(world): F12.18 denial-of-service test suite in CI #560)
design(id): client-side capability providers — one provider model for ESP32/MQTT, terminal, Bevy, smartphone, and web #5686 — Capability providers: ESP32/MQTT → Bevy (extends id: Phase 13 F13.7 client-side capability providers under the ceiling model #789 — core feature per Drew)

3. PRIORITIES AS RULED BY DREW (2026-11-04)

Crate split = top-tier — umbrella pkgs/id: split the monolith crate into sub-crates along module seams (prioritized by Drew 2026-11-01) #3447, steps pkgs/id crate split — step 1: extract id-caps (workspace + leaf foundation already landed as id-core) #4403–pkgs/id crate split — step 7: extract id-cli; facade slimming #4411 all open; already prioritized by Drew 2026-11-01
id: Phase 13 F13.7 client-side capability providers under the ceiling model #789 capability providers = core
id: design: issuer key rotation and compromise recovery for currency issuers (from #2041) #2804 identity/delegation (via design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684) = keen, simplicity-first
Residency trio = wanted, framework-first, lower urgency

4. IN FLIGHT ALREADY

Implementation issues #5521–#5546 (the 27-item remainder from the design inventory: 18 implemented / 15 partial / 12 zero by code presence), plus queue tasks on repo-health-code-pilot. Note: the inventory is a snapshot — #2804's issuer_rotation.rs already landed during 2026-11-04.

5. KDL FINDING

No standalone old KDL brainstorming doc exists in the repo doc/, notes, or zettel corpora; traces are pkgs/id/README.original.md, pkgs/roc/out-in.kdl, and the 2022 developing-today/hygge builder repo. The deep material is likely in Drew's late-2023 ChatGPT conversations; recovery is a follow-on inside #5688.

6. NEXT STEP

Each design above carries its own decomposition sketch; the follow-on pass breaks them into further design tickets, then implementation issues.

Design gap & expansion pass (WS-F, 2026-11-04) — results

Drew's order: walk all open + closed ID design/feature issues for (1) ideas called done but skipped, (2) narrow scopes, (3) V1s needing V2/V3/V4 design issues filed now, (4) rhyming improvements. Coverage: all 836 app/id issues pulled (219 open / 381 closed at pass start per the label listing; full bodies via API); the 70 design-titled issues deep-reviewed; all 16 expansion parents' decomposition sketches read in full; recent design discussions mined via PR #5707 and the design packets.

Drew's five named items — filed

id: design: deterministic testing over time — simulated clock, replay, seeded fuzz corpus, soak runs #5779 — deterministic testing over time (simulated clock, replay, seeded fuzz corpus, soak runs)
id: design: native Android client — identity custody, offline worlds, full client (extends the #1831 PoC) #5780 — native Android client (full design; Proof-of-concept Android app + input interface extension (touch, mouse, hover) for relaying into live apps #1831 linked as its input-relay PoC precursor)
id: design: Bevy incorporation — ID worlds as Bevy applications (ECS mapping of the entity/triple model) #5781 — Bevy incorporation (ECS mapping of the entity/triple model)
id: design: graphical client & tooling surface — windowing, world inspector, debug UI #5782 — graphical client & tooling surface (windowing, world inspector, debug UI)
id: design: ESP32 hardware platform line — boards, provisioning, firmware lifecycle, OTA, power #5783 — ESP32 hardware platform line (id: MQTT device bridge id.device.v1 — spec + labelled PoC (ESP32 path recommendation) (#2027) #2343 scopes board firmware/OTA/power OUT; design(id): client-side capability providers — one provider model for ESP32/MQTT, terminal, Bevy, smartphone, and web #5686 is target-agnostic — the hardware line was homeless)

Skipped idea + done-check failure + ladders — filed

id: design: output safety beyond plain text — HTML/JS output modes, safe-plain as a user choice, ingest without execution (follow-on to #3455) #5785 — output safety beyond plain text: Design: a value cannot act on the terminal — one format-character (Cf) contract for pkgs/id plain output #3455 closed 4/4-complete with Drew's three extensions (HTML/JS output modes, safe-plain as user choice, ingest-without-execution) explicitly "not covered" and its ANSI/OSC question filed nowhere (source: PR docs(id): answers to Drew's 2026-11-04 ID program questions #5707 §10).
id: audit: produce the #3232 closing-audit evidence — field disposition table for artifact.rs never landed (closed as superseded) #5786 — done-check failure: Phase 3 (audit) of #3231 — field-by-field receipt-validation audit for pkgs/id artifacts + contract statement #3232 closed 2026-11-04 as "superseded" by the receipt-contract implementation; its acceptance deliverable was the audit evidence (field-by-field disposition table for artifact.rs, five named dispositions, module-doc verification) and none was produced — implementation ≠ audit, so the gap-discovery step never ran. id: audit: produce the #3232 closing-audit evidence — field disposition table for artifact.rs never landed (closed as superseded) #5786 carries the unfinished evidence; Phase 3 (audit) of #3231 — field-by-field receipt-validation audit for pkgs/id artifacts + contract statement #3232 stays closed.
id: design: spill v2 — native spill pools, lease failover and multi-holder fencing (extends #2819) #5787 — spill v2 (id: design: native-spill write lease protocol for hot worlds (from #2059) #2819's lease is single-spill-node by design; failover/pool fencing undesigned)
id: design: feature-leveled build variants on the crate split — client-only, server, headless, embedded (from #3447) #5788 — feature-leveled build variants on the crate split (pkgs/id: split the monolith crate into sub-crates along module seams (prioritized by Drew 2026-11-01) #3447's stated mechanism, never designed; Android/ESP32/Bevy consumers are queuing)
id: design: writer sets v2 — composable views, set algebra, federation (extends #5545) #5789 — writer sets v2: composable views, set algebra, federation (extends id: implement Writer-set view projection - view projection and discovery query (design doc) #5545 before its encoding freezes)

Decomposition tickets — 120 filed (#5791–#5912)

Every follow-on design ticket named in the 16 expansion parents' decomposition sketches (#5671, #5672, #5674–#5678, #5679–#5686, #5688) is now its own issue, and each parent carries a comment listing its tickets, satisfying their "follow-on design tickets filed" acceptance items. One deliberate non-filing: #5688's parser-evaluation ticket — already answered by the #5753 fork research (kdl-rs selected over knuffel/kaydle).

Verified NOT gaps (checked, homes exist)

id: design+PoC: friendly-name reference resolution, local store — reference representation, index, ranking (from #2047) #2259's out-of-scope v2 (cross-store fan-out/locator fetch) → filed as id: friendly-name reference resolution v2 — cross-store fan-out and locator fetch (follow-on to #2259) #5178.
id: design: server-side identity backup blob + rate-limited blinded unwrap (from #2381) #5033's out-of-scope set → id: key export/import — passphrase-wrapped identity key envelope (key-recovery slice 1) #2279, id: encrypted identity backup — seed-phrase export/restore + passphrase-wrapped server backup #2381, id: guardian social recovery — threshold approvals + delayed, cancellable key rotation #2382, id: design: issuer key rotation and compromise recovery for currency issuers (from #2041) #2804 all exist.
id: Phase 12 designs to run through the research workflow #534 and id: Phase 13 F13.8 multi-server, multi-client topology; client-only mode always supported #790 closures are honest (designs landed / implemented, remainders tracked open).
id: design: jurisdiction-aware per-user store routing (signup jurisdiction field, DO/blob/directory pinning) #2283's region-choice UI is a recorded product deferral ("ship when a customer needs it"), not a skip.

WS-F2 raw-conversation mining pass — results (2026-11-04). WS-F bounded its chat coverage to the triage packets + PR #5707; this pass mined the raw conversations directly, per Drew's "don't forget the raw conversations."

Sources mined: (1) OpenCode session store on the laptop — all 4,842 root-session user messages extracted and signal-mined (96 core-signal passages reviewed), plus phrase spot-checks across all 12,046 user rows incl. child sessions (dictation phrases live in root sessions; child rows are subagent prompts). Store coverage ends 2026-10-05. (2) Muse chats — the "Id platform project status" side chat (its ID asks were already converted to issues in-chat) and the main chat (Nov dictation already distilled into PR #5707 + WS-F). (3) ~/memory/2026-*.md daily logs as cross-check. Method: no quote, no filing — every candidate carries verbatim provenance and was verified against the full ID issue universe + WS-F's filings before any gap was claimed.

Newly filed (1):

id: design: build-time defaults file — embed network defaults from an optional JSON file instead of only hardcoded consts #5916 — build-time defaults file: embed network defaults (discovery topic/secret, relays, DNS) from an optional JSON file at build time instead of only hardcoded consts, with replace-vs-append build flag and serve-time skip. Source: peer-discovery plan review, 2026-03-23 — Drew confirmed the trio "no-gossip, built time defaults, and mdns"; the other two landed, this one never did (verified: no mechanism in tree, no build.rs, no issue).

Cross-linked onto existing issues (5) — near-misses where the raw wording carries a mechanism/constraint the filed version lost:

design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684 (comment 6647774385) — one-time token minted by CLI/authenticated web login to log in as yourself in a browser (2026-04-02).
id: encrypted identity backup — seed-phrase export/restore + passphrase-wrapped server backup #2381 (comment 6647778816) — local identity store encrypted at rest with the node's own iroh private key (2026-04-01).
id: design: ID selective sharing and foreign data-store adapters v1 #5672 (comment 6647783409) — p2pandas as a named foreign data-store adapter candidate; zero tracker hits before this (2026-04-02).
id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674 (comment 6647788157) — relay roles (lookup vs publish), multi-relay behaviour, self-hostable discovery DNS (2026-03-23).
id: investigate global (Mainline DHT) content discovery for public worlds #2263 (comment 6647792864) — discovery chatter at thousands of servers + what actually lands on the DHT, as acceptance questions (2026-03-23).

Judged NOT gaps (with reasons, full ledger in the pass worklog): named-instance/workspace folder + random-port ask (landed: id --new, serve-lock — #3144/#3040); the whole tags-v2 cluster — postcard binary keys, search syntax, CLI↔REPL parity, binary key/value handling (shipped and heavily tracked: #2121, #1735, #1617, collab WS issues); MemoryLookup (exists in tree, envelope_net.rs); one-shot-command connection close/reuse (shipped client behaviour); dozens/hundreds of instances over web + iroh (#790's topology, closed+implemented).

Coverage honesty: the OpenCode store's dictation density is concentrated in the Mar–Apr 2026 file-era sessions; the worlds-era design dictation (late Oct/Nov) lives in Muse chats and was already the substrate for PR #5707 and WS-F — this pass found no additional unfilled worlds-era strays there. Two early full-table probes of the v1 message/part tables were abandoned as too slow and superseded by the session_message route; nothing was silently narrowed — the root-session extraction is complete (4,842/4,842 rows parse-verified).

Capability-provider research widening filed as #5931 (per Drew's 2026-11-04 ruling that the #5686 split filings needed a real option space beneath them). One survey issue: per-class field state for terminal / smartphone-Android / web-browser / Bevy-engine / ESP32-MQTT providers, plus the cross-cutting layer (MCP at spec 2026-07-28, WASI component model at 0.3, Cap'n Proto/CapTP, UCAN/Biscuit/macaroon capability tokens, sandbox hosts) mapped against the writer-set provider shape (#5545). Cross-linked from #5686, all eleven split issues, and #5545. Survey's structural finding: the 2026 field has separated into four layers (declaration/discovery, invocation transport, sandbox enforcement, authority artefacts) — ID's originality sits in the authority layer, and the standing risk for the design issues is importing a layer-1/2/3 system and accidentally inheriting its layer-4 assumptions. Dead/changed options flagged with evidence in #5931 §7.

Coverage spot-check (WS-F3, 2026-11-04 ~21:40 CST; Drew's ask: re-check the largest late-Oct/early-Nov conversations at conversation granularity, both sides of the transcript).

Method note that matters: in-window OpenCode activity lives ENTIRELY in the fork's session_v2 store (6,891 sessions) — the legacy session table and the v1 message/part tables have zero activity after Oct 5 / Oct 2 respectively, so WS-F2's user-message diff structurally could not see this window's conversations. The six largest session_v2 trees in 2026-10-25→11-04 (by bytes and message count) were extracted in full (all user messages + all assistant text parts) and diffed thread-by-thread.

Result: 0 new design gaps. All six are fleet execution conversations (zero direct Drew dictation in this store/window — his input flowed via Muse chats → PR #5707, as WS-F2 recorded), and every substantive thread is tracker-resident: #242 impl (decision posted on the issue; PR #3998 merged; issue closed), the Oct 26 review coordinator (its FINAL.md is the Oct 12–26 era's own audit artifact; era followed through via the Oct 27 chat → #1061–#1072 and the design packets WS-F consumed), the two Daily codebase audit runs (five pkgs/id filings #5745–#5749 plus already-tracked cross-refs #4723/#173; sibling run → PR #5731 merged for #5725), the #3793 match-audit (PR #5201 merged, issue closed), the #806 replica task (Phase 5 / Policy B design carried in #806's own comments; still in flight at window end), and a null queue-lane run. Only bookkeeping was missing: the audit→filing mapping for the two Daily runs is now commented on #5724 (6649138356) and #5727 (6649138939). Verdict: the two passes' coverage claim HOLDS at conversation granularity for this window. Full audit trail: ~/workspace/scratch/id-gap-pass/WORKLOG3.md.

Docs consolidation (Drew, 2026-11-04): documentation/designs not strictly about the sandbox (hatch-personal/hatch) or the flake (darwin-nix) are getting code as their canonical home — tracking issue #5983, batches #5976 (backups), #5978 (fleet designs + task-system schema), #5980 (architecture/tooling), #5981 (Atlas sweep), #5982 (darwin-nix non-flake docs). Fleet-gap exits for the stay-until-replaced items: #5972, #5974, and existing #1357. Copy-not-delete; historical copies stay in the source repos.

New design program filed from Drew's 2026-11-04 worlds mega-brief (advanced Roc libraries, capability model, permission UX, dynamic user functions, licensing): tracking issue #5955 with 26 children (#5956–#5990). The brief was decomposed into a 113-statement inventory, each statement mapped to a child or an existing issue — nothing unmapped. V1/V2/V3 staging is in the tracking issue: V1 = pure + platform-dependent imports with today's ceilings + the demo with both negative tests (#5957); V2 = requested-vs-used registry + permission prompts + licensing classifier; V3 = server-compiled DLL user functions with hot-swap.

Navigation Menu

Repository navigation

epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056

Acceptance criteria

Intake review

36 remaining items

Triage: epic child map, verified fresh 2026-11-03 (GraphQL state read of every child)

Blockers / gating named

Verdict

Program map — 2026-11-04 expansion pass (Drew's essay rulings + Q&A)

1. ANSWERS

2. NEW DESIGN ISSUES FILED THIS PASS (16)

3. PRIORITIES AS RULED BY DREW (2026-11-04)

4. IN FLIGHT ALREADY

5. KDL FINDING

6. NEXT STEP

Design gap & expansion pass (WS-F, 2026-11-04) — results

Drew's five named items — filed

Skipped idea + done-check failure + ladders — filed

Decomposition tickets — 120 filed (#5791–#5912)

Verified NOT gaps (checked, homes exist)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056

Description

Acceptance criteria

Activity

developing-today commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

Intake review

dezren39 commented on Oct 29, 2026

36 remaining items

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

Triage: epic child map, verified fresh 2026-11-03 (GraphQL state read of every child)

Blockers / gating named

Verdict

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 4, 2026

Program map — 2026-11-04 expansion pass (Drew's essay rulings + Q&A)

1. ANSWERS

2. NEW DESIGN ISSUES FILED THIS PASS (16)

3. PRIORITIES AS RULED BY DREW (2026-11-04)

4. IN FLIGHT ALREADY

5. KDL FINDING

6. NEXT STEP

dezren39 commented on Nov 5, 2026

Design gap & expansion pass (WS-F, 2026-11-04) — results

Drew's five named items — filed

Skipped idea + done-check failure + ladders — filed

Decomposition tickets — 120 filed (#5791–#5912)

Verified NOT gaps (checked, homes exist)

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions