LLM-Wiki Capture Pipeline

Goal

Design the capture architecture that makes source capture fast, safe and reviewable across channels.

When to use

• The user wants an inbox/raw topology, metadata contract or dedupe boundary designed for LLM-Wiki capture.
• The user asks for a named-channel connector runbook (Telegram, email, Slack, Discord, Teams, browser clips, voice notes, PDFs, GitHub).
• The user needs the triage handoff between capture and wiki-triage/wiki-ingest defined.
• The user is setting privacy defaults or prompt-injection isolation rules for captured content.
• The user is adding a new high-volume or low-confidence capture channel class to an existing vault/repo.

Core rule

Capture should require near-zero filing decisions. Put material into inbox/ or raw/ first; use wiki-triage and wiki-ingest later.

Inputs