Source artifact proposal fixtures
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.
These six independently authored expectations compare the separate
SourceArtifact protobuf (repository access required).
They are not canonical AST or compiler conformance fixtures. Expected ranges,
comment kinds, declaration ordinals, and owner assignments were written by
hand; SHA-256 values were computed independently with Python hashlib, not
the parser or source lowering.
The scoped .gitattributes disables newline conversion so checkout preserves
the digest-bound fixtures’ deliberately mixed LF/CRLF and BOM bytes.
| Fixture | Evidence |
|---|---|
comments-utf8 | Exact Unicode/CRLF line text, multiline block text, declaration/comment source order, string exclusion |
leading-docs | Consecutive doc groups, explicit ordinal zero, indentation, CRLF, empty doc line, later owner |
opaque-script | Real header comment retained; comment-looking opaque body excluded |
ownership-refusal | Blank-line owner remains unsupported; exact comments/ranges still retained |
syntax-refusal | BOM preserved in source digest; failed syntax has no guessed comment map |
empty | Empty-file SHA-256, zero size, explicit retained provenance, no fabricated ranges |
Run python3 tools/check_proposed_source.py or emit one artifact with
node tools/parse_proposed_syntax.mjs --source-artifact input.gnm.
SOURCE_PRESERVATION_PROPOSAL.md
records supported ownership, remaining evidence, and acceptance requirements.