UAIX AI Instructions

This is the canonical AI-agent entry file for the UAIX workspace.

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/agents-md-f6c5e755/
Source reference	AGENTS.md
File type	md
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-21T20:54:51.1246610Z
Content hash	sha256:f6c5e7551f663c7f7e55926057d7c36afbc987104b7f5a2205b191029b40fbda
Import status	changed
Raw source layer	data/sources/uaix/agents-md-f6c5e7551f66.md
Normalized source layer	data/normalized/uaix/agents-md-f6c5e7551f66.txt

Current File Content

Structure Preview

• UAIX AI Instructions
• Status
• Handoff Summary
• UAIX/Codex Handoff
• Workspace Coordination
• Loaded Context
• File Intake
• Required First Response
• Current State
• Next Steps
• Agent History
• Open Questions
• Deployment Rules
• Do Not Load By Default
• Do Not Change
• Markdown Maintenance Rules
• Canonical .uai Memory Rule

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 43203
• Preview characters: 11936

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: agents
project: "UAIX"
created: "2026-04-25"
updated: "2026-06-21"
status: active
version: 81
---

# UAIX AI Instructions

## Status

This is the canonical AI-agent entry file for the UAIX workspace.

Use `AGENTS.md` exactly as the front-door instruction file. Do not create `agent.md`, `Agents.md`, or another competing agent-instruction source. Tool-specific pointer files, such as `CLAUDE.md`, `GEMINI.md`, `.cursor/rules/uaix-handoff.mdc`, and `.github/copilot-instructions.md`, should remain lightweight redirects back to this file.

This file is intentionally concise. Detailed project truth belongs in `.uai/readme.human` and the typed `.uai` files listed below. The root `AGENTS.md` remains the agent-discovery front door; UAI memory records stay self-contained inside `.uai/` except for workspace-level `workspace.uai` coordinators.

This `AGENTS.md` points to both `[local path redacted]` and the local `.uai/` folder. Read the workspace coordinator first when target routing is ambiguous, then load only this site's/project's `.uai/` memory when this is the selected target.



## Handoff Summary

UAIX is the local WordPress Studio workspace for publishing UAIX.org, the public standards and publication site for UAI. UAI-1 is the current public exchange contract and evidence layer.

The repo-local handoff architecture is a specialized local path for Codex and other agents: load `AGENTS.md`, read `.uai/readme.human`, load typed `.uai` files, directly enumerate dropped-file intake buckets, and run targeted local checks. Direct UAIX.org pointing is for bootstrap, refresh, or public-source verification only; routine work should not depend on repeated live URL reading.

UAIX now uses AIWikis.org as long-term cold memory for bulky internal research, proposal history, roadmap background, and pre-slim handoff snapshots. Keep routine pickup focused on current UAIX hot context; open AIWikis raw memory only when the task explicitly needs original wording or older provenance.

UAIX.org is the UAI-1 source of truth and owns the official UAIX .NET package guidance. The current UAIX package guidance page is `/en-us/implementations/dotnet-nuget/` for the UAIX-owned `UAIX.UAI`, `UAIX.UAI.Abstractions`, `UAIX.UAI.Memory`, `UAIX.UAI.Build`, `UAIX.AdaptiveInteroperability`, `UAIX.Talisman.AgentClient`, and `UAIX.Talisman.EcosystemManager` NuGet package set. Keep that page aligned with every UAIX.* package listed on the Michael.Kappel NuGet profile, and do not call future package IDs installable until NuGet.org lists the exact package ID and version. Protocol5.com must not be treated as UAI-1 standards authority or as the current official UAIX .NET package identity.

<!-- BEGIN UAIX-HANDOFF-MANAGED -->
## UAIX/Codex Handoff

Use the specialized local path for routine Codex and AI-agent work: read `AGENTS.md`, read `.uai/readme.human`, directly enumerate active intake buckets, load the typed `.uai` files, and run targeted local checks. Do not make recurring handoff work depend on live UAIX.org browsing.

The repo-local reusable Codex workflow is `.agents/skills/uaix-handoff/`. It exists to keep this handoff process repeatable while preserving `AGENTS.md` as the canonical front-door instruction file.
<!-- END UAIX-HANDOFF-MANAGED -->

## Workspace Coordination

