Tagged: Obsidian

All Tags

Obsidian

9 pages

5 related

Obsidian-specific concepts, APIs, and ecosystem

Related Tags

Architecture 82 Import 28 Data model 24 Graph databases 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/

Challenge 44: E2E testing strategy — CI coverage, visual regression, and the two-framework split

3

The project runs two E2E frameworks: WebdriverIO for the Obsidian plugin and Playwright for the docs site. Plugin E2E never runs in CI, and no screenshot anywhere is diffed against a baseline. Stress-test what belongs in CI at what cost, whether agent-read screenshots substitute for or complement real image diffing, and only then whether the framework split still holds.

Path: /agent-context/zz-challenges/archive/44-e2e-testing-strategy/

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

4

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/

The four Obsidian primitives — folder, heading, tag, wikilink

5

The four orthogonal structural primitives Obsidian gives you for representing hierarchy and relationships — folder, heading, tag, wikilink. Real recipes compose them; the target-structure choice determines how a source ontology lands in Tier 1. (File and frontmatter are the other two building blocks — see Mapping into Obsidian.)

Path: /concepts/hierarchy-primitives/

Mapping into Obsidian — from external data to vault primitives

6

The front half of Crosswalker: how disparate external data (framework spreadsheets, crosswalks, ontologies) is morphed onto Obsidian's native primitives — folders, files, headings, tags, frontmatter, wikilinks. The conventions that take a source row to a note on disk: transformation primitives, the recipe grammar, render(), the two kinds of link, and the Tier 1 contract.

Path: /concepts/mapping-into-obsidian/

The problem

7

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

Path: /concepts/problem/

Commands

8

Obsidian commands registered by Crosswalker, grouped by the task they support.

Path: /reference/commands/

Settings reference

9

Every Crosswalker setting, organized the way the settings tab now presents them — a launchpad, navigable section cards, and a live preview next to each control.

Path: /reference/settings/