gnomonlearn
Docs/RFC-0035/Design Q&A

RFC-0035 · 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.

← Read the authored RFC

Q: Is core.claims.EvidenceRecord a persisted entity or compile-time vocabulary?

Status: Open

Source: RFC-0035 §§1, 3.2, 7.1; RFC-0002 storage manifest Issue: The RFC says every core.* declaration is compiler-provided vocabulary, not a runtime dependency or distributed source module, yet it defines core.claims.EvidenceRecord as an entity. Entities normally have storage identity and a schema in the compiled bundle. The ownership, migration, and versioning of those persisted records are unspecified. Recommendation: Define whether EvidenceRecord is a persisted system entity with a compiler-owned schema and migration path, or a non-persisted value type. Pin its schema/ABI to the compiler or bundle version accordingly.

Q: Which diagnostic reports a declaration under the reserved core namespace?

Status: Open

Source: RFC-0035 §2 M35001/M35002; RFC-0006 §4.C M06040/M06041 Issue: RFC-0035 assigns M35001 to a third-party declaration in core, while RFC-0006 already assigns M06040 to the same reserved namespace violation. An unknown core.* name may likewise be M35002 or the general unresolved-FQN M06041. The compiler cannot emit a stable single code without precedence. Recommendation: Make RFC-0006’s existing codes canonical for namespace and FQN resolution, or publish an explicit alias/supersession table with migration tests.

Q: Where are HTTP status-to-core.errors mappings specified?

Status: Open

Source: RFC-0035 §4.2; RFC-0025 §5; RFC-0034 §5 Issue: RFC-0035 says the HTTP handler maps status codes to core.errors.* and that RFC-0025 defines the mapping. RFC-0025 classifies 4xx/5xx selectors as terminal, transient, or ignore but does not choose NotFound, Unauthorized, or another structured error type. Server serialization therefore lacks an authoritative status/error mapping. Recommendation: Define a versioned mapping in the HTTP server binding, including defaults, operation overrides, and serialization of errors.common types.