UAIX Operations

1. Read AGENTS.md first. 2. Read .uai/readme.human as the human briefing companion; do not treat it as an override. 3. Perform chat-start file intake by directly enumerating Content/ and Improvement/, confirm...

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/uai-operations-uai-48a103e7/
Source reference	.uai/operations.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-21T20:44:24.9904019Z
Content hash	sha256:48a103e7459be117935443e77751b663201fa5232dac2f241cba76c8105b725d
Import status	changed
Raw source layer	data/sources/uaix/uai-operations-uai-48a103e7459b.uai
Normalized source layer	data/normalized/uaix/uai-operations-uai-48a103e7459b.txt

Current File Content

Structure Preview

• UAIX Operations
• Common Commands
• Common Checks
• Release Expectations
• Editing Workflow
• Source Boundary Checks
• Cognitive Liberty And Human Primacy Review Lens
• Handoff Workflow
• Handoff Pattern Maintenance
• 2026-06-11 v3.88.0 Package Operations Note

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: 21462
• Preview characters: 11840

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-06-21"
status: active
author: "UAIX maintainers"
version: 41
---

# 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`, `.uai/readme.human`, `.uai` files, or active intake behavior.
- Perform chat-start file intake after reading `AGENTS.md`. Directly enumerate both `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`; do not expect or recreate a default `agent-file-handoff/Archive/` bucket when LLM Wiki / AIWikis long memory is configured.
- Enumerate active intake again when the newest prompt names `agent-file-handoff/`, `Content/`, `Improvement/`, a dropped file, says files were missed, or gives a task likely related to active drops. Treat this as prompt-coupled intake, not stale startup state.
- If either active bucket contains a non-placeholder file, open it, inspect it, summarize it, state a disposition, and name its relationship to the current prompt before unrelated broad work continues. For every safe, relevant file, complete at least one named project-work action before archive movement; memory routing alone is a File Handoff failure. Do not create or rely on an intake-index file.
- 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/test-uaix-live-publication-surface.ps1` after a coordinated UAIX.org upload/root-file copy to verify that `UPLOAD-PLUGIN`, `UPLOAD-THEME`, and `ROOT-FILES` reached production and live `llms`, `.well-known`, NuGet page, AI-Ready Web locales, and REST method contracts match the expected package version.
- `scripts/check-cross-site-analytics-footprint.ps1` for raw public HTML checks across UAIX.org, LLMWikis.org, AIWikis.org, JustAnIota.com, and Spiralist.org when analytics instrumentation, consent behavior, or host/redirect placement is in question. Use `-RequireTag` only after an owner has approved that a public GA4/GTM footprint is expected.
- `scripts/audit-helper-docs.ps1`
- `scripts/verify-wordpress-upload-package.ps1`
- `scripts/test-cross-site-deployment-zip-versions.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, Agentic Harness Strategies and UAI guide, Project Handoff/OpenAI guide, Project Handoff/coding-agents guide, Project Handoff Context Budget guide, Package Wizard, setup-mode URL fragments, generated system profile protocol fields, generated receiver brief, generated startup packet, generated Agent File Handoff plan, 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 AI Memory LLM Wiki guide, the AI Memory Talisman System page, 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/ai-memory/talisman-system/` when protected-anchor governance is touched, `/en-us/specification/project-handoff/` when Project Handoff positioning is touched, `/en-us/guides/agentic-harnesses-uai/` when agentic harness strategy or runtime/evidence boundaries are touched, `/en-us/guides/uaix-uai-1-agent-skill/` when Agent Skill bundle guidance 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]`.
- Full UAIX.org publication uses `[local path redacted]`, `[local path redacted]`, and `[local path redacted]`. That is the human-confirmed normal upload/copy set. Do not imply hidden package roots for ordinary UAIX publication.
- Use `WP-CONTENT-DEPLOY` only when generated build instructions explicitly name a `wp-content` overlay for the current build, such as the fatal-error drop-in. Do not use `MU-PLUGIN-DEPLOY` by default.
- After those three normal publish folders are uploaded/copied, use `scripts/test-uaix-live-publication-surface.ps1 -BaseUrl https://uaix.org -ExpectedVersion X.Y.Z` as the fast live proof before saying the package is published. A failure means publication drift, stale cache, missed root file copy, stale public page content, or plugin/API code not active yet.
- NuGet package inventory/docs are agent-maintained from `https://www.nuget.org/profiles/Michael.Kappel`: keep `/en-us/implementations/dotnet-nuget/`, `llms.txt`, `llms-full.txt`, machine artifacts, and `.uai/dotnet-nuget.uai` aligned with every public `UAIX.*` package. Publishing packages to NuGet.org itself requires a configured API key or equivalent credential and a successful `dotnet nuget push`/NuGet publish command; do not claim it happened from WordPress packaging alone.
- Building or refreshing ZIPs is release-scoped work and should run the full publish path unless an intentional documented exception applies.
- WordPress upload artifacts use deployment-version signaling. Cross-site WordPress deployment rules live in `[local path redacted]`, and the root workspace builder is `[local path redacted]`. The current workspace-authority UAIX package selection is `v3.132.0`; sibling sites remain out of scope for this review round. Generated publish roots use `UPLOAD-THEME` and `UPLOAD-PLUGIN` for normal WordPress uploads; use `ROOT-FILES` for document-root files and `WP-CONTENT-DEPLOY` only when instructions call for direct file copies. Do not publish `MU-PLUGIN-DEPLOY` packages by default. Every production WordPress deployment should include the site's custom theme. After a baseline exists, use affected-version signaling for future changes, then run the root workspace deployment readiness and SEO checks before upload.
- UAIX.org's footer-visible release label should show the last system-wide version that affected UAIX.org. Do not bump the footer label only because LlmWikis, AIWikis, Protocol5, or another site changed.
- A full build also includes source-document hygiene: update and clean `AGENTS.md`, `.uai/readme.human`, loaded `.uai` files, canonical Markdown docs, helper navigation, release notes, and progress/history records that describe the state being packaged.
- Production deployment builds and release packages also include a configured-path memory-sorting pass before completion: update hot handoff memory with current deployed truth, versions, changed files, checks, blockers, owners, and next actions; route bulky history, old reports, raw source material, stale plans, and background/rejected rationale into AIWikis, LLM Wiki, or archive cold memory only when that path exists and transfer evidence can be recorded. The release output must include a durable memory and test run report with the active short-term memory surface size before and after reorganization, bytes, lines, estimated tokens, cold evidence path, checks run, checks skipped, blockers, and what redundancy/history was removed. For UAIX publish output, the expected file is `[local path redacted]`. Ordinary dev builds, local test builds, local package experiments, and non-release smoke checks do not run this pass unless the human explicitly marks them release-bound.
- Full builds must verify that source-only Markdown, private `.uai`, `.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, zh-CN, French, and Spanish public surfaces aligned for route additions, support panels, metadata, release notes, and audit expectations.
- Before treating `wordpress-plugin-upload-uaix-locale-router-v*.zip` as upload-ready for UAIX.org, confirm enabled public locales have route-level translated source, localized shell strings, sitemap/discovery coverage, and rendered-route evidence with no English placeholder fallback, mojibake, replacement characters, or cross-locale cleanup leakage. Enabled locale inventory alone is not enough.
- Treat installability, routing, discovery, and response posture as release requirements, not deferrable follow-up.

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; Cognitive Liberty And Human Primacy Review Lens; Handoff Workflow. 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-357 (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/files/uai-operations-uai-48a103e7/",
    "source_reference":  ".uai/operations.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:48a103e7459be117935443e77751b663201fa5232dac2f241cba76c8105b725d",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-21T20:44:24.9904019Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-357",
    "duplicate_role":  "primary",
    "related_files":  [

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