Obsidian Plugin

The seed

Obsidian is where a lot of personal thinking already lives: local Markdown files, a vault the user fully owns, a graph of linked notes. It is local-first by design. What it lacks is a bridge — a way for that private knowledge base to reach out to, and draw from, the broader EvoBioSys ecosystem without surrendering its sovereignty.

This quest is that bridge, built as an Obsidian plugin. It keeps the vault where it belongs — on the user’s machine, in plain files — while opening a controlled channel between personal knowledge management and the wider network of EvoBioSys tools and quests.

Why it matters

Knowledge that stays sealed in a single vault can’t participate in a larger regenerative system; knowledge that’s uploaded wholesale to a platform stops being sovereign. A plugin threads that needle: it connects the personal graph to the ecosystem on the user’s terms, choosing what flows out and what stays in.

• Local-first — the vault remains plain Markdown the user owns outright.
• Connection — personal notes can link into and draw from the EvoBioSys network.
• Control — the bridge is opt-in and scoped, never a wholesale export.

What building it out looks like

• Scaffold an Obsidian plugin using the official plugin API and TypeScript toolchain.
• Define exactly which EvoBioSys touchpoints the plugin connects to, and what data crosses the bridge.
• Keep every sync direction explicit and user-controlled, so the vault’s sovereignty is never assumed away.
• Ship a first useful integration end to end before broadening the plugin’s scope.

Status

Dormant. The intent is captured but development hasn’t started. It awaits a decision on which EvoBioSys touchpoints the plugin should bridge to first.