Validate before render.

Validation

Producer rules

• Validate against /protocol/v1/schema.json before sending events to a renderer.
• Use one public semantic channel: nominal, advisory, warning, critical, recovery, opportunity, or handoff.
• Keep VET, intensity, hue, and pulse normalized inside the schema ranges.
• Put renderer-safe context in metadata; keep private formulas and substrate out of public events.
• Treat examples as fixtures, not as permission to publish private operational data.

{
  "schema": "https://vibenet.ai/protocol/v1/schema.json",
  "command": "ajv validate -s public/protocol/v1/schema.json -d event.json",
  "expected": "valid Signal Contract event"
}

Renderer expectations

Consumers should stay predictable.

• Renderers may ignore optional metadata, but they must respect required flat fields.
• Renderers should degrade gracefully when audio is blocked or reduced motion is requested.
• Renderers should not invent private channel codes or expose protected substrate in public UI.
• Receipts should preserve event id, producer, entity, occurred_at, and schema_version for audit.

Example arc

Validate the recovery arc, not just a happy path.

The public demo fixture is useful because it includes productive work, a waste loop, an unsupported claim, a grounding failure, handoff, and recovery. Conformance should preserve that distinction instead of flattening every event into success or failure.

• Waste loop: repeated tool calls can stay valid while channel shifts to warning.
• Unsupported claim: a critical event can show rising valence while confidence drops.
• Recovery: claim retraction and task completion should resolve tension without inflating confidence.