# ADR-0001: Adopt the create-cmp harness conventions

- **Status:** accepted
- **Date:** (scaffold date)

## Context

This project was generated by create-cmp, which ships an opinionated, mechanically-enforced
set of conventions: Clean Architecture with inward-pointing dependencies, a frozen and
CI-verified dependency version set (Kotlin/KSP/Compose/Room/AGP move as one), unit tests with
hand-written fakes (no mocking frameworks), testTag-addressable screens, theme-token-only
design values, and a verify lane whose committed evidence receipt is the definition of done.
AI collaborators are bound to these via `CLAUDE.md`.

## Decision

We keep the harness conventions as the project's baseline. Deviations are made consciously:
each one gets its own ADR superseding the relevant part of this record.

## Consequences

- Any contributor (human or AI) can rely on the exemplar `home` feature as the canonical
  pattern, and on `node qa/verify.mjs` as the single gate.
- Upgrades stay on proven-green version sets (`npx create-cmp-cli upgrade`) rather than
  ad-hoc bumps.
- The cost: less per-developer freedom in structure and tooling — accepted in exchange for a
  codebase that stays verifiable at AI speed.

This ADR also records *why ADRs*: significant decisions die in chat threads and PR comments;
a one-page record in the repo is the industry-standard fix
([MADR](https://adr.github.io/madr/)-style, trimmed). Copy `template.md` to
`NNNN-<slug>.md` for the next decision.