Codifix v3.0.0-rc.1

Codifix 3.0.0-rc.1

Release candidate. Codifix 3.0.0-rc.1 is the first distribution under the
Codifix name. Packages are built from immutable source
66c2d1ecc4ca9b0c052e1d854f71a0703f998b71. All 11 jobs in
release run 39073102523
passed, including source/security validation, native package checks and final
artifact collection. This is a prerelease, not stable 3.0.0.

What changes

Codifix 3.0.0 is a breaking technical rename from Memory Layer. Product-owned
commands, package identities, service names, configuration paths and federation
enrolment names use Codifix identities. The old Memory Layer packages are not
upgraded in place, and Codifix does not provide old command aliases. Treat the
move as an explicit single-user reinstall and cutover, following the
release-specific reinstall procedure.

The rename preserves canonical and received knowledge, memory_entries,
existing content and attachments, and established identifiers. Existing
federation records and their signed history remain available as historical
evidence. Retirement disables old subscriptions and contribution bindings,
blocks unfinished source and publication work, invalidates old leases and
rotates the reviewed gateway epoch. Old queued, accepted and proposed payloads
are retained with their original bindings; they are not moved into a new
enrolment or published as new work. Participating instances require fresh,
explicit enrolment and sharing grants before federation resumes. See the
federation cutover operator guide.

The cutover keeps area topology and canonical/auth/area identifiers intact.
Database names and roles remain unchanged except for the exact product-owned
macOS onboarding names documented in the reinstall procedure. Previously
published releases, their artifacts, signatures and release notes are unchanged.

Reinstall and recovery

Back up and verify a matched recovery set before retiring the old installation:
database snapshot, configuration, environment files, state, credentials, service
definitions, active-state inventory and exact old executables. Keep the old
release packages and manifests unchanged. Stop and inventory old writers,
watchers, schedulers and federation workers before the cutover. Do not purge old
configuration or state, and do not enable previously inactive services as part
of reinstall. The detailed procedure covers Linux, macOS and Windows-specific
steps and recovery limits.

Platform status

Linux amd64/arm64 builds and package installation checks passed. Intel and Apple
Silicon macOS standard/application-update package checks passed. The macOS
packages are unsigned and are not notarized; they do not bundle PostgreSQL.
Windows ZIP, user MSI and server-tools MSI checks passed; Windows remains a
preview and does not bundle the full PostgreSQL/PDS/Pi stack. Windows build 1
uses MSI version 3.0.1. The Windows packages are also unsigned.

Use release-inventory.json, SHA256SUMS and the individual checksum files
published alongside the assets to verify the exact source and package bytes.
Neither native macOS pixel-level UI acceptance nor CA-host deployment is claimed.

Preserved-installation tooling

The running Monolith and Mac cutovers preserve existing knowledge, identities,
history and recovery copies. The Mac has passed actual read/sync, restart and
Workshop contribution checks. Its private app build is not a notarized release.

Two subsequent operational fixes are intentionally separate from the frozen
candidate: PostgreSQL boolean serialization in the Mac handover helper, and the
reviewed fresh-device local binding transition. Existing populated installations
must use the operator guide pinned at 269f419e
and its adjacent scripts. These fixes are not contained in the candidate source
archive and do not change the tested package executables. Later agent-bootstrap
wording and tool-name fixes are on main; they are not claimed as candidate bytes.

The CA/Trust installation remains on its existing version pending separate
approval. SSH there remains disabled.

Earlier releases

This candidate does not rewrite or replace the 2.1.0 release note, previously
published packages, signatures or release manifests.

Debian download filenames

GitHub replaces ~ with . in release asset names. The Debian downloads are
therefore codifix_3.0.0.rc.1_amd64.deb and
codifix_3.0.0.rc.1_arm64.deb; their .sha256 sidecars use the same spelling.
Package contents and the frozen checksum/inventory files are unchanged. The
Debian package version is still 3.0.0~rc.1, preserving prerelease ordering.

Save the download with its original name before checking the checksum. For amd64:

curl -fL -o 'codifix_3.0.0~rc.1_amd64.deb' 'https://github.com/3vilM33pl3/codifix/releases/download/v3.0.0-rc.1/codifix_3.0.0.rc.1_amd64.deb'
curl -fL -o 'codifix_3.0.0~rc.1_amd64.deb.sha256' 'https://github.com/3vilM33pl3/codifix/releases/download/v3.0.0-rc.1/codifix_3.0.0.rc.1_amd64.deb.sha256'
sha256sum -c 'codifix_3.0.0~rc.1_amd64.deb.sha256'

Replace amd64 with arm64 for ARM. If using all assets and the aggregate
SHA256SUMS, restore the two Debian packages and their sidecars to the original
~rc.1 names first. All 43 downloaded files matched the original candidate bytes
after this exact four-name mapping; no package was rebuilt.