Release note · N.05 · 2026-10-02

Rev 0328: receipts and a politer builder.

The autumn release is out to all licensed teams. Headline items: Ghost Chain push confirmations where you can see them, a traffic profile per build, audit that exports, and a desktop client that updates itself.

READING TIME ≈ 4 MIN AUTHOR THE AXIS TEAM STATUS SHIPPED · 2026-09

Quarterly releases are supposed to be boring in the good way: nothing breaks, old agents keep talking, and the new things are things you asked for. Rev 0328 is that kind of release. The full revision history lives on the changelog; this note is the annotated version — what shipped, and why it works the way it does.

Ghost Chain now gives you a receipt

The blockchain fallback channel has always been the feature we hope you never need, which made its one visible flaw worse: when you did push tasking through it, the panel said very little until an agent happened to check in. In 0328, push confirmations surface on the dashboard and inside the workspace, per agent, with the confirmation state in the audit log next to everything else.

A fallback channel you cannot observe is a rumor, not a capability.

The receipt changes how the feature gets used in practice: teams now treat Ghost Chain as a measured channel with a known delay instead of a leap of faith, which is exactly what a recovery path should be.

A traffic profile per build

The builder now takes a traffic profile per build rather than per campaign, with per-customer polymorphism applied across the whole batch. One teamserver can therefore run a campaign that reads like cloud telemetry and, ten minutes later, a build for a different target that reads like developer tooling — without touching server config.

The reason this took until the fourth release is the reason most things take time here: profiles interact with the module fetch path, and we were not willing to ship a profile switch that made depot fetches louder. The fetch still inherits the build's profile; the difference is that the choice is now per-artifact, where it belonged all along.

Audit exports, the client updates itself, and the panel speaks two languages

Three smaller items that each got asked about enough to earn a paragraph. The audit log — per-campaign, thirteen grants deciding who sees what — now exports to CSV from the panel and the API, which is the feature after-action reports were waiting for. The desktop client gained its own updater and tray alerts for new check-ins, so it stops depending on the panel for the two things a native window is actually good at. And the panel now ships fully localized in English and Russian, per operator, down to the audit strings.

Under the waterline: the usual quarter of re-testing named techniques against current defensive products — the matrix and the ship rule now have their own note — and a builder queue that no longer serializes behind a single long polymorphic batch. Nothing to demo, everything to notice.

Upgrading

The update is in the licensed channel now; the server updates in place and agents on older revisions keep working — the compatibility rule did not bend for this one either. If your term is current, 0328 is already yours. If it is not, renewal is a one-command affair and your install picks up where it left off.

Next in the queue: the Rust agent line (target payload 150–200 KB with the full module system) and the desktop client's road to 1.0. Listed as in progress, not as a promise — the changelog will say when it ships.