C² is adaptive, not fixed

The fastest way to misread C² is to treat the six folders as a standard you have to comply with. They aren't. They're a starting shape — the layout that held up across a couple of years of real production work — handed to you so you don't start from a blank repo.

What matters isn't the folders. It's the two ideas underneath them: context is a first-class artifact, and the agent reads it before it acts. Everything else is arrangement, and arrangement should serve your project.

What's load-bearing

Three things are genuinely structural. Keep these and you're doing C²:

• The Router — one file your agent reads first, that points to everything else.
• The Session Brief — written memory across the gap between sessions.
• Knowledge capture — discoveries committed to git, read again next time.

The numbered folders are just where those things live by default. Move them, rename them, split them — as long as the Router still points to them and the agent can still find them.

How to adapt it

A few moves that are not just allowed but encouraged:

• Add a folder. Tracking velocity and estimation accuracy? Add a 07-metrics/. Running a research project? You might want an 08-experiments/.
• Sub-divide. A big product might split 01-planning/ into product-requirements/, strategy/, and roadmap/.
• Drop what you don't use. A solo project may never touch 06-agents/. Delete it. An empty folder teaches nothing.
• Rename for your team. If "release-notes" lands better as "changelog", rename it. The Router is the source of truth, not the folder name.

The test

Before you add or remove anything, ask one question: will the agent find what it needs, faster, because of this change? If yes, do it. If you're adding structure to feel organised rather than to load context, you're decorating, not building.

The structure serves the work. Not the other way round.

See the docs structure it adapts from, or read the full method.