LLMWikis AI Instructions

This is the canonical AI-agent entry file for the LlmWikis WordPress Studio workspace.

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-agents-md-3f71523c/
Source reference	raw/system-archives/llmwikis/internal-memory-reorg/2026-05-01/AGENTS.md
File type	md
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-04-29T02:06:48.2271934Z
Content hash	sha256:3f71523c27508d14aa4d68739c1ea703675492046de152b591c9930fbe543f1c
Import status	unchanged
Raw source layer	data/sources/llmwikis/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-agents-md-3f71523c2750.md
Normalized source layer	data/normalized/llmwikis/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-agents-md-3f71523c2750.txt

Current File Content

Structure Preview

• LlmWikis AI Instructions
• Status
• Handoff Summary
• Loaded Context
• Quick Start For A New AI
• Required First Response
• Current State
• Current Strategy
• Do Not Change Without Explicit Human Approval
• Deployment Rules
• Do Not Load By Default
• Agent History
• Open Questions

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: 26620
• Preview characters: 11980

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: agents
project: "LlmWikis"
created: "2026-04-26"
updated: "2026-04-28"
status: active
version: 25
---

# LlmWikis AI Instructions

## Status

This is the canonical AI-agent entry file for the LlmWikis WordPress Studio workspace.

This workspace uses the public UAIX Project Handoff pattern: read `AGENTS.md` first, read root `readme.human` as the human briefing, then load the `.uai` files listed below before making broad project changes.

## Handoff Summary

LlmWikis.org is a prelaunch WordPress handbook for building, structuring, maintaining, and auditing personal and team LLM Wikis. Its public center of gravity is now the reusable LLM Wiki pattern: immutable `raw/` sources, a dynamic AI-maintained markdown `wiki/`, a compact schema such as `AGENTS.md` or `CLAUDE.md`, deterministic `index.md` and `log.md` navigation, and the `ingest` / `query` / `lint` operating loop.

LlmWikis remains complementary to UAIX.org. UAIX remains the canonical standards and machine-readable UAI-1 source of truth, while LlmWikis keeps UAIX, UAI, and adjacent protocol material in a non-normative Protocols and Case Studies track.

The canonical local workspace is `[local path redacted]`. It is a WordPress Studio site. The active public production theme is `llmwikis-knowledge-theme`, and the structured content plugin is `llmwikis-core`. The UAIX Project Handoff prototype package may be installed for internal AGENTS.md, `readme.human`, and `.uai` export/import work, but it must not be described as official UAIX generator, validator, certification, or endorsement support.

## Loaded Context

Load these files before planning or editing:

@uai[.uai/context.uai]
@uai[.uai/stack.uai]
@uai[.uai/architecture.uai]
@uai[.uai/public-surface.uai]
@uai[.uai/constraints.uai]
@uai[.uai/decisions.uai]
@uai[.uai/progress.uai]
@uai[.uai/operations.uai]
@uai[.uai/test-plan.uai]
@uai[.uai/style.uai]
@uai[.uai/strategy.uai]
@uai[.uai/handoff-pattern.uai]
@uai[.uai/file-handoff.uai]
@uai[.uai/intake-index.uai]

## Quick Start For A New AI

