RFC-0026 · 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: Which diagnostic is emitted for an expired gRPC deadline?
Status: Open
Source: RFC-0026 §§2.3, 4.2, 7
Issue: §2.3 requires M26616 for every expired call and reports DEADLINE_EXCEEDED subject to the operation’s error classification. §4.2 instead raises M26610 when no matching selector exists and may retry when one does. The precedence of M26616, M26610, and a transient retry is unclear.
Recommendation: Define a single status-to-policy sequence: cancel the attempt, classify DEADLINE_EXCEEDED, retry only if allowed, and emit one terminal diagnostic after exhaustion with a documented relationship between M26616 and M26610.
Q: Is a gRPC response stream an RFC-0020 subscription?
Status: Open
Source: RFC-0026 §§3.2–3.4; RFC-0020 §§3–8
Issue: The RFC says a server-streaming Stream<T> follows RFC-0020’s open/pause/close lifecycle, but RFC-0020 subscriptions tail the Gnomon event log, deduplicate eventId, and filter by query/read scope. Arbitrary gRPC messages need not have those fields or guarantees.
Recommendation: Define a transport stream handle with explicit flow control, cancellation, status, and message ordering; share only lifecycle methods with RFC-0020 where their semantics match. Do not inherit event-log delivery guarantees without a bridge contract.
Q: Can streaming operations have non-stream metadata input fields?
Status: Open
Source: RFC-0026 §§3.3–3.5
Issue: The prose says input MUST contain exactly one field of type Stream<T>, which permits other fields, while the summary table says input is “One field: Stream<T>”. Real RPC requests may also need metadata fields, but the permitted shape is unclear.
Recommendation: Require exactly one stream-typed field and explicitly allow or forbid additional non-stream fields, with a defined mapping to the gRPC request stream.
Q: Which environment source controls the production TLS guard?
Status: Open
Source: RFC-0026 §6.2
Issue: Production may be determined by a deployment manifest or GNOMON_ENV, but their precedence and behavior on disagreement are unspecified. A stale non-production environment variable could weaken the plaintext guard if it overrides a production manifest.
Recommendation: Treat either source indicating production as production, and fail closed on contradictory settings; specify how the runtime records M26614 before refusing startup.