dsh_cardian

The Knowledge Center in mainstream agentic IDEs tends to be locked inside the host: code-repo documentation, atomic knowledge cards, and cross-session memory cannot be searched offline or folded into a personal knowledge base. cardian re-creates all three pillars as a local engine where every wiki page, knowledge card, and memory entry is a Markdown file with YAML frontmatter, persisted into a single Obsidian vault you can open, search, and graph at will—no cloud dependency required.

The three pillars work together. RepoWiki scans local code repositories to build a structured skeleton, then an agent session back-fills each entry with semantic descriptions covering responsibilities, key implementations, dependencies, and caveats. Knowledge Cards organise atomic units by category and tag, support typed relations, bidirectional links, and SM-2 spaced-repetition scheduling. Memory persists cross-session facts grouped by scope, with an append-only revision history. All three share a hybrid keyword-plus-semantic search, an activity-driven auto-refresh that rebuilds MOC indexes whenever the project directory sees conversation activity, and a one-click Condense flow that is idempotent by design: already-enriched cards are preserved, never clobbered.

Whether embedded in the DeepSeek Harness desktop client via a sidebar Knowledge Tree panel or run standalone as a CLI, cardian exposes the same matrix of 36 tools, each annotated as read-only, idempotent, or destructive so agents pick the right operation without trial-and-error. It is built for developers and small teams who want to externalise what their AI-assisted coding sessions learn into a local, Obsidian-native knowledge base that survives project changes and session resets.