docs(adr): promote proposals 0001 + 0002 → ADR-0002 + ADR-0003#116
Merged
Conversation
9c007ad to
348833c
Compare
This was referenced May 30, 2026
Promotes the two `[accepted]` (2026-05-30) proposals to architecture decision records. - Add `docs/decisions/0002-multi-producer-carrier-sections.adoc` — ADR for `typedwasm.regions` + `typedwasm.capabilities` carriers (and reserved slots for access-sites + region-imports). - Add `docs/decisions/0003-access-site-carrier.adoc` — ADR for `typedwasm.access-sites` per-instruction `(region_id, field_id)` carrier (proposal 0001 Open Question §5 → option A). - Cross-link proposals 0001 + 0002 to their ADRs via new `Promoted to` row in each metadata table + inline NOTE. - Rewrite `docs/decisions/README.adoc` from stub to proper ADR index (was a 2-line placeholder; now lists ADR-0001/0002/0003 with authoring guidance and cross-refs). - Update `docs/proposals/README.adoc` to show promotion arrow + revise NOTE block. - LEVEL-STATUS.md Open-gating item #4 (ADR promotion) → DONE. Proposal files are retained as canonical wire-format / producer- obligation references; the ADRs record the decision and consequences in the standard `Context / Decision / Consequences` shape. Existing ADR 0001 (`adopt-rsr-standard`, 2026-02-14) is unaffected — this is purely additive, with new ADR numbers picking up from 0002 in chronological order.
348833c to
9339d6e
Compare
This was referenced May 30, 2026
Merged
hyperpolymath
added a commit
that referenced
this pull request
May 30, 2026
…ss stale references (#117) ## Summary Companion to #115 (acceptance flip) and #116 (ADR promotion). Sweeps the remaining files that still carried `[draft]` / `[review]` proposal status or referenced now-closed cross-repo gating issues. ## Files changed | File | What changed | |---|---| | \`README.adoc\` | Proposal status flipped to \`[accepted]\` + ADR links; added 0003/0004 to forward-looking section; rewrote the verifier-pass status sentence (was "gated on proposal 0002's acceptance"; now reflects PR #109 having shipped). | | \`CHANGELOG.md\` | New Unreleased section "Multi-producer carrier ABI: proposals 0001 + 0002 accepted, promoted to ADRs (2026-05-30)" covering PRs #110-#116 + the seven closed issues + producer-side gates that remain. | | \`crates/typed-wasm-verify/Cargo.toml\` | Feature-flag comments updated to reflect post-acceptance state. \`unstable-l2\` / \`unstable-l15\` feature gates retained while Phase 3 stabilisation is open. | | \`docs/PRODUCTION-PATH.adoc\` | Proposals 0001/0002 flipped to \`[accepted]\` with PR pointers; added 0003/0004 to active-design-work list. | | \`spec/type-safety-levels-for-wasm.adoc\` | Wire-section status column updated for \`typedwasm.regions\` / \`typedwasm.capabilities\` / \`typedwasm.access-sites\`; tail references enumerate all four proposals with current status. | | \`.machine_readable/6a2/STATE.a2ml\` | Capabilities-by-level entries flipped 30→100; rewrote critical-next-actions; rewrote \`[carrier-abi]\` section with accepted-date / acceptance-pr / adr-pr for both proposals + added \`[draft]\` entries for 0003/0004. | ## What was deliberately left alone \`spec/{ARG,CRG,FRG,TRG}-PROFILE.adoc\` — these are point-in-time audit snapshots, not config. They mention the proposals as the live RFC corpus, but rewriting audit history adds more noise than signal. ## Test plan - [ ] CI green (docs + config only; no source changes) - [ ] Cross-links resolve in rendered AsciiDoc 🤖 Generated with [Claude Code](https://claude.com/claude-code)
🔍 Hypatia Security ScanFindings: 96 issues detected
View findings[
{
"reason": "Action perpolymath/standards/.github/workflows/governance-reusable.yml@main\n needs attention",
"type": "unpinned_action",
"file": "governance.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in boj-build.yml",
"type": "unknown",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in c5-regenerate.yml",
"type": "unknown",
"file": "c5-regenerate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in cargo-audit.yml",
"type": "unknown",
"file": "cargo-audit.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "unknown",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "unknown",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stacks on #115. Promotes the two
[accepted](2026-05-30) proposals toarchitecture decision records under
docs/decisions/. Closes the lastopen gating item from PR #115's LEVEL-STATUS rewrite (#4 — "ADR
promotion").
Changes
New files:
docs/decisions/0002-multi-producer-carrier-sections.adoc—ADR for
typedwasm.regions+typedwasm.capabilitiescarriers,plus reserved slots for access-sites (→ ADR-0003) and region-imports
(→ proposal 0003
[draft]). Adopted pins: WBool 4B wire, LEB128per field (option B), cardinality-1 producer surface in v1, opt-in
Cargo features.
docs/decisions/0003-access-site-carrier.adoc— ADR fortypedwasm.access-sitesper-instruction(region_id, field_id)carrier (proposal 0001 OQ §5 → option A). Realised by
verify_access_sites_from_modulein PR feat(verify): verify_capabilities + verify_access_sites passes (proposal 0002 §Gate 4) #109.Updated files:
docs/decisions/README.adoc— rewritten from 2-line stub to properADR index (ADR-0001 RSR + new ADR-0002 / 0003 + authoring guidance
docs/proposals/README.adoc— index entries gain promotion arrows;NOTE block updated to reflect the promotion instead of the deferral.
docs/proposals/0001-multi-producer-carrier-section.adoc,docs/proposals/0002-access-site-carrier.adoc— addPromoted tometadata row + inline NOTE under the metadata table. Proposal
content is unchanged; they remain canonical wire-format references.
LEVEL-STATUS.md— Open-gating item Snapshot local work before sync #4 (ADR promotion) → DONEwith file-path pointers.
Why now
#115 flipped proposals 0001 + 0002 to
[accepted]but deliberatelydeferred ADR promotion as a separate auditable PR (file moves +
numbering choices). This PR closes that follow-up:
adopt-rsr-standard(2026-02-14). New ADRspick up at 0002 / 0003 in chronological order without renumbering
anything else.
short decision records; the proposals carry the wire-format detail,
error variants, and producer-readiness checklists. Cross-references
point in both directions.
Stacking note
Branched off PR #115's head commit
d9869bbso the proposal statusfields and
docs/proposals/README.adocare already at the[accepted]baseline. Will rebase cleanly when #115 merges; nocontent conflict with #115.
Test plan
docs/decisions/README.adocindex entries link to the right filesPromoted torows resolve to the new ADRs🤖 Generated with Claude Code