Architecture

This chapter explains the shape of the implementation. Behavioral truth lives in the earlier chapters; architecture exists to make that behavior implementable without smuggling privileged paths through the side door.

Read in this order:

1. Crate layout
2. Daemon
3. gRPC service
4. State schema
5. Op-log watcher
6. Harness adapter

The architectural rule is simple: kkd owns behavior; clients observe and request. kk, kk-hook, the overlay, the sidebar, and future UIs all use the same service contract.

System shape