Document families
Current fixture areas include text, JSON, JSONC, TOML, YAML, Markdown, and source-language families.
Conformance corpus
Fixtures keep the contract honest.
The fixture corpus records expected behavior for document families and implementation capabilities. It is shared across implementations instead of belonging to one engine.
Diagnostics
Cases can describe parse failures, unsupported capabilities, active policies, skipped cases, and unresolved review state.
Backends
A family can support more than one backend. Backend restrictions are declared explicitly instead of changing the family contract silently.
Interchangeable implementations
An implementation can be written in any language. The initial set of implementations includes Go, TypeScript, Rust, and Ruby. What matters is whether each implementation consumes the shared rules and fixtures and reports behavior in the expected shapes.
That keeps the project from depending on one runtime, parser, or library namespace.
Fixture roles
- Define portable expected behavior
- Expose capability boundaries
- Support named suites and manifests
- Make skipped cases visible
Want to inspect the current corpus?
Browse fixtures on GitHub