Note composition

A Brain note is one markdown document that can compose many content types — the same idea as Notion pages or Obsidian notes with embeds.

Model

Piece	What it is	Standalone?
Text / headings	Normal markdown body	Lives in the host note
![[Other note]]	Transclusion / include of another note	Target is its own note
![[Other#Heading]] / ![[Other#^block]]	Section or block include	Same
![[arc://view/name]]	Saved database / board / calendar view	BrainView row; reusable anywhere
```arc-view fence	Inline database definition	Can be split out into its own note
```arc-chart / graph fences	Live chart / graph widgets	Same — split or leave inline
Wikilink [[X]]	Reference, not inclusion	Target may or may not exist

Rule: anything worth reusing or opening alone should be its own note (or saved view). The host note then includes it with ![[…]] instead of duplicating content.

Compose

A project note might look like:

# Willow & Ivy

Launch narrative…

## Pipeline
![[Willow pipeline database]]

## Relationship map
![[Willow people graph]]

## This week
![[arc://view/this-weeks-training]]

• Willow pipeline database is a normal note whose body is mostly an arc-view (or embeds a saved view).
• Willow people graph is a graph-oriented note.
• Both can be opened alone, linked from elsewhere, or included in other hosts.

Split out

Take a heading section, ^block, or byte range from a host note → create a child note → replace the extracted range with ![[Child title]] (and an EMBED link).

Use when a section grew into its own document (database, long reference, graph).

Include

Insert ![[Target]] (or heading/block variant) into a host without copying body text. Prefer include over paste.

MCP / API

• brain_include — insert an embed into a host note
• brain_split — promote a section/block into a new note and leave an embed behind
• brain_read with include: ["outline"] — composition outline (text vs embeds vs arc fences)

ClaudeContext stays LLM scratch; composition is Brain-only.