1.0.x Trust it

Planned

Make the launch boringly reliable.

After 1.0. Version numbers mark the intended order, not dates or paid upgrades; scope is provisional and may change with evidence and demand. Checked against the development repository on 15 October 2026.

In short

The first releases after 1.0 do one thing: make it boringly reliable. Crash, save, recovery and security fixes come first, then installation, updates, signing and compatibility.

Corrections that come in through support go ahead of any new architecture. New capabilities start with 1.1.

In practice

If 1.0 has a problem saving to a particular kind of drive, or updates misbehave on one Mac, a 1.0.x release fixes that before anything from 1.1 ships.

Why it isn’t simple

  • Problems that only show up on real Macs. After a launch, crash and save problems often depend on a particular macOS version, disk, file system or synced folder. Each has to be reproduced before it can be fixed without causing another.
  • Every fix goes through the whole release path. A fix still has to be built, signed, notarised, verified and delivered through the updater. A fix that breaks updating would be worse than the bug it fixes.
  • Fixes can’t disturb what people already have. Save and recovery changes must keep existing documents, settings and recovery copies intact across the upgrade.

What it won’t do

  • No new architecture until the launch is stable.

What it covers

1.0.xTrust it

Planned

  • Crash, save/recovery and security fixes
  • Install, updates, signing and compatibility
  • Support-led corrections before new architecture

Depends on Public macOS 1.0.

Product direction, October 2026Plan reference 1.0.x

Builds on

Leads to

What the labels mean

Planned
an accepted direction; the detailed scope isn’t committed.