LLMWikis Progress

LLMWikis Progress is a uai-system source file exposed by AIWikis.org with provenance, current content, and generated explanation.

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/uai-progress-uai-0d9af670/
Source reference	.uai/progress.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-13T22:31:31.9970456Z
Content hash	sha256:0d9af67025160a41760b0066fb3319ac9c36e19f5bd41261850012059e64fbb0
Import status	unchanged
Raw source layer	data/sources/llmwikis/uai-progress-uai-0d9af6702516.uai
Normalized source layer	data/normalized/llmwikis/uai-progress-uai-0d9af6702516.txt

Current File Content

Structure Preview

• LlmWikis Progress
• Recently Completed
• Intake Outcome Ledger
• 2026-05-24 next-level source map, repair mode, and UAIX memory alignment
• 2026-05-15 follow-up site review intake: short-route compatibility and evidence preservation
• 2026-05-15 Improvement batch: strict constraint and shared-wiki topology overhaul
• 2026-05-11 Improvement handoff recovery: wizard, guidance, and memory loop
• 2026-05-09 AI Dreaming Memory management intake
• 2026-05-06 targeted setup wizard refinement
• 2026-05-06 Canonical AI Memory cross-site intake
• 2026-05-06 Knowledge Graph guidance and wizard intake
• 2026-05-03 setup wizard and feature/UI reports
• Current Focus
• Known Blockers
• Next Work
• Done Means
• 2026-06-13 Full .uai And Wiki Wizard Dogfood Alignment
• 2026-06-13 Desktop Sticky Header Source Pass
• 2026-06-13 Long-Run Agent Wiki Strategy Intake
• 2026-06-13 UAIX And LLMWikis Quality Sweep
• 2026-06-13 Workspace v3.106.0 Package Build

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: 70798
• Preview characters: 11831

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: progress
title: "LlmWikis Progress"
created: "2026-04-26"
updated: "2026-05-31"
author: "LlmWikis maintainers"
version: 60
---

# LlmWikis Progress

## Recently Completed

- Retired the source-site `agent-file-handoff/Archive/` pattern for UAI File Handoff plus LLM Wiki/AIWikis long memory. Current rule: active intake lives in `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`; processed originals are preserved in the configured AIWikis/LLM Wiki evidence path with checksums/manifests, then removed from the source site unless explicitly kept active. LlmWikis preserved 64 retired Archive files into AIWikis raw system archives under `raw/system-archives/llmwikis/agent-file-handoff/retired-source-archive-2026-06-13/` with manifest `raw/system-archives/2026-06-13-llmwikis-agent-file-handoff-archive-retirement.json`. Older progress entries that mention local Archive paths are historical provenance, not current storage guidance.
- Tightened the LLM Wiki Setup Wizard and local Project Handoff suite for update-ready coding standards. Accepted work: added `.uai/coding-standards.uai`, added it to required agent context and workspace guidance, updated short- and long-term memory with a compact overview and durable requirement, and changed the wizard output/model/tests so code-capable setup creates or verifies `.uai/coding-standards.uai`, reflects on the target codebase good parts, preserves DRY and once-and-only-once ownership, applies SOLID defaults, and requires automated testing for every language. The wizard still treats existing systems as additive updates and preserves existing preferences, customizations, source evidence, and coding standards.
- Hardened LLMWikis multisite guidance after the AIWikis route-boundary defect surfaced. The setup wizard/spec/public guidance now says each `https://aiwikis.org/{site}/` namespace is its own AI Wikisite, site-owned files and memory must live under `/{site}/...`, `/site/` is the directory, `/org/` is the global organization namespace, and root mixed-memory surfaces such as `/files/`, `/concepts/`, `/reports/`, `/browse/`, and `/browser/` are invalid.
- Deepened the 2026-05-24 specification and search surface after the next-level pass. Accepted work: added `/reference/specification/` as a managed public reference route with profile contracts, conformance levels, required artifacts, minimal page record, search/retrieval requirements, and validation gates; linked it from Reference, Explore, Source Map, header/footer navigation, `llms.txt`, `sitemap.xml`, route metadata, and public-surface tests; expanded the metadata standard with search-result fields; and rebuilt the WordPress search template into a styled reader-facing surface with shortcut links, search-state panels, result cards, and no-result recovery links. Checks passed: scoped LlmWikis preflight, `npm test` (unit plus Playwright e2e across Chromium/Firefox/WebKit), `scripts/Test-LlmWikisPublicSurface.ps1`, `studio wp eval-file scripts/lint-llmwikis.php`, local HTTP smoke for `/reference/specification/`, `/reference/metadata/`, `/?s=metadata`, and `/?s=specification`, marker checks for specification/search/result-card content, and `git diff --check` with line-ending warnings only. Package publishing, ZIP refresh, deployment checklist, upload, and production smoke were intentionally out of scope.
- Processed the 2026-05-24 next-level LLMWikis intake into public handbook, wizard, discovery, runtime, and hot-memory work. Accepted work: added `/source-map/` as a public topic atlas and authority map; upgraded existing-wiki repair guidance with a standards scorecard, input/platform map, migration/remediation outputs, and automation boundary; aligned the LLM Wiki vs AI Memory page and setup wizard with UAIX AI Memory Package Wizard outputs (`UAI_MEMORY_SYSTEM_PROFILE.md`, `UAI_MEMORY_RECEIVER_BRIEF.md`, `UAI_MEMORY_STARTUP_PACKET.md`, optional `LLM_WIKI_MEMORY_PLAN.md`); exposed Source Map from home, Explore, header, footer, `llms.txt`, `sitemap.xml`, route metadata, and public-surface tests; refreshed hot memory in `readme.human`, `.uai/context.uai`, and `.uai/public-surface.uai`. Long-memory/archive: source files are preserved locally under `agent-file-handoff/Archive/2026-05-24/`; external AIWikis cold-memory transfer was not performed because this was a LlmWikis source/public-surface pass and the default root-corpus preflight currently has unrelated AIWikis topology blockers. Checks passed: scoped LlmWikis corpus preflight, `npm test` (unit plus Playwright e2e across Chromium/Firefox/WebKit), `scripts/Test-LlmWikisPublicSurface.ps1`, `studio wp eval-file scripts/lint-llmwikis.php`, local HTTP smoke for touched routes and discovery files, marker checks for the new rendered content, and `git diff --check` with line-ending warnings only. The unscoped default `node scripts/llmwiki-preflight.js validate --root .` remains blocked by existing AIWikis root-corpus namespace/root-file issues outside this LlmWikis change.
- Processed the second 2026-05-15 follow-up site-review intake into route-compatibility work and long-memory preservation. Accepted work: `llmwikis_legacy_redirect_map()` now redirects `/start/`, `/metadata/`, `/trust/`, `/repair/`, and `/starter/` to canonical handbook routes, and `scripts/Test-LlmWikisPublicSurface.ps1` asserts those aliases stay out of `llms.txt`, `sitemap.xml`, header links, and footer links. Long-memory preservation: the two follow-up reports were copied into AIWikis cold memory at `raw/system-archives/llmwikis/2026-05-15-followup-site-review/` with `MANIFEST.json`, moved to `agent-file-handoff/Archive/2026-05-15/Improvement/`, and compiled into AIWikis source/log nodes. Checks passed: intake refresh with zero active files, LlmWikis preflight, public-surface test, unit tests, Playwright e2e, AIWikis preflight, wiki lint, smoke test, regenerated AIWikis handoff export, workspace package rebuild at `3.0.0`, recovery sync, deployment readiness, SEO sweep, Anti-Christ live content, and diff check with line-ending warnings only. Live wiki.fftac.org still needs the rebuilt AIWikis Core package uploaded before its live content check can pass.
- Processed the 2026-05-15 strict constraint Improvement batch into enforcement work instead of memory-only routing. Accepted work: `.llmwiki/preflight.config.json` now scopes multisite topology enforcement to the AIWikis source-side `wiki/` corpus while still validating AIWikis public page stores; `llmwiki-preflight.js` now validates root-relative `llms.txt` routes as canonical discovery entries instead of only checking absolute URLs; `CLAUDE.md` names concrete shared-wiki namespaces; the setup wizard now emits the explicit `wiki/{Site}/` semantic-memory action for multisite output; and the WordPress content filter now prepends a full public trust/status card with Owner, Status, Source Status, Last Reviewed, and Canonical Source when a page lacks the canonical status block. Long-memory preservation: the five original Improvement reports were copied into AIWikis cold memory at `raw/system-archives/llmwikis/2026-05-15-strict-constraint-overhaul/` with `MANIFEST.json`, then moved to `agent-file-handoff/Archive/2026-05-15/Improvement/`. Checks passed: LlmWikis preflight, setup-wizard JS syntax, unit tests, Playwright e2e, public-surface test, workspace package rebuild at `3.0.0`, deployment readiness, SEO sweep, Anti-Christ live content, and diff check with line-ending warnings only. Live wiki.fftac.org still needs the rebuilt AIWikis Core package uploaded before its content check can pass.
- Processed the 2026-05-11 Improvement handoff recovery batch into real source work instead of memory-only routing. Accepted work: LLMWikis Setup Wizard now includes proof-of-use File Handoff completion, `INTAKE_OUTCOME_LEDGER.md` starter guidance, map/canvas/canonical-page planning, `wiki/knowledge-map.md` starter output, starter-bundle schema/checklist updates, browser model output, and regression coverage. Cross-site work: UAIX AI Memory Package Wizard and generated File Handoff/LLM Wiki plans now require proof-of-use ledger evidence and map-to-canonical-page guidance. Long-memory preservation: all 10 original reports were copied into AIWikis cold memory at `raw/system-archives/llmwikis/2026-05-11-improvement-handoff-recovery/` with manifest `MANIFEST.json`.
- Promoted the 2026-05-09 AI Dreaming Memory intake into current LlmWikis handbook and setup-wizard guidance. `/guides/ai-dreaming-memory-management/` now explains dreaming as offline, review-only consolidation over visible source-backed memory, with raw run artifacts, candidate queues, contradiction drafts, metrics, protected surfaces, and reviewed promotion gates. The setup wizard now captures AI Dreaming Memory mode, inputs, run/candidate/contradiction paths, review policy, metrics, first files/actions, readiness, setup packet output, structured model JSON, unit tests, Playwright fixture coverage, and public-surface assertions while rejecting hosted dream services, hidden model memory, model-weight training, automatic writes/sync, SDK, CLI, certification, endorsement, and UAI-1 conformance claims.
- Added the cross-site WordPress Studio health guard and disabled the SpeedyCache `WP_CACHE` early drop-in after affected Studio sites showed front-end critical-error loops that cleared when `/wp-admin` was requested. The guard writes local redacted PHP-wrapped JSONL logs to `wp-content/site-health-logs/`, exposes recent logs only to admins or a configured token, and attempts conservative request-time recovery after recorded front-end fatals without adding daemons, cron, CI, public log exposure, release packages, or production deployment.
- Refined `/tools/llm-wiki-setup-wizard/` from a long-form planning surface into a step-by-step browser wizard. The top wizard page now has a more deliberate planning brief and route-specific page-header styling; the existing visual entry cards remain. Project Handoff is now a selectable branch that reveals hot-memory/transfer-context follow-up questions only when selected, and the combined File Handoff plus LLM Wiki path keeps Project Handoff optional. The second polish pass added active setup-path styling, selected-answer states, styled textarea fields, and browser coverage for manual setup-mode routing. Targeted checks passed: `node --check wp-content/themes/llmwikis-knowledge-theme/assets/js/site.js`, `node --check wp-content/themes/llmwikis-knowledge-theme/assets/js/setup-wizard-core.js`, `npm run test:unit`, `npm run test:e2e`, `scripts/Test-LlmWikisPublicSurface.ps1`, and intake refresh with zero active files.
- Rebuilt the LlmWikis `v2.8.0` release artifacts as part of the five-site package round. The theme and core plugin metadata now report `2.8.0`, the publish output contains `llmwikis-knowledge-theme-v2.8.0.zip`, `llmwikis-core-v2.8.0.zip`, and the UAIX-sourced `uai1-project-handoff-v2.8.0.zip`, and the dynamic starter-bundle route now uses `/downloads/llm-wiki-starter-bundle-v2.8.0.zip`. Local static starter ZIP generation was not confirmed because `php` is not on PATH.
- Promoted the 2026-05-06 Canonical AI Memory intake into current LlmWikis handbook and setup-wizard guidance. `/guides/canonical-ai-memory/` now explains the source-backed layer map across raw sources, reviewed LLM Wiki memory, optional derived graph projections, compact AI Memory, Project Handoff transfer context, and execution agents, with canonical UAIX links. The setup wizard now carries Canonical AI Memory layer routing in the digest, page copy, setup packet, structured model JSON, and unit/public-surface assertions while rejecting hosted graph/database/API/SPARQL services, automatic writes/sync, SDK, CLI, certification, endorsement, and conformance claims.

Why This File Exists

This is a UAI AI Memory handoff file from llmwikis.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 progress 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 Progress; Recently Completed; Intake Outcome Ledger; 2026-05-24 next-level source map, repair mode, and UAIX memory alignment; 2026-05-15 follow-up site review intake: short-route compatibility and evidence preservation; 2026-05-15 Improvement batch: strict constraint and shared-wiki topology overhaul; 2026-05-11 Improvement handoff recovery: wizard, guidance, and memory loop; 2026-05-09 AI Dreaming Memory management intake. 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-066 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LLMWikis Progress",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/uai-progress-uai-0d9af670/",
    "source_reference":  ".uai/progress.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:0d9af67025160a41760b0066fb3319ac9c36e19f5bd41261850012059e64fbb0",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-13T22:31:31.9970456Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-066",
    "duplicate_role":  "primary",
    "related_files":  [

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