Use the canonical UAIX validator when a candidate UAI-1 exchange needs public evidence. LlmWikis can explain the workflow; UAIX defines validator behavior.
Before validating
- Know which UAI-1 profile the message claims to use.
- Keep the exact payload that will be reviewed or released.
- Check whether registry, schema, trust, and provenance references are current.
- Do not treat a local helper result as canonical UAIX validator behavior.
Check profile
Start by confirming the message declares the intended UAI-1 profile. The profile determines which fields and validation expectations apply.
Check required fields
Confirm required envelope, delivery, trust, provenance, and integrity fields before debugging deeper behavior.
Check registry references
Resolve referenced names and compact values against canonical UAIX records instead of local aliases or stale examples.
Check provenance and integrity
Make sure source lineage, trace context, and integrity anchors describe the exact payload being reviewed.
- Choose the intended UAI-1 profile and gather the candidate JSON payload.
- Validate against the UAIX validator route or tool surface.
- Read typed, path-aware errors before changing the payload.
- Resolve field, registry, trust, provenance, and integrity failures against canonical UAIX records.
- Keep the validation result with the release or handoff evidence.
Read validator errors
| Error family | Likely next page | Action |
|---|---|---|
| Missing or invalid field | UAI-1 Message Model | Check the expected field shape before editing. |
| Registry mismatch | UAIX Registry | Refresh the canonical record and avoid local aliases. |
| Trust or provenance issue | Glossary and UAIX trust records | Confirm sender, source, credential, trace, and lineage context. |