Skip to content
aiWikis.org

Test Plan

Use targeted checks for ordinary edits and full package checks for release or package work.

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/uai-test-plan-uai-43cd3212/
Source reference.uai/test-plan.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-03T02:48:13.1276041Z
Last changed2026-05-02T01:49:04.9815551Z
Content hashsha256:43cd32123b57a5f5432902e7d7a7539b032d4e0dfb840d26bdd36c621cad6e20
Import statusunchanged
Raw source layerdata/sources/aiwikis/uai-test-plan-uai-43cd32123b57.uai
Normalized source layerdata/normalized/aiwikis/uai-test-plan-uai-43cd32123b57.txt

Current File Content

Structure Preview

  • Test Plan
  • Targeted Checks
  • Package Checks

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.

---
uai: "1.0"
type: test-plan
project: "AIWikis.org"
updated: "2026-05-02"
status: active
---

# Test Plan

Use targeted checks for ordinary edits and full package checks for release or package work.

## Targeted Checks

- Run `scripts/Invoke-UaiFileIntake.ps1` when handoff state or dropped files matter.
- Run `tools/smoke-test.ps1` after theme, plugin, package, or source-package reference changes.
- Run `tools/wiki-lint.ps1` after changes to `raw/`, `wiki/`, `config/CLAUDE.md`, or `config/graph.jsonld`.
- Run `tools/generate-handoff-export.ps1` after changes to `.uai`, `AGENTS.md`, `readme.human`, recommendation docs, or wiki nodes marked `handoff_export: include`.
- Run `tools/wiki-lint.ps1` and verify the transfer manifest parses as JSON after changes to `raw/system-archives/`.
- Run `scripts/Invoke-UaiFileIntake.ps1` after dispositioning active intake into the Deep Cognitive Archive, System Memory Archive, or Intake Outcome Ledger.
- Run `tools/fetch-sources.ps1` when source URLs, manifests, or source observations change.
- Run `tools/reprocess-content.ps1 -DryRun` before recovered-content import work, then run `tools/reprocess-content.ps1` for the real import and inspect `reports/import-summary.md`, `reports/duplicate-resolution.md`, `reports/broken-links.md`, and `reports/final-content-map.md`.
- Run `tools/sync-source-files.ps1 -DryRun` before transparent source-file work, then run `tools/sync-source-files.ps1` for the real sync and inspect `reports/source-file-inventory.json`, `reports/source-file-inventory.md`, `reports/sync-log.md`, `reports/changed-files.md`, `reports/generated-explanations.md`, `reports/duplicate-resolution.md`, `reports/archive-recovery.md`, `reports/broken-links.md`, and `reports/final-content-map.md`.
- Run `tools/generate-manifest.ps1` when source-package references change.
- Run `tools/smoke-test.ps1` after changing the file-backed router, nested route behavior, discovery routes, generated public pages, or package-visible content pages.
- `tools/smoke-test.ps1` must fail if a non-code Markdown link points to an AIWikis route without a reviewed content page or supported discovery endpoint, or if missing Markdown-backed public routes no longer emit an explicit 404.
- Run `tools/link-crawl-test.ps1` when live or local HTTP link integrity matters. The crawler starts from `https://aiwikis.org/` by default, follows same-site HTML routes with bounded page, link, depth, queue, and sitemap-entry limits, writes `reports/link-crawl-report.md` and `.json`, and exits nonzero when bad links are found unless `-NoFail` is used for report-only triage. Localhost crawls trust the local Markdown route map for same-site page-target checks while still GET-crawling rendered pages; live `https://aiwikis.org/` crawls use HTTP target checks unless `-TrustLocalRoutes` is deliberately passed. Sitemap indexes are walked iteratively and used as fallback seeds after linked-page frontiers, not recursive priority crawls. Use `-NoSitemap` for linked-depth local graph crawls when sitemap coverage is not needed.
- Run `tools/smoke-test.ps1` after changing the source-file sync script, generated `/uaix/`, `/llmwikis/`, `/protocol5/`, `/files/`, `/concepts/`, or `/reports/` pages, report generation, public path redaction, or raw-code rendering behavior.
- `tools/smoke-test.ps1` must fail if a generated `file_type: "html"` source-file page exposes a fenced raw HTML block instead of the normalized readable text layer.
- Run `tools/smoke-test.ps1` after changing `content/pages/017-roadmap.md` or roadmap navigation so `/roadmap/` stays package-visible and support boundaries remain explicit.
- Run `tools/smoke-test.ps1` after changing `content/pages/018-uaix-source-memory-guide.md`, `content/pages/019-llmwikis-source-memory-guide.md`, `content/pages/030-protocol5-source-memory-guide.md`, or source-memory navigation so `/uaix/source-memory-guide/`, `/llmwikis/source-memory-guide/`, and `/protocol5/source-memory-guide/` stay package-visible and source authority boundaries remain explicit.
- Run `tools/smoke-test.ps1` after changing `content/pages/027-cross-site-memory-atlas.md`, `content/pages/028-source-memory-operations-playbook.md`, or cross-site memory navigation so authority routing, artifact ownership, evidence flow, operations workflow, and non-claims stay package-visible.
- Run `tools/smoke-test.ps1` after changing `content/pages/031-source-site-outcome-routing.md` or outcome-routing navigation so source-site staged work, AIWikis visibility, and non-claims stay package-visible.
- Run `tools/smoke-test.ps1` after changing `content/pages/029-memory-coverage-matrix.md`, `content/pages/029-claim-boundary-register.md`, or coverage/claim navigation so covered, partially covered, source-only, dogfood-only, planned, and blocked support language stays package-visible.
- For UAIX AI Memory Wizard source-sync work, inspect that generated UAIX pages and public docs name populated protocol outputs while preserving non-claims around hosted import, automatic writes, automatic LLM Wiki sync, SDK, CLI, certification, and endorsement.
- For Protocol5 source-sync work, inspect that generated Protocol5 pages and public docs name UAI .NET package, route-contract, starter ZIP, NuGet, and compatibility-mirror evidence while preserving non-claims around UAI-1 standards authority, validator authority, conformance approval, certification, endorsement, and generated Prime/Fibonacci route syncing.

