RFC-0014 · 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 makes a committed module.lock stale during a locked build?
Status: Open — owner decision requested.
Context: §7.2 embeds a generated timestamp and §7.3 compares a fresh resolution against current registry state, while §10.2 makes the lockfile authoritative and §9 reserves version refresh for gnomon update. RFC0014_LOCKFILE_PROPOSAL.md recommends deterministic lockfile bytes and M01401 for manifest or locked-graph mismatch, with registry refresh only in an explicit update operation.
Where normative: RFC-0014 §§6–7, 9–11 after reconciliation.
Q: Which imports entry syntax is canonical across RFC-0001, RFC-0008, and RFC-0014?
Status: Open
Proposal: RFC-0001 §4 and RFC-0008 §8.19 specify FQN: "constraint"; RFC-0014 §5 instead shows "FQN" version: "constraint" and assigns M01402 to a missing version: key. The checked-in 62 RFC-style module.gnm manifests use the first form. Make FQN: "constraint" canonical, revise RFC-0014’s example and M01402 wording to mean a missing constraint value, and test both valid entries and an absent value. The exact alternatives and acceptance criteria are in IMPORT_SYNTAX_PROPOSAL.md.
Where normative: RFC-0001 §4, RFC-0008 §8.19, RFC-0014 §5 and §8 — pending owner decision
Q: Registry protocol — what is the registry API contract?
A: RFC-0019 defines the registry API and authentication model. Its §3.3 requires the version-list and manifest endpoints used by RFC-0014 resolution; §5 defines publisher credentials and scoped tokens. Implementations must follow those contracts when resolving or publishing modules.
Where normative: RFC-0019 §§3.3 and 5
Q: Should gnomon lint --semver validate version bumps against the detected change surface?
A: Yes. gnomon lint --semver compares a module’s public surface (exported entity fields, action signatures, policy declarations) against its previous release version and validates that the declared version bump is consistent with the detected change surface. A breaking change with a MINOR bump produces error L01401. A non-breaking change with a MAJOR bump produces warning L01402 (over-bumping is allowed but flagged). gnomon lint --semver is a pre-publish step in the recommended workflow; CI enforcement is optional and module-author-configured.
Where normative: §6 (semver linting) of RFC-0014
Q: How does workspace monorepo resolution interact with the lockfile for local path dependencies?
Status: Open Context: Deferred. The current RFC does not address local path dependencies. Path dependencies require a workspace-level resolution model that affects the lockfile format. Reserved for a future workspace RFC.
Where normative: n/a — pending future RFC or implementation experience
Q: Should pre-release versions require explicit opt-in?
A: Explicit opt-in required. If a pre-release version is the only version satisfying a semver constraint, the resolver MUST NOT select it automatically. The module author MUST opt in by adding --allow-pre-release to gnomon update or by specifying the pre-release version explicitly in the imports block.
Where normative: §5 (resolver behavior) of RFC-0014
Q: Should the lockfile support digest algorithm agility?
A: SHA-256 is normative for the v1 lockfile format. Algorithm upgrade paths are handled via the bundle format version field (RFC-0002 §3): a v2 bundle format MAY specify a different digest algorithm. Implementations that read v1 lockfiles MUST support SHA-256; implementations that read v2 lockfiles MUST support the algorithm declared in the format version header. Cross-version lockfile migration is done via gnomon update --migrate-lockfile.
Where normative: §4 (lockfile format) of RFC-0014