RFC-0020 · 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: When does an event enter the deduplication window?
A: The completed window receives an ID only after callback acknowledgement. An in-flight marker is separate; rejection clears it and allows retry. RFC-0020 §4.3 now specifies this.
Source: RFC-0020 §4.3–4.4; §10 invariant 3 Issue: The runtime tracks “delivered” event IDs, but a callback rejection re-queues the same event for redelivery. If its ID entered the window before acknowledgement, the deduplication rule would silently discard the required retry. Recommendation: Record an ID as completed only after callback acknowledgement; retain a separate in-flight marker so a retry is not discarded as a duplicate.
Q: How do current authorization changes affect an opened subscription?
A: Effective delivery scope is the intersection of scope fixed at open and current grants. Revocations restrict delivery immediately; new grants require a new subscription. RFC-0020 §8 now specifies this.
Source: RFC-0020 §2 goal 4; §8 rules 1–3; §10 invariant 4 Issue: The subscription scope is fixed at open, but every event is rechecked against the principal’s current scope. The text does not explicitly state whether a later grant can widen delivery, while invariant 4 forbids widening. Recommendation: Define effective delivery scope as the intersection of the scope fixed at open and the principal’s current grants. Revocation then restricts delivery immediately; new grants require a new subscription.
Q: Which events count toward the at-least-once promise?
A: The at-least-once guarantee covers open, non-overflowed subscriptions and events within effective scope. M20003 or M20004 signals overflow before event loss. RFC-0020 §§2, 4.1, and 6.1 now agree.
Source: RFC-0020 §4.1; §6.1; §10 invariants 1 and 5 Issue: Section 4.1 says every matching event MUST be delivered, while the default overflow policy drops events. Invariant 1 narrows the promise to non-overflowed subscriptions, but the earlier statement has no exception. Recommendation: State the overflow exception at the first at-least-once rule and require M20003 or M20004 before any event is lost.
Q: When will a DSL-level subscription declaration be specified?
Status: Open
Source: RFC-0020 §1
Issue: The RFC explicitly defers .gnm subscription declaration syntax to a future RFC, so the runtime API does not establish an authoring contract.
Trigger: Assign a language-surface RFC and compiler owner before claiming module-authored subscriptions are supported.
Q: Which RFC owns the runtime event ID and read-scope descriptor types?
Status: Open
Source: RFC-0020 §§3.1–3.3, 8, 10; RFC-0007 query contract; RFC-0008 §8 readScope grammar; RFC-0010 event log Issue: Five RDF relationships misidentify the event ID source, make readScope provenance a self-reference, freeze effective scope despite revocation, or assign named runtime types to RFCs that do not define them. Recommendation: Define the runtime binding types in RFC-0020, preserve RFC-0007 and RFC-0008 as the owners of the underlying mechanisms, and apply the exact relationship mapping in the RDF model proposal after reviewing consumer impact.