Manifest editor schema¶
Download manifest.schema.json beside your manifest and point your YAML editor at it, for example:
# yaml-language-server: $schema=./manifest.schema.json
name: My policies
policies: []
The schema is an editor aid generated from the shipped rule registry and parser declarations. It describes required keys, registered rule names, parameter types, enums, bounds, field paths and nested compound conditions. Optional parameters accept null, matching an unset YAML value. Unknown top-level metadata is accepted; unknown risk classifications remain runtime warnings.
Print the installed engine's schema with kyvvu schema manifest, or validate
a file offline with kyvvu schema manifest --validate policies.yaml. Validation
uses the canonical parser and engine loader. Diagnose configuration with
Kyvvu doctor and exercise policies with
Kyvvu try. The canonical parser and engine
loading remain authoritative. A schema pass alone cannot establish loadability.
| Runtime check | Editor-schema limit |
|---|---|
| Unique policy names | JSON Schema cannot enforce uniqueness of one property across differently shaped objects. |
| Regex compilation and semantic conditions | The engine validates executable rule details when loading policies. |
| YAML/Python numeric representations | JSON Schema follows JSON numeric semantics; integral floats can satisfy its integer type. |
Tests compare this schema with the canonical parser on every public manifest and inputs exercised by the engine's manifest, parameter, unknown-key and field path tests. The duplicate-name case is explicitly retained as a documented editor limitation. No runtime validator is replaced or added by this schema.