UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Guides

UAIX Talisman Client

Download and configure the UAIX-published WordPress client-node package for protected-anchor readout, hub sync evidence, and request-only talk-back without plugin-local .uai memory.

  • Record UAIX-DOC-3283
  • Path /en-us/guides/uaix-talisman-client/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-3283
Surface
Guides
Access
Public and linkable

How to use this page

Use this page as part of the current Guides public record, then follow its linked standards pages for the next step.

Use with

Talisman SystemAI Memory Package WizardProject HandoffRoadmap

Talisman Client

Sync evidence, preserve human review

Download the UAIX-published WordPress client-node package for protected-anchor readout, hub sync evidence, and request-only talk-back without plugin-local .uai memory. UAIX owns official Talisman client and ecosystem-manager plugin/package lines, development, and distribution for WordPress, PHP, .NET, and Python.

Ownership

UAIX owns official tooling

Official uaix-talisman-client and uaix-talisman-ecosystem-manager specifications, guidance, public docs, package docs, validators, package behavior, standards alignment, and WordPress/PHP/.NET/Python plugin/package development and distribution stay under UAIX authority.

Receiver

Use the site .uai root

Receiver sites keep their own .uai files at site level; the client package does not ship plugin-local .uai memory.

Evidence

API success is not approval

Sync, messages, and acknowledgements are evidence for human review, not protected-anchor mutation or publication authority.

Boundary

No SDK or certification claim

The package is not an SDK, CLI, hosted importer, OpenAI adapter, certification, endorsement, or automatic repository writer. Ecosystem Talisman sites may publish exact redacted implementation examples in all software languages for their own configuration without passwords, private keys, tokens, secrets, private endpoints, or credentials, but that does not transfer UAIX package distribution authority.

Use with

Talisman SystemProtected-anchor governance.AI Memory Package WizardGenerate site-level .uai files.Project HandoffKeep receiver guidance outside the plugin package.RoadmapCheck planned support before widening claims.
Review RuleTalk-back is request-only
API success is not approval; client talk-back can request human review but cannot mutate protected anchors. UAIX owns official Talisman client/manager distribution; Teleodynamic-style examples must omit secrets and remain ecosystem-specific evidence.

Use this line when a client sync or acknowledgement could be mistaken for approved execution.

UAIX.org publishes the UAIX Talisman Client WordPress package as the canonical public download for this client line. Use it when a WordPress receiver node needs to read its own protected anchors as data, send bounded sync or status evidence to a Talisman hub, and produce request-only talk-back without directly mutating protected anchor files.

Download the UAIX Talisman Client WordPress package. The current client package is uaix-talisman-client-v0.1.27.zip with SHA-256 037D6698C78EC3A089581FC69656ACED5714BF39E115B69B3988D28FC0B48552.

What the client does

  • Reads configured .uai/totem.uai, .uai/taboo.uai, .uai/talisman.uai, and selected local .uai files as data-only evidence.
  • Builds bounded sync packets for a configured Talisman hub.
  • Stores received policy or instruction evidence locally for administrator review.
  • Provides REST routes for admin-authorized status, messages, and instruction retrieval.
  • Uses no-op/talk-back behavior when a request conflicts with protected-anchor boundaries.

Package boundary

  • The UAIX-published package does not ship plugin-local .uai memory. Receiver sites use their own site-level .uai folder.
  • The client may report, propose, acknowledge, or request review. API success is not approval, execution, incident closure, protected-anchor mutation, publication, credential validation, runtime safety certification, model training, AGI, consciousness, sentience, or biological equivalence.
  • Changing totem.uai, taboo.uai, or talisman.uai still requires a separate human-governed apply event with review and audit evidence.
  • This package is not an SDK, CLI, hosted importer, official adapter, certification program, endorsement, automatic repository writer, automatic remediation system, or automatic LLM Wiki sync service.

Install and configure

  1. Upload uaix-talisman-client-v0.1.27.zip through WordPress Plugins > Add New > Upload Plugin.
  2. Activate the plugin, then open Settings > UAIX Talisman Client.
  3. Confirm the hub URL, ecosystem key, node key, local .uai root, and protected-anchor paths match the receiving site.
  4. Keep each receiver site’s project memory in its site-level .uai folder, not in the plugin directory.
  5. Treat sync, message, and acknowledgement responses as evidence for human review, not as authority to apply protected changes.

Use beside current UAIX records