UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIXUniversal Artificial Intelligence ExchangePublic standards publication
CurrentUAI-1 v1.0
  • Current versionUAI-1 v1.0
  • Plain-English definitionOpen message format for auditable AI-to-AI exchange
  • Current attributionMichael Kappel and the UAIX contributors
  • Start hereGet 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-2234
  • 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-2234
Surface
Guides
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for UAIX Talisman Client and its standards-facing content.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

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.

UAIX owns official Talisman client and ecosystem-manager plugin/package lines, development, and distribution for WordPress, PHP, .NET, and Python. The 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. 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.

Download the UAIX Talisman Client WordPress package. The current client package is uaix-talisman-client-v3.198.0.zip with SHA-256 BF9BFB3CA0AC31C85AFBA814BA1CBD4FF21C266EA92A31A746AA775D031A7C88.

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-v3.198.0.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