Project manifest syntax reconciliation
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.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
Owner: Language and Tooling. Status: source conflict identified; no manifest contract changed. The owner has not selected a syntax correction.
Evidence
RFC-0008 §8 defines project-decl as project followed by STRING and a
project-body. The body accepts version: STRING, optional imports: and
modules: string lists, and an optional compiler { ... } block. The
generated PEG accepts a minimal manifest of that form.
RFC-0008 §7’s illustrative project "benefits-demo" uses modules [ without
the colon. The checked-in narrative/examples/savvi/project.gnm also uses an
unquoted name, an imports { FQN: version } block, modules [ and
governance [ lists, a description field, and a root ruleCompiler block.
It is not a fixture for the current §8 grammar. RFC-0032 §7 says Gazelle
consumes the modules [] list, and its Lean projection repeats that form.
RFC-0017 refers to compiler.ruleCompiler, which matches the §8 location
but not the checked-in manifest’s root block.
python3 tools/check_peg.py now checks that the §8 form parses and that the
unquoted name and colonless modules form do not. The broader example audit
still reports 0/14 files parsing; this probe does not establish compiler
conformance or settle the other sample constructs.
Recommended first-release contract
Keep a quoted project name and a nested compiler {} block, as both §7 and
§8 already describe them. Keep modules as a list of module directories, as
RFC-0032 and the project example describe it. Choose one punctuation rule
for that list and apply it in §7, §8, RFC-0032, Lean, generated catalogs, the
sample manifest, and the compiler. The §8 modules: form is the smallest
source correction, but the owner should decide whether the list syntax is
colonless for consistency with other DSL list blocks. Decide whether project
imports are supported and, if so, whether they are versioned map entries or
a string list. Remove or formally define the sample-only description,
governance, and root ruleCompiler fields.
Acceptance
- One RFC-0008 project grammar and its illustrative example parse the same manifest; RFC-0032 describes that exact form.
- The checked-in
project.gnmeither migrates to the chosen syntax or is explicitly marked historical and excluded from conformance examples. - Lean grammar catalogs, RDF source claims, generated references, PEG, compiler fixtures, and LSP project loading agree on field locations and diagnostics. Positive and negative fixtures cover project name, module list, imports, compiler settings, and unknown fields.
- The complete authored example audit and compiler-backed fixture gate pass before normative publication.