Relationship Audit Of Aiwikis, Llmwikis, And UAIX

This audit can verify the source-side relationship with high confidence, but it cannot produce a fully verified live inventory of AIWikis in this session. The browser was able to crawl LlmWikis and key UAIX pages, but...

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/raw-system-archives-aiwikis-agent-file-handoff-content-2026-04-28-relati-14b0b11e/
Source reference	raw/system-archives/aiwikis/agent-file-handoff/Content/2026-04-28/Relationship Audit of AIWikis LlmWikis and UAIX.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-04-28T23:36:36.1272597Z
Content hash	sha256:14b0b11e8f6b90ff5c47025ab08f1b1625f7993ce9772e0e21a79cc4a348c0e3
Import status	unchanged
Raw source layer	data/sources/aiwikis/raw-system-archives-aiwikis-agent-file-handoff-content-2026-04-28-relationship-audit-of-aiwikis-14b0b11e8f6b.md
Normalized source layer	data/normalized/aiwikis/raw-system-archives-aiwikis-agent-file-handoff-content-2026-04-28-relationship-audit-of-aiwikis-14b0b11e8f6b.txt

Current File Content

Structure Preview

• Relationship Audit of AIWikis, LlmWikis, and UAIX
• Executive summary
• Research method and limitations
• Verified structure of LlmWikis and UAIX
• AIWikis crosswalk and gap analysis
• Prioritized roadmap and implementation plan
• Sample page edits and success metrics
• AIWikis
• Read first
• What this site is
• Authority boundary
• Discovery
• Source Policy
• What this page governs
• Page states
• Source tiers
• Claims that require visible sourcing
• AI-assisted drafts
• Content Quality Audit
• Purpose
• Read next
• Current audit questions
• Backlog
• What Is UAI-1?

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: 31824
• Preview characters: 11836

# Relationship Audit of AIWikis, LlmWikis, and UAIX

## Executive summary

This audit can verify the source-side relationship with high confidence, but it cannot produce a fully verified live inventory of AIWikis in this session. The browser was able to crawl LlmWikis and key UAIX pages, but it could not render the AIWikis homepage, which returned repeated fetch/cache-miss errors. As a result, the report below cleanly separates **verified findings** about LlmWikis and UAIX from **inferred implementation recommendations** for AIWikis. citeturn13view0turn1view1turn1view2

The relationship among the three sites is structurally clear. **LlmWikis** is the handbook and editorial-system source: its public route map exposes a broad handbook covering architecture, operations, templates, source policy, governance, content-quality pages, model pages, benchmark pages, comparisons, guides, and related links. Its template and policy pages define required metadata, review states, source-status labels, and publish gates. LlmWikis also states explicitly that **UAIX remains canonical** for UAI-1 specifications, schemas, registry records, validator behavior, roadmap, governance, and Project Handoff guidance. citeturn6view0turn18view0turn19view0turn54view0turn1view1

**UAIX** is the canonical technical authority. Its public site organizes the current release around a Core Record, Launch Kit, and Governance/About surfaces; publishes clean locale-prefixed paths; exposes a validator-centered evidence model; and provides machine-facing routes under `/wp-json/uaix/v1/…`, including a field registry that specifies the required root-field order for UAI-1. The validator page also makes an important boundary explicit: a passing validation result is evidence for a reviewed packet, not blanket certification or universal ecosystem support. citeturn50view0turn25view0turn25view1turn50view2turn52view0

The strongest conclusion is therefore architectural rather than cosmetic: **AIWikis should behave as a public implementation layer** that applies LlmWikis’ editorial discipline and navigation model while using UAIX visibly and consistently as the canonical authority for UAI-related pages. The highest-priority work is not “more content first”; it is **crawlability and discovery**, **metadata normalization**, **authority-boundary labeling**, **content-quality operating pages**, and **standards/guide pages that route readers to UAIX’s canonical proof surfaces**. citeturn54view0turn18view0turn50view1turn50view2

## Research method and limitations

This report used only public/official site surfaces that were accessible during the session: LlmWikis homepage, `llms.txt`, `robots.txt`, and several representative inner pages; UAIX homepage, roadmap, UAI-1 specification, validator page, and the machine-readable field-registry route. I did **not** have access to any private CMS, unpublished routes, or internal export. I also did not assume that every linked page on either source site was fetchable; several LlmWikis and UAIX subpages returned cache-miss or timeout errors in this session, so the route inventories below are assembled from accessible root/discovery pages plus accessible representative inner pages. citeturn5view3turn6view0turn17view1turn19view0turn39view0turn40view0turn1view2turn24view1turn24view3turn32view1turn20view0turn22view0turn33view0turn49view0

