Node Types

Every document in a Context Nest vault has a type field in its frontmatter. The type tells agents how to interpret the content.

Types

Type	Purpose	Example
`document`	General knowledge	Architecture overview, meeting notes, guides
`snippet`	Reusable text fragments	Boilerplate, templates, standard responses
`glossary`	Term definitions	Domain-specific vocabulary
`persona`	Agent role definitions	”You are a senior architect who…”
`prompt`	Reusable prompt templates	Code review checklist, analysis framework
`source`	Instructions for fetching live data	Jira sprint tickets, GitHub PRs, Slack threads
`tool`	Tool documentation	API endpoint docs, CLI reference
`reference`	Reference material	Standards, regulations, external specs

Default type

If type is omitted, the document is treated as document.

Source nodes

Source nodes are special — their body contains instructions for agents to follow, not knowledge to absorb. See Source Nodes for details.

Example


---
title: "Brand Voice Guide"
type: persona
tags: ["#brand", "#writing"]
status: published
version: 3
---
 
# Brand Voice
 
When writing on behalf of the company, use these guidelines:
 
- Tone: Professional but approachable
- Avoid: Jargon, buzzwords, passive voice
- Always: Lead with the user benefit