Update

The published v2.1.0 release is the previous Memory Layer product. It does not install Codifix, and there was no published Codifix v2.0 or v2.1 release. Codifix v3.0.0 is the current stable release. (v3.0.0). Its technical rename changes package, executable, service, and configuration identities, so installing a Codifix package over Memory Layer is not an in-place upgrade.

Before changing an existing installation, read the Codifix 3.0 release-specific reinstall procedure. It describes the preservation and explicit cutover boundaries. Review the release notes and verify downloads using the published SHA256SUMS.

Before a v2-to-v3 cutover

First record the exact installed Memory Layer package, version, configuration, service state, database target, and active watchers. Preserve a matched, recoverable backup of the database, attachments, configuration, credentials, state directories, and old executables. Keep this recovery material private. Do not purge the old package or remove its data during preparation.

Codifix is a separate product identity. The installers do not transfer Memory Layer configuration or state, start old services, or run an automatic database migration. Semantic memory records, canonical IDs, and area topology are intended to be preserved by the reviewed release-specific cutover. Follow that procedure for exact state reconciliation, service shutdown, package retirement, and new installation; do not infer a general database rename from matching names.

v3.0.0 package names

These 3.0.0 assets are available on the release page linked above.

Debian packages use stable versioned filenames. Verify them using the release checksum files.

Use a standard macOS package for a fresh Codifix installation. The application-update package is only for an existing Codifix installation; it does not migrate Memory Layer. The Windows packages are a preview. Homebrew is HEAD-only until a pinned Codifix formula is published with the release source archive and checksum.

After an approved installation

Configure and verify the new Codifix installation using its own documented configuration and service commands:

codifix --version
codifix doctor
codifix health
codifix status --project <project-slug>

The service includes append-only database migrations through 0085 and applies pending migrations at startup. Those application migrations do not perform the product-identity cutover described above. Keep the old installation available for recovery until the reviewed reconciliation and post-install checks are complete. Never run the old Memory Layer binary against a database after Codifix has accepted writes.

Previous release history

The v2.1.0 release remains available as a Memory Layer release. Its packages and history retain their original identity. Do not use an old release asset as a Codifix installer or interpret it as a Codifix v2 release.

Read Release compatibility and known limitations, Operations, or the platform-specific install guide.