Get Started

Get Started

First reading path for understanding JustAnIota, the UAI authority boundary, and the tool workflow.

  • Record JAI-GUID-0009
  • Path /get-started/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-GUID-0009
Surface
Get Started
Access
Public and linkable

How to use this page

Use this page to move from orientation into the current UAI-1 reading, validation, and implementation path.

Launch kit

UAI-1Route InventoryStarter Evidence NotesValidator

Fastest Public Path

Zero context to first valid UAI-1 packet

Use the public launch kit in one pass: resolve the adoption kit, pick one profile, validate one packet, test the same packet against the live mock exchange, then carry the result into a named implementation track.

Read boundary

One profile, one contract

Start with UAI-1, then keep the matching schema and registry entry in view so the public contract stays concrete.

Run proof

Validator-backed first evidence

Use one example or candidate message, run the validator, and keep the exported result with the exact records you resolved.

Carry forward

Choose the release lane

Move into Implementations, then attach the release trail through the changelog, news, and contributor handoff pages.

Launch kit

UAI-1Current normative contract.Route InventoryRoute handbook and OpenAPI export.Starter Evidence NotesPublished first-proof bundle and starter files.ValidatorHuman-facing proof run and result export.Mock ExchangeLive reference response surface for one real reply shape.Evidence Pack NotesReusable release packet for launch review.

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.
Starter callsFirst machine checks
curl -s https://justaniota.com/wp-json/uaix/v1/catalog
curl -s https://justaniota.com/wp-json/uaix/v1/schemas/uai.intent.request.v1
curl -s https://justaniota.com/wp-json/uaix/v1/adoption-kit
curl -s -X POST https://justaniota.com/wp-json/uaix/v1/validate -H "Content-Type: application/json" -d @validate-request.json
curl -s -X POST https://justaniota.com/wp-json/uaix/v1/mock-exchange -H "Content-Type: application/json" -d @mock-exchange-request.json

Resolve the catalog first, then one schema, then the adoption kit, then one validator run, then one live mock exchange. That is the shortest machine-facing path into the public record and back out through a real response envelope.

Plain English

Start with what JustAnIota does: it turns compact AI messaging into inspectable pages, tools, examples, and validation records.

Technical summary

Read the product definition, UAI-1 implementation profile, registry model, examples, and validator output before treating any compact message as reusable.

Deep spec

The first decision is authority: UAIX.org controls UAI-1, while JustAnIota controls only its own implementation profiles, interfaces, registry drafts, examples, and release claims.

  • About: understand what JustAnIota is and is not.
  • Specification: review the UAI-1 implementation profile.
  • Registry: see where compact identifiers get controlled meaning.
  • Tools: run the JustAnIota Converter, Concept Bridge, HTML Keyless Extractor, and Validator / Encoder prototypes.
  • Governance: check claim boundaries before repeating support language.