ADR-002 — Product and module rename to Burrow™

From the Burrow™ specification set.

ADR-002 — Product and module rename to Burrow™

Context

The product shipped internally as PlatypusVault (Jira VLT, GitHub PlatypusDBA/PlatypusVault, Swift package PlatypusVault / PlatypusVaultEngine). The approved product name is Burrow™. VLT-131 applied Burrow™ chrome while leaving the engine module and compatibility identifiers unchanged. Local catalogs and operator secrets already exist under the old names.

Decision

Rename the user-facing product, Swift package, executable, and engine library to Burrow™ / BurrowEngine. Keep the Jira project key VLT. Keep the Vercel project slug vault. Public hostnames are burrow.jasonkoch.io / burrow-dev.jasonkoch.io (VLT-133; see ADR-003).

Preserve compatibility aliases so existing local setups are not stranded:

  • HTTP: send X-Burrow-Secret; still accept X-PlatypusVault-Secret.
  • Engine env: prefer BURROW_ENGINE_SECRET; still accept PLATYPUSVAULT_ENGINE_SECRET.
  • UI env: prefer NEXT_PUBLIC_BURROW_ENGINE_SECRET / NEXT_PUBLIC_BURROW_ENGINE_PORT; still accept the PlatypusVault names.
  • Application Support: prefer Burrow; if that catalog or session file is missing, read the legacy PlatypusVault folder.

The official brand kit lives in brand/ and is the source for site tokens and marks. GitHub repository rename to PlatypusDBA/Burrow is a hosting operation outside this change; new copy uses that URL.

Alternatives

  • Leave the Swift module as PlatypusVaultEngine and only change chrome. Rejected: the user authorized a full identifier rename and the brand skill treats PlatypusVault as retired.
  • Hard-break the secret header, env names, and Application Support folder. Rejected: that would orphan local catalogs and running operator scripts.

Consequences

New code, docs, and tests use Burrow™. Legacy names remain only as documented aliases, historical changelog notes, and excluded leftover filenames such as PlatypusVault-Design-Package. The engine secret must not be set on Vercel.