schemalisted

# Schema Every wiki page has a `type` field. The type determines which JSON Schema validates the frontmatter, how fields are indexed, and what graph edges are declared. For frontmatter field conventions, see the [frontmatter](../frontmatter/SKILL.md) skill. ## Epistemic roles The type field carries epistemic distinctions: | Role | Types | Question answered | |------|-------|-------------------| | Synthesized knowledge | `concept` | What do we know? | | Source provenance | `paper`, `article`, `documentation`, ... | What does this source claim? | | Reasoning output | `query-result` | What did we conclude? | | Structure | `section` | How is knowledge organized? | | Agent workflow | `skill` | How to perform a task? | | Reference | `doc` | What are the specifications? | Classify by the source material's nature, not its topic. A blog post about academic research is `article`, not `paper`. ## Built-in types Shipped by `llm-wiki spaces create`: | Type | Schema | Description | |------|--------|-------------| | `default` | `base.json` | Fallback for unrecognized types | | `concept`, `query-result` | `concept.json` | Synthesized knowledge and saved conclusions | | `paper`, `article`, `documentation`, `clipping`, `transcript`, `note`, `data`, `book-chapter`, `thread` | `paper.json` | Source types — one page per source document | | `skill` | `skill.json` | Agent skill with workflow instructions | | `doc` | `doc.json` | Reference document | | `section` | `section.json` | Section i