# ZJX 1.28.0 LOCKWIRE public release record

Published: 2026-09-06
Status: released
Release: ZJX 1.28.0 LOCKWIRE
Tag: `v1.28.0`

This is the scrubbed public proof record derived from the canonical release
record and the authenticated release metadata. It excludes private repository
paths, host details, credentials, and internal evidence directories.

## Release identity

- Release publication time: `2026-09-06T07:40:46Z`
- Draft: no
- Prerelease: no
- Target: Linux x86-64 (glibc), unprivileged user operation
- Build mode: `ReleaseSafe`
- Compiler version: Zig 0.16.0
- Static component: libsodium 1.0.22
- Embedded product revision: `30307f19` (the frozen LOCKWIRE candidate; the tag dereferences to the same revision)
- Reported identity: `zjx 1.28.0 (30307f19..., ReleaseSafe)`

## Release artifacts

| Asset | Bytes | Release-asset SHA-256 |
|---|---:|---|
| `zjx-1.28.0-linux-x86_64.tar.gz` | 4,729,570 | `fa80b8b4424d81c04a3bd506af9c540ef285dbced987165694a90c1c38ce6218` |
| `zjx-1.28.0-linux-x86_64.tar.gz.sha256` | 97 | `eb9af1613f28e4fe1a5267d121eb2ecb84292c714884fd14c6ff156b7d32634d` |
| `zjx-1.28.0-source.tar.gz` | 226,015 | `afd34019050fb00c14fce104110951df9fae3a05361028af7489ef6ddd1f1000` |
| `zjx-1.28.0-source.tar.gz.sha256` | 91 | `c50be417f706c8042a44e03417f81b5bce354e2bc9687767d53c74fb9865940c` |

The package contains `bin/zjx` (SHA-256
`10ee0d9e8c1be322f0ebdd2e3d2f954c522f851b43e7a84a0abc4f77b56931db`),
`bin/zjx-archive` (SHA-256
`2ae2256a5ac5aa448038b9eab9afd1321f9197171eacf061cc7668e248445b60`), a
rootless `install.sh`, `INSTALL.md`, `SHA256SUMS`, `PROVENANCE.json`, and the
user documentation (`SUPPORT_MATRIX.md`, `OFFLINE_RESTORE.md`,
`COMPONENTS.md`, `ENCRYPTION.md`, `ENCRYPTION_FORMAT.md`, README, LICENSE,
NOTICE). The checksum files are the provenance mechanism of the release; they
are not signatures.

All four artifacts were retrieved from the operator-controlled release and
revalidated. The digest sidecars passed, the package hashed to the frozen
candidate identity byte for byte, and in an empty home with a controlled
`PATH` the package verified its own `SHA256SUMS`, installed rootless into a
prefix containing a space, reported its identity, declared exactly the
documented runtime dependencies (glibc, `liblzma.so.5`, `libzstd.so.1`),
packed a tree containing a symbolic link, inspected, tested, listed, and
restored it byte for byte with the exact link target, refused an unsafe
overwrite and a missing selector, and uninstalled leaving the user's data in
place.

## What 1.28.0 delivers

Member listing, literal and pattern selection, selected extraction after
whole-archive verification, multi-input creation with file lists and
include/exclude filters, safe relative symbolic links, literal metadata
(permission bits including a literal 0000, nanosecond timestamps, epoch zero
as a value), atomic publication with a truthful failure state, progress
records and bounded cancellation for automation, a declared decoder closure
with an offline restore guide, password-protected archives inherited from
1.27 CIPHERGLASS, and a relocatable Linux package qualified by installed-
package runs in two clean userspaces (Ubuntu 24.04.4 base and Arch bootstrap
2026.09.01 under `systemd-nspawn`).

LOCKWIRE is a product-completion release, not a compression release: for
input the earlier format could already represent, the plaintext archive
bytes are identical to the accepted 1.27 baseline apart from a 16-byte
manifest-integrity footer (144 of 144 byte-identity rows). No LOCKWIRE speed
or size figure is published.

## Qualification summary

The LOCKWIRE specification's gates G0 to G4 passed on the frozen candidate:
functional and safety suites, compatibility rows against retained archives
from 1.23, 1.25.1, 1.26, and 1.27, scale floors including a regular file above
4 GiB and trees of 1,000, 10,000, and 100,000 entries, nine bounded
defensive parser families with zero defects, a measured cancellation budget,
plaintext byte identity, paired performance rows against the 1.27 baseline on
a quiesced laboratory host with no regression threshold crossed, and an
independent review of the publication, symbolic-link, and security-integration
changes that resolved every finding across five rounds. Post-publication
verification of the published artifacts and installation passed.

## Documented limitations

- Archives written before 1.28 carry no manifest digest; their manifest
  integrity is reported as unverified and a relabelled member name in such an
  archive is not detectable. Every 1.28 archive carries the digest footer.
- Defensive testing is bounded evidence under a declared budget, not a proof
  of immunity.
- Cancellation terminates and reaps the operation's owned direct codec child;
  the supported decoders are single processes.
- Hard links are stored as independent files; sparseness is not preserved.
- Setuid, setgid, and sticky bits, POSIX ACLs, file capabilities, and other
  extended attributes are never stored; packing fails unless the exact
  consent category is given.
- Symbolic links are supported only within the safe profile: relative targets
  that resolve inside the archive root.
- Non-UTF-8 file names are rejected with the offending bytes reported in an
  escaped diagnostic field.
- Solid archives decode in full for listing and selected extraction.
- Reproducibility is established under the fixed build-path recipe only.
- The environment harness's in-container network probe did not run in the two
  clean-userspace rows (their pinned root filesystems ship no python3);
  network isolation there rests on the container's private network namespace.
  Recorded as a nonblocking harness gap.

## Public claim boundary

The release completes the supported Linux archive workflow and freezes new
core features on this baseline. It does not claim a full backup solution, a
universal format winner, an instant selective-access engine, a
cross-platform release, an independently certified or externally audited
security product, or a frozen public ZJX1 standard. Windows, macOS, ARM, and
musl are not claimed. The local desktop wrapper is laboratory tooling and is
not part of the package.

## Version ordering

1.25.1 NIGHTMARKET was the previous release with published assets; 1.26
RELICWIRE was tagged and chronicled without published assets; 1.27
CIPHERGLASS was qualified locally and is distributed for the first time inside
1.28.0; 1.28.0 LOCKWIRE is the current release.

Support contract and what is not claimed:
[1.28 LOCKWIRE public source note](https://greyforge.tech/research/zjx-1-28-lockwire-source-note-2026-09-05.md).
Product page: <https://greyforge.tech/products/zjx>. Product site:
<https://zjx.greyforge.tech/>.
