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
readme.human
.uai/
context.uai
stack.uai
constraints.uai
operations.uai
progress.uai
style.uai
agent-file-handoff/
Content/
Improvement/
Archive/
raw/
public-sources/
internal-sources/
restricted-sources/
wiki/
index.md
log.md
concepts/
teams/
systems/
sources/
syntheses/
decisions/
runbooks/
contradictions.md
review-queue.md
Why teams need the handoff bundle
| Bundle part |
Team value |
Review concern |
AGENTS.md |
Defines the operating contract for every AI session. |
Must name protected paths, final reporting, and verification checks. |
readme.human |
Gives non-AI teammates a short briefing on what to clarify before asking for work. |
Must stay subordinate to constraints and current human decisions. |
.uai/constraints.uai |
Keeps privacy, legal, security, destructive-operation, and publication boundaries durable. |
Must be updated when policy changes, not patched through chat. |
.uai/progress.uai |
Records recently completed work, current focus, blockers, and done criteria. |
Must distinguish shipped behavior from planned work. |
agent-file-handoff/Content/ |
Receives candidate public or team-facing content. |
Needs review before promotion. |
agent-file-handoff/Improvement/ |
Receives audits, QA notes, bug reports, and roadmap suggestions. |
Should become fixes or backlog state, not public pages by default. |
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.
Team operating controls
| Control |
What it prevents |
Implementation pattern |
| Source intake queue |
Unreviewed files becoming organizational truth. |
Separate Content and Improvement intake; require explicit disposition. |
| Write staging |
Single-pass AI rewrites to reviewed pages. |
Candidate patch, reviewer approval, then durable write. |
| Ownership metadata |
Pages with no accountable reviewer. |
Owner, reviewer, domain, and next-review fields. |
| Access boundary |
Restricted material leaking into public or broad team pages. |
Path-based source classes and least-privilege agent permissions. |
| Release log |
Teams losing track of what changed and why. |
Append-only log plus release summary for broad-visible 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.
