Architecture And ADRs

This section is the implementation history and design map for KiloLock.

If you are evaluating the project for the first time, start with the top-level overview or the self-hosting and protocol docs first. Come here when you want the deeper design rationale behind the backend, query model, state-engine direction, and control-plane split.

Suggested reading order

1. ADR 0006: Refresh implementation
2. ADR 0007: Parallel apply
3. ADR 0014: File-scoped plan/apply
4. ADR 0015: Control-plane separation
5. ADR 0029: State-engine protocol for sliced state and resource locking
6. ADR 0032: State branch access policies

What you will find here

• accepted and proposed architecture decisions
• implementation history across backend, refresh, apply, and state-engine work
• design boundaries for OSS, self-hosting, and future hosted/cloud capabilities
• lower-level rationale than the public-facing overview docs

Evaluation aid

• ADR status matrix - practical evaluation of which

  ADRs are implemented, in progress, or still genuinely proposed