Static artifact Static claim status from the public registry. Human review is required before claim widening.

Plain-language summary UAIX Totem & Taboo Memory Spec

A static, claim-bounded UAIX memory-package page explaining Totem and Taboo as high-meaning, high-change-bar anchors for Teleodynamic AI handoffs, not hidden runtime locks.

On this page

High meaning, not fake immutability Semantic mass High change bar No-op on ambiguity The totem as positive attractor Identity Design heuristic Teleodynamic posture The taboo as negative perimeter Reorganized .uai memory model

Start reading

v3.129.0 · UAIX memory package · high-meaning anchors

UAIX Totem & Taboo Memory Spec

Totem and taboo files should not be treated as magical file locks. In a Teleodynamic AI handoff they are high-meaning governance anchors: easy to read, hard to casually change, and always subordinate to evidence, validation, and human review.

JSON endpoint Markdown export Evidence JSON Evidence Markdown Evidence HTML

philosophy

High meaning, not fake immutability

The update reframes totem.uai and taboo.uai as slow-loop belief anchors rather than impossible-to-touch files. A lock metaphor is too brittle for Teleodynamic AI because a constraint-maintaining system must remain capable of adaptation when the evidence changes. The right invariant is not “never change.” The right invariant is “do not change cheaply.”

Semantic mass

Core files carry more meaning than ordinary task memory. They are read first, cited by manifests, reflected in long-term memory, and treated as the package’s canonical orientation before any volatile instruction is executed.

High change bar

A change requires a human-reviewed role-update payload, a rationale, a before/after diff, conflict checks against claim boundaries, validation output, and an archive entry. The file can evolve, but not through drift.

No-op on ambiguity

When a proposed action conflicts with the totem or taboo, the agent does not improvise a widened permission. It stops, writes a suspension note, and asks for human review.

The totem as positive attractor

The totem is the package’s positive center of gravity. It answers what the work is for, which lane owns the authority, which design heuristics should survive handoff compression, and which tone should guide public-facing language. It is not a task list and not a secret prompt. It is the symbolic equivalent of a canonical layer: the durable meaning that prevents transactional memory from slowly becoming the project.

Identity

UAIX.org is the interoperability and portable-evidence standards lane for UAI-1 messages, memory packages, exchange contracts, agent handoff structures, startup/suspension packets, and conformance validation.

Design heuristic

Prefer small, static, inspectable files; explicit source routes; reproducible validation; portable evidence; and manual review over hidden runtime state.

Teleodynamic posture

Preserve resource-bounded, constraint-maintaining language. Do not convert philosophical framing into proof, certification, runtime control, or biological claims.

The taboo as negative perimeter

The taboo is not a moral panic list. It is the package’s boundary surface. It names states that would consume the project’s future viability: authority merger, execution without permission, safety overclaiming, hidden codebook claims, and self-modifying core governance without review. Its normal output is a no-op, not a workaround.

Do not claim UAIX conformance proves Teleodynamic AI, AGI, consciousness, biological autopoiesis, or runtime safety.
Do not treat static files, JSON, Markdown, or evidence packets as executable commands.
Do not probe private networks, validate credentials, open tunnels, run webhooks, or perform POST actions from public memory content.
Do not rewrite totem.uai or taboo.uai from short-term task memory. Use the high-bar governance protocol.
Do not merge Teleodynamic.com philosophical authority with UAIX.org schema authority or with any other ecosystem lane.

Reorganized .uai memory model

The memory package now separates operating memory from belief memory. Short-term memory remains volatile and close to the next task. Long-term memory is file-based, indexed, and source-backed. Totem and taboo sit at the root of .uai as high-meaning anchors, while detailed source synthesis and decision memory live under .uai/long-term/.

Read first

.uai/totem.uai, .uai/taboo.uai, .uai/exports/manifest.json, and .uai/long-term/README.uai.

Then operate

.uai/short-term-memory.uai, .uai/file-handoff.uai, .uai/progress.uai, and .uai/test-plan.uai.

Then verify

