The Validator Workbench is explained here as a workflow. UAIX owns the canonical validator behavior and evidence route; LlmWikis shows how to preserve the result in a reviewable project record.
Workbench jobs
| Workflow | Output | What to save |
|---|---|---|
| Load a starter example | Known-good profile payload from the public example route. | Example URL, profile, and date checked. |
| Validate candidate message | Pass/fail result against profile schema, registry, field order, policy, trust, provenance, integrity, and conformance checks. | Validator request and validator result. |
| Inspect typed errors | Path-aware diagnostics that point to missing, invalid, extra, unresolved, or policy-breaking fields. | Error code, JSON path, severity, linked artifact, and fix note. |
| Resolve against registry | Canonical records for profiles, fields, errors, transports, trust channels, and conformance levels. | Record URLs used while debugging. |
| Export conformance evidence | A portable uai.conformance.result.v1 record when the validator exposes one. |
Conformance result beside release, CI, or handoff evidence. |
| Run mock exchange | A deterministic reference response shape after a passing request. | Mock request and response payloads. |
Operator sequence
- Choose the profile. Start with the exact profile family, not a general idea of the message.
- Load a fixture. Compare the candidate payload to a published UAIX example or adoption-kit packet.
- Run validation. Save the exact request and result before editing the payload again.
- Fix by layer. Schema first, then registry, delivery, trust, provenance, integrity, and policy issues.
- Export evidence. Keep any conformance record with the implementation evidence trail.
- Record limits. Say what the validation did and did not prove before a page, release, or handoff uses the result.
Evidence interpretation
| Output | Strong statement | Unsafe overstatement |
|---|---|---|
| Validator pass | This exact payload passed current public validator checks. | The whole implementation is certified or endorsed. |
| Validator warning | The payload can be inspected, but a specific support or evidence weakness remains. | Warnings can be ignored because the payload is usable. |
| Conformance record | The result links a checked artifact to public schema, registry, validator, and conformance references. | The organization has full UAI-1 conformance for all workflows. |
| Mock exchange | The reference surface can produce a deterministic example response for a supported scenario. | The mock route proves production runtime behavior for a third-party system. |
Workbench notes for LLM Wikis
When a wiki page discusses validator behavior, store the exact validator route, checked profile, result date, and conformance output path. If the page only explains a workflow, mark it as non-normative and point to UAIX for current behavior.