# Brain Wiki Schema

This document defines the three page types in the brain wiki.
The LLM must follow this schema exactly when generating wiki pages.

## Output Format

Return a JSON array. Each element:

```json
{
  "title":   "exact page title",
  "type":    "source | concept | entity",
  "subtype": "see below — omit for concept",
  "domain":  "see domains — omit if none fits",
  "content": "Markdown body only — no frontmatter, no path"
}
```

- `subtype` for **source**: `article | pdf | book | video | note | project`
- `subtype` for **entity**: `person | company | tool | model | framework | technology`
- The pipeline computes slugs and frontmatter — never include them in output.

## Wikilink Format

All cross-references use `[[Display Name]]` — just the display name, no slug, no pipe.

Rules:
- Only link to pages in the inventory or pages you are creating in this response
- The pipeline converts `[[Display Name]]` to `[[slug|Display Name]]` automatically
- Section links must match their section type (Related Concepts → concept pages only, etc.)

Examples: `[[Domain Driven Design]]`, `[[Ryan Singer]]`, `[[Shape Up]]`

## Domains

Use one of: `ai-llm`, `software-engineering`, `product-strategy`, `finance-markets`,
`personal`, `consulting`, `climate`, `infrastructure`, `security`

---

## Source Pages — wiki/sources/<slug>.md

One page per ingested source. Books are NEVER split across multiple source pages — update the existing one.

Body sections (in this order):

### Summary
2–3 sentences. Core argument or finding.

### Key Claims
Bulleted list. Paraphrase — no verbatim quotes or code.

### Concepts Introduced or Reinforced
Wikilinks to concept pages ONLY. One per line.

### Entities Mentioned
Wikilinks to entity pages ONLY. One per line.

### Open Questions Raised
Gaps or follow-up questions from this source.

For books only, also add:

### Chapters
One bullet per chapter with 1–2 sentence summary.

### Argument Arc
Overall narrative as it becomes clear across chapters.

### Updates
Dated entries appended on re-ingestion. NEVER rewrite — only append.

---

## Concept Pages — wiki/concepts/<slug>.md

One page per idea, framework, methodology, or pattern.

Body sections (in this order):

### Definition
One-paragraph plain-language explanation.

### Why It Matters
Practical significance. Why should anyone care?

### Related Concepts
Wikilinks to concept pages ONLY.

### Related Entities
Wikilinks to entity pages ONLY.

### Sources
Wikilinks to source pages ONLY.

### Evolving Notes
Updated as new sources arrive. Append, do not rewrite.

---

## Entity Pages — wiki/entities/<slug>.md

One page per person, tool, organisation, technology, or product.

Body sections (in this order):

### Description
One-line description.

### Relevance
Why this entity matters to this knowledge base.

### Key Positions, Products, or Claims
With dates where known.

### Related Concepts
Wikilinks to concept pages ONLY.

### Related Entities
Wikilinks to entity pages ONLY.

### Sources
Wikilinks to source pages ONLY.

---

## Non-Negotiable Rules

1. Output ONLY a valid JSON array — no markdown fences, no prose before or after
2. Each element: `{"title": "...", "type": "...", "subtype": "...", "domain": "...", "content": "..."}`
3. Never include slugs, paths, or frontmatter in output — the pipeline handles these
4. Wikilinks: `[[Display Name]]` only — no pipe, no slug
5. Dates always YYYY-MM-DD (used only in content body where contextually relevant)
6. Never reproduce verbatim code — describe the pattern or technique
7. Section links must match their section type
8. One source page per book — if inventory shows it exists, include it as an UPDATE