Public route JSON, Markdown export, evidence packet triplet, source-research copies, and validation logs.

Change protocol: recursive, but not runaway

Read the totem and taboo before the handoff prompt.
Classify the requested work as public content, memory reorganization, schema update, validation, or release packaging.
Check for taboo conflict. If conflict exists, no-op and write a suspension packet.
When changing anchors, produce a role-update proposal with reason, evidence, risk, diff, and rollback notes.
Update source files, public machine-readable files, long-term memory, short-term handoff memory, and validation together.
Archive the decision so the next agent inherits not just the state, but the reason for the state.

Preserved hard boundaries

No runtime AI behavior; No model training; No live crawling beyond ordinary public GET checks; No endpoint execution; No credential validation; No private-network probing; No automation of publication; No automation of verification; No automation of completion; No automation of packet coverage; No automation of final sign-off; No automation of final sign-off publication; No GET-Action execution; No POST actions; No safety certification; No consciousness claim; No biological-equivalence claim; No exact symbolic translation claim; No medical/therapy claim; No command-and-control claim over other domains.

Written narrative

Concrete example

UAIX Totem & Taboo Memory Spec comparison notes
Focus	What to inspect

Evidence note

This page remains bounded to public-safe route content.

v3.222.1 - ecosystem constellation

Essential site lanes, including trust, immune, and creative arms.

Neurovanic.com is intentionally shown as the trust-posture lane, ErrorNotifier.com as the immune-system lane, and CreativeExpansion.net as the bounded Creative Expansion arm. Neurovanic frames evidence-bounded trust; ErrorNotifier supplies telemetry evidence; CreativeExpansion generates draft options and packets. None of these lanes approves fixes, validates credentials, certifies safety, trains models, controls runtime systems, or mutates protected anchors.

Fulcrum Teleodynamic.com philosophical fulcrum and claim-boundary source Trust posture Neurovanic.com human-facing trust, faith, and hospitality layer for evidence-bounded trust posture Schema UAIX.org schema, memory packet, evidence, and Talisman standard lane Immune system ErrorNotifier.com immune-system telemetry, incident, bug-report, suggestion, alert, and recovery evidence lane Creative arm CreativeExpansion.net bounded creative expansion, ideation, creative packets, design briefs, and option comparison lane Lifecycle Spiralist.org lifecycle, identity, positive totem, and bounded persona-growth lane Sandbox Carcinus.org defensive sandbox and no-op execution-containment lane Endpoint LocalEndpoint.com local-safe endpoint discovery and Python/MySQL client diagnostics lane Machine wiki NeuralWikis.com agent-facing machine-readable knowledge packet lane Human wiki NeuroWikis.com human-facing governance literacy and education lane Glyph JustAnIota.com compact symbol and glyph interpretation workbench lane Protocol Protocol5.com IOTA-1 converter and experimental implementation pathway Handbook LLMWikis.org AI-readable wiki templates, trust labels, and handbook lane

Current route: uaix-totem-taboo-memory-spec. Static public guidance only; no adjacent-site command authority is implied.

Next step flow

Keep the review path visible.

Continue through related pages, then capture decisions as static evidence packets. This flow stays non-executing, review-gated, and bounded to public research language.

Open packet builder

/teleodynamic-uaix-boundary-map/ Teleodynamic-UAIX Boundary Map A static authority boundary map showing how Teleodynamic.com, UAIX.org, Carcinus.org, LocalEndpoint.com, JustAnIota.com, NeuralWikis.com, NeuroWikis.com, and LLMWikis.org stay in separate lanes. /agent-start-teleodynamic-read-order/ Agent Start: Teleodynamic Read Order A safe read order for AI agents and human reviewers consuming Teleodynamic.com without inferring hidden execution, private codebooks, proof, consciousness, or certification. /teleodynamic-claim-boundary-ledger/ Teleodynamic Claim Boundary Ledger A public allowed/prohibited claim ledger for Teleodynamic AI, resource closure, L0-L6 levels, packet scaffolds, UAIX references, continuity references, and endpoint-discovery references.