Interoperating your knowledge silos — making every note-taking tool work together, with a sovereign local-first system at the core.
OnePager v0.1.1Part of kidur — Tech Foundation
SilkNotes is the note-taking interface of kidur, the foundational tech layer of EvoBioSys. Where kidur provides the binding infrastructure — databases, sync, deployment — SilkNotes turns that foundation into the knowledge operating system you actually touch every day.
The future home of SilkNotes — sovereign, local-first knowledge operating system
The Promise
Knowledge lives in silos. Your thoughts are scattered across Obsidian vaults, Logseq graphs, Notion workspaces, Tana nodes, and a dozen other tools — each with its own format, its own lock-in, its own partial view of what you know. SilkNotes exists to dissolve these walls.
A complete feature set grounded in how the brain actually works. Backlinks, canvas views, structured output, and deep search — designed from neuroscience, not feature checklists.
Your notes flow freely between tools. No exports, no copy-paste, no Zapier, no manual reconciliation. SilkNotes bridges your silos directly, on your machine.
The complexity of interoperation stays invisible. The experience stays fluid. Effortless and smooth — because a tool that disrupts your thinking is no tool at all.
As a sovereign basis, SilkNotes will host its own local-first note-operating system with an open-source free tier and premium support — ensuring that your knowledge always belongs to you.
Interoperability Map
SilkNotes connects tools through typed bridges. Each bridge handles format translation, conflict resolution, and bidirectional sync — so you work in whatever tool you prefer, and SilkNotes keeps the threads connected.
Active integration via a dedicated plugin. Graph-level data exchange with bidirectional sync.
File-level interop operational. Markdown vault sync with frontmatter preservation.
Development environment bridge. Code context flows into knowledge graph and back.
Open-source knowledge base with docs, whiteboards, and databases. Natural interop partner.
AI-powered private note-taking. Investigating bidirectional sync with the CRDT layer.
Task management with deep linking. Planned bridge for project-knowledge integration.
API-based adapter translating between proprietary schemas and SilkNotes' open interchange format.
Architecture
SilkNotes treats interoperability as a layered problem. Rather than building one monolithic converter, it creates typed bridges between tool categories.
Tools that share open formats can be connected deeply. Logseq, Obsidian, Cursor, and other open-source tools communicate through file-system-level sync and shared data structures. This is the highest-fidelity layer — no information is lost in translation.
Tools like Notion and Todoist expose APIs but control the format. SilkNotes builds adapter layers that translate between proprietary schemas and its own open interchange format — preserving as much structure as the API allows.
Every bridge feeds into a unified output API, so downstream consumers — dashboards, publishing pipelines, AI agents — can access your knowledge regardless of which tool originated it.
A core promise. SilkNotes handles interoperation natively. You should not need a third-party glue service to make your own tools talk to each other. Bridges run locally, on your terms.
Roadmap
Development follows a practical sequence: prove interoperation between existing tools first, then build inward toward the sovereign core.
Establish the foundational file-level bridge and prove bidirectional sync. Markdown vaults flow seamlessly between Obsidian and the SilkNotes interchange layer.
OperationalExtend the Logseq Plugin sub-holon to handle graph-level data exchange. This is the deepest integration point, proving that outliner-style and document-style tools can truly share data.
ActiveGeneralize the bridge architecture to Reor, Affine, Legend, and beyond. Each new bridge validates and strengthens the interchange format.
PlannedBuild SilkNotes' own editing surface with backlinks, canvas views, and structured output — informed by neuroscience research on how humans actually organize knowledge.
PlannedLaunch the sovereign, local-first platform with open-source free tier and premium support. Every bridge, every feature, one silky interface.
PlannedTech Vision
The long-term architecture centers on conflict-free collaboration and sovereignty. Every layer is designed so that the server is optional and your data is always yours.
Conflict-free replicated data types ensure that edits from any device or tool merge cleanly without a central authority. The foundation for true local-first collaboration.
Real-time propagation of changes across connected clients and bridges. When you edit in Obsidian, your Logseq graph updates within seconds.
Durable storage layer for the canonical state. Queryable, portable, and compatible with the broader kidur stack via Apache AGE.
Ambient context capture that feeds into the knowledge graph. What you see and work with becomes queryable knowledge, with full privacy control.
Your data lives on your machine. The server is optional, never required. Fully offline-capable with seamless reconnection when you choose to sync.
The free tier includes the full editing surface, all FOSS bridges, and local storage. Premium support covers hosted sync, priority bridges, and enterprise features.
Partnerships
SilkNotes is reaching out to aligned projects and teams to co-develop the interoperability layer. The bridges are stronger when both sides are invested in making them work.
Open-source knowledge base with docs, whiteboards, and databases. A natural interop partner for SilkNotes' bridge layer — shared primitives for block-level data exchange.
Privacy-first, open-source knowledge management. The Logseq Plugin sub-holon is the most advanced bridge in development and the proving ground for graph-level interop.
AI-powered private note-taking with local inference. Investigating bidirectional sync with SilkNotes' CRDT layer for unified AI-augmented knowledge management.
Network thinking and text analysis. Exploring how graph-based insight tools can plug into the SilkNotes interchange format for emergent pattern discovery.
Decentralized file collaboration. Exploring shared primitives for sovereign document exchange — particularly relevant for the CRDT-based sync layer.
Sub-holons & Related Tools
The Logseq Plugin is the most advanced sub-holon and the proving ground for the entire SilkNotes architecture. It extends Logseq with SilkNotes features — graph-level data exchange, bidirectional sync, and typed bridges that demonstrate what interoperability actually looks like in practice. This is not just a plugin; it is the first concrete proof that knowledge silos can dissolve.
A meta-communities wiki tool — a sub-system of SilkNotes that structures shared knowledge across communities as an interconnected tree. Think of it as a collaborative knowledge commons built on the same interop primitives.
FOSS Ecosystem
SilkNotes is embedded in a FOSS ecosystem. The working bridges — Logseq, Obsidian, Cursor — already prove that open tools can share knowledge at the file and graph level. The planned bridges to Affine, Reor, and Legend will expand this into a full mesh of interoperating knowledge tools.
I intend for us to use Tana until SilkNotes itself is stable enough and can perform all of these features. Tana is the best tool for structured thinking right now — but the end goal is sovereign, open-source, local-first.
Building It
SilkNotes is not waiting for perfection. The approach is pragmatic: cobble together a working system from the best available tools, then refine toward the sovereign vision.
Use Devin for rapid prototyping. Build with legendapp for reactive state management, AI for acceleration, and Canvas for visual thinking. The first milestone is a Tana replica — cobbled together from proven pieces, then evolved into something that transcends any single tool.
SilkNotes is not just a tool — it is an exercise in ontological design. The structure of the tool shapes the structure of thought. How you organize knowledge changes what knowledge you can produce. SilkNotes is designed with this philosophy at its core: the interface should reveal connections that would otherwise remain invisible, and the architecture should respect how humans actually think — not how databases store data.
The grand vision: SilkNotes becomes a complete information processing network. Not just notes, not just interop — a living system where every piece of knowledge you encounter is captured, connected, and made actionable. From ambient context (Screenpipe) to structured output (publishing pipelines), from personal knowledge graphs to shared community wikis — one network, fully sovereign, fully yours.
Feature Vision
Beyond the basics of note-taking and interop, these are the features that would make SilkNotes a genuine replacement for Tana and the full tool stack.
Linking should not require knowing a nodeId. Natural, human-readable backlinks that feel as intuitive as writing a sentence — not managing a database.
A structured output API so downstream systems — publishing pipelines, citation tools, dashboards — can pull from your knowledge graph the way Mendeley Cite pulls from a reference library.
Deep integration with lex.page for collaborative writing that feeds back into the knowledge graph. Writing as a knowledge act, not a separate export.
A living feed of what is happening across your knowledge graph — new connections, edits by collaborators, emerging patterns, and suggested links.
Know when a shared note has been read. Request review on specific nodes. Collaborative knowledge work needs the same communication primitives as any team tool.
Non-destructive editing layers — annotate, comment, and propose changes without altering the original. Think version control for knowledge, not just code.