gnomonlearn
Docs/RFC-0023/Design Q&A

RFC-0023 · 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 does a static Studio publish a module in embedded WASM mode?

Status: Open

Source: RFC-0023 §§2–4, 6–7; RFC-0019 §4.1 Issue: Studio is a static browser app, but its publish surface says it runs gnomon publish via subprocess or remote API. A browser in embedded WASM mode has no subprocess, and the RFC does not define a browser transport or service that can build, authenticate, upload, and confirm the same bundle as the CLI. Recommendation: Specify a publish adapter per mode with the RFC-0019 build/digest/lookup/lint/auth/upload/confirm sequence and byte-equivalence requirements. If embedded mode lacks a safe adapter, disable publish in that mode and narrow the parity claim.

Q: What happens when both the remote LSP and embedded WASM mode are unavailable?

Status: Open

Source: RFC-0023 §4.3; §8; §9 invariants 5–6 Issue: The RFC requires fallback to WASM whenever the configured mode is unavailable, but also defines M23300 for WASM initialization failure, where editing is unavailable. Invariant 6’s unconditional fallback guarantee cannot hold in that state. Recommendation: Define a visible terminal initialization-error state after a failed fallback, and require the mode guarantee only when WASM initializes successfully.

Q: Which requests are permitted by Studio’s Content Security Policy?

Status: Open

Source: RFC-0023 §§4.1–4.2, 6.3, 7.2 Issue: connect-src is limited to registry and LSP URLs, while the browser must load or fetch its own WASM and assets, may use a publish API, and can receive registry URLs selected by scoped configuration. The RFC does not define how these endpoints enter the policy or which origin supplies credential-bearing publish requests. Recommendation: Specify an allowlist derived from the selected registry, LSP, same-origin assets, and a publish endpoint if one exists. Keep token-bearing requests confined to the selected authoritative registry or an explicitly trusted adapter.