中Release readiness

RELEASE MANIFEST · V1

One release record.
Every published artifact.

When a public release exists, this page will resolve the Captain Who version, stream, build, source, publisher, and artifact hashes to one signed record.

MANIFEST STATUSNo published manifest

UNRELEASED

Version 1.0.0 is a target, not a published release. Downloads, update metadata, signatures, and public artifacts remain disabled or absent.

Stateunreleased
Target version1.0.0
Planned streamstable-macos
Downloadsdisabled
Artifacts0
Release claims0
Manifest signaturenot present
Legal publisher—
View readiness JSON View readiness schemaView published v1 contractView latest pointer contractView platform acceptanceView product media readinessView RC rehearsal recordView GA rollout rehearsal

This readiness record is intentionally unsigned. It is not an updater endpoint and contains no installer URL. Raw release evidence may retain MyCopilot as a legacy technical identifier until the desktop package completes a versioned migration.

RC DRILL · NON-PRODUCTION

Release mechanics exercised.
GA remains blocked.

A synthetic, test-only candidate traversed the repository contracts and byte-verification path. It used no production credentials or origin, attempted no publication, and grants no production release credit.

REHEARSAL STATUScompleted-non-production

GA BLOCKED
EnvironmentNON_PRODUCTION
Fixture suite44 / 44 passed
Candidate sourcesynthetic-fixture
Origin files inspected6
Production creditnone
Publication attemptedno
Real artifacts published0
Production statusblocked

11 production blockers remain open. The public manifest, downloads, updater metadata, and platform claims stay disabled.

JSON SCHEMA READ THE REHEARSAL NOTE

CONTROL PLANE · TEST-ONLY

Control path rehearsed.
GA has not started.

Ten signed synthetic revisions exercised staged expansion, pre-expiry renewal, full-rollout pause and resume, and direct fail-safe recovery from expiry. The rehearsal contacted no production network or provider and grants no production release credit.

REHEARSAL OUTCOMEcompleted-test-only

GA NOT STARTED
  1. 01Initial
    staged / 5%SEQ 100
  2. 02Expand
    staged / 25%SEQ 101
  3. 03Pause
    paused / 25%SEQ 102
  4. 04Resume
    staged / 25%SEQ 103
  5. 05Expand
    staged / 50%SEQ 104
  6. 06Full
    full / 100%SEQ 105
  7. 07Renew
    full / 100%SEQ 106
  8. 08Pause
    paused / 100%SEQ 107
  9. 09Resume
    full / 100%SEQ 108
  10. 10Expiry recovery
    withdrawn / 0%SEQ 109
Frozen stages5 → 25 → 50 → 100%
Signed revisions10
Controls passed12
Probes rejected16
Production networkno
Provider mutationno
Real artifacts0
Production creditnone

6 production blockers remain. This record is proof of control behavior, not proof of a release, live automatic updates, or real client cohorts.

PLATFORM TARGETS

Frozen scope.
No implied availability.

Targets describe the intended validation scope. A target becomes supported only when a published manifest references verified immutable artifacts.

macOS · Apple siliconGA targetTarget minimum · 14.0
macOS · Intel x64GA targetTarget minimum · 14.0
Ubuntu Desktop · x64Separate Preview targetTarget minimum · 24.04
Windows · arm64Unsupported in 1.0—
Windows · x64Unsupported in 1.0—

PUBLICATION BLOCKERS

Publishing is a state transition,
not a copy edit.

The validator rejects a published state while any blocker remains, while release artifacts are absent, or while publisher and signature evidence are missing.

  1. 01

    Complete final installation, upgrade, and data-recovery acceptance on both native architecturesfinal-install-and-upgrade-acceptance

    OPEN
  2. 02

    Capture and review real bilingual product media from the final RCfinal-product-media-and-rights

    OPEN
  3. 03

    Complete a 14-day final-RC soak with no open P0 or P1 issuesfinal-rc-soak

    OPEN
  4. 04

    Configure an immutable HTTPS origin, readback verification, and atomic pointer promotionimmutable-origin-and-atomic-promotion

    OPEN
  5. 05

    Establish a real publisher and complete rights chainlegal-publisher-and-rights

    OPEN
  6. 06

    Provision production Developer ID, Apple, trust-root, and release-signing credentialsproduction-release-credentials

    OPEN
  7. 07

    Establish denominator-backed rollout monitoring, alerts, and on-call coverageproduction-rollout-observability-and-on-call

    OPEN
  8. 08

    Provision protected native arm64 and x64 macOS runnersprotected-native-release-runners

    OPEN
  9. 09

    Record trademark-clearance findings and sail-mark rights evidencepublic-brand-clearance

    OPEN
  10. 10

    Complete bilingual release documents, terms, and support channelsrelease-documents-and-support

    OPEN
  11. 11

    Create and verify the release tag from a clean frozen source treesigned-source-tag

    OPEN
  12. 12

    Sign and notarize both macOS architecturessigning-and-notarization

    OPEN

PUBLISHED CONTRACT

What a verified publication must bind together.

01

Source & build

Signed tag, clean commit and tree, build number, initial release sequence, and frozen toolchain.

02

Artifacts & hashes

The public manifest fixes each immutable URL, filename, role, architecture, exact byte size, and SHA-256.

03

Release evidence

Separate candidate evidence records Developer ID, Team ID, notarization, stapling, Gatekeeper, component receipts, SBOM, and provenance before publication.

04

Updates & lifecycle

A separately signed pointer owns the current rollout and advances on every renewal, pause, resume, or withdrawal.

RELEASE WITH EVIDENCE

Until the evidence is complete,
the download stays closed.

Review the platform scope and current gates, or read how release-sensitive documentation is marked.

View release readiness Read release docs