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/raw-system-archives-uaix-internal-memory-reorg-2026-05-01-agents-md-f5f34d1c/ |
| Source reference | raw/system-archives/uaix/internal-memory-reorg/2026-05-01/AGENTS.md |
| File type | md |
| Content category | uai-system |
| Last fetched | 2026-06-22T01:56:21.9510185Z |
| Last changed | 2026-05-01T17:51:17.0371686Z |
| Content hash | sha256:f5f34d1c8fd4a96db4f093098e835a5e9bc355ecf4ff4ab81c7fa09076fb821d |
| Import status | unchanged |
| Raw source layer | data/sources/uaix/raw-system-archives-uaix-internal-memory-reorg-2026-05-01-agents-md-f5f34d1c8fd4.md |
| Normalized source layer | data/normalized/uaix/raw-system-archives-uaix-internal-memory-reorg-2026-05-01-agents-md-f5f34d1c8fd4.txt |
Current File Content
Structure Preview
- UAIX AI Instructions
- Status
- Handoff Summary
- UAIX/Codex Handoff
- 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
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:
13392 - Preview characters:
11994
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-05-01"
status: active
version: 40
---
# 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 root `readme.human` and the typed `.uai` files listed below.
## 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 `readme.human`, load typed `.uai` files, refresh dropped-file intake, 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.org is the UAI-1 source of truth. Protocol5.com is only a .NET plugin and NuGet distribution/backlink surface.
<!-- BEGIN UAIX-HANDOFF-MANAGED -->
## UAIX/Codex Handoff
Use the specialized local path for routine Codex and AI-agent work: read `AGENTS.md`, read `readme.human`, refresh active intake, 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 -->
## Loaded Context
Load these files before broad planning or editing:
@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]
@uai[.uai/intake-index.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:
1. Inspect `agent-file-handoff/Content/`.
2. Inspect `agent-file-handoff/Improvement/`.
3. Ignore `agent-file-handoff/Archive/` unless the human explicitly names an archived file or moves it back into an active bucket.
4. Refresh `.uai/intake-index.uai` when a helper exists; this repo uses `scripts/Invoke-UaiFileIntake.ps1`.
5. Summarize each `needs-agent-review` file before unrelated planning or edits.
6. Record one disposition per file: `apply-now`, `convert-into-roadmap-progress`, `archive-as-duplicate`, `defer-with-reason`, `ask-for-clarification`, or `block-as-unsafe-or-out-of-scope`.
7. Move processed source files to `Archive/` only after the disposition is recorded in durable state.
8. Never auto-execute blocked or untrusted files.
Indexing 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.
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.
3. The refreshed intake status, including the disposition for every `needs-agent-review` file.
4. The hard constraints from `.uai/constraints.uai`, especially support-claim boundaries, secrets/data boundaries, and destructive-operation limits.
5. The exact files or public routes expected to change for the current task.
6. The targeted checks expected to run, and any full release/package checks intentionally not running.
## Current State
- Active public theme: `wp-content/themes/uaix-authority-theme/`.
- Compatibility theme: `wp-content/themes/uaix-theme/`, still packaged and smoke-tested but not the production public surface.
- Public production routes use clean locale-prefixed paths under `/en-us/...`; enabled public languages are `en-US` and `zh-CN`.
- Main machine-discovery assets: `robots.txt`, `sitemap.xml`, `sitemap.html`, `/.well-known/uaix.json`, and `/.well-known/uai.json`.
- Public handoff surfaces include `/en-us/ai-memory/`, `/en-us/tools/ai-memory-package-wizard/`, `/en-us/specification/project-handoff/`, `/en-us/guides/project-handoff-openai/`, `/en-us/guides/project-handoff-coding-agents/`, `/en-us/specification/agent-file-handoff/`, and `/en-us/specification/agents-md/`.
- `agent-file-handoff/Content/`, `agent-file-handoff/Improvement/`, and `agent-file-handoff/Archive/` are active repo-local source-only handoff folders.
- `scripts/lint-uaix-handoff.ps1` is the local structural check for this handoff bundle. It is not UAI-1 validator evidence.
- `.agents/skills/uaix-handoff/` is the repo-local Codex skill for repeatable handoff pickup, intake review, and targeted verification.
Use `docs/navigation/README.md` for topic navigation when the loaded context says deeper docs are needed. Use the canonical reading order from `README.md` only when final project truth beyond the `.uai` bundle is required.
## Next Steps
- [ ] Keep `AGENTS.md` concise and operational; move detailed state into typed `.uai` files.
- [ ] Keep Project Handoff positioned as portable project memory for humans and AI agents, not an agent runtime, scheduler, orchestrator, OpenAI replacement, or tool-calling framework.
- [ ] Keep the cross-coding-agent guide and local pointer files thin: they should route Codex, Claude Code, Cursor, Copilot, Gemini Code Assist, local agents, vendors, and humans back to `AGENTS.md`, `readme.human`, and `.uai` records without creating official adapter claims.
- [ ] Keep AI Memory public copy search-friendly while preserving current/planned support boundaries.
- [ ] Keep Agent File Handoff as AGENTS.md-triggered chat-start intake with no CI job, watcher, daemon, queue-folder, scheduled job, repository automation, or always-on background-service requirement.
- [ ] Keep root `AGENTS.md`, root `readme.human`, and `.uai/` files current whenever project truth changes.
- [ ] Keep `.agents/skills/uaix-handoff/` aligned with this file when the handoff workflow changes.
- [ ] Keep UAIX.org as UAI-1 authority and Protocol5.com as only .NET/NuGet distribution plus backlinks.
- [ ] Run targeted checks for ordinary edits; reserve full launch, performance, locale, package validation, and smoke-test sweeps for release/package work, broad launch-surface changes, or explicit human requests.
- [ ] Deploy current source packages and fallback root assets when release work resumes to clear known production drift for the AI Memory Package Wizard route, well-known manifests, HSTS, and static security headers.
## Agent History
Detailed historical progress lives in `.uai/progress.uai`. Keep this front-door table short and current.
| Date | Agent | Model | Work Done |
|------|-------|-------|-----------|
| 2026-05-01 | Codex | GPT-5 | Added `/en-us/guides/project-handoff-coding-agents/`, thin Cursor/Gemini/Copilot pointers, and discovery/test coverage so cross-tool coding-agent handoff uses one local bundle without official adapter claims. |
| 2026-05-01 | Codex | GPT-5 | Added the repo-local `.agents/skills/uaix-handoff/` skill and processed the cross-tool handoff integration reports into durable handoff state without widening current support claims. |
| 2026-05-01 | Codex | GPT-5 | Processed the active handoff optimization reports, standardized the local Codex handoff path on `AGENTS.md`, typed `.uai` files, active file intake, and local handoff linting, while keeping direct UAIX pointing as bootstrap/refresh only. |
| 2026-05-01 | Codex | GPT-5 | Processed OpenAI orchestration reports, repositioned Project Handoff as portable project memory, added `/en-us/guides/project-handoff-openai/`, and kept adapter/exporter/conformance claims planned. |
| 2026-05-01 | Codex | GPT-5 | Converted the AI Memory Package Wizard into a six-step staged review/export flow with validation, local draft restore, review previews, and bounded support claims. |
| 2026-04-30 | Codex | GPT-5 | Deepened Get Started, UAI-1, and Standards Fit with UAI-1/MCP/A2A chooser guidance without widening SDK, CLI, certification, compliance, endorsement, or replacement claims. |
| 2026-04-30 | Codex | GPT-5 | Expanded the AI Memory Package Wizard generated operating artifacts and protocol fields while keeping hosted import, automatic writes, sync, SDK, CLI, certification, and endorsement out of current support. |
## Open Questions
- Some canonical/helper Markdown files may be ACL-protected in this local environment. If a required doc update fails with access denied, update writable canonical surfaces and record the blocker in `.uai/progress.uai`.
- The 2026-04-29 live production response check reported production drift: the AI Memory Package Wizard route was 404 on `https://uaix.org`, well-known manifests were stale, and production static/HTTPS responses needed HSTS and security-header configuration.
- The full launch-surface HTTP audit passes locally but can report the expected Studio-local `X-Powered-By: Express` warning; production should suppress host/runtime version headers.
## Deployment Rules
- Deployment guidance is centralized in `docs/deploy.md`.
- Publish distributable ZIP packages to `[local path redacted]`.
- Use `studio wp`, not bare `wp`, for WordPress CLI work.
- Normal prompt-driven work should run targeted checks from `.uai/test-plan.uai`, not package publishing or the full suite by default.
- Full build/release work should also clean and update source-only `.md`, `.uai`, and `.human` docs while keeping them out of upload ZIPs, sitemap output, and public discovery unless deliberately converted into public copy.
## Do Not Load By Default
Skip these non-primary traversal zones unless the task explicitly targets generated output, archives, screenshots, diagnostics, packaged mirrors, or upstream files:
- `.tmp/`
- `wp-content/Publish/`
- `wp-content/themes/uaix-authority-theme-local-install/`
- bundled WordPress core or third-party upstream areas
- `[local path redacted]` for UAI truth after the split, unless the human explicitly asks for historical migration or cross-repo cleanup
## Do Not Change
Do not change these without explicit human approval:
- Do not switch the public launch theme away from `uaix-authority-theme`.
- Do not publish query-string URLs such as `?page_id=`, `?p=`, or `?s=` as launch URLs.
- Do not remove the `uiax.org` and `www.uiax.org` anonymous typo-domain redirect, and do not redirect typo-domain `/wp-admin/`, `/wp-login.php`, or logged-in WordPress sessions away from the typo host.
- Do not claim hosted `.uai` upload/import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, official adapter support, or repo-local `.uai` UAI-1 conformance until public tooling and evidence exist.
- Do not claim disabled locale inventory entries as supported public languages until full content, metadata, hreflang, sitemap, and rendered-text audit coverage exist.
- Do not describe Protocol5.com as the public site, canonical host, validator authority, registry authority, roadmap authority, or source of truth for UAI-1.
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; Loaded Context; File Intake; Required First Response; Current State. 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-1187(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/raw-system-archives-uaix-internal-memory-reorg-2026-05-01-agents-md-f5f34d1c/",
"source_reference": "raw/system-archives/uaix/internal-memory-reorg/2026-05-01/AGENTS.md",
"file_type": "md",
"content_category": "uai-system",
"content_hash": "sha256:f5f34d1c8fd4a96db4f093098e835a5e9bc355ecf4ff4ab81c7fa09076fb821d",
"last_fetched": "2026-06-22T01:56:21.9510185Z",
"last_changed": "2026-05-01T17:51:17.0371686Z",
"import_status": "unchanged",
"duplicate_group_id": "sfg-1187",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-06-22T01:56:21.9510185Z"
} Next Useful Routes
- Start Here A task-first reading path for AIWikis.org, separating newcomer learning, source-memory lookup, maintainer workflow, and AI-agent retrieval.
- Topic Index A tag-oriented index for LLM Wiki, AI memory, UAI, source governance, crawling, and retrieval topics.
- Source Map AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
- UAIX.org UAIX.org source-system overview for transparent AIWikis memory demonstration.
- UAIX.org Source Memory Guide AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
- UAIX.org Files Site-scoped current-source file index for UAIX.org.