The main limitation is straightforward: **AIWikis could not be crawled successfully by the browser tool in this session**, so I could not verify a page-by-page public inventory, title list, or word-count table for the live implementation site. Where the user requested AIWikis page mappings, I therefore provide a **source-derived crosswalk backlog**: these are the pages AIWikis should expose or normalize if it is intended to implement the structure and content program described by LlmWikis and UAIX. That is less complete than a live crawl, but it is more rigorous than guessing at inaccessible page content. citeturn13view0turn4view0

| Site | What was publicly verifiable in this session | Confidence |
|---|---|---|
| AIWikis | Homepage fetch attempt only; live page bodies were not retrievable | Low for live inventory |
| LlmWikis | Homepage, `llms.txt`, `robots.txt`, Start Here, What Is an LLM Wiki, Operations, Ingest, Personal LLM Wiki, Page Templates, Source Policy, Governance, Related Links, AGENTS guide | High for structure; moderate for every leaf page |
| UAIX | Homepage, UAI-1 spec, Roadmap, Validator, field-registry JSON route | High for authority model; moderate for every leaf page |

The table above reflects the actual accessible public surfaces used for this report. citeturn13view0turn5view3turn6view0turn39view0turn40view0turn40view1turn42view0turn17view1turn19view0turn54view0turn17view0turn55view1turn1view2turn24view1turn24view3turn32view1turn52view0

```mermaid
flowchart LR
    UAIX[UAIX\nCanonical UAI-1 public record\nspec · validator · roadmap · machine routes]
    LLMWikis[LlmWikis\nNon-normative handbook\nstructure · policy · templates · content quality]
    AIWikis[AIWikis\nTarget public implementation\ncontent + navigation + metadata + discovery]

    UAIX -->|canonical authority for UAI pages| LLMWikis
    LLMWikis -->|editorial model and page taxonomy| AIWikis
    UAIX -->|canonical links, validator, evidence model| AIWikis
```

This relationship diagram reflects explicit source statements from LlmWikis that UAIX is canonical for UAI-1 material, plus UAIX’s own public record layout. AIWikis is shown as the target implementation layer because that is the role requested for this audit, even though its public pages were not retrievable in-session. citeturn1view1turn54view0turn50view0turn13view0

## Verified structure of LlmWikis and UAIX

LlmWikis is unusually explicit about structure. Its homepage advertises discovery files (`llms.txt`, `robots.txt`, `sitemap.xml`), route families, and an explicit “source and authority boundary,” and its `robots.txt` allows the public site and discovery file while publishing the sitemap location. Its `llms.txt` identifies **60 named public routes** spanning handbook pages, standards and comparison pages, model/evaluation/security pages, and governance/content-quality pages. That route map is already rich enough to serve as the recommended page taxonomy for AIWikis. citeturn15view3turn5view3turn6view0

LlmWikis also defines the editorial operating system in detail. The Page Templates page requires page-level metadata such as `title`, `type`, `status`, `source_status`, `last_reviewed`, `canonical_source`, and `related`, and it declares reusable template families for architecture guides, how-to tutorials, runbooks, schema pages, example builds, navigation pages, concepts, protocols, comparisons, model profiles, benchmarks, and implementation tools. Its universal article skeleton requires a visible status panel, a clear definition, practical importance, mechanics, evidence/caveats, example, and related pages; its publish gates require source status, time-sensitive dates, and internal links before publication. citeturn18view0

LlmWikis’ Source Policy and Governance pages sharpen that further. They define status labels such as canonical-source-linked, non-normative explainer, draft, reviewed, needs-update, contradicted, and archived; they define source tiers; they require sentence-near sources for time-sensitive or high-risk claims; and they create a specific **authority gate** for UAI-1 pages: such pages must link to UAIX for canonical specifications, schemas, registry, validator behavior, roadmap, and governance. Governance also adds a **discovery gate**, warning that public discovery files and navigation must not expose private intake or internal audit material. citeturn19view0turn54view0

