Developing CCC

For anyone changing CCC, human or agent.

Rules come first, and they are not here

AGENTS.md and .specify/memory/constitution.md hold the rules and keep their authority. This collection holds no rules. It explains the domain those rules operate on.

If this collection and the code disagree, the code is the evidence and this collection gets corrected, under the repository's existing authority order.

Start here

1. Architecture, the framework and where each kind of thing lives.
2. The change map, task to layers to checks.
3. Verification, what each check actually proves.
4. Local setup.

Understand the domain before changing it

When something is broken

Queues and crons · Missing or stale data · Reconcile customers · Recalculate margin · Backfill history · Release and recovery

Maintaining this collection

Documentation maintenance is the authoring contract. A change that alters a published field, rule behaviour, a source window, identity logic, a screen workflow or a recovery procedure updates its documentation in the same change.

• Users and database inspection