## Package Checks

Package work should verify:

- Theme ZIP root is `aiwikis-authority`.
- Theme ZIP contains `aiwikis-authority/style.css` with forward-slash archive entries.
- Plugin ZIP root is `aiwikis-core`.
- Plugin ZIP contains `aiwikis-core/data/pages/*.md`, the file-backed Markdown router, and no `aiwikis_core_import_seed_pages` or `wp_insert_post` seed importer path.
- Release evidence ZIP root is `aiwikis-release-evidence`.
- Source-package references name LlmWikis.org as publisher of `llm-wiki-starter-bundle.zip`, UAIX.org as publisher of `uai1-project-handoff.zip`, and Protocol5.com as publisher of Protocol5 UAI .NET implementation artifacts.
- `[local path redacted]` exists after packaging, uses plugin root `uai1-project-handoff`, and remains labeled as UAIX.org-owned in the release manifest and checksum output.
- `[local path redacted]` does not contain `aiwikis-starter-pack.zip` or `aiwikis-starter-pack-v*.zip`.
- No `.git`, `node_modules`, `.env`, secrets, private keys, raw private material, or cache folders enter ZIPs.
- Source-side wiki lint passes and raw local source inputs remain outside WordPress upload ZIPs.
- Local Project Handoff export generation passes and includes `.uai/context.uai` plus `wiki-nodes/concepts/uai-handoff-export-loop.md` when package/release evidence is built.
- PHP lint runs when `php` is available; otherwise record the skip reason.

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 test-plan 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: Test Plan; Targeted Checks; Package Checks. 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-119 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Test Plan",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/uai-test-plan-uai-43cd3212/",
    "source_reference":  ".uai/test-plan.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:43cd32123b57a5f5432902e7d7a7539b032d4e0dfb840d26bdd36c621cad6e20",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-02T01:49:04.9815551Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-119",
    "duplicate_role":  "primary",
    "related_files":  [

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