Schema validation boundary

The schema provider gives rules a stable, file-first validation boundary before telemetry enters customer systems.

Current configuration

The nginx module remains a build and design scaffold. The implemented daemon-side provider is enabled through:

[schema]
enabled = true
config_ref = "file:/etc/nginz-iot/integration-edge.schemas"

Schema and rule candidates reload together. References support exact or latest bounded versions, checksums, and stable failure reasons.

Dialect boundary

The current nginz-json-object-v1 dialect validates JSON objects, required fields, and basic property types through the configured broker payload ceiling.

It is deliberately not a published JSON Schema draft, Protobuf registry, or Avro registry. Do not describe it as standards-complete schema support. Those providers remain future work.

A valid subject record includes a bounded identifier, version, checksum, and the object dialect body. Rules reference latest or an exact version. Candidate schema and rule files reload together; a parse failure keeps the last good pair.

Schema validation is available only in the Max and Enterprise lanes. Inspect loaded subjects from the console Rules page or the operator CLI (ngz-iot schemas).