gnomonlearn
Docs/RFC-0001/Design Q&A

RFC-0001 · 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: Should strict mode reject unknown keys by default?

A: Yes. Unknown keys in .gnm declaration bodies MUST produce error M01070 in all modes. There is no “strict mode” toggle — unknown keys are always an error. The parser is not lenient; unrecognized syntax signals either a typo or a version mismatch between author tooling and compiler version.

Where normative: §3 (parser and diagnostics) of RFC-0001

Q: Which declaration classes require mandatory schema references?

A: All top-level declaration kinds (entity, action, flow, policy, facet, aspect, agent, view) MUST declare meaning: at the declaration level (M01071: missing meaning on top-level declaration). Inline declarations (fields, relation entries, operation entries within a declaration body) do not require meaning:. The module declaration itself does not require meaning: — it is structural, not semantic.

Where normative: §4 (declaration kinds) of RFC-0001

Q: What is the minimum authoring profile required for M0 parity?

A: M0 parity requires a module with: at least one entity declaration, at least one action declaration, at least one flow declaration with at least one state, at least one policy declaration, and a module.gnm manifest with valid version, type, objects, and operations lists. A module without a view declaration compiles but produces warning M03220 for each app bundle route that has no corresponding view.

Where normative: §5 (module structure) of RFC-0001

Q: Should module-type declaration be enforceable via schema validation, or warnings only?

Status: Open Issue: RFC-0001 §4 and §5 assign M01001 to a missing or invalid module type, while its §9 diagnostic table assigns M01072 to an invalid value. M01060 means the manifest has the wrong number of module declarations, not a missing type. The authored backend-only and UI-only rules use M01002 and M01003; this older answer instead names unallocated M01073 and M01074 and describes a different UI-only condition. Recommendation: Keep M01001 for a missing type, use the already listed M01072 for an invalid value, and retain the authored M01002/M01003 module-class rules. Align §4, §5, §9, Lean, RDF, compiler diagnostics, and tests after the owner decides. The alternative is to use M01001 for both missing and invalid values and retire M01072 explicitly.

Where normative: RFC-0001 §§4, 5, and 9 — pending owner decision