Activity vocabulary, declarations and lossless history pages. Lifecycle stays in the engine.

Markdown comments shared by the Companion and TUI. Resolved history remains body text.

Vis configuration vocabulary and JSON Schema validation.

Canonical content validation from JSON Schema.

Versioned code diffs keep exact patch text separate from human review comments.

Loads canonical JSON Schemas and validates payloads against their roots or definitions.
`schema/common.json` supplies shared definitions. Raw validators reject values outside
the JSON data model; engine adapters may normalize keyword maps before validation.

Gateway payload schemas and their HTTP transport metadata.

Editable Improve records and immutable source links, validated by JSON Schema.

Renders the gateway payload schemas and HTTP metadata as OpenAPI 3.1.
Extension routes remain in their extension-owned contracts.

Version-addressed planning artifacts and explicit review actions for both clients.

Provider limits vocabulary and report validation from JSON Schema.

JSON Schema contract for language-tool results.

Language-neutral test selection and result contract, validated by JSON Schema.

Feature-toggle vocabulary and contribution validation from JSON Schema.

View vocabulary and JSON Schema validation.

Canonical value and JSON codecs shared by Core, the gateway and every SDK.

This namespace is a pure deterministic boundary: it performs no transport,
filesystem, process or lifecycle work. Engine EDN becomes total JSON data;
in-process readers receive exactly the shape a remote JSON reader receives.