▋
docs/adr/0006-clanky-to-clankie-rebrand.md

ADR 0006: Rename clanky → clankie

  • Status: Accepted
  • Date: 2026-07-07

Context

The product is renamed from Clanky to Clankie (domain clankie.bot). The name is threaded through nearly everything: package scope (@clanky), package directories, the clanky CLI/binary, clanky:<slug> pane prefixes, CLANKY_* environment variables, clanky-* bundled skills, branding assets, docs, and prose. A partial rename would leave a permanent clanky/clankie split; a blind sed would break identity strings that must keep matching the old spelling at runtime.

Decision

Do a full one-pass rename across the monorepo: package dirs (clanky-agent→clankie-agent, clanky-contract→clankie-contract), ~6.4k identifiers across all casings, @clanky→@clankie, the CLI/binary, clankie: pane prefixes, CLANKIE_* env vars, clankie-* skill dirs, branding, and docs. The GitHub repo is renamed Volpestyle/clanky→Volpestyle/clankie (redirects preserved).

Deliberate exclusions / carve-outs:

  • clanky-internal — the frozen archive repo — is left as-is.
  • clankvox is unaffected (no clanky substring).
  • The private iOS/desktop app repo stays clankies (a distinct slug is required because GitHub disallows two same-named repos under one owner; the desktop surface is tracked as VUH-644).
  • The Linear team key VUH is opaque and unchanged.

Runtime back-compat (the strings a blind rename would break):

  • Voice wake-names keep "clanky" alongside "clankie" — people still say it — with all phonetic aliases intact and a guard comment.
  • Transcript author matching still maps "clanky"→assistant for pre-rename transcripts.
  • A temporary CLANKY_*→CLANKIE_* env-alias boot shim (clankie-agent/agent/lib/env-aliases.ts, imported first in every process entrypoint) mirrors any set CLANKY_* var onto its unset CLANKIE_* counterpart, so existing deployment config keeps working. Remove once deployments migrate.

Consequences

  • The full gate (pnpm check: typecheck + eve build) passes on the renamed tree; symlinks intact.
  • Existing CLANKY_* config and clanky voice wake-ups keep working, so a running deployment can rebuild/restart on the renamed build safely.
  • The env-alias shim is intentional tech debt with a clear removal trigger.
  • iOS bundle id changes (pre-launch, so no TestFlight/App Store continuity to preserve).