AIWikis Memory and Site Structure

AIWikis.org is a layered memory site. The public site should feel simple, but the source system behind it keeps enough structure for maintainers and AI agents to verify where a claim came from.

The Five Layers

Layer	What It Does	Use It When
Public pages	Reviewed Markdown pages rendered by the AIWikis Core plugin.	You need current human-facing guidance, source boundaries, or a stable route to cite.
Search and indexes	/search/, /topics/, /source-map/, /files/, and /reports/.	You know a term, source, concept, file role, or evidence type but not the exact route.
Generated evidence pages	Bounded source-file pages with source reference, hash, provenance, and noindex rules when appropriate.	You need proof that a file existed, changed, or supports a claim.
Source-side wiki	wiki/ concept, source, log, and source-system index nodes.	You are maintaining the repository and need reasoning history, lineage, or compact retrieval paths.
Raw system archives	raw/system-archives/ copied originals and manifests with checksums.	You need cold provenance after a source-site file has been dispositioned or explicitly accepted for long memory.

Route Families

• Orientation routes: /, /start-here/, /what-is-an-llm-wiki/, /how-to-build-an-llm-wiki/, and this page.
• Search and browse routes: /search/, /topics/, /source-map/, /files/, /reports/, and /browser/.
• Source-system routes: /uaix/, /llmwikis/, /protocol5/, /justaniota/, /geotrackable/, /neurokinetic/, and source-memory guide routes.
• Evidence routes: generated /{source}/uai-system/files/... and /files/... pages.
• Operations routes: /cross-site-memory-atlas/, /source-memory-operations-playbook/, /source-site-outcome-routing/, /memory-coverage-matrix/, and /claim-boundary-register/.

What Changed In This Improvement Pass

• Added a visible site search route backed by the packaged AIWikis route index.
• Promoted task-first navigation in the header, footer, home page, and Start Here page.
• Added breadcrumb and contextual route links around Markdown-backed pages.
• Added legacy /files/aiwikis/... hash-route redirects so stale source-file URLs can recover to canonical pages or current evidence routes.
• Preserved the audit reports as AIWikis long-memory evidence instead of leaving them active in the Improvement bucket.

Source Boundary Rule

AIWikis can preserve and explain memory from UAIX.org, LLMWikis.org, Protocol5.com, JustAnIota.com, and other source systems. It does not become their standards authority, deployment proof, conformance evidence, certification provider, SDK, CLI, hosted validator, or automatic publication system.

When a claim matters, route it through Source Map, Memory Coverage Matrix, and Claim Boundary Register before treating it as safe public copy.

Maintenance Rule

Public pages should answer human tasks first. Source-side wiki nodes should preserve why the structure exists. Raw archives should preserve original inputs and checksums. Search and route metadata should connect those layers without forcing a reader or agent to open everything.