Is the name "dira" clear of collisions on the channels that matter?

**Answered: yes, on every channel dira actually ships through.** Verified 2026-07-29:

| Channel | Status | |---|---| | `kazi-org/dira` on GitHub | free (404) | | Homebrew formula `dira` | free (404 on formulae.brew.sh) — this is the real distribution channel | | GitHub exact-name repos | no collision; nearest hits are `dirac`, `diracnets`, `DIRACGrid/DIRAC`, `DiRA` | | npm `dira` | **taken**, but abandoned: v0.0.1, single publish, 2017-07-11, "Deep zoom with WebGL" | | crates.io | inconclusive — the API returned 403 to an unauthenticated check |

The npm squat does not bind: dira is a Go binary distributed via Homebrew and GitHub releases (dec-0001, int-0002), so the npm namespace is not on the path. It would only matter if `npx dira` ever became a desired entry point, at which point a scoped `@kazi-org/dira` is the standard fix.

One adjacency worth carrying knowingly rather than discovering later: **`dirac-run/dirac`** (~1.4k stars) is "a coding agent singularly focused on efficiency and context curation" — a name one letter away, in a neighbouring problem space. Not a blocker and not a trademark issue, but expect occasional confusion, and it is a reason to be crisp in positioning: dira is the direction layer, not a context-compression agent.

Meaning, for the record: *dira* is Swahili for compass. The sibling story is "**kazi** is the work, **dira** is the bearing."