Core Concepts#

CafeKit is not just a command set. It is a runtime model built around a few core ideas:

• specs are first-class project artifacts
• implementation happens one task at a time
• verification controls state transitions
• docs update incrementally after verified work

Start Here#

• Spec Lifecycle
• Task Registry

Why This Matters#

These concepts explain why CafeKit pushes back on:

• coding without an approved spec
• marking work done without evidence
• silently changing named technologies or contracts
• skipping docs sync after verified task completion