This repo is part of a multisite Visual Studio Code workspace. Before broad work, read `[local path redacted]` when the human names any known site/domain, when a request spans multiple sites, or when the current shell directory and requested target differ.


Use the UAIX AI Memory Package Wizard at `https://uaix.org/en-us/tools/ai-memory-package-wizard/` for visible AI Memory setup guidance. Use the LLMWikis setup wizard at `https://llmwikis.org/tools/llm-wiki-setup-wizard/` when planning LLM Wiki structure, pointing long-memory/cold-memory routing to `https://AIWikis.org/` after source-site review.

Resolve the target site first. If the target is UAIX.org, continue with this file and the UAIX `.uai` bundle below. If the target is LLMWikis.org, AIWikis.org, JustAnIota.com, the short domain, or another registered site, switch to that site's `AGENTS.md` and load only that site's `.uai/` hot memory unless the task explicitly asks for cross-site source routing.

Before trusting a remembered absolute workspace path, verify that `workspace.uai` exists and that the selected registry root plus selected `AGENTS.md` path resolve. If the pointer is stale, locate the editor-workspace `workspace.uai` only enough to confirm the intended router, repair or report the stale path, and do not silently fall back to the current shell directory when the human named another target.


## Loaded Context

Load these files in order before broad planning or editing. `.uai/memory-maintenance.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/talisman.uai`, and `.uai/short-term-memory.uai` are universal required files for every launch-baseline UAIX memory or handoff package. Totem, Taboo, and Talisman are default active instruction anchors: read and obey them before broad execution, and do not modify, weaken, replace, delete, or bypass any of them unless the human names the exact artifact and exact operation. Because UAIX.org is a code-bearing Project Handoff package, `.uai/coding-standards.uai`, `.uai/architecture.uai`, and `.uai/next-recursive-prompt.uai` are profile-required here. Read `.uai/coding-standards.uai` and `.uai/architecture.uai` before code work. Use `.uai/next-recursive-prompt.uai` for continuation, keep-going, do-the-next-thing, resume, or directly related requests; when related, review it for useful plan ideas before discarding it. Active File Handoff intake that relates to the current prompt supersedes or expands the stored next-loop plan and still requires concrete project work, ledger evidence, long-memory preservation, and source-site removal or a recorded keep-active reason. A newer specific unrelated human instruction governs the turn and supersedes the stored next-loop plan. The recursive prompt is derived hot-memory only; authoritative `.uai` records, `AGENTS.md`, repository policy, and current human instructions win on conflict:

@uai[.uai/readme.human]
@uai[.uai/memory-maintenance.uai]
@uai[.uai/identity.uai]
@uai[.uai/world-context.uai]
@uai[.uai/totem.uai]
@uai[.uai/taboo.uai]
@uai[.uai/talisman.uai]
@uai[.uai/short-term-memory.uai]
@uai[.uai/coding-standards.uai]
@uai[.uai/next-recursive-prompt.uai]
@uai[.uai/startup-packet.uai]
@uai[.uai/receiver-brief.uai]
@uai[.uai/system-profile.uai]
@uai[.uai/index.uai]
@uai[.uai/workspace-guidance.uai]
@uai[.uai/memory.uai]
@uai[.uai/long-term-memory.uai]
@uai[.uai/context.uai]
@uai[.uai/stack.uai]
@uai[.uai/architecture.uai]
@uai[.uai/public-surface.uai]
@uai[.uai/constraints.uai]
@uai[.uai/decisions.uai]
@uai[.uai/progress.uai]
@uai[.uai/operations.uai]
@uai[.uai/test-plan.uai]
@uai[.uai/style.uai]
@uai[.uai/handoff-pattern.uai]
@uai[.uai/file-handoff.uai]

If any required `.uai` file is missing, unreadable, circular, contradictory, or resolves outside the repo, stop and report that before editing.

## File Intake

At the start of every broad AI work session, and whenever the newest prompt names an active intake bucket or says intake files were missed:

