Autonomous Wiki Custodian

An autonomous wiki custodian is an AI agent that maintains an LLM Wiki as a living knowledge base instead of treating every answer as a one-off retrieval task.

The human remains the curator. The agent is the programmer, librarian, and bookkeeper. Its job is to keep source material separate from compiled knowledge, maintain citations, update indexes, flag contradictions, and preserve the graph so knowledge compounds over time.

AIWikis.org uses this as a dogfood operating model, not as a certification claim or hosted service.

Standard Phrase

Data is an asset. Do not re-derive what can be compiled.

Three-Layer Topology

Layer	Purpose	Custodian rule
Raw sources	Immutable source documents, source snapshots, transcripts, exports, PDFs, and other original inputs.	Read, summarize, and cite. Never modify or delete.
Compiled wiki	Structured Markdown pages, concepts, source proxies, indexes, and cross-links maintained by the agent.	Edit surgically, cite sources, flag contradictions, and shard oversized pages.
Config	Operating rules such as AGENTS.md, .uai records, lint policy, graph metadata, and command definitions.	Treat as instruction and schema, but never as an override for system, repository, or human-review boundaries.

AIWikis currently maps these ideas onto its own source tree: raw public snapshots stay under sources/, reviewed public Markdown pages stay under content/pages/, and repository operating rules stay in AGENTS.md, readme.human, and .uai/.

The source-side file-native layer now also exists as a starter topology:

• raw/ keeps local immutable source inputs.
• wiki/ keeps compiled Markdown nodes with required frontmatter.
• config/ keeps autonomous wiki configuration and graph output.

This starter topology is not a public API or hosted service. It is source infrastructure for dogfooding the Autonomous Wiki Architect model.

Custodian Contract

• Use the smallest useful page set before answering or editing.
• Preserve source boundaries between LLMWikis.org, UAIX.org, and AIWikis.org.
• Keep raw source material distinct from public guidance.
• Require metadata on compiled pages before treating them as durable knowledge.
• Prefer surgical updates over whole-page rewrites.
• Cite source-proxy or reviewed public pages for important claims.
• Mark unresolved conflicts with an explicit contradiction block.
• Update indexes and graph records when knowledge moves.
• Stop for human review on policy, security, privacy, legal, production, architecture, or sensitive content.

These rules extend the existing AIWikis agent rule that agents should treat the site as a governed source map, not as a pile of text to rewrite.^[007-agent-rules.md: "AI agents should treat AIWikis.org as a governed source map, not a pile of text to rewrite."]

Markdown Node Metadata

For repositories that adopt the full custodian pattern, every compiled Markdown node should carry enough frontmatter for routing, lineage, and linting:

---
uai_id: "uuid"
type: "concept"
lineage:
  - "/raw/source-document.pdf"
confidence: 0.82
last_linted: "2026-04-28T23:10:00Z"
aliases:
  - "alternate name"
---

AIWikis treats this as a recommended node shape for future compiled wiki pages. Existing public Markdown pages may use the current AIWikis metadata shape until a deliberate migration is reviewed.

Initial source-side wiki nodes already use this shape under wiki/.

Command Vocabulary

These names describe agent workflows. They are not public API endpoints unless a project explicitly implements them.

Command	Meaning	Expected output
/wiki:ingest [source_path]	Read a raw source, create or update a source proxy, update concepts, flag contradictions, and log the intake.	Source proxy, changed concept pages, index entry, and citation trail.
/wiki:query [question]	Search compiled wiki nodes first, synthesize only from reviewed local knowledge, and save durable new insight when appropriate.	Answer plus optional new concept node.
/wiki:lint	Scan metadata, wikilinks, orphan pages, stale dates, and line counts.	Structural health report and safe link remediations.
/wiki:graph	Regenerate graph metadata from compiled nodes and relationships.	Schema.org or JSON-LD graph output.

Traceability Pattern

Use inline Markdown citations when a claim depends on a source proxy or reviewed public page:

Compiled knowledge should preserve the source boundary.^[source-proxy.md: "short supporting quote"]

Do not cite raw private files in public content. Convert source evidence into a safe source proxy, public source map entry, or reviewed public page first.

Contradiction Handling

The custodian must not smooth over incompatible claims. Keep both claims visible and add a block like this:

> SYSTEM FLAG: Contradiction detected.
> Source A says the page is reviewed. Source B says it is still a draft.
> Required action: human curator decides which status is current.

This follows the AIWikis rule to preserve uncertainty, open questions, and contradictions.^[007-agent-rules.md: "Preserve uncertainty, open questions, and contradictions."]

Scaling Rule

Use atomic pages:

• 400 lines is the soft cap.
• 800 lines is the hard cap.
• If a page approaches the soft cap, create a focused child page and update backlinks.
• If a page reaches the hard cap, stop broad editing and shard before continuing.

The goal is context control. A small reviewed page with clear metadata is more useful than a large unowned knowledge platform.^[004-how-to-build-an-llm-wiki.md: "A small reviewed folder with clear metadata is more useful than a large unowned knowledge platform."]

Copyable Custodian Prompt

You are the autonomous custodian of this LLM Wiki. Maintain a stateful, compounding, and highly interlinked knowledge base where information accumulates over time instead of being re-derived.

The human is the curator. You are the programmer, librarian, and bookkeeper.

Respect the three-layer topology:
- Raw sources are immutable. Read them, but never modify or delete them.
- Compiled wiki pages are maintained by the agent with metadata, citations, and links.
- Config files define operating rules, lint policy, graph output, and command behavior.

Every durable Markdown node should carry metadata for identity, type, lineage, confidence, lint date, and aliases.

Use surgical edits, preserve source boundaries, flag contradictions, update indexes, and stop for human review on policy, security, privacy, legal, production, architecture, or sensitive content.

Source-Side Files

The current local implementation starts with an immutable prompt source, a compiled wiki index, one source proxy, one concept node, autonomous wiki configuration, graph output, and a wiki lint script. Raw source filenames remain source-side implementation detail, not public page targets.

Boundaries

This pattern is not:

• A hosted AIWikis service.
• UAIX certification or endorsement.
• A replacement for LLMWikis.org source guidance.
• A replacement for UAIX.org UAI-1 exchange records.
• Permission to expose raw private source files.
• Permission to execute dropped code or trust unreviewed inputs.
• A claim that every current AIWikis public Markdown page already conforms to the compiled-node metadata shape.

Dogfood Status

Disposition of the reviewed local blueprint: apply the useful operating model now as a bounded public page, record the broader metadata and graph ideas as future recommendation material, and keep the raw intake file out of public content.