Skip to content

Latest commit

 

History

History

Proposals

Forward-looking design proposals that don’t yet rise to the level of an architectural decision record (ADR — those live in docs/decisions/).

Status legend:

  • [draft] — circulating; not yet shippable

  • [review] — ready for maintainer review

  • [accepted] — accepted; usually gets promoted to an ADR or to a docs/architecture/ doc when work starts

  • [rejected] — closed without merge; reasoning preserved in-file

  • [superseded] — replaced by another proposal; pointer to successor

Current proposals

Number Title Status

0001

Multi-producer carrier sections for L2–L6 and L15

[accepted] (2026-05-30) → promoted to ADR-0002

0002

Access-site carrier section (typedwasm.access-sites) for L2 enforcement

[accepted] (2026-05-30) → promoted to ADR-0003

0003

Region imports carrier section (typedwasm.region-imports) for L13 cross-module schema agreement

[draft]

0004

Capability grants carrier section (typedwasm.capability-grants) for L15-C per-call-site enforcement

[draft]

Note
Proposals 0001 and 0002 were promoted to ADR-0002 and ADR-0003 on 2026-05-30. The proposal files remain in docs/proposals/ as the canonical wire-format and producer-obligation references; the ADRs record the decisions and their consequences.

The strategic decisions (D1–D6) from docs/PRODUCTION-PATH.adoc §"Load-bearing decisions" are tracked there directly; each will land an ADR under docs/decisions/ when made rather than first landing as a proposal.

When the engineering surface grows (Phase 2+), this directory becomes the natural staging ground for design-doc-level proposals before they harden into ADRs.

Authoring a proposal

  1. File: docs/proposals/NNNN-short-slug.adoc (numbering starts at 0001; pad to 4 digits)

  2. Top-of-file metadata: status, author, date, last-updated

  3. Sections: Context, Proposal, Alternatives considered, Open questions, Acceptance criteria

  4. Cross-link to the relevant phase issue (#48–#54) and to related ADRs / architecture docs