Architecture & Repo Structure¶
Repository layout, subsystem organization, and development conventions
Details¶
The work-buddy repo is organized around a Python package (work_buddy/), a unified knowledge store (knowledge/store/ — workflow definitions, capability metadata, agent documentation), metacognition patterns (metacognition/), agent session data (data/agents/, gitignored), and slash commands (.claude/commands/). Contracts live in the Obsidian vault at the path configured by contracts.vault_path in config.yaml (default: work-buddy/contracts, resolved relative to vault_root). The knowledge store is the canonical documentation source for all subsystems.
Children¶
- Artifact System
- Artifact System
- Backups
- Backups
- Capability Registry
- Context Pipeline
- Context Pipeline
- Contracts
- Contracts
- Control Graph
- Control Graph
- Conversation Observability
- Conversation Observability
- Data First Capabilities
- Data First Capabilities
- Embedding Service
- Embedding Service
- Event Bus
- Event Bus
- Feature Cards
- Feature Cards
- Health
- Health
- Inference
- Inference
- Knowledge System
- Knowledge System
- Llm Runner
- Llm Runner
- Llm With Tools
- Llm With Tools
- Markdown Db
- Markdown Db
- Mcp Import Discipline
- Mcp Import Discipline
- Migrations
- Migrations
- Repo Structure
- Repo Structure
- Resilience
- Retry Queue
- Retry Queue
- Summarization Framework
- Workflows
- Workflows