System surfaces
A file class with one job.
A sanitized example. Naming the surface class of every file is what keeps a multi-session project legible. This example uses four classes.
| Surface | Path | Role | Write rule |
|---|---|---|---|
| Memos | .cca/memos/ | Authoritative contracts and decisions | Authoritative; change through a new superseding memo |
| Reports | .cca/reports/ | Derived artifacts and analysis outputs | Writable in execution |
| Logs | .cca/logs/ | Day logs and lab narrative | Writable when a lane is authorized |
| State | .cca/state/ | Current system state | Read-only during proposal and intake |
The rule that makes it work
Each file resolves to exactly one surface class. A reader knows, from the path alone, whether a file is authoritative, derived, narrative or state. That single property is what lets a new session trust what it reads.
Back to the walkthrough · 00, the orchestrator · A step log