gnomonlearn
Docs/RFC-0044/Design Q&A

RFC-0044 · 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: How is a remote transform source pinned for a reproducible clean build?

Status: Open

Source: RFC-0044 §§3.1, 5.4, 6.2 Issue: The example fetches a mutable latest URL. URL plus observed content hash does not tell a fresh build which bytes to expect, and an offline build may reuse an arbitrary prior cache entry. A diagnostic for drift does not define whether the build fails. Recommendation: Require an expected content digest or immutable artifact pin in the manifest or lockfile, fail on digest mismatch, and allow offline fallback only for that exact digest.

Q: Which projector identity and ordering enter the transform cache key?

Status: Open

Source: RFC-0044 §§3.5, 5.2, 5.4 Issue: Projectors execute in order and later projectors may read earlier outputs, but the cache key uses sortedList(projectors), erasing explicit order. It also omits projector implementation versions and compiler version, so changed code can reuse stale generated files. Recommendation: Hash the ordered projector identity/version list and the relevant compiler and adapter identities, plus the resolved default projector order.

Q: How can an IR file containing fetchedAt be deterministic across builds?

Status: Open

Source: RFC-0044 §§4.2, 4.5, 8 invariant 5 Issue: The IR includes fetch time and is checked into source control, but repeated fetches of identical content yield different IR bytes. Sorted-key printing does not remove that nondeterminism. Recommendation: Exclude observed fetch time from the canonical generated IR or keep it in a separate provenance record outside the deterministic artifact.

Q: How are generated object paths wired into the compiled manifest?

Status: Open

Source: RFC-0044 §§3.3, 5.3, 6.1; RFC-0040 §9.6 Issue: Projectors write .gnm files under output directories, while RFC-0040 loads only file paths named in the objects map. The RFC does not define how thousands of generated files are added to that map without manual enumeration or whether generated keys can collide with authored keys. Recommendation: Specify a deterministic generated-object manifest with names, paths, ownership, and collision diagnostics, consumed by the module compiler before object validation.

Q: What schema governs TransformIR exchanged across parser and projector stages?

Status: Open

Source: RFC-0044 §§4–5 Issue: TransformIR crosses a stage and file boundary as an open JSON shape with adapter-specific kind and attributes. No machine-checkable schema or compatibility rule is specified beyond transformIRVersion: 1, making projector interoperability and version migration unverifiable. Recommendation: Define a versioned protobuf IR with typed core fields and explicit extension payloads, or adopt an existing project schema layer with equivalent validation and compatibility gates.