We build compact AI messaging tools.
JustAnIota official shield mark JustAnIota UAI tooling ɩ.com Compact AI messaging tools Language-neutral AI messaging: registries, schemas, validation.
Draft IOTA-1 tools
  • Current surface JustAnIota tooling draft
  • Plain-English definition Compact, structured AI messaging tools
  • Current attribution Michael Joseph Kappel, MCP
  • Short-domain status ɩ.com redirects to JustAnIota.com

Implementation / Dev Docs

Implementation / Dev Docs

Developer documentation for building JustAnIota tooling on top of UAI without redefining the protocol.

  • Record JAI-IMPL-0025
  • Path /implementations/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-IMPL-0025
Surface
Implementation / Dev Docs
Access
Public and linkable

How to use this page

Use this page to choose the publication or runtime path that fits your environment and release needs.

Support evidence

ValidatorEvidence Pack NotesGovernanceNews

Support Boundary

Read named implementation tracks as the current public implementation claim

Treat the published implementation tracks as the only current public software support lanes until wider repository, SDK, or showcase programs are formally published.

Evidence first

Validator and pack evidence travel with support claims

A runtime or package becomes supportable only when its public release record, validator evidence, and implementation notes stay aligned.

Published now

Use the named tracks and packaged artifacts

Point readers to the current implementation-track pages and attached release evidence before implying a broader public repository or SDK program.

Future work

Wider showcases need published handoff first

Additional SDKs, issue feeds, community submissions, or broader implementation showcases should not count as public support until they are formally published here.

Support evidence

ValidatorHuman-facing conformance review.Evidence Pack NotesReusable packet for release review.GovernanceChange-handling and support-claim posture.NewsPublic release summaries attached to implementation work.

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

Implementation pages explain how to build and test JustAnIota tools.

Technical summary

Developers should keep UAI ownership, route behavior, registry versions, schemas, validation reports, and release notes aligned.

Deep spec

Reference implementations should publish fixtures before public support claims. A working local prototype is not a certification badge or protocol endorsement.

Developer surfaces

  • WordPress publication surface for canonical pages and locale routing.
  • Browser tools for first-pass validation, HTML extraction, and encoding review.
  • .NET bridge planning for strict parsing and service integration.
  • Fixture and evidence packs for future regression checks.