Skip to content

id: investigate: world-VM Wasm portability audit — what of the worlds runtime runs inside a Worker #2057

Closed

Description

@dezren39

Source: the Cloudflare Workers fit investigation (on #2044) open question 1. Audit pkgs/id's world execution (sandboxed Roc/Wasm programs in shared journaled worlds) against the Workers Wasm reality: Wasm supported (SIMD yes, threading NO, WASI experimental), 128 MB memory, CPU-time limits. Which world programs and VM features port to an isolate, which need a native-node fallback, and what the hosted edition may therefore promise app authors.

Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md). Parent epic: #2056.
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

  • A written portability audit exists mapping pkgs/id world-VM features against Workers Wasm limits (no threading, WASI experimental, 128 MB, CPU-time caps)
  • Each world program/feature is classified: ports to an isolate, needs native-node fallback, or is excluded from the hosted edition's promises
  • The resulting promise list for app authors is stated explicitly

Activity

  1. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Oct 29, 2026
  2. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Parent epic: #2056 — ID platform expansion (2026-10-28 directive). Filed as batch 2 from PREPARED-ACTIONS.md.

  3. developing-today commented on Oct 29, 2026

    @developing-today
    Contributor
  4. added
    effort/mMedium: expected under 1 day of work
    kind/questionQuestion or design decision to resolve
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    priority/highImportant and time-sensitive
    source/humanFiled directly by a human
    on Oct 29, 2026
  5. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Intake review

    Part of the ID platform expansion program (parent epic #2056; source: the Cloudflare Workers fit investigation on #2044, open question 1). Filed by Drew 2026-10-28; not resolved by any merged PR. Suggested approach: audit the worlds runtime feature-by-feature against the documented Workers limits in the issue body and record the classification on this issue. Risk: an un-audited feature silently becoming a hosted-edition promise.

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

  6. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3359 in repo-health-code-pilot at queue priority 20 (only breakage-class work at priority 10 outranks it). Wave-1 is the ungated investigations and designs; syntheses and PoCs stay gated on their named inputs. Investigation route: Workhorse.

  7. added
    work/assignedQueue worker lifecycle state
    and removed on Oct 29, 2026
  8. 7 remaining items

  9. added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    work/assignedQueue worker lifecycle state
    on Oct 29, 2026
  10. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    Queued: repo-health-code-pilot task 3927 (2026-10-30), wave-2 follow-on. The 2026-10-29 triage verified this issue and recorded 'write the investigation' as the next step; this task is that write — investigation doc PR under doc/, follow-up issues for buildable pieces, close with the doc link. Ordered by Drew ('queue unrun').

  11. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 30, 2026
  12. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up (write the investigation doc in this pass)

  13. added a commit that references this issue on Oct 30, 2026
  14. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · done (investigation doc delivered; PR merged)

    Investigation write — world-VM Wasm portability (#2057)

    Task 3359's 2026-10-29 audit is now the wave-pattern doc at doc/2026-10-30T19-36-00Z_investigation_world_vm_wasm_portability/ (PR #2817, merged), re-verified against current main: fuel/memory/manifest machinery and example worlds confirmed; #2271 and #2046 open as scoped. One drift corrected: the tree pins wasmtime = "=48.0.7", not 43 — the host-replaceable framing is unaffected.

    PoC #2271 remains the only open buildable from this issue; nothing new filed.

  15. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    Closed: portability audit delivered in PR #2817 (merged as df9381f) — doc/2026-10-30T19-36-00Z_investigation_world_vm_wasm_portability/. PoC #2271 stays open; synthesis #2046 unblocked from this issue's side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/mMedium: expected under 1 day of workkind/questionQuestion or design decision to resolvemeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivesource/humanFiled directly by a human

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions