Analytical Review Of LLMWikis Guidance And Wizard Implementation On AIWikis

AIWikis is not a random accumulation of AI-generated pages. Its live structure shows a deliberate implementation of LLMWikis patterns: handbook-style orientation pages, governance pages, source memory guides, archive-...

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-2026-05-15-strict-constraint-overhaul-analy-1fd8eff9/
Source reference	raw/system-archives/llmwikis/2026-05-15-strict-constraint-overhaul/Analytical Review of LLMWikis Guidance and Wizard Implementation on AIWikis.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-15T22:05:08.8302596Z
Content hash	sha256:1fd8eff9282dbea8e88eb4a7d21104e9e7104062fc1c54ecbdb340827441d090
Import status	unchanged
Raw source layer	data/sources/llmwikis/raw-system-archives-llmwikis-2026-05-15-strict-constraint-overhaul-analytical-review-of-llmwikis-1fd8eff9282d.md
Normalized source layer	data/normalized/llmwikis/raw-system-archives-llmwikis-2026-05-15-strict-constraint-overhaul-analytical-review-of-llmwikis-1fd8eff9282d.txt

Current File Content

Structure Preview

• Analytical Review of LLMWikis Guidance and Wizard Implementation on AIWikis
• Executive summary
• Research scope and method
• Catalog of AIWikis pages and memory artifacts created from LLMWikis guidance
• Failure modes and root causes
• Comparison with external best practices
• Revised guidance and wizard design
• Revised prompt templates
• Validation checks to add
• Memory schema changes
• Moderation rules for public wiki operation
• UX changes that matter most
• Mapping old guidance to proposed replacements
• Migration plan and monitoring
• Milestones, risks, and rollback criteria
• Metrics to monitor after deployment
• Open questions and limitations
• Sample improved outputs
• How To Build an LLM Wiki
• Before you start
• Build sequence
• Define scope
• Register sources

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: 49362
• Preview characters: 11630

# Analytical Review of LLMWikis Guidance and Wizard Implementation on AIWikis

## Executive summary

AIWikis is not a random accumulation of AI-generated pages. Its live structure shows a deliberate implementation of LLMWikis patterns: handbook-style orientation pages, governance pages, source memory guides, archive-transfer and intake ledgers, and per-file evidence pages that preserve provenance while separating AIWikis from canonical source authority. AIWikis repeatedly states that LLMWikis remains the handbook source, while AIWikis acts as a dogfood and long-term memory layer; that claim is consistent across the home page, the system-memory archive, the source map, and the LLMWikis source memory guide. citeturn21search2turn2view5turn18view0turn37view0

The strongest parts of the implementation are the authority boundary model, the archive-and-provenance mindset, and the exposure of compact, queryable evidence objects such as source memory guides, decisions logs, and intake ledgers. Those parts line up well with the better parts of current LLMWikis guidance: explicit source policy, required trust signals, metadata fields, agent stop conditions, and a browser-only wizard that avoids pretending to be an automatic publisher. citeturn24view0turn8view1turn24view1turn24view2turn6view3

The weakest parts are operational rather than conceptual. Many AIWikis public pages are too thin to stand alone, despite being public routes. Visible trust and freshness metadata are often absent on human-facing pages even though LLMWikis requires them in metadata. Several stale hashed artifact URLs still surface and now return 404. Some pages openly admit missing governance infrastructure, such as the source map’s statement that source manifest records are “not available yet.” The site also carries duplication and audience-blur: large provenance indexes, repeated boilerplate, recovered-summary stubs, and public summaries of internal prompts and local source paths. citeturn36view0turn2view8turn13view0turn13view1turn18view0turn11view0turn11view2turn16view0turn16view1turn16view2turn16view3turn16view4

The root cause is that current LLMWikis guidance is stronger on high-level governance than on enforced execution. The wizard is explicitly a planning tool, not an importer or repository writer, and it generates copyable packets rather than validated deployments. That makes sense for safety, but it leaves a gap: no mandatory public-page completeness threshold, no required visible trust card, no route-regression testing gate, no freshness TTL for generated explanations, no mandatory moderation/redaction scan for artifact pages, and no mode-specific simplification for teams that do not need the wizard’s full combinatorial surface. citeturn24view3turn24view4turn24view5turn24view6

The best path forward is not to discard the LLMWikis model. It is to tighten it. The guidance should keep its source-governed philosophy, but add a narrower, mode-specific wizard; mandatory validation and evaluation steps; rendered, visible metadata; route and redirect QA; stronger private-versus-public rendering rules; and a memory schema that explicitly manages authority, duplication, freshness, visibility, and moderation. Those changes would bring the system much closer to established documentation, governance, memory, and safety practice. citeturn29view3turn40view0turn29view4turn31view3turn29view5turn33view2turn33view3turn29view13turn30view0turn30view2turn29view12

## Research scope and method

This review focused on the current public surfaces of LLMWikis.org and AIWikis.org as of May 15, 2026, with emphasis on the LLMWikis handbook pages, the setup wizard, and the AIWikis routes that explicitly implement or preserve those patterns. The most important LLMWikis reference points were the setup wizard, metadata standard, source policy, trust model, agent rules, governance page, build guide, and AI-agent guide. citeturn2view1turn24view1turn24view0turn8view1turn24view2turn8view4turn2view2turn8view7

On AIWikis, the sampled set included direct human-facing pages such as Start Here, What Is an LLM Wiki, How To Build an LLM Wiki, Agent Rules, Governance, Source Map, System Memory Archive, Intake Outcome Ledger, Lessons Learned, Recommendation Adjustments, and several “recovered-source summary” pages and source-file evidence routes. I also examined LLMWikis-specific preservation pages on AIWikis, such as the LLMWikis source memory guide, the LLMWikis UAI system index, the LLMWikis public surface file, and the LLMWikis decisions log. citeturn2view9turn2view8turn36view0turn20view0turn4view4turn18view0turn2view5turn18view6turn18view3turn18view4turn13view0turn13view1turn37view0turn35view0turn13view9turn13view8

The most important limitation is visibility. AIWikis often does not surface creation date, reviewer, or author on direct public pages, even though LLMWikis metadata guidance requires owner, last reviewed, review cycle, status, source status, and related fields. Because of that, dates and authors could only be recorded when a page, prompt page, search result, or source-file artifact explicitly exposed them. citeturn24view1turn2view8turn36view0turn13view2turn13view6turn13view8

A second limitation is that I did not verify private repositories or backend internals. Where AIWikis mentions machine routes or internal folders, this report treats those claims as public-site statements rather than directly verified backend capabilities. That matters because AIWikis explicitly says some important infrastructure is still incomplete, most notably the missing source-manifest records. citeturn18view0

## Catalog of AIWikis pages and memory artifacts created from LLMWikis guidance

The live AIWikis implementation falls into five clearly recurring artifact classes: direct handbook-like pages, recovered-source summaries, source memory guides, logs and ledgers, and individual file-evidence pages under `/uai-system/files/` or `/files/...`. That layering is consistent with AIWikis’ own description of preserving raw source inputs, compiling reviewed wiki nodes, and keeping public pages, compact handoff packets, and deep source-side memory separate. citeturn37view0turn2view5turn35view0

The score below uses a simple rubric: **5** means strong and close to publishable best practice, **4** good with minor issues, **3** useful but materially flawed, **2** weak or stub-like, and **1** broken.

| URL | Page type | Creation date if available | Author or agent if available | Quality assessment |
|---|---|---:|---|---|
| `https://aiwikis.org/start-here/` | Orientation / reading-path page | Not surfaced | Not surfaced | **3** — clear entry path, but thin and missing visible trust, owner, freshness, and source citations. citeturn2view9turn24view1 |
| `https://aiwikis.org/what-is-an-llm-wiki/` | Concept page | Not surfaced | Not surfaced | **3** — concise and accurate boundary statement, but derivative claims are citation-light and do not surface owner/review metadata that LLMWikis expects. citeturn2view8turn24view0turn24view1 |
| `https://aiwikis.org/how-to-build-an-llm-wiki/` | How-to page | Not surfaced | Not surfaced | **3** — useful seven-step skeleton, but it is too short for a public how-to and lacks examples, visible status, and review data. citeturn36view0turn40view0turn24view1 |
| `https://aiwikis.org/agent-rules/` | Agent governance page | Not surfaced | Not surfaced | **4** — one of the stronger direct pages; concise read-order and stop-condition guidance, but still lacks visible metadata and local evidence links for important claims. citeturn20view0turn24view2 |
| `https://aiwikis.org/source-map/` | Provenance / governance page | Not surfaced | Not surfaced | **2** — important boundary statements, but the page openly says source manifest records are not available yet, which is a major governance gap for a provenance-first site. citeturn18view0 |
| `https://aiwikis.org/system-memory-archive/` | Long-term memory policy / archive guide | First transfer dated **2026-04-28** in page body | Not surfaced | **4** — strong authority-boundary language and explicit archive flow, though the page is still more policy note than full operational reference. citeturn2view5turn17search10 |
| `https://aiwikis.org/intake-outcome-ledger/` | Public-safe intake ledger | Latest visible entry dated **2026-05-14** | Not surfaced | **4** — very good proof-of-use pattern and one of the most valuable operational pages, but dense presentation and raw-path-heavy rendering make it harder than necessary for humans. citeturn18view6 |
| `https://aiwikis.org/lessons-learned/` | Dogfood lessons page | Not surfaced on canonical page; raw version exposed as working draft | Not surfaced | **4** — useful and candid, with real implementation lessons; however, the raw version exposes a status/trust tension (`working-draft` plus `reviewed`) that should be normalized. citeturn18view3turn14search4 |
| `https://aiwikis.org/recommendation-adjustments/` | Recommendation-change ledger | Not surfaced | Not surfaced | **4** — strong change-tracking concept and aligned with dogfooding, but still brief and missing visible ownership/review cadence. citeturn18view4turn24view1 |
| `https://aiwikis.org/ai-memory-systems/aiwikis-starter-readme/` | Recovered-source summary from archived starter material | Archived source path indicates retired starter draft from **2026-04-28** | Not surfaced | **2** — currently more of an orientation stub than a usable README; it says what the starter pack is for but not enough for a maintainer to use it well. citeturn13view0turn18view1 |
| `https://aiwikis.org/best-practices/autonomous-wiki-architect-prompt/` | Prompt artifact summary | Captured **2026-04-28T23:20:00Z** | “Local curator prompt” surfaced as source type | **3** — strong provenance and retrieval notes, but public exposure of internal prompt summaries should be far more selective. citeturn13view2 |
| `https://aiwikis.org/llmwikis/source-memory-guide/` | Source memory guide | Not surfaced | Not surfaced | **5** — among the best pages on the site; clear authority boundary, operating loop, update triggers, do-not-claim rules, and practical memory routing. citeturn37view0 |
| `https://aiwikis.org/llmwikis/uai-system/files/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-uai-decisi-ea3341dc/` | UAI system file page for LLMWikis decisions log | `created: 2026-04-26`, `updated: 2026-04-28` | `author: LlmWikis maintainers` | **4** — excellent provenance surface and one of the clearest demonstrations of long-term memory artifacts, but the public page is bulky and better suited as evidence than as a primary reading route. citeturn12search6turn13view8 |
| `https://aiwikis.org/files/aiwikis/raw-system-archives-aiwikis-agent-file-handoff-content-2026-04-29-improv-37d5b75a/` | Memory-file report | Last changed **2026-04-29T02:40:31Z** | Not surfaced | **3** — useful long-memory evidence, but highly path-heavy and too close to raw internal archive structure for a public-facing route. citeturn13view6 |
| `https://aiwikis.org/files/aiwikis/raw-system-archives-llmwikis-source-site-report-preservation-2026-05-01-4a5e1ce1/` | Stale artifact URL discovered in search | Not available | Not available | **1** — currently broken; search still surfaces it as a “Codex Promotion Report,” but the live URL returns 404. This is the clearest current broken-route symptom in the sampled set. citeturn10search0turn11view0 |

Why This File Exists

This is a memory-system evidence 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 file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: Analytical Review of LLMWikis Guidance and Wizard Implementation on AIWikis; Executive summary; Research scope and method; Catalog of AIWikis pages and memory artifacts created from LLMWikis guidance; Failure modes and root causes; Comparison with external best practices; Revised guidance and wizard design; Revised prompt templates. 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-155 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Analytical Review Of LLMWikis Guidance And Wizard Implementation On AIWikis",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-2026-05-15-strict-constraint-overhaul-analy-1fd8eff9/",
    "source_reference":  "raw/system-archives/llmwikis/2026-05-15-strict-constraint-overhaul/Analytical Review of LLMWikis Guidance and Wizard Implementation on AIWikis.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:1fd8eff9282dbea8e88eb4a7d21104e9e7104062fc1c54ecbdb340827441d090",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-15T22:05:08.8302596Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-155",
    "duplicate_role":  "primary",
    "related_files":  [

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