I2 — Bun-exclusive surface
Goal: implement the native API surface Bun ships that Node and Deno do not — as first-class scripty APIs, on scripty’s own Zig VM (Linux only).Why exclusive-only
scripty’s long-term product story includes Node, Deno, and Bun shaped APIs. Overlap (fs, http, fetch, …) is huge and already planned as shared host/Node-compat work.
I2 is deliberately narrower: what you lose if you only implement Node+Deno. Exclusivity is by namespace + shape (see Principles), so a Bun-shaped API such as Bun.serve counts even when a similar capability exists elsewhere under a different name (Deno.serve, Node http). That list is finite and marketable.
Success definition
Tag
0.0.1 requires the docs bar and honest statuses. Full green I2 is not required to name the tag if I1 is met — but empty inventories are not acceptable.
Out of scope
Read next
Inventory
Bun-only APIs catalogued for implementation.
Matrix
Living status rows.
Roadmap
B-0 … B-6 delivery waves.
Program roadmap
How I2 sits under pre-v0.0.1.