Skip to content
LogosPilot
Request private preview

Release integrity

Release history

No public LogosPilot release has been published yet. This page explains how the history will be kept, so that the first entry arrives in a form you can already read.

The six conditions a release must satisfy before it exists Six nodes in a descending line, labelled Branded, Versioned, Signed, Checksummed, Verified and Stored. Each is joined to the next, and the final node is drawn as the point at which a release record appears. Branded Versioned Signed Checksum Verified Stored A release record appears only after the last gate.
Conceptual illustration. Every condition must hold before a release exists. None has been satisfied yet, which is why this page lists nothing.

Published releases

Release history
No public release has been published yet

LogosPilot is in private preview. The Windows build is code-signed and held in our permanent artefact repository, but it is delivered to approved churches rather than published here, so there is no public release to list and nothing on this page to download.

A release record appears here only once the installer has been branded as LogosPilot, versioned, code-signed, checksummed, verified, stored in the designated permanent artefact repository, and cleared for public download. Each of those steps produces evidence, and the record is written from that evidence rather than typed alongside it.

See the private preview How we will verify releases

Why the page exists before the first release

A release history that appears for the first time on release day is a history nobody can check. Publishing the format first means the first entry can be read against a standard that was set before there was any release to flatter.

How to read a release entry

Every release entry contains the same seven sections, in the same order, so you can find what you need without reading the whole thing.

New capabilities
What the release adds
Fixes
Defects corrected, and what you would have seen
Security updates
Stated separately, never folded into fixes
Compatibility
Certified vendor versions for that release
Upgrade guidance
Anything to do before or after updating
Checksum
So an older version can still be verified
Address
A permanent link to that release alone

Security updates are listed separately

A security fix folded into a general list of fixes is easy to miss. Keeping it in its own section means an administrator deciding whether to update this week can find the answer in one place.

Where this history begins

This history will begin at the first public release of LogosPilot. Builds made before that are internal and are never distributed, so they will not appear here.

We will not reconstruct a history that was not recorded at the time. A release history is only useful if every entry in it is real, so this one starts where the records start — which, today, is nowhere.

Where to go next

Next steps

LogosPilot is in private preview

There is no installer to download yet. If you want to take part in the private preview, the licensing route is the one that reaches a person.

Request private preview See the private preview page