Schemas

Schemas

Shape rules for JustAnIota envelopes, registry references, validator input, and export records.

  • Record JAI-SCHE-0017
  • Path /schemas/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-SCHE-0017
Surface
Schemas
Access
Public and linkable

How to use this page

Use this page for the published schemas that check UAI-1 messages before release.

Proof path

Validator-backed proof path

Keep the public reading order tied to one evidence trail: profile, schema, example, validator result, and release record.

  1. 1Pick a message profile.Start with a published UAI-1 profile and the record family that matches the exchange you need to prove.
  2. 2Compare it with schemas and examples.Resolve the schema, registry entry, and one fixture before writing or mapping your candidate packet.
  3. 3Run validator evidence.Validate keyed, minified-keyed, or keyless JSON against the current public UAI-1 records.
  4. 4Attach the result to implementation or handoff records.Carry the exported result into implementation notes, changelog entries, or Project Handoff evidence.

Plain English

Schemas check whether a message has the right shape before anyone interprets its meaning.

Technical summary

They require fields such as profile, UAI target version, locale, normalization, registry, and payload, then leave semantic interpretation to registry and validator layers.

Deep spec

A schema cannot prove semantic correctness by itself. It proves structure; registry lookup and validation prove whether a compact mapping is acceptable for the declared profile.

Schema jobs

  • Reject missing required metadata.
  • Separate readable source forms from compact export forms.
  • Preserve validator reports as evidence instead of hidden state.
  • Allow future server-side validators without changing the page structure.