RFC-0016 · Design Q&A
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
Q: How should coordinated cross-module migrations be handled?
Status: Open Context: Deferred. Migrations that require coordinated changes across two module namespaces are not addressed by this RFC. A future RFC should define a multi-module migration primitive.
Where normative: n/a — pending future RFC or implementation experience
Q: What is the specific expression language for transform: in changeType?
Status: Open
Context: Deferred. The transform: expression in changeType is described as a total function but the specific expression language (lambda syntax, built-in coercion helpers) is not yet standardized. A companion RFC or addendum to RFC-0007 should formalize this.
Where normative: n/a — pending future RFC or implementation experience
Q: Should partial or phased rollout strategies be supported for migrations?
Status: Open Context: Deferred. This RFC assumes migrations are applied to all nodes simultaneously. Canary or phased rollout strategies are not addressed.
Where normative: n/a — pending future RFC or implementation experience