Skip to content
aiWikis.org

UAIX Test Plan

This file tells AIs how to choose verification for ordinary UAIX work without turning every edit into a release sweep.

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/raw-system-archives-uaix-recent-work-sweep-2026-05-03-uai-test-plan-uai-1a697c14/
Source referenceraw/system-archives/uaix/recent-work-sweep/2026-05-03/.uai/test-plan.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-02T23:56:59.0030290Z
Content hashsha256:1a697c146c80b661ce03c540402a035715a88988dfbcc33f17bbde605e267f0f
Import statusunchanged
Raw source layerdata/sources/aiwikis/raw-system-archives-uaix-recent-work-sweep-2026-05-03-uai-test-plan-uai-1a697c146c80.uai
Normalized source layerdata/normalized/aiwikis/raw-system-archives-uaix-recent-work-sweep-2026-05-03-uai-test-plan-uai-1a697c146c80.txt

Current File Content

Structure Preview

  • UAIX Test Plan
  • Purpose
  • Default Rule
  • Targeted Check Selection
  • Full Sweep Triggers
  • Full Release Path
  • Full Build Documentation Hygiene
  • First And Final Response

Raw Version

---
uaix: "1.0"
type: custom
title: "UAIX Test Plan"
created: "2026-04-28"
updated: "2026-05-02"
status: active
author: "UAIX maintainers"
version: 16
---

# UAIX Test Plan

## Purpose

This file tells AIs how to choose verification for ordinary UAIX work without turning every edit into a release sweep.

## Default Rule

For normal prompt-driven work, run the smallest meaningful set of checks tied to the files, routes, records, or behaviors changed. Do not build ZIPs, refresh publish outputs, or run the full launch/performance/locale/package sweep unless the task is release scoped, package scoped, explicitly asks for that level of verification, or touches global behavior that makes the full sweep relevant.

## Targeted Check Selection

- Always consider `git diff --check` after edits.
- Run the chat-start intake helper before broad work, and rerun it when active intake files are moved or dispositioned.
- Run `scripts/lint-uaix-handoff.ps1` after editing `AGENTS.md`, `readme.human`, `.uai` records, or `agent-file-handoff/` intake/index behavior.
- Validate `.agents/skills/uaix-handoff/` after editing the Codex-local skill, using the Codex skill validator when Python is available through `py` or another local launcher.
- For thin coding-agent pointer files such as `CLAUDE.md`, `GEMINI.md`, `.cursor/rules/uaix-handoff.mdc`, and `.github/copilot-instructions.md`, run the handoff linter and verify the files still point back to `AGENTS.md` instead of duplicating project truth.
- Handoff lint and intake refresh are chat-session targeted checks, not CI jobs. Do not add CI, scheduled, or background automation for this workflow.
- For edited PHP, run the narrowest available PHP syntax or Studio lint check that covers the touched theme/plugin/script files.
- For edited JSON, YAML, or machine records, parse the changed files or run the focused route/catalog check that exercises them.
- For public copy, homepage CTA, or route-linking changes, check the affected page route, page metadata, and any paired public discovery entry when the local runtime is available. For homepage entry-path changes, include a rendered home-route check and launch-surface/performance checks when the change can affect first-viewport usability or page weight.
- For public UI, wizard, guide, hero, or card-grid changes, inspect representative desktop and mobile rendering for wasted real estate, awkward text wrapping, cramped labels beside empty space, oversized blank bands, and decorative assets that displace useful content. A layout is not done if it burns space while making text harder to read.
- For AI Memory taxonomy, template, manifest, Project Handoff, Agentic Harness Strategies and UAI guide, OpenAI/Codex guide, coding-agents guide, Context Budget guide, rendered sample, optional LLM Wiki guide, Package Wizard, setup-mode URL fragments, generated system profile protocol fields, generated receiver brief/startup packet, generated Agent File Handoff plan, generated LLM Wiki plan/readiness behavior, or starter bundle changes, run `scripts/test-uaix-ai-memory-bundle.php` through `scripts/studio-wp-quiet.ps1 eval-file` and check representative affected page/ZIP route output when the local runtime is available.
- For handoff-only or Markdown-only changes, verify whitespace, the affected navigation links, the relevant handoff file load list, and the local handoff linter. Do not run package publishing just because docs changed.
- For REST, discovery, sitemap, robots, well-known, locale-routing, localized source content, redirect, cache, fallback `.htaccess`, HSTS, or security-header changes, add the focused audit that covers that surface. Use `scripts/test-uaix-static-discovery-assets.ps1` for Studio-independent static root asset and public locale source URL-hygiene checks, `scripts/run-uaix-launch-surface-http-audit.ps1` when runtime route behavior is in scope, and `scripts/test-uaix-production-response-surface.ps1` after deployment or edge/header changes.

