SDTK-BRAIN
SDTK-BRAIN is deliberately NOT a pipeline stage and NOT part of the sdtk-kit umbrella. It is a separate local-first tool: one vault folder holds immutable raw/ sources and a compiled markdown wiki/ knowledge layer, maintained by deterministic rails (ingest, compile, lint, search, graph viewer) while your AI agent — reading the vault's own CLAUDE.md contract — does the actual thinking. Everything is local: no LLM in the CLI, no network, no telemetry, no entitlement.
When a solo founder reaches for this
You keep finding useful open-source repos, papers, and notes while building your product — and losing them. Drop each one into raw/inbox, run sdtk-brain ingest + compile, and they become linked knowledge pages (sources, comparisons, syntheses) your agent can search and cite next time you ask 'which orchestration library did we shortlist, and why?'. Open the same folder in Obsidian or your agent — it's all plain markdown.
Product truth
These cards summarize the current shipped or internal surface exactly as it exists in the local source tree.
raw/ holds immutable source documents (articles, papers, repos, notes, meetings) — the agent reads but never edits meaning there. wiki/ is the compiled knowledge layer (sources, concepts, entities, comparisons, syntheses) the agent maintains freely. .brain/ is CLI-owned machine state.
There is deliberately no `ask` command. The vault ships a CLAUDE.md operating contract; open the vault in your agent and ask there — grounded synthesis with page citations is the agent's job. The CLI provides only the deterministic rails.
sdtk-brain open builds a self-contained docs + graph viewer (the same guarded viewer SDTK-WIKI uses). If you also use SDTK on a project, sdtk-wiki's multi-workspace switcher can show your project wiki and your brain vault side by side. That is the only connection — the tool installs no SDTK skills and needs no other kit.
Core workflow
Maintenance
| Runtime | Project | User | Notes |
|---|---|---|---|
| Claude | n/a | n/a | Installs no skills for either runtime — the vault's own CLAUDE.md is the agent operating contract. Open the vault folder in your agent and it knows how to maintain it. |
| Codex | n/a | n/a | Identical: no skills, no runtime coupling. Any agent (or Obsidian) that reads markdown can operate the vault. |
Package README
products/sdtk-brain/distribution/sdtk-brain-kit/README.md
Install, quick start, full command list, vault layout, boundaries.
Family links
These product pages map the current suite boundaries so users can move from specification to coding to operations deliberately.