Skip to content
aiWikis.org

LlmWikis Test Plan

This file tells AIs how to verify LlmWikis changes without turning every content or handoff edit into a package release.

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-test-p-843aaba0/
Source referenceraw/system-archives/llmwikis/internal-memory-reorg/2026-05-01/.uai/test-plan.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-02T01:47:31.8867765Z
Last changed2026-04-28T17:48:37.5207341Z
Content hashsha256:843aaba077ba0f78deed77e503d063df43da44308b1738466591217ac0bb7aec
Import statusunchanged
Raw source layerdata/sources/aiwikis/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-test-plan-uai-843aaba077ba.uai
Normalized source layerdata/normalized/aiwikis/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-test-plan-uai-843aaba077ba.txt

Current File Content

Structure Preview

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

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: "LlmWikis Test Plan"
created: "2026-04-28"
updated: "2026-04-28"
author: "LlmWikis maintainers"
version: 1
---

# LlmWikis Test Plan

## Purpose

This file tells AIs how to verify LlmWikis changes without turning every content or handoff edit into a package release.

## 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 `[local path redacted]`, or run full package/runtime smoke checks unless the task is release scoped, package scoped, explicitly asks for that level of verification, or changes global public behavior that needs broad confirmation.

## Targeted Check Selection

- Always consider `git diff --check` after edits.
- Run `scripts/Invoke-UaiFileIntake.ps1` before broad work, and rerun it when active intake files are moved or dispositioned.
- For edited PHP, run `studio wp eval-file scripts/lint-llmwikis.php` when the corrected Studio site is available; if the Studio registration blocker remains, report that blocker instead of claiming runtime lint passed.
- For edited root discovery files, check `llms.txt`, `robots.txt`, or `sitemap.xml` directly and verify private `AGENTS.md`, `readme.human`, `.uai/`, intake files, and package archives are not exposed.
- For public page copy or route changes, check the affected route, route metadata, and related sitemap or `llms.txt` entry when the runtime is available.
- For starter-template or bundle changes, run `php scripts/test-llmwikis-starter-bundle.php` when PHP CLI is available and `powershell -NoProfile -ExecutionPolicy Bypass -File scripts/Test-LlmWikisPublicSurface.ps1`; these checks guard canonical template definitions, bundle manifests, dynamic ZIP drift, public routes, discovery files, and private-file exclusions.
- For handoff-only changes, verify the load list, active intake state, whitespace, and public guidance that names the pattern. Do not run package publishing just because handoff files changed.

## Full Sweep Triggers

Run the package and broad smoke path 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, mirrored UAIX package handling, theme/plugin activation behavior, or upload-package boundaries.
- The task changes root discovery files, public sitemap coverage, `llms.txt`, route seeding, canonical routes, permanent `410` retirement behavior, or global metadata behavior in a way that affects the whole public surface.
- The task is a pre-production, release-candidate, deployment, migration, or broad public-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-llmwikis-packages.ps1`. That path owns the WordPress upload ZIPs, checksum refresh, mirrored UAIX dogfood package copy, and source/site archive outputs.

## Full Build Documentation Hygiene

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

- Reconcile `AGENTS.md`, `readme.human`, loaded `.uai` files, strategy/progress/public-surface records, source-document disposition notes, and any active Markdown source files that describe the state being packaged.
- Refresh `.uai/intake-index.uai` and archive or disposition active source files before publishing release evidence.
- Verify `llms.txt`, `robots.txt`, `sitemap.xml`, WordPress upload ZIPs, and source/site archive boundaries do not expose private `AGENTS.md`, private `.uai` files, root `readme.human`, raw intake files, archived source files, package archives, or retired private docs.
- Keep source docs source-only unless a specific page intentionally converts their guidance into public handbook 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: LlmWikis 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-02T01:47:31.8867765Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-237 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LlmWikis Test Plan",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-test-p-843aaba0/",
    "source_reference":  "raw/system-archives/llmwikis/internal-memory-reorg/2026-05-01/.uai/test-plan.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:843aaba077ba0f78deed77e503d063df43da44308b1738466591217ac0bb7aec",
    "last_fetched":  "2026-05-02T01:47:31.8867765Z",
    "last_changed":  "2026-04-28T17:48:37.5207341Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-237",
    "duplicate_role":  "primary",
    "related_files":  [

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