gnomonlearn
Docs/RFC-0032/Design Q&A

RFC-0032 · 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: Which artifact is the canonical compiled module bundle?

Status: Open

Source: RFC-0032 §§2, 4.1; RFC-0002 bundle contract; RFC-0019 §4.3 Issue: gnomon_module emits <name>.bundle as an rkyv binary, while publish computes a digest over a .gnomonpkg bundle. The RFC does not define whether these are identical bytes, a wrapper format, or separate build stages. Recommendation: Define a canonical .gnomonpkg output and make its digest the publish, lockfile, and cache identity; name any internal rkyv IR as a separate artifact with an explicit conversion.

Q: How does gnomon_kernel compose Rust compilation under Bazel analysis?

Status: Open

Source: RFC-0032 §§3, 4.3 Issue: The rule says it internally invokes a rules_rust rust_binary target after generating Rust. It does not specify how that target is declared and wired into Bazel’s analysis graph, so the build plan lacks a reviewable action/provider boundary for generated sources. Recommendation: Define a macro or explicit generated-source target feeding a declared Rust/WASM target, with toolchains and outputs represented in the analysis graph.

Q: Can migration planning read a live installed schema during a Bazel build?

Status: Open

Source: RFC-0032 §§4.5, 7 Issue: Omitting from_version diffs against an installed schema in the target environment, but bazel build is also promised to produce a hermetic, cacheable plan. Live environment state is not a declared input, and bazel run applies changes to external state. Recommendation: Require an immutable schema snapshot or prior bundle as a declared planning input, and separate the plan artifact from an explicitly authorized apply executable.

Q: What is the declared Bazel input for URL- or registry-backed adapter schemas?

Status: Open

Source: RFC-0032 §§4.6, 7; RFC-0024–0031 adapter contracts Issue: The Bazel rule tracks local specs files and forbids network access during compilation, while the adapters permit live OpenAPI, GraphQL, and Buf sources. A live fetch inside the compiler would be undeclared and non-hermetic. Recommendation: Fetch schemas in a separate pinned repository/input stage and pass immutable snapshots or descriptors to gnomon_client as declared inputs. Make locked builds fail if that snapshot is absent.

Q: Which fingerprints can gnomon_kernel compare?

Status: Open

Source: RFC-0032 §4.3, §10 M32004; RFC-0010 §6.9 Issue: The RFC proposes comparing the SHA-256 of WASM bytes with the fingerprint of a different module bundle artifact. Those byte hashes will differ even for a correct build. It does not define an embedded expected bundle digest or manifest link. Recommendation: Embed the source bundle digest and ABI version in kernel metadata, then verify that metadata against the bundle and storage manifest; hash WASM bytes separately for artifact integrity.