LLMWikis Shared Wiki Namespace Topology

A company-wide LLM Wiki can hold memory for many sites, but the source-side topology must keep site memory visibly separated.

Metadata

Field	Value
Source site	aiwikis.org
Source URL	https://aiwikis.org/
Canonical AIWikis URL	https://aiwikis.org/aiwikis/files/wiki-concepts-llmwikis-shared-wiki-namespace-topology-md-427d8b79/
Source reference	wiki/concepts/llmwikis-shared-wiki-namespace-topology.md
File type	md
Content category	llm-wiki
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-15T23:32:23.1118920Z
Content hash	sha256:427d8b79730c186f8cd6d4e92f1d2b77383ce6f859d57521d50e2f1a7fe2c07f
Import status	unchanged
Raw source layer	data/sources/aiwikis/wiki-concepts-llmwikis-shared-wiki-namespace-topology-md-427d8b79730c.md
Normalized source layer	data/normalized/aiwikis/wiki-concepts-llmwikis-shared-wiki-namespace-topology-md-427d8b79730c.txt

Current File Content

Structure Preview

• LlmWikis Shared Wiki Namespace Topology
• Why This Matters
• LlmWikis Application
• Promotion Rule
• Non-Claims
• Related Nodes

Raw Version

---
uai_id: "418e8beb-bfd5-446c-bd25-b8947286cc38"
type: "concept"
owner: "AIWikis maintainers"
status: "Reviewed"
source_status: "local synthesis from LlmWikis strict-constraint overhaul and AIWikis source-side topology"
sensitivity: "public-safe source-side memory"
agent_use: "load when deciding where cross-site company memory, site-specific memory, and shared LLM Wiki guidance should live"
lineage:
  - "wiki/sources/llmwikis-strict-constraint-overhaul-2026-05-15.md"
  - "raw/system-archives/llmwikis/2026-05-15-strict-constraint-overhaul/MANIFEST.json"
  - "wiki/index.md"
source_trace:
  - "LlmWikis AGENTS.md"
  - "LlmWikis CLAUDE.md"
  - "AIWikis wiki/ source-side directory layout"
confidence: 0.88
confidence_label: "reviewed-local"
last_linted: "2026-05-15T00:00:00Z"
handoff_export: "include"
aliases:
  - "Shared Wiki Namespace Topology"
  - "Company LLM Wiki Site Directories"
  - "Multisite Workspace Memory Layout"
last_reviewed: "2026-05-15"
typed_relations:
  part_of:
    - "wiki/llmwikis/index.md"
  depends_on:
    - "wiki/sources/llmwikis-strict-constraint-overhaul-2026-05-15.md"
  supersedes: []
  contradicts: []
  source_for:
    - "wiki/logs/llmwikis-strict-constraint-overhaul-2026-05-15.md"
---
# LlmWikis Shared Wiki Namespace Topology

A company-wide LLM Wiki can hold memory for many sites, but the source-side topology must keep site memory visibly separated.

The operating rule is:

- Use `wiki/global/` for company-wide standards, organization facts, shared coding standards, shared styling rules, and cross-site governance.
- Use `wiki/{Site}/` for site-specific memory, source guides, decisions, logs, diagnostics, and retrieval indexes.
- Use `raw/system-archives/{site}/` for preserved raw evidence after a site-specific intake has been dispositioned.
- Keep public page stores separate from source-side `wiki/` topology when the CMS requires flat or numbered files.

## Why This Matters

Without site directories, an agent maintaining one site can over-read unrelated memory and blend taxonomies. The shared wiki then becomes noisy: site-local observations look like company standards, drafts look canonical, and public pages can appear to support unrelated source systems.

With site directories, an agent can start with `wiki/index.md`, choose `wiki/{Site}/index.md`, then load only the source, concept, or log nodes required for the task.

## LlmWikis Application

LLMWikis.org now teaches and follows the same pattern:

- Source-specific AIWikis memory about LlmWikis belongs under `wiki/llmwikis/`.
- Company-wide rules remain under `wiki/global/`.
- Deterministic preflight enforces source-side topology on `wiki/`, while public WordPress page stores are checked for trust labels, canonical routes, and discovery safety.
- Agent schemas name concrete allowed namespaces so an agent is not invited to brute-force scan the full monolithic tree.

## Promotion Rule

Raw or source-side memory becomes active public truth only after promotion into the owning site:

- LLMWikis truth must be restated in LlmWikis public handbook copy, `.uai` state, agent instructions, code, tests, discovery files, release notes, or package evidence.
- AIWikis memory remains source-side evidence unless AIWikis intentionally publishes a reviewed public page about it.

## Non-Claims

This topology is not automatic sync, deployment proof, source authority transfer, certification, or a hosted ingestion product. It is a maintenance constraint for shared long-memory repositories.

## Related Nodes

- `depends_on`: [[../sources/llmwikis-strict-constraint-overhaul-2026-05-15]]
- `source_for`: [[../logs/llmwikis-strict-constraint-overhaul-2026-05-15]]
- `part_of`: [[../llmwikis/index]]
- `part_of`: [[../index]]

Why This File Exists

This is a LLM Wiki memory 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 belongs to the source-side wiki layer. It preserves a focused concept, source proxy, graph record, or operating rule so the public site can cite reviewed conclusions without flattening every reason into a single long page.

Structure

The file is structured around these visible headings: LlmWikis Shared Wiki Namespace Topology; Why This Matters; LlmWikis Application; Promotion Rule; Non-Claims; Related Nodes. 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-328 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LLMWikis Shared Wiki Namespace Topology",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/wiki-concepts-llmwikis-shared-wiki-namespace-topology-md-427d8b79/",
    "source_reference":  "wiki/concepts/llmwikis-shared-wiki-namespace-topology.md",
    "file_type":  "md",
    "content_category":  "llm-wiki",
    "content_hash":  "sha256:427d8b79730c186f8cd6d4e92f1d2b77383ce6f859d57521d50e2f1a7fe2c07f",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-15T23:32:23.1118920Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-328",
    "duplicate_role":  "primary",
    "related_files":  [

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