Architecture & Repo Structure¶
Repository layout, subsystem organization, and development conventions
Details¶
The Work Buddy repo is organized around the work_buddy/ Python package,
tracked knowledge/store/ workflow and agent documentation, private registered
data stores beneath the configured data root, and .claude/commands/ launchers.
Journal, Contracts, Projects, Tasks, and Personal Knowledge own distinct SQLite
authorities; rich mutable bodies may bind to Co-work. The tracked knowledge
store remains the canonical documentation source for all subsystems.
Children¶
- Agent Execution
- Artifact System
- Artifact System
- Backups
- Consolidated Index
- Context Pipeline
- Context Pipeline
- Contracts
- Contracts
- Control Graph
- Control Graph
- Conversation Observability
- Conversation Observability
- Data First Skills
- Embedding Service
- Embedding Service
- Event Bus
- Event Bus
- Feature Cards
- Feature Cards
- Health
- Health
- Hot Path Discipline
- Inference
- Inference
- Knowledge System
- Llm Runner
- Llm Runner
- Llm With Tools
- Llm With Tools
- Local Human Identity
- Markdown Db
- Mcp Import Discipline
- Mcp Import Discipline
- Migrations
- Migrations
- Process Execution
- Repo Structure
- Repo Structure
- Resilience
- Retry Queue
- Retry Queue
- Skill Registry
- Source Foundation
- Summarization Framework
- Truth
- Vault Index
- Workflows
- Workflows
- Harness