RFC-0015 · 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 this RFC define a normative gRPC inference service interface, or defer to a separate RFC?
Status: Open Context: Deferred. gRPC binding requires a separate protobuf service definition. Reserved for a future RFC once a concrete gRPC backend implementation exists and the payload shape is informed by real usage.
Where normative: n/a — pending future RFC or implementation experience
Q: Should the binding declare a streaming mode, and how should partial outputs interact with the atomicity guarantee?
Status: Open Context: Deferred. Streaming is architecturally significant; partial output atomicity is non-trivial. Reserved for a future RFC after the non-streaming binding is stable.
Where normative: n/a — pending future RFC or implementation experience
Q: Should circuit breaking be supported as an optional declaration on the binding?
A: Yes, as an optional declaration on the binding. A circuitBreaker block may be added to a binding declaration with failureThreshold and resetAfter properties. When the circuit is open, dispatch MUST fail with error M01540 (circuit open) rather than retrying. Circuit state is per-binding-per-process; it is not persisted across restarts.
Where normative: RFC-0015 §§4.1 and 10 (circuit-breaker syntax and diagnostic)
Q: Should action-level timeouts be allowed to override binding-level timeouts?
A: Action-level timeout override is allowed. An action that invokes an agent MAY declare agentTimeout: Duration in its action body to override the binding’s timeout: for that specific invocation. The action-level timeout MUST be shorter than or equal to the binding-level timeout; a longer action-level timeout produces warning M01541.
Where normative: RFC-0015 §10 (action timeout ceiling and diagnostic)
Q: Should the binding declaration carry a version field?
A: Yes. The binding declaration MUST carry an explicit version: String field that the module author increments when any binding property changes. Binding version is NOT semver — it is a monotone string used purely for change detection. The lockfile includes the binding version hash.
Where normative: §4 (binding declaration) of RFC-0015
Q: How should read scope be defined — as part of the permissions block or as a separate block?
A: A separate readScope block is introduced in the agent declaration (RFC-0008 §8.10). The permissions block remains write-oriented. readScope declares which entity kinds and fields the agent may read when constructing its prompt context. The runtime MUST enforce readScope at prompt assembly time. An agent with a permissions block but no readScope MUST produce warning M08932.
Where normative: RFC-0008 §8.10 (read scope and diagnostic)