Repo context and agent context were mostly task-local.
2026 February
Agent workflow stage
From repo sessions to a vault-backed operating layer.
The scope widened from coding tasks to a broader knowledge and action system. Notes, tasks, context, schemas, and agent work started to live in one markdown-first environment rather than scattered chat history.
Markdown vaultsystem/ contextschema thinkingClaude Code
Agent work had a durable knowledge substrate outside the coding session.
Anatomy
Input
Vault notes, system folders, task records, repo work, agent context.
Shift
The source of truth moved out of chat and into durable markdown structures.
Output
A vault-backed way to preserve context, route work, and connect coding with personal/project knowledge.
Limit
The system was powerful but internally named and still evolving. It needed better routing, public language, and procedural reuse.
The missing layer was a command bus plus reusable skills that could make this operational day-to-day.