RFC-0023 · Reference catalog
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.
Generated reference catalog. This page renders structured Lean data for RFC-0023: defined terms, diagnostics, dependencies, and invariants. It does not establish proof coverage or runtime conformance. The authored narrative lives in
RFC-0023.This page is generated from the
lean/Gnomon/Spec/module for RFC-0023. Edit that source and regenerate this catalog.
Title: Gnomon Studio — In-Browser Authoring Environment
Status: draft
Owners: DX
Diagnostic range: M23300-M23399
Proof citations in source: 11 / 11. Standalone proof verification is pending.
Definitions
(none defined)
Diagnostics
| Code | Severity | Description |
|---|---|---|
M23300 | Error | Studio WASM module failed to initialize; editing features unavailable. |
M23301 | Warning | Semantic preview panel update exceeded the 2-second latency budget. |
M23302 | Warning | Language server returned a diagnostic code not present in the allocated diagnostic table. |
Invariants
- A Studio build that omits any normative panel (file tree, editor, semantic preview, problems) is non-conformant.
- A Studio deployment that does not serve a conformant Content Security Policy is non-conformant regardless of runtime behavior.
- All Studio language features MUST be backed by the same RFC-0017 protocol surface as the VS Code extension; Studio MUST NOT implement language features independently.
- If the configured LSP mode is unavailable, Studio MUST fall back to WASM mode rather than failing to open, with the fallback visibly indicated to the author.
- Session credentials MUST NOT be written to persistent storage; loss of credentials on tab close is expected behavior. (enforced by: runtime)
- Studio MUST NOT execute .gnm declarations against live state; only analysis (compilation, type inference, semantic preview) is permitted. (enforced by: compile-time + CSP)
- The Studio publish flow MUST produce the same outcome as gnomon publish for the same module and credentials and MUST NOT bypass any CLI-enforced gate.
- The semantic preview panel MUST update within a 2-second latency budget from keystroke to updated preview under normal conditions.
Normative Statements
Statements are structured source data. Proof citations, where present, have not passed a standalone Gnomon proof gate.
Goals
- MUST_NOT — Studio MUST NOT execute .gnm source code; it may compile, type-check, and render semantic previews but MUST NOT invoke agent bindings or apply install plans.
- MUST — Studio MUST be implementable as a static single-page application with no server-side rendering requirement.
- MUST — Studio MUST provide an authoring experience functionally equivalent to VS Code with the Gnomon extension, powered by the same language server.
- MUST — Studio MUST work in two modes: embedded WASM language server and remote LSP over WebSocket.
- MUST — The publish flow in Studio MUST be identical in outcome to running gnomon publish from the CLI and MUST NOT bypass the semver lint gate. (proof citation:
rfc0023_b27_grounded; verification pending) - MUST — The semantic preview panel MUST update reactively as the author types within a 2-second latency budget under normal conditions.
Invariants
- MUST — A Studio build that omits any normative panel is non-conformant. (proof citation:
rfc0023_b18_grounded; verification pending) - MUST — A Studio deployment that does not serve a conformant Content Security Policy is non-conformant. (proof citation:
rfc0023_b37_grounded; verification pending) - MUST — All language features in Studio MUST be backed by the same RFC-0017 protocol surface as the VS Code extension; Studio MUST NOT implement language features independently. (proof citation:
rfc0023_b1_grounded; verification pending) - MUST — If the configured LSP mode is unavailable, Studio MUST fall back to WASM mode and the fallback MUST be visibly indicated to the author.
- MUST_NOT — Session credentials MUST NOT be written to persistent storage. (proof citation:
rfc0023_b23_grounded; verification pending) - MUST_NOT — Studio MUST NOT execute .gnm declarations against live state; analysis is permitted, execution is not.
- MUST — The Studio publish flow MUST produce the same outcome as gnomon publish for the same module and credentials and MUST NOT bypass any gate the CLI enforces. (proof citation:
rfc0023_b13_grounded; verification pending)
Language Server Integration
- MUST — If the WebSocket connection fails or is not configured, Studio MUST fall back to wasm and display a status indicator.
- MUST_NOT — Studio MUST NOT silently degrade without notifying the author. (proof citation:
rfc0023_b25_grounded; verification pending)
Module Publish Flow
- MUST_NOT — Studio MUST NOT provide a ‘skip lint’ toggle in the publish UI. (proof citation:
rfc0023_b7_grounded; verification pending) - MUST — The semver lint gate MUST run on publish; if it blocks, the panel displays the blocking lint codes and does not proceed. (proof citation:
rfc0023_b3_grounded; verification pending)
Panel Layout Contract
- MUST — File tree context menu MUST support new file, rename file, and delete file, and these operations MUST be reflected in the language server’s incremental model.
- MUST — Implementations MUST provide the file tree, editor, semantic preview, and problems panels; all panels MUST be present and reachable. (proof citation:
rfc0023_b20_grounded; verification pending) - MUST_NOT — The editor MUST NOT allow arbitrary script execution.
- MUST — The editor MUST display diagnostic codes inline with hover detail including the diagnostic message and a link to the relevant RFC section.
- MUST_NOT — The semantic preview MUST NOT render synthetic data or execute any rules; it is a structural display, not a live runtime preview.
Security Constraints
- MUST — Future Studio features that require live data interaction MUST be defined in a separate RFC with explicit security review.
- MUST_NOT — Session credentials MUST NOT be written to localStorage, sessionStorage, IndexedDB, cookies, or any persistent storage; they are cleared when the Studio tab is closed. (proof citation:
rfc0023_b9_grounded; verification pending) - MUST_NOT — Studio MUST NOT execute .gnm source code in the browser, including invoking agent bindings, applying install plans, or invoking action declarations against live data.
- MUST_NOT — Studio MUST NOT request broad filesystem access beyond the module root; mounted directories MUST NOT traverse parent directories.
- MUST — Studio’s HTML shell MUST be served with a strict CSP prohibiting inline scripts, eval, and new Function, and restricting connect-src to the configured registry and LSP WebSocket URL.
What Studio Is and Is Not
- MUST_NOT — Studio MUST NOT invoke agent bindings or apply install plans.
Linked References
(no cross-RFC dependencies)