RFC-0056 · 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: Should materialized views become a fourth transform species?
Status: Open
Source: RFC-0056 §9; RFC-0053 §5
Original question: RFC-0053 §5 describes view materialization as a kind of build-time transform. Consider a fourth category, “view transform”, in a follow-up.
Trigger: Review the view materialization contract before adding a fourth species.
Q: Should streaming transforms be part of this taxonomy?
Status: Open
Source: RFC-0056 §9; RFC-0020
Original question: A reactive (stream<input>) → stream<output> expression transform is permitted by RFC-0008 §6.32 but the semantics in the streaming context are not fully specified by RFC-0020. Defer until reactive Gnomon is normalized.
Trigger: Normalize reactive Gnomon semantics before defining stream transforms.
Q: Should the manifest field be renamed from transforms to ingest_transforms?
Status: Open
Source: RFC-0056 §9; RFC-0040 §8
Original question: A future major version could rename transforms: to ingest_transforms: for clarity. The cost (every existing manifest changes) is high; deferred.
Trigger: Revisit only in a major-version compatibility plan for existing manifests.