Validator errors should be treated as typed evidence. The goal is to move from a path-aware failure to a concrete fix without guessing or widening a support claim.
What the validator is checking
| Layer | What can fail | Where to look next |
|---|---|---|
| Schema alignment | The selected profile does not match required envelope or body fields. | Open the profile schema and the UAI-1 message model. |
| Registry resolution | A profile, error code, conformance level, transport binding, trust channel, or compact value is not published. | Open the registry, field registry, error registry, transport bindings, trust channels, or conformance levels. |
| Delivery policy | Async acceptance, task references, acknowledgement, expiry, or retry posture conflicts with the expected profile behavior. | Check delivery semantics and transport-binding records. |
| Trace and provenance | Trace context, issued time, log reference, source lineage, or evidence links are missing or malformed. | Check provenance fields and W3C trace-context expectations where relevant. |
| Trust channel | Credentialed, signed, DID/VC, or authenticated context is absent, malformed, or inconsistent with the declared channel. | Check trust-channel records and avoid exposing secrets in evidence. |
| Integrity | Canonicalization, algorithm, checksum, or canonical-hash equivalence does not match the exact payload. | Regenerate the integrity record from the reviewed payload and keep the conformance output. |
| Capability statement policy | A capability statement omits supported transports, trust channels, profiles, operations, or conformance levels. | Compare the statement to UAIX capability and conformance records. |
| Typed error policy | An error body uses an unpublished code or lacks the shape expected for uai.error.v1. |
Open the UAIX error registry and correct the error record. |
Error families
| Error family | Likely meaning | Fix path |
|---|---|---|
| Missing field | A required envelope or body field is absent for the selected profile. | Check the profile schema, then add the missing value with source and review context. |
| Type mismatch | A value exists but does not match the expected scalar, object, array, enum, date, or URI shape. | Correct the value shape before changing registry or policy fields. |
| Registry mismatch | A compact value, profile, error code, transport, trust channel, or conformance level does not resolve. | Refresh against canonical UAIX records and avoid local aliases. |
| Undeclared field | The payload includes extra keys outside the profile schema or compact field registry. | Move the data into an allowed field, a declared extension, or remove it from the exchange evidence. |
| Trace context failure | Traceparent or trace-related fields are absent or malformed for the intended evidence path. | Use a valid trace context or mark the provenance gap explicitly. |
| Trust evidence failure | The declared trust channel is not backed by expected principal, credential, signature, or replay-window context. | Correct the trust evidence or lower the trust claim. |
| Integrity failure | A checksum, canonical hash, or canonicalization record does not match the exact payload. | Recompute from the exact payload after all edits are complete. |
Debugging workflow
- Do not patch blindly. Read the JSON path, code, severity, and linked public artifact first.
- Fix outer structure first. Resolve profile, version, message ID, source, target, and body shape before policy-level errors.
- Resolve registries from UAIX. Avoid copying old examples or local aliases into a payload.
- Retest the exact payload. Integrity evidence should be created after the final payload shape is known.
- Save the result. Keep validator output or a conformance record with CI logs, release notes, or handoff evidence.
What a passing result does not prove
A passing validation result does not certify an organization, prove a whole implementation, or make LlmWikis an authority for UAI-1. It shows that the candidate artifact passed the checks exposed by the current UAIX validator path. Implementation support still depends on source records, release evidence, and current UAIX roadmap/changelog boundaries.