Skip to content

The unified vault at D:\FSS\KB\ is the operating system for managing Talbot’s businesses and (eventually) personal domains. It is the single source of truth for all information — providing clear context for AI agents and humans operating at any scope, from a single department to the full multi-business picture.


D:\FSS\KB\
├── Core\ — Cross-business: governance, AI, processes, logs, misc
├── MBR\ — myBetterRates
├── SDC\ — $MART DEBT Coach
├── FSS\ — Talbot Stevens
└── .obsidian\ — Vault config (plugins, themes, settings — one for all)

Key rule: Content that applies to two or more businesses lives in Core\. Content specific to one business lives in that business’s folder.


FilePurpose
Core\CONSTITUTION.mdVault charter — mission, structure rules, governing principles
Core\DASHBOARD.mdOperational hub — current focus, recent decisions, active projects
<Biz>\<Dept>\JOB_DESCRIPTION.mdDept scope, responsibilities, and SSOT links

Start at CONSTITUTION to understand the whole; start at DASHBOARD for current work.


Each business (MBR, SDC, FSS) uses a dept-first layout:

FolderContains
Strategy\Identity, positioning, IP, competitive analysis
IT\Systems, processes, dev standards, UX
Mktg\Brand, content, distribution, growth
Offerings\Products, services, pricing
Notes\ or Misc\Notes without a clear dept home
_WorkingOn\Active tasks, projects, research

Not every dept exists until there’s content to put in it (activate on first need).


DeptContents
AI\Claude Code, skills, prompting guides, AI tool notes
Cancer50\Cross-business pledge coordination
IT\Cross-business IT (apps, infrastructure)
Logs\AI, Branding, Dev, Decisions, Projects, Snapshots, System logs
Misc\Clippings, Glossary, meeting notes, miscellaneous
Processes\SMTM, KB-Obsidian, Software Dev, cheatsheets
Utils\Custom and external utility references

Full guide: Core\Processes\Simple Markdown Task Management\SMTM_System.md

Key rules:

  • Task files: <Biz>\_WorkingOn\Tasks\<Name>.md (no date prefix)
  • Cross-business tasks: Core\_WorkingOn\Tasks\<Name>.md
  • Logs: YYYY-MM-DD_Description.md (date prefix on logs, not tasks)
  • Scratch: _WorkingOn\Tasks\_tmp.md per business — Talbot’s personal scratch space, never modified by AI without explicit request

Full guide: Core\Ideas-Workflow.md

Summary:

  1. Capture — bullet in appropriate <Dept>\Inbox.md (or _tmp.md when routing uncertain)
  2. Promote — when ready to act, convert to TaskNote in <Dept>\Tasks\<Name>.md
  3. Archive — completed/parked tasks move to <Dept>\Tasks\archive\YYYY-MM\

Mobile capture: Obsidian mobile → dept Inbox directly.


RuleDetail
No Folder NotesFolder Notes + Waypoint plugins removed. Navigation via CONSTITUTION/DASHBOARD/JOB_DESCRIPTION.
Misc\ per businessNotes without a clear dept home go here, not spread across folders.
WikilinksUse bare [[filename]] (no path prefix) for stability across restructures. Path-prefixed [[Core/Folder/File]] breaks on folder rename.
SSOTOne home per concept. Never copy content to a second location — create a pointer instead.
GitSingle repo at D:\FSS\KB\. Commit after any session that adds substantive content.

CLAUDE.md files — each _WorkingOn\ has a CLAUDE.md providing project-specific context to Claude Code sessions. The global ~/.claude/CLAUDE.md sets cross-project behavior.

Graphify — knowledge graph lives at Core\Misc\graphify-out\. To regenerate:

  • Run /graphify from the main Claude Code session (not a background agent — API key required)
  • .graphifyignore at vault root excludes plugin JS, .git\, graphify-out itself

Claude Code entry points:

  • Vault-level work: open session in D:\FSS\KB\
  • MBR work: open session in D:\FSS\KB\MBR\_WorkingOn\ (picks up CLAUDE.md there)
  • Core/cross-business: open in D:\FSS\KB\Core\_WorkingOn\

Single repo initialized 2026-06-09 at D:\FSS\KB\. Initial commit: b157a9e (791 files).

.gitignore excludes: **/graphify-out/, workspace.json, plugin compiled JS, OS artifacts. .gitattributes: * text=auto (normalizes CRLF/LF across platforms).

No remote configured — local-only as of 2026-06-09.