Example: Team LLM Wiki - LlmWikis.org

A team LLM Wiki adds review, ownership, permissions, and release discipline. The core architecture is the same, but every public or shared claim needs a source trail and a reviewer.

Team folder tree

team-wiki/
  AGENTS.md
  raw/
    public-sources/
    internal-sources/
    restricted-sources/
  wiki/
    index.md
    log.md
    concepts/
    teams/
    systems/
    sources/
    syntheses/
    decisions/
    runbooks/
    contradictions.md
    review-queue.md

Roles

Role	Can do	Cannot do alone
Reader	Read reviewed pages and source summaries allowed by access policy.	Edit wiki pages or ingest restricted sources.
Contributor	Add sources, draft pages, propose links, and flag contradictions.	Mark pages reviewed or resolve conflicts alone.
Reviewer	Approve source-backed pages, resolve contradictions, and mark stale pages.	Override legal, privacy, or access policy.
Maintainer	Change schema, run releases, manage redirects, and package exports.	Delete source history without approval.

Review gate

Draft page includes metadata, source links, related pages, and uncertainty notes.
Agent runs lint on the changed page set.
Human reviewer checks claims against source summaries and raw paths as needed.
Reviewer marks status as reviewed or needs-update.
Maintainer updates index.md, log.md, and release notes for public or team-wide changes.

Access metadata

---
title: "Incident Review Pattern"
type: runbook
status: reviewed
source_status: source-linked
visibility: internal
owner: platform-team
reviewer: ops-lead
last_reviewed: 2026-04-27
related:
  - [[provenance]]
  - [[incident-response]]
---

Operational safeguards

Separate public, internal, and restricted raw sources.
Require reviewer approval before publishing AI-assisted drafts.
Run lint before each release or major content import.
Do not claim live freshness without an automated source and timestamp path.
Keep legal, privacy, license, and takedown decisions explicit before opening public contribution.