RFC-0019 · 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: When is the local bundle digest computed during publish?
A: Build the deterministic bundle and compute its digest before querying the selected authoritative registry. Equal digests are a no-op; differing digests emit M01901. RFC-0019 §4.1 now orders those steps.
Source: RFC-0019 §4.1 steps 2 and 4; §9 invariants 1–2 Issue: Step 2 compares an existing registry digest to the local bundle digest, but step 4 builds the bundle and computes that digest. The required order cannot be implemented literally. Recommendation: Build the deterministic bundle and compute its digest before the existing-version comparison, then apply the idempotent same-digest rule and immutability error M01901.
Q: Which publish steps does dry-run execute?
A: Dry-run performs the local build, digest, registry lookup, semver lint, and credential resolution. It skips upload and the post-upload confirmation. RFC-0019 §§4.1–4.3 now specify the sequence.
Source: RFC-0019 §4.1 steps 5–7; §4.2 --dry-run
Issue: The CLI description says dry-run runs all validation steps but skips upload. Step 7 reads back the uploaded manifest and checks its digest, which cannot confirm a skipped upload.
Recommendation: Define dry-run as local build, lint, digest, registry lookup, and credential resolution without upload or post-upload confirmation; keep actual publication confirmation mandatory for a normal publish.
Q: What is the canonical private-registry routing configuration?
A: registry.scopes is the canonical prefix-to-URL map. The longest module-ID segment-prefix match wins; otherwise registry.default applies. registry.private is outside this draft contract. RFC-0019 §6 now specifies routing.
Source: RFC-0019 §6.1–6.2
Issue: One example declares registry.private as a single URL while the routing text requires a module-ID prefix; the next example declares prefix-to-URL mappings under registry.scopes. It is unclear whether private is a shortcut, whether both forms may coexist, or how a prefix is attached to the single URL.
Recommendation: Make registry.scopes the explicit routing map and document precedence with registry.default; retain registry.private only if its matching rule is specified for compatibility.
Q: What is the HTTP PUT body for publishing a bundle and manifest?
Status: Open
Source: RFC-0019 §3.3 PUT endpoint; §4.1 step 6; RFC-0002 canonical bundle contract
Issue: The RFC requires one PUT of a .gnomonpkg bundle and manifest but does not define the request media type, field ownership, response, or concurrent-create behavior. An independent CLI and registry cannot interoperate from the current text.
Recommendation: Use the atomic multipart publish request, server-owned publication fields, and conditional create semantics in REGISTRY_UPLOAD_PROPOSAL.md. Amend the RFC and bundle schema together after the owner decides.
Trigger: Approve one request schema and wire format before connecting the HTTP upload adapter or claiming public registry compatibility.
Q: Is the scoped-token JSON example a normative wire schema?
Status: Open
Source: RFC-0019 §5.1–5.3; the RFC-0019 RDF domain projection
Issue: The prose defines short-lived scoped credentials and permitted operations, but only an example supplies tokenId, scope.moduleId, scope.operations, and expiresAt. The RDF projection treats them as a stable record and fields. It also classifies tokens and manifests as Gnomon named declarations, contrary to the domain ontology’s declaration-instance meaning.
Recommendation: Define a token schema with field requirements, scope and expiry semantics, and a separate registry-document class before publishing the RDF identities. Review existing CLI and registry consumers of those shapes and regenerate the projection from the approved source contract.