Parent and roadmap
Outcome
Measure the current archetype/map pipeline and select constrained YAML 1.2 or JSONC using the shared lossless corpus rather than preference alone.
Scope
Superseded path / cleanup target
Remove no production parser yet. The decision must identify which implicit types, aliases/tags, duplicate keys, and ambiguous custom fields the new syntax rejects.
Acceptance criteria
Validation baseline
Before: the current format and performance are understood through several incomplete implementations.
After: the project has one measured syntax decision and a complete runtime grammar baseline.
Run both syntax prototypes across the shared corpus, malformed fixtures, and Linux/Windows parser tests where applicable.
This issue is a bounded child of atrinik/atrinik#166. The parent remains open until every sibling child is complete.
Ownership boundary
#17 exclusively owns grammar discovery, consumer inventory, and the parity corpus. This issue begins from those outputs and owns constrained YAML-versus-JSONC prototypes, reproducible performance/safety measurements, the authored-syntax decision, and documented parser limits.
Parent and roadmap
Outcome
Measure the current archetype/map pipeline and select constrained YAML 1.2 or JSONC using the shared lossless corpus rather than preference alone.
Scope
Superseded path / cleanup target
Remove no production parser yet. The decision must identify which implicit types, aliases/tags, duplicate keys, and ambiguous custom fields the new syntax rejects.
Acceptance criteria
Validation baseline
Before: the current format and performance are understood through several incomplete implementations.
After: the project has one measured syntax decision and a complete runtime grammar baseline.
Run both syntax prototypes across the shared corpus, malformed fixtures, and Linux/Windows parser tests where applicable.
This issue is a bounded child of atrinik/atrinik#166. The parent remains open until every sibling child is complete.
Ownership boundary
#17 exclusively owns grammar discovery, consumer inventory, and the parity corpus. This issue begins from those outputs and owns constrained YAML-versus-JSONC prototypes, reproducible performance/safety measurements, the authored-syntax decision, and documented parser limits.