Tagged: Obsidian

All Tags

Obsidian

7 pages

5 related

Obsidian-specific concepts, APIs, and ecosystem

Related Tags

Data model 23 Import 19 Graph databases 4 Config 4 Evidence mapping 3

Pages with this tag

Knowledge organization

1

How to organize framework knowledge in Obsidian — structural primitives, meta-frameworks, and the hierarchy vs. graph tension.

Path: /agent-context/knowledge-organization/

Challenge 22: Target-structure expressivity in import recipes (archived)

2

RESOLVED 2026-05-04: closed grammar of 5 mechanisms (folder/file/heading/tag/wikilink) × ordered layout × also_emit × graph_edges; render(Recipe, ConceptIdentity) → Address as single coupling point; content addressing computed BEFORE render (target structure is a view); managed/user_preserve frontmatter split; v0.1 ships full schema with folder+file+heading wired. See callout.

Path: /agent-context/zz-challenges/archive/22-target-structure-expressivity/

SEACOW + folder-tag-sync — prior-art the project owner built before Crosswalker

3

Documenting two of the project owner's existing tools (SEACOW meta-framework in cyberbase, obsidian-folder-tag-sync plugin) as Foundation-phase prior-art that should inform Crosswalker's hierarchy-vs-graph decisions — and flagging a formal reuse investigation as a research item.

Path: /agent-context/zz-log/2026-04-10-seacow-and-folder-tag-sync-prior-art/

Vault hierarchy primitives — folder, heading, tag, wikilink-graph

4

Obsidian provides four orthogonal mechanisms for representing hierarchy in a vault. Real recipes compose them. The target-structure choice is what determines how a source ontology lands in Tier 1.

Path: /concepts/hierarchy-primitives/

The problem

5

Why filesystems and knowledge graphs don't mix — and what Crosswalker does about it.

Path: /concepts/problem/

Commands

6

Obsidian commands registered by Crosswalker.

Path: /reference/commands/

Settings reference

7

All Crosswalker plugin settings and their defaults.

Path: /reference/settings/