Arising from int-0002 — Zero-ceremony operation — one binary, no server, no daemon

dira never requires a network service, an account, or a hosted tier to function

Every core capability — capture, `brief`, `why`, `map`, `check`, `ui` — works with the network unplugged, against files in the local repository, with no account and no login.

This constrains the roadmap in three specific places, which is the point of writing it down:

- The **hosted tier** (dec-0007, tier 3) may add convenience — zero-setup rendering, shared review, notifications — but never capability. Any feature that only works hosted is a violation. - The **mobile app** uses GitHub as transport (dec-0005) because that is the user's own infrastructure, not dira's. A dira-operated sync service is out of bounds. - **Telemetry is opt-in and absent by default.** A tool trusted with strategic rationale and private personal context does not phone home.

The commercial reading of this constraint: dira's pitch to a developer audience is "your data never touches our servers." That sentence has to remain literally true, or the pitch and the product diverge — and this audience checks.