Knowledge Base
Docs
C² gives your project a docs/ structure — six numbered folders that hold what guides the build. These docs explain what each folder is for and how they work together. The kit is the product; this is how to use it.
The structure
Six folders, each with a job. Planning sets direction; Working executes it; Knowledge captures what’s learned; Operations, Reference and Agents support the rest. Each folder’s page explains what it’s for, what lives in it, and how it connects.
What you're building and why — the strategic layer every feature inherits from.
docs/01-planning/
Active execution — the briefs you hand the agent and the session memory it leaves behind.
docs/02-working/
The self-improving layer — gotchas, patterns, and decisions the agent reads before it acts.
docs/03-knowledge/
How the project runs and ships — deployment checklists and runbooks.
docs/04-operations/
The stable facts — tech stack and naming conventions the agent loads on demand.
docs/05-reference/
Who's on the team — the lead, the bench, the specialists, and their rules of engagement.
docs/06-agents/
It’s adaptive. Six folders is the starting shape, not a rule. Add your own — a 07-metrics/, sub-folders under 01-planning/, whatever the project needs. The structure serves the work.
Help shape the method
C² is open, and it gets sharper when builders push back on it. Got a question or an idea? Start a discussion. Found a gap or a typo? Open an issue.