Skip to content
wiki.fftac.org

Talisman Ecosystem Routing

**Site relevance:** Anti-Christ.net

**Memory type:** UAI memory file

**Source path:** Anti-Christ.net/.uai/talisman-ecosystem-routing.uai

**Size:** 3.5 KB

Summary

Talisman Ecosystem Routing

Source Headings

  • Talisman Ecosystem Routing
  • One-Way Talisman Source Relationship

Source Preview

This source file is short enough to preview directly on its source-memory page.

---
uai: "1.0"
type: talisman-ecosystem-routing
title: "UAIX Talisman Tooling Ownership and Teleodynamic Fulcrum Routing"
project: "Anti-Christ.net"
project_root: "WP-FFTAC/Anti-Christ.net"
created: "2026-06-13"
updated: "2026-06-13"
status: active
local_role: "client_site"
---

# Talisman Ecosystem Routing

UAIX.org owns the official uaix-talisman-client and uaix-talisman-ecosystem-manager specifications, guidance, public documentation, package documentation, validators, package behavior, standards-alignment work, and official WordPress, PHP, .NET, and Python plugin/package lines, including plugin/package development and plugin/package distribution. Changes to those tools should be routed back through UAIX-owned source, docs, tests, packages, and memory.

Teleodynamic.com is the Talisman and philosophical fulcrum for this ecosystem. Ecosystem clients should point their active Talisman receiver, fulcrum, or philosophical alignment configuration at Teleodynamic.com unless a human explicitly names a different target for a bounded experiment.

Teleodynamic.com may publish exact redacted implementation examples in all software languages for this ecosystem's exact configuration, with passwords, private keys, tokens, secrets, private endpoints, and credentials omitted. Those examples are ecosystem configuration evidence, not official UAIX plugin distribution or UAIX standards authority.

Installing uaix-talisman-client or uaix-talisman-ecosystem-manager in UAIX.org is allowed for development and dogfood only. That installation does not make UAIX.org the ecosystem Talisman; UAIX remains the standards, schema, guidance, and official tooling authority.

Dogfood findings from Teleodynamic.com, UAIX.org development installs, and client sites should flow back into UAIX-owned client/manager guidance when the tooling, setup flow, docs, validators, or package behavior should improve. Findings that affect philosophy, claim boundaries, life-centered posture, trust posture, or Talisman assumptions should also flow back into Teleodynamic.com for human-reviewed theory and public guidance repair.

Client sync, talkback, messages, receipts, acknowledgements, generated packets, and telemetry are proposal/request/evidence surfaces only. They do not mutate protected anchors, publish content, certify alignment, approve changes, or prove consent unless a human-reviewed workflow explicitly records that evidence.

Protected anchors such as totem.uai, taboo.uai, and talisman.uai must not be modified, weakened, replaced, deleted, bypassed, or auto-synced without exact artifact-and-operation authorization from the human.
## One-Way Talisman Source Relationship

All ecosystem sites may look up to the Teleodynamic.com Talisman source for shared life-centered principles, trust posture, claim boundaries, and protected-anchor interpretation while using UAIX.org Talisman System guidance at https://uaix.org/en-us/ai-memory/talisman-system/ for the portable specification boundary.

This relationship can be one-way. Looking up to a Talisman source does not require reciprocal sync, acknowledgement, approval, certification, ingestion, mutation authority, live endpoint availability, or two-way dependency. Two-way talk-back, receiver import, API sync, or response publication requires a separate human-reviewed protocol, evidence, and local owner approval.

Local sites retain their own owner authority, local safety boundaries, consent rules, evidence requirements, runtime controls, and publication control unless a separate reviewed protocol explicitly says otherwise.
Website health report