1. Read this file completely.
2. Read root `readme.human` as the human briefing. It explains what people need to know from the AI perspective, but it does not override `AGENTS.md`, `.uai/constraints.uai`, system instructions, repository rules, or the human's current request.
3. Perform chat-start file intake: inspect `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, ignore `agent-file-handoff/Archive/` unless the human explicitly names an archived file, then refresh the intake index before planning. Use `scripts/Invoke-UaiFileIntake.ps1` when available; the requirement is the AGENTS.md-triggered scan behavior, with no watcher, daemon, or always-on background service.
4. Load every file in the Loaded Context section, including the refreshed `.uai/intake-index.uai`.
5. If `.uai/intake-index.uai` lists any file with `needs-agent-review`, inspect each one immediately, summarize it, and give it an explicit disposition before unrelated broad work continues: apply now, convert into roadmap/progress state, defer with a reason, ask for clarification, or block as unsafe/out of scope.
6. Summarize LlmWikis, its relationship to UAIX, and the current public surface in 3-5 bullets before broad changes.
7. Confirm the hard constraints from `.uai/constraints.uai`.
8. Read `.uai/strategy.uai` when the task changes site direction, public positioning, taxonomy, governance, source-document disposition, or roadmap.
9. Prefer narrow, verifiable edits that keep the public site, handoff files, and strategy docs aligned.

## Required First Response

Before making a broad change, a new AI should reply with:

1. A 3-5 bullet summary of what LlmWikis is and how it relates to UAIX.
2. The active theme, plugin surface, public route shape, and main handoff/discovery files.
3. The intake status from `.uai/intake-index.uai`, including the disposition for every `needs-agent-review` file.
4. The hard constraints from `.uai/constraints.uai`, especially UAIX authority boundaries and destructive-operation limits.
5. The exact files or public routes it expects to touch for the current task.
6. The targeted checks it expects to run, any full release/package checks it is intentionally not running, or the reason a check is not practical in the current environment.

If any required `.uai` file is missing, unreadable, circular, or contradictory, stop and report that before editing.

## Current State

- The local workspace is `[local path redacted]`.
- WordPress runs through WordPress Studio with SQLite; use `studio wp`, not bare `wp`.
- The active production theme is `wp-content/themes/llmwikis-knowledge-theme/`.
- The structured content plugin is `wp-content/plugins/llmwikis-core/`.
- The UAIX Project Handoff prototype plugin may be present at `wp-content/plugins/uai1-project-handoff/`.
- Root `readme.human` is the human-facing companion to `AGENTS.md`; it tells people what the AI sees, protects, and needs clarified before work is steered.
- Active file intake is dogfooded through the AGENTS.md load process, `agent-file-handoff/Content/`, `agent-file-handoff/Improvement/`, `agent-file-handoff/Archive/`, `scripts/Invoke-UaiFileIntake.ps1`, `.uai/file-handoff.uai`, and `.uai/intake-index.uai`. `Content/` is for candidate public/editorial material; `Improvement/` is for audits, SEO reports, QA findings, bug notes, and site-fix work. `Archive/` is for already-dispositioned files and is ignored by routine AI intake unless a human explicitly references an archived file or moves it back into an active bucket. Listed active intake files are required immediate review inputs before unrelated broad work; watchers, daemons, queue folders, manifests, and out-of-chat auto-pickup processes are outside the base pattern.
- The current LlmWikis archive was drained into `[local path redacted]` on 2026-04-28 as long-term system memory after explicit human direction. LlmWikis remains the handbook source for LLM Wiki patterns and keeps UAIX/UAI material non-normative.
- Public root discovery files now include `llms.txt`, `robots.txt`, and `sitemap.xml`.
- Current ZIP packages are published under `[local path redacted]` with `checksums.sha256.txt`, and the mirrored UAIX dogfood package is copied from `[local path redacted]`.
- Normal prompt-driven work uses `.uai/test-plan.uai` for targeted checks and does not rebuild ZIPs or run the full package/runtime suite unless the task is release scoped, package scoped, broad public-surface scoped, or explicitly asks for full verification.
- Full build/release work also cleans and updates internal `.md`, `.uai`, and `.human` source files that describe the packaged state, while keeping those private source files out of public discovery and WordPress upload ZIPs unless deliberately converted into public handbook copy.
- The active theme now includes a content/SEO readiness pass with 74 managed public routes in `sitemap.xml`, full public coverage in `llms.txt`, per-route meta descriptions, canonical links, social metadata, and section-aware structured data for managed pages. The obsolete prelaunch `/start-here/what-is-an-llm-wiki/` route is retired from managed pages instead of preserved as a public SEO redirect; the canonical definition route is `/what-is-an-llm-wiki/`.
- LlmWikis now has first-class implementation-ready standard/build routes for `/what-is-an-llm-wiki/`, `/why-llm-wikis/`, `/how-to-build-an-llm-wiki/`, `/llm-wiki-structure/`, `/starter-template/`, `/content-types/`, `/trust-model/`, `/metadata-standard/`, `/for-ai-agents/`, `/llm-wiki-vs-rag/`, `/llm-wiki-vs-ai-memory/`, `/checklist/`, `/maturity-model/`, and `/security-and-privacy/`.
- `/starter-template/` renders canonical template definitions, and `/downloads/llm-wiki-starter-bundle.zip` is generated dynamically from the same registry with manifest metadata and SHA-256 file hashes; do not replace it with a drifting static ZIP.
- LlmWikis.org is the source publisher for `llm-wiki-starter-bundle.zip`. Consumer/dogfood sites such as AIWikis.org should link to or consume this source-published bundle rather than publishing site-branded starter clones.
- The former `docs/` Markdown planning set has been migrated into public handbook/report routes where it has reader value and into `.uai/strategy.uai`, `.uai/progress.uai`, and roadmap state where it is internal operating context.
- LlmWikis has one maintained release theme: `llmwikis-knowledge-theme`. Default WordPress fallback themes may exist locally, but they are not LlmWikis release packages.
- Only the root ZIPs `llmwikis-knowledge-theme.zip`, `llmwikis-core.zip`, and `uai1-project-handoff.zip` are WordPress upload packages. `source-and-site-archives\` contains source-only or site-archive bundles and must not be used as theme or plugin uploads.
- Launch-ready public pages use clean root paths such as `/`, `/start-here/`, `/architecture/`, `/operations/`, `/navigation/`, `/schema-engineering/`, `/examples/`, `/reports/`, `/protocols-case-studies/`, `/explore/`, `/standards/`, `/guides/`, `/comparisons/`, `/glossary/`, `/implementations/`, `/mission/`, `/uaix-bridge/`, `/model-registry/`, `/evaluation-hub/`, `/security/`, `/source-policy/`, `/related-links/`, `/page-templates/`, `/community/`, `/contribute/`, `/governance/`, and `/roadmap/`.
- LLM Wiki handbook subroutes include `/architecture/three-layer-architecture/`, `/architecture/rag-vs-incremental-compilation/`, `/architecture/memory-lifecycle/`, `/operations/ingest/`, `/operations/two-step-ingest-pipeline/`, `/operations/query/`, `/operations/lint/`, `/navigation/index-and-log/`, `/navigation/graph-navigation/`, `/schema-engineering/agents-md/`, `/schema-engineering/durable-llm-wikis/`, `/schema-engineering/page-schema-standard/`, `/examples/personal-llm-wiki/`, and `/examples/team-llm-wiki/`.
- Seeded subroutes include `/standards/what-is-uai-1/`, `/standards/uai-1-message-model/`, `/standards/validator-errors/`, `/comparisons/uai-1-vs-mcp/`, `/comparisons/uai-1-vs-openapi/`, `/comparisons/uai-1-vs-a2a/`, `/guides/agent-handoff-patterns/`, `/guides/validate-a-uai-1-message/`, `/glossary/provenance/`, `/glossary/delivery-semantics/`, `/glossary/trust-channel/`, `/implementations/validator-workbench/`, `/implementations/tooling-landscape/`, `/model-registry/model-profile-template/`, `/model-registry/compare-models/`, `/evaluation-hub/benchmark-page-template/`, `/evaluation-hub/benchmark-contamination/`, and `/security/owasp-llm-top-10/`.
- Reports include `/reports/using-llm-wiki-with-uai/`. The former `/content-quality/` audit pages are now treated as internal improvement/backlog material, not public handbook content, and the active theme permanently returns `410 Gone` for that route family.
- Future structured record singles use `/records/...` rewrite prefixes where needed so custom post types do not steal seeded public child page routes under `/guides/`, `/comparisons/`, `/glossary/`, or `/implementations/`.
- LlmWikis is non-normative. UAIX.org is canonical for UAI-1 specifications, schemas, registry, validator behavior, roadmap, governance, and Project Handoff guidance.
- The strategy docs recommend a complementary scope first, then a possible standalone expansion after six to nine months of traffic, contributor, and operating evidence.
- Public claims should separate current launch-ready pages from planned live benchmarks, automated ingestion, public MCP, contributor programs, grants, memberships, and multilingual expansion.
- Public LLM Wiki pages should not attribute the LLM Wiki concept by creator name. They may link directly to the foundational idea file as a reference source.

## Current Strategy

- Keep the launch-ready public surface coherent, useful, and source-backed.
- Operate as an LLM Wiki creation handbook first, with UAIX and adjacent AI interoperability material kept as non-normative case studies.
- Seed a useful taxonomy before opening broad contribution.

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

AGENTS.md is the entry contract for agents. It tells an agent which context files to load, what authority boundaries apply, how file intake works, and which operations are out of bounds before broad edits start.

Structure

The file is structured around these visible headings: LlmWikis AI Instructions; Status; Handoff Summary; Loaded Context; Quick Start For A New AI; Required First Response; Current State; Current Strategy. 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-315 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LLMWikis AI Instructions",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/raw-system-archives-llmwikis-internal-memory-reorg-2026-05-01-agents-md-3f71523c/",
    "source_reference":  "raw/system-archives/llmwikis/internal-memory-reorg/2026-05-01/AGENTS.md",
    "file_type":  "md",
    "content_category":  "uai-system",
    "content_hash":  "sha256:3f71523c27508d14aa4d68739c1ea703675492046de152b591c9930fbe543f1c",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-04-29T02:06:48.2271934Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-315",
    "duplicate_role":  "primary",
    "related_files":  [

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