## Full Sweep Triggers

Run the supported publish/release path and broad audits only when one of these is true:

- The human asks to build, refresh, publish, or validate release ZIPs.
- The task changes package contents, checksums, publish scripts, upload-package validation, activation behavior, or bundled release artifacts.
- The task changes root discovery files, sitemap output, robots output, well-known manifests, canonical host behavior, locale routing, public search/cache posture, REST guardrails, security headers, or production fallback assets in a way that affects the launch surface.
- The task is a pre-production, release-candidate, deployment, migration, or broad launch-readiness pass.
- A targeted check exposes a failure whose blast radius cannot be bounded without the full sweep.

## Full Release Path

When a full sweep is required, use `scripts/publish-wordpress-packages.ps1` and the release guidance in `docs/deploy.md`. That path owns ZIP output, checksum refresh, package validation, launch-surface audit, zh-CN audit, and Studio smoke testing unless a documented release exception says otherwise.

## Full Build Documentation Hygiene

A full build or release pass must also clean and update source documentation before the result is treated as ready:

- Reconcile `AGENTS.md`, `readme.human`, loaded `.uai` files, canonical Markdown docs, helper navigation, progress, roadmap, deployment notes, and agent history with the public state being built.
- Run whitespace and helper-document checks such as `git diff --check` and `scripts/audit-helper-docs.ps1` when Markdown or navigation files are part of the release truth.
- Refresh `.uai/intake-index.uai` and archive or disposition active source files before publishing release evidence.
- When slimming internal `.md`, `.human`, or `.uai` files into AIWikis cold memory, verify the AIWikis transfer manifest parses, spot-check copied hashes or run the transfer script's hash verification, and then run UAIX handoff lint plus wiki lint if AIWikis wiki nodes changed.
- Keep intake refresh and handoff lint as in-chat/local checks even during release work; do not introduce CI pickup for the handoff workflow.
- Verify WordPress upload ZIPs and public sitemap/discovery output still exclude repository Markdown instruction files, private `.uai` files, root `readme.human`, raw intake files, and archived source files.
- Keep source docs source-only unless a specific page intentionally converts their public guidance into website copy.

## First And Final Response

Before broad edits, the AI should name the targeted checks it expects to run and say whether a full release sweep is out of scope. In the final response, report which checks ran, which release/package checks were intentionally not run, and any blocker that prevented a relevant targeted check.

Why This File Exists

This is a UAI AI Memory handoff file from aiwikis.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 Test Plan; Purpose; Default Rule; Targeted Check Selection; Full Sweep Triggers; Full Release Path; Full Build Documentation Hygiene; First And Final 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

Provenance And History

  • Current observation: 2026-05-03T02:48:13.1276041Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-050 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Test Plan",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/raw-system-archives-uaix-recent-work-sweep-2026-05-03-uai-test-plan-uai-1a697c14/",
    "source_reference":  "raw/system-archives/uaix/recent-work-sweep/2026-05-03/.uai/test-plan.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:1a697c146c80b661ce03c540402a035715a88988dfbcc33f17bbde605e267f0f",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-02T23:56:59.0030290Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-050",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-03T02:48:13.1276041Z"
}