Compartment 1.15.0: engRAM, renamed

engRAM is now Compartment

• engram is still a working command. It is what sits in every MCP client
  config, shell alias and Hermes setup already written, so it keeps working.
  Nothing you have installed breaks. compartment and cmpt are the new names
  for the same thing.
• Your vault does not move. Compartment prefers ~/.compartment, but falls
  back to ~/.engram whenever that is the directory that exists. Nothing is
  copied, moved, or rewritten.
• ENGRAM_VAULT and every other ENGRAM_* variable still work.
• Old GitHub links redirect. MaxFreedomPollard/engRAM → …/Compartment.

The dangerous part of a rename, for anyone doing one

Sixteen of the 878 occurrences replaced in this release were not names. They
were AEAD associated data, KDF context labels and file-format tags baked into
every vault already written - engram-keyslot, engram-record:,
engram-payload:, the 2FA keyfile separator, the macOS Keychain service and
account, and others.

engram-keyslot is the associated data that wraps the master key. Renaming it
does not rename anything: the keyslot stops unsealing, and the vault cannot be
opened again by anyone, with any passphrase. Every memory in it is gone.

All sixteen are restored to their original spelling and frozen by
tests/test_ondisk_format.py, which fails if a future rename touches them.
Verified against a real 6,835-memory vault written before the rename: it
opens, unlocked, every record intact.

Downloads

File	For
Compartment-1.15.0.pkg	macOS, one click, with the optional menu bar utility. Start here.
Compartment-1.15.0.dmg	macOS, drag to Applications
compartment-1.15.0-py3-none-any.whl	pip / offline installs, any OS
compartment-1.15.0.tar.gz	source distribution, packagers, air-gapped builds

pip install compartment

macOS blocks the first launch of anything not signed with a paid Apple
Developer ID. The .pkg handles that; with the .dmg you allow it once in
System Settings → Privacy & Security → Open Anyway.