Obsidian Block References — Design

Status (2026-10-31): design approved; Phase 1 (block references) is being planned. Canonical spec: docs/superpowers/specs/2026-10-31-obsidian-block-references-design.md.

Follows Native Wikilinks & Embeds, Obsidian Vault Import and Live Preview & Daily Notes. Those covered everyday Obsidian use. This design brings in the syntax they left out of scope, which heavy Obsidian users depend on and which import used to delete.

Phases

PhaseFeature
1Block references: ^id anchors, [[Page#^id]] links, ![[Page#^id]] embeds, copy-block-link, [[Page#^ completion, import keeps block ids
2==highlight== and %% comments %%
3Tick task checkboxes from the reader
4Inline #tags: rendered, indexed, completed

Each phase ships on its own. Before a phase deploys, the live corpus is scanned for text the new syntax would capture, so no existing page silently loses visible text.

Block references (Phase 1)

Source vs reader text

Markers and comments are part of page source. They are stripped from everything derived for reading: rendered HTML, ?format=md, excerpts, chunks/embeddings, search, feeds and Knowledge Graph input. Source surfaces always keep block markers, so agents can link to blocks and never delete ids on write-back. Comments on source surfaces are kept for editors and admin MCP, and stripped for view-only readers and knowledge MCP. No new MCP tools: agents read and write markers as text.

Later phases

Out of scope

Canvas, Dataview, citations addressed by block id, automatic link rewrite when a block id changes, block-level backlinks, and nested-tag hierarchy.