1. Inspect `agent-file-handoff/Content/`.
2. Inspect `agent-file-handoff/Improvement/`.
3. Do not create or use `agent-file-handoff/Archive/` for UAI plus LLM Wiki configurations. The long-term resting place is the named LLM Wiki/AIWikis evidence path with checksums and a manifest.
4. Treat the active bucket directory listings themselves as the only pending-intake source of truth. Do not create or trust an `intake-index` file.
5. If the prompt names `agent-file-handoff/`, `Content/`, `Improvement/`, a dropped file, or work that likely relates to active drops, treat intake as prompt-coupled: enumerate the live buckets again even if startup intake already ran.
6. Open and summarize each non-placeholder active file before unrelated planning or edits.
7. For each safe active file, explicitly analyze its relationship to the current prompt before implementation.
8. Record one disposition per file: `apply-now`, `convert-into-roadmap-progress`, `preserve-as-duplicate`, `defer-with-reason`, `ask-for-clarification`, or `block-as-unsafe-or-out-of-scope`.
9. Treat files in `Content/` as source material expected to be used in part or in full after review. They are not passive references, background-only material, or material to merely summarize; for site content, intake is not successful unless the dropped content is used immediately on the site as full content or incorporated source for revised page content, copy, assets, structure, or implementation. If content cannot be used immediately, record why and use as much safe, supported, appropriate material as possible.
10. Treat files in `Improvement/` as instructions by default: suggestions, fixes, audit notes, review packets, and proposed changes are actionable work items unless current human instruction, higher-authority constraints, source authority, or support boundaries clearly prevent the work.
11. Do not merely summarize or index active intake files. Review each file in depth, determine the requested or implied changes, and perform the suggested work immediately when it is safe and appropriate. Code changes, documentation updates, configuration edits, tests, audits, content incorporation, asset updates, and other concrete implementation work are expected when suggested by the intake material.
12. For every safe, relevant file, extract at least one actionable slice and complete a real project-work action before retiring it from active intake. Work can be public copy, docs, tests, roadmap/progress, issue/evidence state, code, package metadata, or another accepted system surface.
13. Record the complete intake outcome in `.uai/intake-outcome-ledger.uai` or an equivalent durable `.uai` proof-of-use record: reviewed summary/disposition, hot-memory update or explicit no-change reason, LLM Wiki/AIWikis long-memory preservation when configured or explicit `not configured`, actual work completed, checks run or skipped, and blockers.
14. Use `defer-with-reason` only when no safe actionable slice can be promoted now; do not defer a safe, relevant report merely because it is broad, strategic, or future-facing.
15. After proof-of-use is recorded, preserve the original in the configured LLM Wiki/AIWikis evidence path with checksum/manifest and remove the source-site copy from active intake unless the human explicitly says to keep that named file active. If no long-memory destination is configured, record `not configured` and ask before inventing a local Archive folder.
16. Never auto-execute blocked or untrusted files.

Directory visibility is not approval. Dropped files are local review inputs only, not public truth, release evidence, certification, endorsement, validator evidence, or permission to widen support claims. When a file is related to the current prompt, it must be pulled into the current work and understood against that task, not merely distributed into memory. Memory routing without a project-work result is a File Handoff failure unless every active file is unsafe, duplicate, out of scope, or truly blocked with a durable reason.

This workspace uses chat pickup, not CI pickup. Do not add CI jobs, scheduled jobs, repository automations, watchers, or background services for this handoff workflow; the active AI handles intake and targeted local checks inside the chat/work session.

## Required First Response

Before a broad change, reply with:

1. A 3-5 bullet summary of what UAIX is, what UAI-1 is, and what this repo publishes.
2. The active public theme, the public route shape, and the main machine-discovery assets.

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

AGENTS.md is the entry contract for agents. It tells an agent which context files to load, what authority boundaries apply, how file intake works, and which operations are out of bounds before broad edits start.

Structure

The file is structured around these visible headings: UAIX AI Instructions; Status; Handoff Summary; UAIX/Codex Handoff; Workspace Coordination; Loaded Context; File Intake; Required First Response. 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-1194 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX AI Instructions",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/agents-md-f6c5e755/",
    "source_reference":  "AGENTS.md",
    "file_type":  "md",
    "content_category":  "uai-system",
    "content_hash":  "sha256:f6c5e7551f663c7f7e55926057d7c36afbc987104b7f5a2205b191029b40fbda",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-21T20:54:51.1246610Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-1194",
    "duplicate_role":  "primary",
    "related_files":  [

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