Wiki Ingest

# Wiki Page Templates

## Concept Page (concepts/)

```markdown
# Page Title

> One-line definition

## Key Points
(3-5 points, 1-2 sentences each)

## Details
(Expanded explanation, may include subsections)

## Context
(Which articles/documents it appears in, what role it plays)

## Related Pages
- [[related-concept]]

## Sources
- Article/Document X: specific reference point
```

## Product Page (products/)

```markdown
# Product Name

> One-line positioning

## Core Capabilities
(3-5 key features)

## Technical Highlights
(Architecture, implementation approach, etc.)

## Use Cases
(When to use it)

## Related Pages
- [[related-product]]
- [[related-concept]]

## Sources
- Article/Document X: specific reference point
```

## Pattern Page (patterns/)

```markdown
# Pattern Name

> One-line summary of what problem this pattern solves

## Problem Context
(When you need this pattern)

## Solution
(Core approach of the pattern)

## Trade-offs
(What you give up by using this pattern)

## Related Pages
- [[related-pattern]]
- [[related-concept]]

## Sources
- Article/Document X: specific reference point
```

## Comparison Page (comparisons/)

```markdown
# A vs B

> One-line summary of the core difference

## Comparison

| Dimension | A | B |
|-----------|---|---|
| ... | ... | ... |

## Strengths of Each

## Selection Guide
(When to choose A, when to choose B)

## Related Pages
- [[A]]
- [[B]]

## Sources
- Article/Document X: specific reference point
```


---
name: wiki-ingest
description: "Compile articles, documents, or notes into a structured wiki knowledge base. Use when user says 'ingest to wiki', 'compile to knowledge base', 'update wiki', 'wiki ingest', 'add this to wiki', or invokes /wiki-ingest. Supports single or batch ingest. Triggers: wiki, ingest, knowledge base, compile, digest, index, catalog."
---

# Wiki Ingest — Knowledge Base Compiler

Compile any text content (articles, documents, notes) into structured wiki pages with cross-references, building a searchable, interconnected knowledge network.

IRON LAW: One wiki page = one knowledge entity. Never cram multiple concepts into one page.

## Wiki Directory Structure

Wiki defaults to `wiki/` under the current project root. User may specify a different path.

```
wiki/
├── index.md              # Full table of contents
├── log.md                # Append-only operation log
├── concepts/             # Core concept pages
├── products/             # Product/tool entity pages
├── patterns/             # Engineering patterns & design decisions
└── comparisons/          # Cross-topic comparison pages
```

## Workflow

### 1. Confirm Input

Accept user-specified content source:
- Pasted text directly
- File path(s) (md, txt, pdf, etc.)
- Directory path (batch processing)

If user doesn't specify a wiki path, use `wiki/`. Create the directory if it doesn't exist.

### 2. Check Existing Wiki

Read `wiki/index.md` (if exists) to understand existing pages and avoid duplicates.

### 3. Extract Knowledge Entities

Extract from content:
- **Concepts** (`concepts/`): Abstract ideas, terminology, theories
- **Products** (`products/`): Specific products, tools, services
- **Patterns** (`patterns/`): Engineering patterns, design decisions, methodologies
- **Comparisons** (`comparisons/`): Cross-product or cross-approach analysis

Extraction threshold: An entity deserves its own page only if it would be referenced by other pages.

### 4. Create or Update Pages

Each entity maps to one wiki page.

→ Load [references/page-templates.md](references/page-templates.md) for page templates.

Rules:
- If page already exists → **update** it, append new information, don't overwrite existing content
- Keep the one-line definition stable unless the new content provides a clearly better one
- Prioritize updating "Sources" and "Related Pages" sections

### 5. Update Cross-References

Check all existing wiki pages. If new content involves concepts referenced in other pages:
- Update their Related Pa