feature-registry
For LLMs4 sections
Registry of language versions and feature gates (work package WP-32). Normative source for every implementation: the compiler must require the EXACT language … version and reject a program that uses a semantically active feature it does not know. The registry is data, not code: adding a feature means editing this file plus a migration note.
Versions
Section titled “Versions”Accepted schemaVersion: law.core.features/0.1.
Top-level fields
Section titled “Top-level fields”| name | type-or-$ref | required | description |
|---|---|---|---|
schemaVersion | "law.core.features/0.1" | yes | — |
languageName | string | yes | Canonical language name in the file header: language "<languageName>" version "<version>";. Exactly one spelling — otherwise the “exact version” requirement has no meaning. |
languageVersions | array | yes | — |
features | array | yes | — |
Enumerations
Section titled “Enumerations”| location | values |
|---|---|
properties/schemaVersion | "law.core.features/0.1" |
properties/languageVersions/items/properties/status | "supported", "deprecated", "withdrawn" |
properties/features/items/properties/status | "active", "reserved", "deprecated" |
Raw schema
Section titled “Raw schema”Documentation for Arxo. Writings — blog.arxo.io.
Anonymous visit counts on stats.arxo.io, no cookies.