Skip to content

docs: record #16 decision — publishing deferred, consumers pin git refs / prerelease artifacts #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lann merged 1 commit into from
Aug 9, 2026
Merged

docs: record #16 decision — publishing deferred, consumers pin git refs / prerelease artifacts #33

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -532,7 +532,7 @@ are kept as gates.
| Testing wasmtime-with-wasmtime blind spots | medium | official suite + definitions.py ports as independent checks; consumer suites as real-workload gates |
| Testing-toolchain format skew: testgen assembles with `wast` 255 while the shim validates with wasmparser 0.252 (wasmtime-47 pin) — the 0.253–0.255 window re-arited 🧵 thread opcodes (byte-level desync) | low, bounded | known 5-entry xfail set; exits on the wasmtime bump ([#1](https://github.com/lann/deltic/issues/1)); testgen cannot downgrade (suite text syntax needs `wast` ≥255) |
| CSP variance in embedders | low | baseline needs only `wasm-unsafe-eval` — an invariant, no path may require full `unsafe-eval` (§3); specialized JS is emission-only, deploy-time or server-side cache import ([#8](https://github.com/lann/deltic/issues/8)) |
| Consumer coupling churn: 7+ downstream repos tracking pre-1.0 plan/contract formats | medium | versioned releases ([#16](https://github.com/lann/deltic/issues/16)); strict formatVersion equality already fails loud; consumer matrices as release gate (the wasmtime↔embedder relationship); both sides practice exact pinning |
| Consumer coupling churn: 7+ downstream repos tracking pre-1.0 plan/contract formats | medium | exact pinning via git refs and/or `pre-<shorthash>` prerelease artifacts — registry publishing deferred ([#16](https://github.com/lann/deltic/issues/16), decision 2026-08-09); strict formatVersion equality already fails loud; consumer matrices as release gate (the wasmtime↔embedder relationship); both sides practice exact pinning |
| Consumer scope creep pulling WASI implementations into the core | medium | shim package is a separate deliverable with consumer-driven scope; §2 non-goal stands; the L3 runner belongs in polymorph-test ([#14](https://github.com/lann/deltic/issues/14)) |
| Host-boundary perf vs jco's generated JS (v1 interpreter) | low-medium | translation throughput measured (multi-MB components in tens of ms); cutover benches tracked with [#8](https://github.com/lann/deltic/issues/8); iroh's polling-workaround removal dominates first-consumer numbers regardless |

Expand Down
5 changes: 3 additions & 2 deletions docs/consumers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,9 @@ Their jco blockers map one-for-one onto this project's proven strengths

- **Co-evolution, not compatibility.** Conventions are designed against
the consumers' host modules as reference implementations; they port; both
sides pin exactly and upgrade deliberately (versioned releases:
[#16](https://github.com/lann/deltic/issues/16)).
sides pin exactly and upgrade deliberately — via git references and/or
`pre-<shorthash>` prerelease artifacts; registry publishing is deferred
([#16](https://github.com/lann/deltic/issues/16), decision 2026-08-09).
- **WASI interfaces are design inputs even though implementations stay
out of core.** The conventions must make wasi p2 idioms (pollables, io
streams, error-code enums, resource-heavy surfaces) and p3 idioms
Expand Down
Loading