[RFC-003] Sandboxed proc-macro execution — public comment window (closes 2026-06-25)

[hassard0]

Public comment window for RFC-003 is open through 2026-06-25 (30-day window, opened 2026-05-26).

This thread is the canonical channel for feedback on RFC-003 before it can be normative-accepted into docs/spec/v1.0-rc.md for the v1.0 freeze.

How to participate

Reply with one of:

• ✅ Accept — RFC ships as written
• ✏️ Modify — suggest a specific change (quote the section + propose the alternative)
• ❌ Reject — explain why this RFC shouldn't ship in v1.0
• ❓ Question / concern — flag an ambiguity or gap; doesn't block acceptance but seeds polish

Detailed technical disagreements are best filed as inline comments on the RFC file via a PR; this thread is for the higher-level accept/modify/reject signal.

Reading the RFC

• File: docs/spec/rfcs/RFC-003.md
• Window tracker: docs/spec/rfcs/COMMENT_WINDOWS.md
• Live dashboard: docs/spec/rfcs/RFC_DASHBOARD.md
• Implementation status is recorded in the RFC file's header — several of these RFCs cover work that has already shipped pre-v1.0 (RFC-006 live migration in v0.21, RFC-008 effect rows in v0.13–v0.19, RFC-009 set-of-scopes in v0.13–v0.15). The comment window is procedural ratification for those + design feedback for the still-forward-looking RFCs (RFC-001..005).

Closing the window

On 2026-06-25 this window closes. After that, an integrator collects every reply, dispositions accept / modify / reject in the RFC file's footer, and updates COMMENT_WINDOWS.md + RFC_DASHBOARD.md. Threads stay open after that — they just stop being load-bearing for the v1.0 freeze gate.