中Release readiness

PUBLIC 1.0 · RELEASE READINESS

A download is not just a button.
It is a set of verified release facts.

The target scope for Captain Who 1.0 is frozen, but no installer has completed the full release gate. This page reports readiness without presenting development builds as supported releases.

RELEASE STATUSRelease gates in progress

NOT YET AVAILABLE
Version target1.0.0

Semantic Versioning · stable planned as default · beta disabled for initial GA

Launch platform targetmacOS 14+

Apple silicon and Intel builds produced and validated separately

Availability conditionEvery P0 gate complete

Signing, notarization, installation, upgrade, data, and core workflows

PLATFORM ACCEPTANCE · BYTE-BOUND

The matrix is frozen.
The real runs are not complete.

A target passes only when native or approved virtual environments produce evidence bound to the same release bytes. A valid blocked record is not release evidence.

STABLEAwaiting real acceptance

No same-release arm64 and x64 physical macOS 14 install, launch, upgrade, recovery, performance, accessibility, signing, notarization and staple evidence bundle exists.

PREVIEWAwaiting real acceptance

No same-release Ubuntu Desktop 24.04 LTS x64 packaged acceptance evidence bundle exists.

macOS 14 · Apple siliconAwaiting real acceptanceNo accepted run
macOS 14 · Intel x64Awaiting real acceptanceNo accepted run
Ubuntu Desktop 24.04 LTS · x64Awaiting real acceptanceNo accepted run
Windows · x64UnsupportedNo accepted run
Windows · arm64UnsupportedNo accepted run
Other Linux · arm64UnsupportedNo accepted run
Acceptance record ↗Acceptance schemaFrozen matrixMatrix schema

MACOS GA TARGET

Two native builds.
One release standard.

The plan calls for separate native DMGs for Apple silicon and Intel. A target becomes a public download only when the exact final release-candidate bytes pass every required gate.

MGA TARGET
MACOS · ARM64

Apple silicon

M1 or later · target minimum macOS 14.0 Sonoma

Target 1.0.0SHA-256 ships with the verified artifact
MGA TARGET
MACOS · X64

Intel

Intel Mac · target minimum macOS 14.0 Sonoma

Target 1.0.0SHA-256 ships with the verified artifact
Why are the buttons disabled?

A version number and packaging configuration are build metadata. They do not replace Developer ID signing, Apple notarization, installation on physical devices, or upgrade validation.

RELEASE GATES

A mature release starts
with what remains unfinished.

Every gate requires traceable evidence. The final release candidate is promoted to stable without rebuilding the same version.

✓
Positioning, claim policy, and platform matrixStable channel · macOS arm64 / x64
FROZEN
✓
Pinned supported runtimesNode 22.23.2 · Rust 1.98.0 · Electron 44.0.0
FROZEN
✓
Credentials, database, CI, and updater chainSafe migration, v20→v21, fail-closed gates, and signed metadata
FROZEN
04
Trademark clearance, legal publisher, and rights chainProduct name selected · a real individual or organization is still required
PENDING
05
Native runners and production credentialsBoth architectures, Developer ID, Apple, and Ed25519
PENDING
06
Signing, notarization, and immutable-origin promotionRead back remote bytes before atomically switching the pointer
PENDING
07
Final install/upgrade acceptance and 14-day soakOne RC byte set · no open P0 or P1 issues
PENDING

PLATFORM MATRIX

A limited, verifiable
1.0 scope.

Maturity comes from a support surface that can be verified—not from describing every build entry as cross-platform support. Ubuntu remains a separate Preview target. Windows is outside the 1.0 scope.

OSArchitectureArtifactTarget minimum1.0 status
macOSApple siliconSeparate DMGmacOS 14.0GA target
macOSIntel x64Separate DMGmacOS 14.0GA target
Ubuntu Desktopx64.deb24.04 LTSSeparate Preview
Windowsx64 / arm64——Unsupported in 1.0
Other Linuxarm64 / other——Unsupported in 1.0
UBUNTU PREVIEW TARGET

A separate entry point, update stream, and explicit Preview label.

Only Ubuntu Desktop x64 `.deb` is under consideration. No countdown or download language appears before its separate gates are complete.

NOT AVAILABLE

WHEN RELEASED

A public download will arrive with
the information needed to verify it.

01
Immutable artifacts

Published releases are not overwritten or rebuilt under the same version.

02
Publisher, signing, and notarization

The record identifies the real Developer ID publisher and notarization status.

03
SHA-256 and release manifest

Architecture, version, build number, and Git commit resolve to one record.

04
Release notes and support scope

Features, limitations, upgrade requirements, and known issues appear together.

QUESTIONS

Clear answers before download.

Why not publish a development build now?＋

A public GA release carries responsibility for installation, upgrade behavior, permissions, data migration, and core workflows. A runnable build is not evidence that those responsibilities have been validated.

The version already says 1.0.0. Why is it not released?＋

The package version is build metadata. Version 1.0 becomes a public release only when the exact final RC bytes pass every gate, receive a signed release tag, and ship with release notes.

When will Windows be available?＋

Windows is not in the 1.0 scope, and no public countdown is planned. A separate Preview decision can be made only after its platform-specific security and packaging work is validated.

Is Ubuntu Preview the same as stable?＋

No. Preview uses a separate entry point and stream. It still requires immutable artifacts, a signed manifest or published hash, an upgrade path, and data-safety validation.

RELEASE MANIFEST

Read the state
from one machine-readable record.

The current record intentionally contains no artifact, publisher, signature, or download URL.

View release manifest Explore the product