UAIX, by contrast, is not primarily a handbook; it is a standards and evidence publication surface. Its homepage groups the site into a **Core Record** (Get Started, UAI-1, Project Handoff, AGENTS.md Spec, Agent File Handoff, Schemas, API Reference), a **Launch Kit** (Validator, Conformance Pack, Implementation tracks, Roadmap, Reports, Related Links, Policy and Security), and a **Governance/About** surface. It also states that clean locale-prefixed paths, discovery files, and the changelog carry “current public truth.” citeturn50view0

UAIX pages themselves expose a distinct metadata pattern. The UAI-1 spec, roadmap, and validator pages each show document identifiers such as Record/Code, Path, Use, Surface, Access, an “In this section” navigator, an “On this page” list, and a “proof path” or validation path that tells readers what to read next. The validator page is especially operational: it says the validator checks schema alignment, profile/identifier resolution, field-order expectations, and policy checks; it names six published message families; it lists four conformance levels; and it distinguishes human-facing workbench use from machine-facing validation routes. citeturn25view0turn25view1turn24view1turn50view2

The machine-readable component is not incidental. UAIX’s publicly accessible field-registry JSON route declares the current release as UAI-1, publishes the release date, and specifies **12 required root fields** in order, along with component field orders and profile body orders for the published message families. That means AIWikis should not summarize UAI-1 as if it were just a narrative concept page; if it covers UAI-1 at all, it should explicitly route readers to the canonical machine and validator surfaces. citeturn52view0turn50view2

| Dimension | LlmWikis | UAIX | Practical implication for AIWikis |
|---|---|---|---|
| Authority role | Non-normative handbook and editorial reference | Canonical public record for UAI-1 and related evidence surfaces | AIWikis should be explanatory, not normative, for UAI pages |
| Human route style | Clean slugs and nested handbook routes | Clean locale-prefixed public paths | AIWikis should use stable, human-readable section hubs |
| Discovery | `llms.txt`, `robots.txt`, `sitemap.xml`, route map | Discovery files and machine routes emphasized in roadmap/home | AIWikis needs both human navigation and crawler-friendly discovery |
| Metadata model | Title/type/status/source status/review date/canonical source/related | Record/path/use/surface/access, plus proof-path navigation | AIWikis should combine wiki metadata with a UAIX-style authority panel |
| Evidence model | Source policy, review states, content-quality metrics | Validator, conformance, changelog, roadmap-backed support claims | AIWikis should separate explanation from proof and avoid overclaiming |

This comparison table summarizes patterns visible in the accessible official pages for both source sites. citeturn5view3turn6view0turn18view0turn19view0turn54view0turn50view0turn24view1turn50view2turn52view0

## AIWikis crosswalk and gap analysis

Because AIWikis did not render in the browser during this session, the table below is a **verified source-derived crosswalk**, not a verified current-state AIWikis inventory. I am deliberately leaving the “current live title” and “current live word count” fields unverified rather than inventing them. citeturn13view0

| AIWikis route or target route | Current live title | Current live word count | Suggested source page(s) | Suggested content summary | Gap analysis | Priority | Estimated effort |
|---|---|---:|---|---|---|---|---|
| `/` | Not verifiable in session | N/A | LlmWikis Home, Start Here, What Is an LLM Wiki | Scope, route map, discovery files, quality controls, “read-first” path | Highest-value hub page is unverified; should clearly explain scope, authority boundaries, and where to begin | P0 | M |

Why This File Exists

This is a memory-system evidence 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 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: Relationship Audit of AIWikis, LlmWikis, and UAIX; Executive summary; Research method and limitations; Verified structure of LlmWikis and UAIX; AIWikis crosswalk and gap analysis; Prioritized roadmap and implementation plan; Sample page edits and success metrics; AIWikis. 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-100 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Relationship Audit Of Aiwikis, Llmwikis, And UAIX",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/raw-system-archives-aiwikis-agent-file-handoff-content-2026-04-28-relati-14b0b11e/",
    "source_reference":  "raw/system-archives/aiwikis/agent-file-handoff/Content/2026-04-28/Relationship Audit of AIWikis LlmWikis and UAIX.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:14b0b11e8f6b90ff5c47025ab08f1b1625f7993ce9772e0e21a79cc4a348c0e3",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-04-28T23:36:36.1272597Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-100",
    "duplicate_role":  "primary",
    "related_files":  [

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