Version localizada en revision
Esta pagina aun no esta disponible como norma localizada revisada. Use la fuente inglesa autoritativa para lenguaje normativo, interpretacion de esquemas, obligaciones de implementacion y limites de soporte.
Cómo usar esta página
Use this page as part of the current Guías public record, then follow its linked standards pages for the next step.
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.
Evidencia
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
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.