Repository navigation
Description
Parent and roadmap
- Parent tracker: Proposal: adopt schema-driven map/archetype sources and compiled runtime caches atrinik#166
- Roadmap: Roadmap: replace classic Atrinik with a fresh MIT Go and Rust stack atrinik#168
- Roadmap milestone: M1
- Prerequisites: Content tooling: establish grammar contracts and a lossless parity corpus #17
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
- Consume Content tooling: establish grammar contracts and a lossless parity corpus #17's reviewed grammar/load-mode and producer/consumer inventory as the fixed baseline; record only syntax-prototype findings that require an explicit decision or correction back in Content tooling: establish grammar contracts and a lossless parity corpus #17.
- Measure archetype startup/RSS and cold/warm map load, swap/reload, checker, and collection performance across representative sizes.
- Prototype constrained YAML and JSONC for comment/span retention, deterministic formatting, hostile-input bounds, cross-language support, and review quality.
- Publish the syntax decision and explicit parser limits; preserve stable logical map IDs independently of filename suffixes.
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
- Content tooling: establish grammar contracts and a lossless parity corpus #17's reviewed grammar, load-mode, consumer inventory, and parity corpus are used unchanged as the evaluation baseline.
- Reproducible baseline measurements exist for startup, map entry, swapping, checking, and collection.
- The authored syntax decision is evidence-backed and documents all safety bounds.
- The selected syntax round-trips the shared corpus without unexplained semantic loss.
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.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
[-]Content schema: inventory runtime grammar and select the authored syntax[/-][+]Content schema: prototype and select the authored syntax[/+]github-actions commentedon Aug 7, 2026
🎉 This issue has been resolved in version 1.6.0 🎉
The release is available on:
v1.6.0Your semantic-release bot 📦🚀
feat(content): select strict JSONC authored syntax (#38)