UAIX Operations

1. Read AGENTS.md first. 2. Read root readme.human as the human briefing companion; do not treat it as an override. 3. Perform chat-start file intake from Content/ and Improvement/, ignore Archive/, and then...

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/uai-system/files/uai-operations-uai-165e5c67/
Source reference	.uai/operations.uai
File type	uai
Content category	uai-system
Last fetched	2026-05-02T01:47:31.8867765Z
Last changed	2026-05-01T19:15:31.7728010Z
Content hash	sha256:165e5c67d664352d1d8896dd8c31cc4105b4761c3deb2eea0caeab8c9f8ef8c3
Import status	unchanged
Raw source layer	data/sources/uaix/uai-operations-uai-165e5c67d664.uai
Normalized source layer	data/normalized/uaix/uai-operations-uai-165e5c67d664.txt

Current File Content

Structure Preview

• UAIX Operations
• Common Commands
• Common Checks
• Release Expectations
• Editing Workflow
• Source Boundary Checks
• Handoff Workflow
• Handoff Pattern Maintenance

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: custom
title: "UAIX Operations"
created: "2026-04-25"
updated: "2026-05-01"
status: active
author: "UAIX maintainers"
version: 25
---

# UAIX Operations

## Common Commands

- Use `studio wp ...` for WordPress CLI work.
- Use `scripts/studio-wp-quiet.ps1` when WP-CLI noise would otherwise pollute script output.
- Use `scripts/publish-wordpress-packages.ps1` for the supported publish path.
- Use `.uai/test-plan.uai` to choose targeted checks for ordinary work and to decide when a full release/package sweep is justified.
- Use `.agents/skills/uaix-handoff/` as the repo-local Codex skill for repeatable handoff pickup when the current Codex session supports local skills.
- Keep `CLAUDE.md`, `GEMINI.md`, `.cursor/rules/uaix-handoff.mdc`, and `.github/copilot-instructions.md` as thin compatibility pointers; update them only when the shared handoff pickup rule changes.
- Use `scripts/lint-uaix-handoff.ps1` after changing `AGENTS.md`, `readme.human`, `.uai` files, or active intake/index behavior.
- Perform chat-start file intake after reading `AGENTS.md` and before loading the refreshed intake index. Check both `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`; ignore `agent-file-handoff/Archive/` unless the human explicitly names an archived file; use `scripts/Invoke-UaiFileIntake.ps1` when available.
- If the refreshed index lists any `needs-agent-review` file, inspect it, summarize it, and state a disposition before unrelated broad work continues.
- Do not use CI jobs, scheduled jobs, repository automations, watchers, daemons, bucket-local README instructions, or always-on background services for Agent File Handoff; the supported workflow is chat pickup with a one-shot intake scan during handoff load.

## Common Checks

