docs(proposals): producer-readiness checklist + canonical emit order (closes #97)

[hyperpolymath]

Summary

Closes #97 — addresses both halves of the paired-review meander finding.

(A) Producer-readiness checklist — Appendix B in proposal 0001 (~120 LOC)

Tabulates each carrier section's IR prerequisites, current producer-side status, and roadmap-issue identifier in each producer's tracker where the gap is named:

Carrier	IR prerequisites	Status
typedwasm.ownership	per-fn ownership-kind tracking	SHIPPING
typedwasm.regions	region decls + field offsets + stable indices	NOT YET EMITTABLE (AS Roadmap C1 deferred; Ephapax dead code)
typedwasm.capabilities	per-fn cap decl + module budget + effect IR	NOT YET EMITTABLE (AS Roadmap C2 not started; Ephapax Perform/Handle stubbed)
typedwasm.region-imports (0003)	+ cross-module region tracking + wasm-module-name resolution	NOT YET EMITTABLE
typedwasm.access-sites (0002)	+ per-instr tracking + post-rewrite hook	NOT YET EMITTABLE (depends on regions)
typedwasm.capability-grants (0004)	+ per-callsite grant tracking	NOT YET EMITTABLE (depends on capabilities)

NOTE block surfaces the all-or-nothing implication: do not emit a section you cannot populate.

Proposal 0002 gains a §"Producer-readiness (cross-reference)" subsection (~28 LOC) pointing to 0001's Appendix B plus three access-sites-specific items: per-instruction tracking, post-rewrite hook discipline, region-index stability across sections.

(B) Canonical emit ordering — extends 0001 §"Producer obligations"

New 5th item specifying the recommended emit order matching the runtime dependency graph:

1. typedwasm.ownership
2. typedwasm.regions
3. typedwasm.region-imports        (proposal 0003)
4. typedwasm.capabilities
5. typedwasm.access-sites          (proposal 0002)
6. typedwasm.capability-grants     (proposal 0004)

Consumers MUST NOT depend on this order — the verifier reads sections by custom-section name, so any order is parseable. The canonical order exists for cross-producer module comparability (byte-equal carrier sequences for two producers of the same logical module — useful for cmp / diff / content-addressing).

Acceptance update for #97

• Proposal 0001 gains §"Producer-readiness checklist" appendix listing the IR prerequisites for each section.
• Proposal 0002 gains a one-line cross-reference (expanded to a full subsection with access-sites-specific items) to 0001's checklist.
• Proposal 0001 §"Producer obligations" specifies the canonical emit order with a "consumer MAY accept any order" note.
• When AffineScript / Ephapax start their respective Roadmap C1/C2/C3 implementations, those issues cross-reference this checklist. (Producer-side action, not a typed-wasm gate.)

What this closes

Together with #94, #95, #96 (resolved in PRs #110/#111/#112/#113), this completes all the documentation-side gates around proposals 0001 and 0002. Both proposals are now fully ready for [review] → [accepted] owner decision.

Test plan

• AsciiDoc renders cleanly (cols-tables, lower-alpha sub-list, code-block fences).
• Cross-reference link to Appendix B from proposal 0002 uses AsciiDoc anchor format.
• No code changes — no Cargo/Idris2 build required.

Related

• spec: add producer-readiness checklist + canonical emit ordering to proposals 0001 / 0002 #97 (this PR closes it)
• Multi-producer ABI proposal: region/type-schema + capability carrier section (unblocks L2-6 / L15 on emitted wasm) #34 (proposal 0001 umbrella)
• meta: roadmap from [review] to [accepted] for proposals 0001 + 0002 #106 (acceptance roadmap tracker)
• ephapax#165 §3+§6 / affinescript#402 §4+§7 — paired reviews surfacing the gap
• affinescript#462 (access-sites codegen issue — referenced from Appendix B)

🤖 Generated with Claude Code

[github-actions]

🔍 Hypatia Security Scan

Findings: 96 issues detected

Severity	Count
🔴 Critical	8
🟠 High	19
🟡 Medium	69

⚠️ Action Required: Critical security issues found!

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