Review

LLM Wiki — Review

The human-in-the-loop gate. Drafts (from a local model, or any source) land in vault/_proposed/, mirroring their eventual wiki/ path. Nothing reaches the wiki until a human approves it here.

The _proposed/ + proposed_by contract

This contract is the single review channel for all drafted content (src/commands/propose/propose.ts). There is exactly one _proposed/ channel — no second draft mechanism exists.

Directory layout

Drafts live at vault/_proposed/wiki/<topic>/<page>.md, mirroring the target path they would occupy in vault/wiki/<topic>/<page>.md. _proposed/ is a sibling of wiki/ inside the vault root.

vault/
├── wiki/                  # live wiki pages
│   └── <topic>/<page>.md
└── _proposed/             # staging area — outside all wiki-scoped checks
    └── wiki/
        └── <topic>/<page>.md  # mirrors the target wiki/ path

Frontmatter on a draft

Every draft carries:

• status: draft — marks the page as not yet in the wiki.
• proposed_by: "<source>" — records what produced the draft (e.g. "ollama:llama3", "claude", "local-ingest-stub"). Dropped on promotion — the promoted page carries no proposed_by field.

Outside every wiki-scoped check

Because _proposed/ is a sibling of wiki/, every wiki-scoped hook and gate (validate-frontmatter.sh, check-wikilinks.sh, lint, verify-ingest.sh, the source-index) treats drafts as out-of-scope until promotion. Drafts cannot pollute the wiki.

Promotion (approve)

propose approve is the only sanctioned promotion path. Do not hand-copy draft content into wiki/ — that bypasses the checkpoint and the frontmatter rewrite. On approval, the engine:

1. Moves the file from _proposed/wiki/… to wiki/….
2. Sets status: active.
3. Drops proposed_by.
4. Stamps updated with today's date.
5. Commits the change as a git checkpoint → fully reversible via git revert <sha>.

Rejection

propose reject deletes the draft under a git checkpoint. Reversible via git revert <sha>.

Who uses this channel

All drafted content routes through this one channel:

• Local-model drafts (/claude-wiki-pages:draft, localModel.enabled).
• Durable-memory write-backs (source_type: agent-session, C4-write).
• Local-ingest stub (local-ingest-stub, Pc).

When to invoke

• The user asks to review/approve/reject drafted pages.
• A local-model draft run (/claude-wiki-pages:draft) has produced proposals.
• The orchestrator detected pending drafts in _proposed/.

Duplicate-claim check (P2.4 — ADR-0014 Part B)

Before presenting a draft to the human reviewer, run the duplicate-claim helper to surface any source_quotes that already appear in an existing wiki/ page. This is an advisory WARN only — exit 0, never blocks promotion. A genuine restatement on two legitimately distinct pages is sometimes correct; the call is human judgment.

bash scripts/check-duplicate-claims.sh \
  --target <vault> \
  --proposed <vault>/_proposed/wiki/<topic>/<page>.md

The script prints one WARN block per duplicate, naming the existing wiki page and suggesting [[existing-page]] as a wikilink instead of restating the claim. Present these warnings to the human reviewer alongside the normal readiness output.

Canonical (normalized) form — the check uses exact/normalized string equality only. No fuzzy matching, no edit-distance, no embeddings, no semantic similarity — ever (TEAM-BRIEF §5/§11.1, NO-RAG boundary absolute).

Normalization is applied in this exact order to every source_quotes.quote value before comparison:

1. Strip surrounding YAML scalar quoting (leading/trailing ", ', [, ] characters from the raw scalar string).
2. ASCII lowercase (tr '[:upper:]' '[:lower:]').
3. Collapse every run of whitespace (space, tab, newline) to a single space.
4. Trim leading and trailing whitespace.
5. Remove a fixed ASCII punctuation class — exactly these characters: period, comma, semicolon, colon, exclamation mark, question mark, double quote, single quote, backtick, open/close parenthesis, open/close square bracket, hyphen-minus; plus en dash (U+2013) and em dash (U+2014).

Two quotes are duplicates iff steps 1–5 produce the byte-identical string. A paraphrase — same meaning, different words — does not match. This canonical form is also defined in scripts/check-duplicate-claims.sh header (single definition, two display sites — script header and this skill — as required by ADR-0014).

How to run

List what's pending and how ready each draft is:

bash scripts/engine.sh propose review --target <vault> --json

Each draft reports its target (where it would land in wiki/), proposedBy, and a readiness check (ready, plus issues like no sources). Present this to the human and let them choose per draft.

Promote an approved draft (sets status: active, drops proposed_by, stamps updated, all under a git checkpoint):

bash scripts/engine.sh propose approve --target <vault> --file _proposed/wiki/<topic>/<page>.md --json

Reject a draft (deletes it under a git checkpoint):

bash scripts/engine.sh propose reject --target <vault> --file _proposed/wiki/<topic>/<page>.md --json

After approval — close the loop

Promotion only moves the file; it does not validate the wider graph. After approving one or more drafts, run the maintenance loop so the new pages are healed and indexed:

1. Curator heal — bash scripts/engine.sh heal --target <vault> (or dispatch claude-wiki-pages-curator-agent).
2. Polish — graph colors, vault MOC, per-folder MOC (the claude-wiki-pages-polish-agent).

propose approve returns next: "curator heal + polish" as a reminder.

Safety

• _proposed/ sits outside wiki/, so drafts are never linted, indexed, or cited until promoted — they cannot pollute the wiki.
• Every approve/reject is a git checkpoint; rollback is git revert <sha>.
• Promotion is the only path from a draft to the wiki. Do not hand-copy draft content into wiki/ — that bypasses the checkpoint and the frontmatter rewrite.
• Schema authority for this section: skills/init/template/CLAUDE.md ("Drafts and review (_proposed/)"). This skill aligns with it and does not override it.