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

About / What It Is

References and Contributors

Citation, attribution, and source-boundary guidance for ɩ.com and JustAnIota.com.

  • Record JAI-ABOU-0011
  • Path /about/references/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-ABOU-0011
Surface
About / What It Is
Access
Public and linkable

How to use this page

Use this page when you need the main public links, discovery files, attribution details, and citation pointers for UAIX.

Handoff links

GovernanceChangelogRoute InventoryImplementations

Public Handoff

Use this page as the durable citation, discovery, and contributor packet

Treat References and Contributors as the current public handoff surface while broader repository, issue-tracking, and contact channels remain future work.

Current truth

Carry the exact public record forward

Use this page when another reviewer needs canonical links, discovery routes, release-trail context, and attribution without relying on screenshots or unpublished notes.

Contributor intake

Requests are documentation-led today

Point contributors to the affected record family, canonical path, change type, and attached validator or implementation evidence before treating the request as ready for review.

Repository status

State the current handoff honestly

The public handoff is the published page surface, implementation tracks, packaged artifacts, and release notes, not a separately published source repository or issue queue.

Handoff links

GovernanceAuthority and release-discipline posture.ChangelogMigration posture and dated release truth.Route InventoryMachine-facing discovery and route inventory.ImplementationsPublic support lanes and release evidence.
Discovery routesCanonical public handoff endpoints
https://justaniota.com/.well-known/uaix.json
https://justaniota.com/sitemap.xml
https://justaniota.com/wp-json/uaix/v1/catalog

Use canonical discovery routes and public machine manifests rather than screenshots, local mirrors, or query-string aliases.

Handoff map

How ownership, contributor intake, repository status, and discovery handoff work today

Use this matrix when another reviewer or contributor needs the current public handoff packet without depending on private notes, screenshots, or unpublished repositories.

Operating areaPublished nowVerify hereNot yet public
Ownership and attributionOne named public attribution plus aligned canonical pages, machine-readable records, validator behavior, implementation evidence, and the release trail establish current public truth.A broader reviewer roster, steering group, public contact desk, or certification authority is not yet published.
Contributor intakeContributor requests are documentation-led: identify the affected record family, attach the canonical path and record code, state the change type, and carry validator or implementation evidence when behavior changes.A public issue tracker, mailing list, forum, or RFC portal is still future work.
Repository and issue-tracking statusThe public handoff is the published implementation-track surface and packaged artifact family, not a separate public source repository or package registry claim.A public repository handoff, issue feed, wider SDK set, or broader implementation showcase remains future work until it is published.
Citation and discovery packetCanonical locale-prefixed pages, page-level record codes, .well-known manifests, sitemaps, and the machine-facing route catalog are the current citation and discovery surface.Do not rely on query-string aliases, screenshots, or unpublished mirrors as the public record.
Release-evidence handoffA complete handoff should carry the validator or implementation evidence, the affected canonical records, and the matching release-trail links together.A broader adoption portal, implementation showcase, or institutional contact program is not yet part of the current public handoff.

Until a public repository, issue desk, or contact channel is published, the durable handoff is the canonical site plus the named release evidence attached to it.

Public handoff packet

What a public handoff packet should contain

Use this sequence when another reviewer, contributor, or adopter needs the current public record without relying on private context.

  1. Step 1

    Link the canonical page and record code

  2. Step 2

    Carry the exact artifact set

  3. Step 3

    Attach discovery and citation routes

  4. Step 4

    State ownership and repository status honestly

  5. Step 5

    Point to the release trail and support boundary

Until a public repository or contact desk is published, the handoff packet is the site itself plus the exact artifacts, release links, and support boundaries attached to it.

Plain English

Cite JustAnIota by page path, record title, and the visible ɩ.com brand when you refer to this site.

Technical summary

References should distinguish JustAnIota implementation records from UAI protocol authority at UAIX.org.

Deep spec

Do not cite screenshots, draft prompts, or inherited source documents as current public truth when a canonical JustAnIota page exists.

Citation rule

  • Visible brand: ɩ.com.
  • Canonical host: JustAnIota.com.
  • Protocol boundary: UAIX.org controls UAI-1.
  • Current attribution: Michael Joseph Kappel, MCP.