- Default verification is targeted: choose checks that cover the files, routes, machine records, or behaviors changed.
- Do not run package publishing or the full launch/performance/locale/smoke suite by default for ordinary prompt work.
- `scripts/run-uaix-launch-surface-http-audit.ps1`
- `scripts/run-uaix-performance-audit.ps1`
- `scripts/run-uaix-zh-cn-translation-audit.ps1`
- `scripts/run-uaix-search-metadata-audit.ps1`
- `scripts/test-uaix-static-discovery-assets.ps1`
- `scripts/audit-helper-docs.ps1`
- `scripts/verify-wordpress-upload-package.ps1`
- `scripts/Invoke-UaiFileIntake.ps1`
- `scripts/lint-uaix-handoff.ps1`
- `scripts/test-uaix-ai-memory-bundle.php` through `scripts/studio-wp-quiet.ps1 eval-file` for focused AI Memory page, Project Handoff/OpenAI guide, Project Handoff/coding-agents guide, Project Handoff Context Budget guide, Package Wizard, generated system profile protocol fields, generated receiver brief, generated startup packet, generated LLM Wiki plan/readiness behavior, taxonomy, canonical template, manifest, generated ZIP, shared Project Handoff source, route metadata, and edge-case regression coverage.
- `scripts/uaix-lint.php` and `scripts/uaix-lint-deploy.php` through `studio wp --skip-plugins --skip-themes eval-file` when checking syntax with the Studio OPcache fallback.
- The launch-surface HTTP audit simulates `Host: uiax.org` and `Host: www.uiax.org` against the local Studio URL to verify that anonymous public typo-domain requests return `301` to `https://uaix.org` with path/query preserved and that `/wp-admin/` plus `/wp-login.php` are not typo-domain canonicalized.
- The launch-surface HTTP audit also checks public UAI machine routes for JSON content, public security headers, `X-Robots-Tag: noindex`, and the current short public cache policy.
- Static root discovery, fallback handoff, and shipped locale-source changes should run `scripts/test-uaix-static-discovery-assets.ps1` so `robots.txt`, `sitemap.xml`, `wp-sitemap.xml`, `/.well-known/uaix.json`, `/.well-known/uai.json`, root `.htaccess`, and public locale JSON source keep canonical/public URL posture, aligned public-page maps, current roadmap counts, expected security-header/rewrite markers, and no local/private host leakage even when WordPress Studio is unavailable.
- Direct production response checks now include AI Memory, the optional AI Memory LLM Wiki guide, AI Memory Package Wizard, canonical static root discovery markers, well-known manifest guardrails, HSTS, and static-root header parity in addition to the UAI-1, validator, REST, conformance, and security-header surfaces.
- If the production response check fails while local static discovery passes, treat it as deployment drift: deploy the current packages, refresh permalinks or apply the production `.htaccess`/edge equivalent, update copied root fallback assets, configure static-file HSTS/security headers at the host or CDN, and rerun the production checker.
- AI Memory and handoff route changes should verify `/en-us/ai-memory/`, `/en-us/ai-memory/llm-wiki/` when LLM Wiki guidance is touched, `/en-us/specification/project-handoff/` when Project Handoff positioning is touched, `/en-us/guides/project-handoff-openai/` when OpenAI/Codex compatibility guidance is touched, `/en-us/guides/project-handoff-coding-agents/` when cross-tool coding-agent guidance or local pointer files are touched, `/en-us/guides/project-handoff-context-budget/` when hot/cold memory or context-budget guidance is touched, `/en-us/tools/ai-memory-package-wizard/` when the wizard is touched, the `/AI_Memory` redirect alias, representative on-demand starter ZIP routes, and `scripts/test-uaix-ai-memory-bundle.php` because those surfaces are part of the public memory and handoff entry path.

## Release Expectations

- Publish ZIPs to `[local path redacted]`.
- Building or refreshing ZIPs is release-scoped work and should run the full publish path unless an intentional documented exception applies.
- A full build also includes source-document hygiene: update and clean `AGENTS.md`, `readme.human`, loaded `.uai` files, canonical Markdown docs, helper navigation, release notes, and progress/history records that describe the state being packaged.
- Full builds must verify that source-only Markdown, private `.uai`, `readme.human`, intake, and archive files remain excluded from WordPress upload ZIPs, sitemap output, and public discovery manifests unless deliberately converted into public copy.
- Keep machine artifacts, public pages, docs, and changelog aligned.
- Keep English and zh-CN public surfaces aligned for route additions, support panels, metadata, release notes, and audit expectations.
- Treat installability, routing, discovery, and response posture as release requirements, not optional follow-up.
- Keep the `uaix-seo-sweep` runtime redirect, `wp-content/advanced-cache.php` anonymous drop-in behavior, and generated production fallback `.htaccess` typo-domain redirect aligned.

## Editing Workflow

1. Read `AGENTS.md` first.
2. Read root `readme.human` as the human briefing companion; do not treat it as an override.
3. Perform chat-start file intake from `Content/` and `Improvement/`, ignore `Archive/`, and then load the listed `.uai` files.
4. Process every `needs-agent-review` file from `.uai/intake-index.uai`: inspect, summarize, and disposition it before unrelated broad work.
5. Check canonical docs before changing project truth.
6. Prefer narrow edits that match existing repo patterns.
7. Verify through targeted scripts or WordPress runtime checks where possible, using `.uai/test-plan.uai` to decide scope.
8. Record blockers or support-boundary changes in docs or progress files.
9. Keep recurring handoff work local and auditable; use direct UAIX.org reading only for bootstrap, refresh, or public-source verification.
10. Keep handoff pickup in chat: do not add CI jobs or background automation for intake refresh or handoff lint.

