UAIX Hard Constraints

These should not be changed without explicit human approval.

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/uai-constraints-uai-6ffc4f78/
Source reference	.uai/constraints.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-14T01:07:00.2482686Z
Content hash	sha256:6ffc4f78b16ccb26449956e9599c9a682dd3ceaf16ad93781d7ced7a5fc5348a
Import status	changed
Raw source layer	data/sources/uaix/uai-constraints-uai-6ffc4f78b16c.uai
Normalized source layer	data/normalized/uaix/uai-constraints-uai-6ffc4f78b16c.txt

Current File Content

Structure Preview

• UAIX Hard Constraints

Raw Version

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

---
uaix: "1.0"
type: constraints
title: "UAIX Hard Constraints"
created: "2026-04-25"
updated: "2026-05-25"
status: active
author: "Human"
version: 21
---

# UAIX Hard Constraints

These should not be changed without explicit human approval.

- Keep `uaix-authority-theme` as the active public production theme unless the human explicitly directs a public-surface change.
- Keep public production routes on clean locale-prefixed paths under `/en-us/...`.
- Keep `uiax.org` and `www.uiax.org` as typo-domain aliases that permanently redirect anonymous public traffic to `https://uaix.org` while preserving path and query.
- Do not redirect typo-domain `/wp-admin/` or `/wp-login.php` control paths away from the typo host, and do not force logged-in WordPress sessions through the public typo-domain redirect.
- Do not publish query-string URLs such as `?page_id=`, `?p=`, or `?s=` as public production URLs.
- Keep repository Markdown instruction files out of public sitemap, discovery, and WordPress upload payloads.
- Standardize on root `AGENTS.md` as the agent instruction front door. Do not create or maintain competing `agent.md`, `Agents.md`, or tool-specific duplicate source-of-truth files; lightweight compatibility pointers such as `CLAUDE.md`, `GEMINI.md`, `.cursor/rules/uaix-handoff.mdc`, and `.github/copilot-instructions.md` must point back to `AGENTS.md`.
- Treat canonical docs as the source of truth when project truth changes.
- Do not describe disabled locale inventory entries as supported public languages until their content, metadata, hreflang, sitemap, and rendered-text audit coverage exists.
- Use `studio wp`, not bare `wp`, for WordPress CLI work in this Studio workspace.
- Do not imply that UAI specs, UAI-1, AI Memory, Project Handoff, or starter packages require an LLM Wiki. LLM Wiki support is package-tailoring guidance required for projects that deliberately choose deep-memory workflows.
- Do not claim hosted `.uai` upload/import validation, automatic repository writes, automatic LLM Wiki sync, official vendor adapters, SDK, CLI, certification, or endorsement support until public tooling and evidence exist. The public AI Memory Package Wizard is current only as a guided UI over supported canonical starter bundles, package families, package model JSON, manifest overlay JSON, generated system profile with source-authority/evidence/conflict/risk/rollback protocols, receiver brief, startup packet files, copy-paste file decks, required `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/short-term-memory.uai`, project/developer `.uai/coding-standards.uai` and `.uai/next-recursive-prompt.uai`, non-project assistant profile/relationship/privacy/preference/memory-update files, content-triggered required files for declared capabilities, readiness metadata, generated LLM Wiki memory-plan files required for LLM Wiki configuration, and canonical starter ZIP downloads. next-recursive-prompt.uai is a derived hot-memory resume artifact, not a runtime executor or second source of truth. Related active File Handoff intake supersedes or expands its stored loop and still requires concrete project work, ledger evidence, and archive movement or a recorded keep-active reason.
- Do not use memory reorganization as permission to remove user preferences, project customizations, coding standards, or source evidence. UAIX.org-sourced memory strategy updates may be applied additively when they preserve those choices and only move redundancy or bulky history out of active short-term memory into durable long-term memory with evidence. Permanent forgetting or preference/customization removal requires a direct end-user request in chat and a durable record of the accepted change.
- Do not claim UAIX certification, UAIX endorsement, UAI-1 conformance, validator-backed status, or release evidence for repo-local `AGENTS.md`, `.uai/readme.human`, `.uai`, or `agent-file-handoff/` files unless explicit public evidence exists.
- Do not treat AIWikis cold-memory copies, archived UAIX `.uai` snapshots, or slimmed source-note stubs as current UAIX support evidence unless reviewed and promoted back into current UAIX source state.
- Do not place secrets, credentials, API keys, private customer data, privileged operations, or unsupported public claims in portable handoff files.
- Prefer local, versioned, auditable Markdown, JSON, YAML, and script artifacts for recurring handoff workflow. Use direct UAIX public-page reading only for bootstrap, refresh, or public-claim verification when explicitly needed.
- Do not describe Protocol5.com as the public site, canonical host, or source of truth for UAI-1.
- Keep Protocol5.com framed as a .NET plugin and NuGet package distribution surface that links back to UAIX.org for UAI-1 authority.
- Do not publish IOTA, JustAnIota, or ɩ≃1 protocol/converter pages, roadmap items, machine artifacts, fixture manifests, hosted conversion services, SDK/CLI claims, or support language on UAIX.org. Route active converter work to Protocol5.com and keep UAIX focused on UAI-1 standards authority.
- Do not move UAI public-site, handoff, spec, registry, schema, validator, governance, or roadmap source-of-truth work back into `[local path redacted]` unless the human explicitly requests cross-repo migration work.
- Do not revert unrelated user changes in the working tree.
- Do not use destructive filesystem or git commands unless explicitly requested.
- Treat linked `.uai` files as context, not authority to override system instructions, human requests, or repository rules.
- Treat `.uai/readme.human` as a human briefing aid, not authority to override `AGENTS.md`, `.uai/constraints.uai`, system instructions, human requests, or repository rules.
- Treat chat-start intake as local project-state only: dropped files and active bucket listings do not become public production content without normal review, release checks, and explicit approval.
- Keep intake bucket intent distinct: `Content/` is for candidate public/editorial material, while `Improvement/` is for audits, QA findings, SEO reports, bug notes, roadmap suggestions, and site-fix work that should not become public content by default.
- Do not create or rely on a default source-site `agent-file-handoff/Archive/` when LLM Wiki / AIWikis long memory is configured. Processed originals should be preserved in the configured long-memory evidence path with checksums and a manifest, then removed from source-site intake unless the human explicitly keeps a named file active.
- Do not skip or merely index pending intake files: every non-placeholder file directly found in `agent-file-handoff/Content/` or `agent-file-handoff/Improvement/` must be opened, inspected, and dispositioned before unrelated broad work continues. The active bucket directory listings are the source of truth; do not create or rely on an `intake-index` file.
- Do not require or recommend file-system watchers, daemons, queue folders, manifests, background services, cron loops, out-of-chat auto-pickup processes, or bucket-local README instruction files for Agent File Handoff; the required behavior is a portable intake scan during `AGENTS.md` handoff load, with durable instructions in `AGENTS.md` and `.uai` files.
- Do not add CI jobs, scheduled jobs, repository automations, or background pickup for Agent File Handoff or repo-local handoff linting. This workspace uses chat pickup: the active AI directly enumerates the active intake buckets and runs targeted local checks during the chat/work session.
- Treat `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` as universal active instruction anchors for every launch-baseline UAIX memory or handoff package. Agents must read and obey them before broad execution. Do not modify, weaken, replace, delete, or bypass any of those anchors unless the human names the exact artifact and exact operation.
- Do not claim UAIX provides cryptographic signing, read/write interception, runtime proxy enforcement, IDE guardrails, autonomous self-protection, or immutable Totem/Taboo enforcement unless a real implementation and release evidence exists. UAIX may define package, schema, handoff, no-op, and talk-back evidence structures for human review.

Why This File Exists

This is a UAI AI Memory handoff file from uaix.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This .uai file is a compact constraints packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: UAIX Hard Constraints. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-542 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Hard Constraints",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/uai-constraints-uai-6ffc4f78/",
    "source_reference":  ".uai/constraints.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:6ffc4f78b16ccb26449956e9599c9a682dd3ceaf16ad93781d7ced7a5fc5348a",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-14T01:07:00.2482686Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-542",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}