LLMWikis Stack
llmwikis-core registers structured content types for the future wiki corpus:
Metadata
| Field | Value |
|---|---|
| Source site | llmwikis.org |
| Source URL | https://llmwikis.org/ |
| Canonical AIWikis URL | https://aiwikis.org/llmwikis/uai-system/files/uai-stack-uai-702ea0ae/ |
| Source reference | .uai/stack.uai |
| File type | uai |
| Content category | uai-system |
| Last fetched | 2026-05-15T00:23:56.0837262Z |
| Last changed | 2026-05-09T16:22:08.9830622Z |
| Content hash | sha256:702ea0ae3a494b936236658f011b056540408ce9054d117733aeae355d53d8d3 |
| Import status | changed |
| Raw source layer | data/sources/llmwikis/uai-stack-uai-702ea0ae3a49.uai |
| Normalized source layer | data/normalized/llmwikis/uai-stack-uai-702ea0ae3a49.txt |
Current File Content
Structure Preview
- LlmWikis Stack
- Runtime
- Active Site Surface
- Theme Responsibilities
- Plugin Responsibilities
- Route Shape
- Common Commands
- Package Source
- Publish Output Shape
Raw Version
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: stack
title: "LlmWikis Stack"
created: "2026-04-26"
updated: "2026-05-09"
author: "LlmWikis maintainers"
version: 22
---
# LlmWikis Stack
## Runtime
- Local environment: WordPress Studio
- OS context: Windows / PowerShell
- Database: Studio SQLite integration
- WordPress CLI path: use `studio wp`, not bare `wp`
- Current local URL: use `studio site status`; do not hardcode the port in docs or code
- Intended public URL: `https://llmwikis.org/`
## Active Site Surface
- Theme: `wp-content/themes/llmwikis-knowledge-theme/`
- Core plugin: `wp-content/plugins/llmwikis-core/`
- Optional/internal handoff plugin: `wp-content/plugins/uai1-project-handoff/`
- Human-facing handoff briefing: root `readme.human`
- Internal strategy memory: `.uai/strategy.uai`
- Active file-intake memory: `.uai/file-handoff.uai` and `.uai/intake-index.uai`
- Active file-intake workspaces: `agent-file-handoff/Content/` for candidate public/editorial material and `agent-file-handoff/Improvement/` for audits, QA findings, SEO reports, bug notes, and site-fix work
- Dead archive workspace: `agent-file-handoff/Archive/` for files that already received a complete intake outcome and that routine AI intake ignores unless a human explicitly names an archived file or moves it back into an active bucket
- Former source reports are retired from `docs/`; public value has moved into handbook and report routes, while improvement/audit value stays in internal roadmap and progress state unless intentionally converted into public content
- Root crawler assets: `llms.txt`, `robots.txt`, and `sitemap.xml`
- Shared setup wizard source: `wp-content/themes/llmwikis-knowledge-theme/inc/setup-wizard.php`, testable planning logic in `wp-content/themes/llmwikis-knowledge-theme/assets/js/setup-wizard-core.js`, and browser DOM interactivity in `wp-content/themes/llmwikis-knowledge-theme/assets/js/site.js`. The wizard now models AI Dreaming Memory as review-only proposal memory with run artifacts, candidate queues, contradiction drafts, metrics, protected surfaces, and no automatic writes/sync or hidden-memory claims.
- Multisite dogfood checks now flow through the setup wizard, public integration guide, and tests: per-repository Git preflight before Sync/merge work, plus mutable runtime artifact policy for WordPress Studio SQLite databases.
- Homepage and setup wizard promo assets: `wp-content/themes/llmwikis-knowledge-theme/assets/promos/llm-wiki-knowledge-flow.jpg`, `wp-content/themes/llmwikis-knowledge-theme/assets/promos/llm-wiki-human-wizard.jpg`, and `wp-content/themes/llmwikis-knowledge-theme/assets/promos/llm-wiki-for-agents-wizard.jpg`
- Maintained release theme count: one (`llmwikis-knowledge-theme`). Default bundled WordPress themes are local fallbacks, not LlmWikis release packages.
## Theme Responsibilities
- Visual production surface
- Static navigation and footer
- Seed pages for the first information architecture
- LLM Wiki handbook pages for Start Here, Architecture, Operations, Navigation, Schema Engineering, Examples, and Protocols and Case Studies
- Additional technical handbook modules for Memory Lifecycle, Two-Step Ingest Pipeline, Graph Navigation, Page Schema Standard, and Tooling Landscape
- Root SEO and AI crawler files when deployed with the site root
- Per-route descriptions, canonical links, social metadata, and structured data for the managed public route set
- Site title, tagline, front page, and permalink setup
## Plugin Responsibilities
`llmwikis-core` registers structured content types for the future wiki corpus:
- AI Models
- Benchmarks
- Protocol Notes
- Guides
- Comparisons
- Glossary entries
- Implementation tools
- Shared topics, modalities, evidence-status, page-type, and authority-label taxonomies
- Review metadata fields for last-reviewed date, canonical source URL, and source summary
The UAIX Project Handoff prototype plugin is only for internal handoff package work. It must not be used as proof of official UAIX generation, validation, certification, or endorsement.
## Route Shape
Managed public pages use clean root paths:
- `/`
- `/start-here/`
- `/what-is-an-llm-wiki/`
- `/why-llm-wikis/`
- `/how-to-build-an-llm-wiki/`
- `/llm-wiki-structure/`
- `/starter-template/`
- `/tools/`
- `/tools/llm-wiki-setup-wizard/`
- `/content-types/`
- `/trust-model/`
- `/metadata-standard/`
- `/for-ai-agents/`
- `/llm-wiki-vs-rag/`
- `/llm-wiki-vs-ai-memory/`
- `/checklist/`
- `/maturity-model/`
- `/security-and-privacy/`
- `/architecture/`
- `/architecture/three-layer-architecture/`
- `/architecture/rag-vs-incremental-compilation/`
- `/architecture/memory-lifecycle/`
- `/operations/`
- `/operations/ingest/`
- `/operations/two-step-ingest-pipeline/`
- `/operations/query/`
- `/operations/lint/`
- `/navigation/`
- `/navigation/index-and-log/`
- `/navigation/graph-navigation/`
- `/schema-engineering/`
- `/schema-engineering/agents-md/`
- `/schema-engineering/durable-llm-wikis/`
- `/schema-engineering/page-schema-standard/`
- `/examples/`
- `/examples/personal-llm-wiki/`
- `/examples/team-llm-wiki/`
- `/reports/`
- `/reports/using-llm-wiki-with-uai/`
- `/protocols-case-studies/`
- `/explore/`
- `/standards/`
- `/standards/what-is-uai-1/`
- `/standards/uai-1-message-model/`
- `/standards/validator-errors/`
- `/guides/`
- `/guides/using-llm-wiki-with-codex/`
- `/guides/llm-wiki-agentic-orchestration/`
- `/guides/canonical-ai-memory/`
- `/guides/ai-dreaming-memory-management/`
- `/guides/knowledge-graphs-for-llm-wikis/`
- `/guides/llm-wiki-ai-memory-project-handoff/`
- `/guides/agent-handoff-patterns/`
- `/guides/validate-a-uai-1-message/`
- `/comparisons/`
- `/comparisons/uai-1-vs-mcp/`
- `/comparisons/uai-1-vs-openapi/`
- `/comparisons/uai-1-vs-a2a/`
- `/glossary/`
- `/glossary/provenance/`
- `/glossary/delivery-semantics/`
- `/glossary/trust-channel/`
- `/implementations/`
- `/implementations/validator-workbench/`
- `/implementations/tooling-landscape/`
- `/mission/`
- `/uaix-bridge/`
- `/model-registry/`
- `/model-registry/model-profile-template/`
- `/model-registry/compare-models/`
- `/evaluation-hub/`
- `/evaluation-hub/benchmark-page-template/`
- `/evaluation-hub/benchmark-contamination/`
- `/security/`
- `/security/owasp-llm-top-10/`
- `/source-policy/`
- `/related-links/`
- `/page-templates/`
- `/community/`
- `/contribute/`
- `/governance/`
- `/governance/review-gated-publication-model/`
- `/roadmap/`
No locale-prefixed route is supported yet.
## Common Commands
- `studio site status`
- `studio site start --skip-browser`
- `studio wp theme activate llmwikis-knowledge-theme`
- `studio wp plugin activate llmwikis-core`
- `studio wp plugin activate uai1-project-handoff`
- `studio wp rewrite flush`
- `powershell -NoProfile -ExecutionPolicy Bypass -File scripts/Invoke-UaiFileIntake.ps1`
- Do not use watcher/daemon, queue-folder, manifest, or always-on background services for the base handoff pattern; the requirement is the AGENTS.md-triggered intake pass above.
- Do not use bucket-local README files for active intake instructions; keep durable AI behavior in `AGENTS.md` and `.uai` files, with human-facing briefing in root `readme.human`.
- Non-executable intake files are indexed as `needs-agent-review`; inspect, summarize, disposition them, complete named site/system work for every safe relevant file, record hot-memory and long-memory/archive outcomes, and report checks before unrelated broad work continues.
## Package Source
UAIX Project Handoff package source for this build comes from `[local path redacted]` in the local UAIX workspace. Treat it as an experimental/internal prototype unless and until UAIX publishes official tooling and evidence.
## Publish Output Shape
- Deployable WordPress ZIPs should carry affected system versions in their filenames and internal theme/plugin metadata. Only packages whose contents changed get the current system-wide version; unchanged packages retain the previous artifact name and version.
- `[local path redacted]` is the current maintained LlmWikis theme upload package for the shared package round.
- `[local path redacted]` and `[local path redacted]` are the current plugin upload packages for the shared package round.
- `[local path redacted]` holds source-only or site-archive bundles and must not be treated as WordPress theme or plugin upload packages.
- The source-only handoff bundle includes `readme.human`, `agent-file-handoff/`, `llms.txt`, `robots.txt`, and `sitemap.xml` alongside `AGENTS.md`, `.uai/`, and `scripts/`. It no longer includes retired repository Markdown docs.
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 stack 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 Stack; Runtime; Active Site Surface; Theme Responsibilities; Plugin Responsibilities; Route Shape; Common Commands; Package Source. 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
Provenance And History
- Current observation:
2026-05-15T00:23:56.0837262Z - Source origin:
current-source-workspace - Retrieval method:
local-source-workspace - Duplicate group:
sfg-340(primary) - Historical hash records are stored in
data/hashes/source-file-history.jsonl.
Machine-Readable Metadata
{
"title": "LLMWikis Stack",
"source_site": "llmwikis.org",
"source_url": "https://llmwikis.org/",
"canonical_url": "https://aiwikis.org/llmwikis/uai-system/files/uai-stack-uai-702ea0ae/",
"source_reference": ".uai/stack.uai",
"file_type": "uai",
"content_category": "uai-system",
"content_hash": "sha256:702ea0ae3a494b936236658f011b056540408ce9054d117733aeae355d53d8d3",
"last_fetched": "2026-05-15T00:23:56.0837262Z",
"last_changed": "2026-05-09T16:22:08.9830622Z",
"import_status": "changed",
"duplicate_group_id": "sfg-340",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-05-15T00:23:56.0837262Z"
} Next Useful Routes
- Start Here A task-first reading path for AIWikis.org, separating newcomer learning, source-memory lookup, maintainer workflow, and AI-agent retrieval.
- Topic Index A tag-oriented index for LLM Wiki, AI memory, UAI, source governance, crawling, and retrieval topics.
- Source Map AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
- LLMWikis.org LLMWikis.org source-system overview for transparent AIWikis memory demonstration.
- LLMWikis.org Source Memory Guide AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
- LLMWikis.org UAI System Files Real current UAI / LLM Wiki memory files for LLMWikis.org.