Turn an explicitly selected document into source-linked structural input for downstream interpretation.
- Decompose supported source records without assigning meaning.
- Bind explicit declared input to the exact source revision.
Sensitive input fields are rejected. The consuming language implementation interprets meaning; installation and input binding do not grant an external effect.
Package distribution is not activated by this documentation. Use the checked-in source and the declared dependency versions; published availability must be verified separately.
Install Rust 1.97 or newer and make the declared dependencies available. The generic JSON structure crate resolves from an exact public Zixcel Git revision; other dependencies resolve from crates.io. No private language package, private registry or adjacent checkout is required. Run from this repository:
cargo test --lockedSchemas · Implementation and public interfaces · Verification cases · Contributing · Security reporting · License · Attribution notices
Generic JSON decomposition is owned by zixcel-json-structure in zixcel/document-processing. This role binds source revisions and declared input, preserving source metadata. The public input contains no Sem-lang CompileContext, semantic budget or authority. Language interpretation must add its own explicit context in the language owner. Arrays preserve order instead of being treated as unordered records. The current source interface replaces the private-language-coupled form; no compatibility decoder is retained.
OSS responsibility and source completion defines the supported package boundary and required acceptance. It does not declare unexecuted source, distribution or production checks complete.
Dependency updates: repository policy.
Independent HAT build and release.
The current source package has no linguistic clause frames. Its catalog and foundation dependency digests follow the declared HatSpec source dependency. This source change does not replace previously signed release bytes. A new immutable release identity and consumer acceptance are required before distributing the changed package; language meaning/adoption remains with sem-lang.