RFC-0024 · 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: What is the canonical cross-process adapter result schema?
Status: Open
Source: RFC-0024 §6.1
Issue: The compiler invokes module adapters across a compilation-stage boundary, but the RFC specifies only TypeScript interfaces with Record<string, FieldDef> and runtime-specific TypeRegistry references. It does not define a language-neutral wire schema, version negotiation, or how an adapter module in another language returns the same operation set.
Recommendation: Define versioned protobuf messages for adapter input and result, including operation and type definitions. Keep TypeScript types as generated bindings or illustrative API wrappers.
Q: How can a locked build reconstruct adapter-generated operations without invoking the adapter?
Status: Open
Source: RFC-0024 §6.1–6.3; RFC-0014 §7
Issue: The text says a matching lockfile allows reuse of a cached operation set, but the sample gnomon.lock stores only operationCount and a hash, not the generated operation and type definitions. It also says the compiler MUST NOT re-query a spec if its hash matches the current hash, while determining a changed remote hash requires a query or an immutable source identifier.
Recommendation: Pin a content-addressed, serialized adapter result containing full operation and type definitions, or require replay from a verified immutable schema snapshot. Define offline and stale-source behavior explicitly.
Q: Which lockfile owns adapter schema pins?
Status: Open
Source: RFC-0024 §6.3; RFC-0014 §7
Issue: RFC-0014 makes module.lock the sole locked-build authority for resolved modules, while RFC-0024 introduces a separate required gnomon.lock for adapter schemas without an ordering or staleness relationship. A build can therefore have a current module graph and stale adapter-generated operations.
Recommendation: Extend module.lock with adapter-schema entries or define an explicit versioned dependency from it to an adapter lockfile, then enforce both in CI.
Q: What value does ignore return for a scalar or nonempty output schema?
Status: Open
Source: RFC-0024 §3 error classes
Issue: The ignore error class says to return a zero or empty value for the output schema, but an operation can return a scalar or a record with required fields. Such a value may violate the declared return type and a caller may treat it as successful data.
Recommendation: Make ignored errors return an explicit optional/result variant, or restrict ignore to operations whose output type has a defined neutral value.