## Source Boundary Checks

- Use `[local path redacted]` for UAI public-site, Project Handoff, and UAI-1 source-of-truth work.
- Treat `[local path redacted]` as historical split context unless the human explicitly asks for cross-repo migration cleanup.
- Keep Protocol5.com copy scoped to .NET plugin and NuGet package distribution with links back to UAIX.org.
- When docs mention Protocol5.com, check that they do not make it the UAI-1 standards site, validator authority, registry authority, or public roadmap authority.

## Handoff Workflow

1. Update `AGENTS.md` and `readme.human` when current state, human-facing steering guidance, or next steps change materially.
2. Perform chat-start file intake from `Content/` and `Improvement/` so dropped files become intake records before planning broad work; use `scripts/Invoke-UaiFileIntake.ps1` when available and ignore `Archive/` unless a human explicitly references it.
3. Treat intake records as action-required review inputs: inspect and disposition each `needs-agent-review` file before unrelated broad work using one of `apply-now`, `convert-into-roadmap-progress`, `archive-as-duplicate`, `defer-with-reason`, `ask-for-clarification`, or `block-as-unsafe-or-out-of-scope`.
4. Move processed files into `agent-file-handoff/Archive/` only after their disposition has been recorded in durable state.
5. Update affected `.uai` files when stack, constraints, public surface, decisions, or operations change.
6. Keep agent history append-only.
7. Keep high-impact changes explicit and reviewable.
8. Do not move handoff pickup into CI; chat pickup is the project rule.

## Handoff Pattern Maintenance

- Keep `.uai/handoff-pattern.uai` aligned with `/en-us/specification/project-handoff/`.
- When public handoff guidance changes, update root `AGENTS.md`, `.uai/progress.uai`, `.uai/public-surface.uai`, and the relevant canonical docs in the same pass.
- Treat `Project Handoff` as the practical transfer page and `AGENTS.md .uai Linking Specification` as deeper reference.
- Treat `AI Memory` as the broad public/search entry page, supported bundle taxonomy, and canonical template/manifest source for starter memory packets. Treat Project Handoff as portable project memory for runtimes such as OpenAI and Codex, not as a runtime orchestrator, scheduler, or OpenAI replacement. Treat the LLM Wiki guide as optional package-tailoring guidance, not a standards requirement. Treat `AI Memory Package Wizard` as the six-step guided package-planning UI over those same canonical bundles plus page-level validation, local draft restore, generated system profile with source-authority/evidence/conflict/risk/rollback protocols, generated receiver brief, generated startup packet, generated local overlay, readiness metadata, and optional LLM Wiki plan files, not as a hosted importer, repository writer, automatic wiki sync service, SDK, CLI, certification, or endorsement surface.
- After public-surface changes, run the targeted launch-surface, performance, helper-doc, search-metadata, zh-CN, route, or package checks that fit the changed surface. Run the full package/release suite only for ZIP builds, release candidates, broad launch-surface changes, or explicit human requests.
- During full build/release work, include internal documentation cleanup for `.md`, `.uai`, and `.human` source files alongside package and launch checks.

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 custom 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 Operations; Common Commands; Common Checks; Release Expectations; Editing Workflow; Source Boundary Checks; Handoff Workflow; Handoff Pattern Maintenance. 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
• UAI system index
• Source provenance
• Global File Index
• Reports

Provenance And History

• Current observation: 2026-05-02T01:47:31.8867765Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-039 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Operations",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/uai-system/files/uai-operations-uai-165e5c67/",
    "source_reference":  ".uai/operations.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:165e5c67d664352d1d8896dd8c31cc4105b4761c3deb2eea0caeab8c9f8ef8c3",
    "last_fetched":  "2026-05-02T01:47:31.8867765Z",
    "last_changed":  "2026-05-01T19:15:31.7728010Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-039",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-02T01:47:31.8867765Z"
}