Skip to content

Branch main Status PLATFORM STATUS MATRIX

github-actions[bot] edited this page Jun 29, 2026 · 102 revisions

Platform Status Matrix

Back to Branch Overview

Field Value
Branch main
Source PLATFORM_STATUS_MATRIX.md
Commit 774b981ef226
Synced (UTC) 2026-06-29T06:00:16Z

Visual Context

This page is part of the base-design evidence set and should be read in authority-stack order.

flowchart TB
  ASH["ASH authority"] --> Aeostara["Aeostara base design"]
  Aeostara --> Evidence["Contracts, algorithms, fixtures, CI"]
  Evidence --> Handoff["Downstream implementation handoff"]
Loading

Reading Checklist

Question Where to look
What role does this page play? Read the summary and source content.
What does it constrain? Trace named contracts, algorithms, fixtures, or handoff docs.
How is it checked? Use the linked CI and conformance artifacts.

Source Content

Downstream Platform Status Matrix

This matrix records the downstream repository split. It is not an active Aeostara base-design completion gate.

Aeostara completion does not require native Windows, Mac, or iOS source files. Platform repositories consume Aeostara and report their own implementation status using the handoff templates under templates/platform_repo/.

Downstream repo Aeostara version pin Required adapters mapped Required contracts implemented Fixtures passed Deviations logged Judgment
flynn33/Aeostara-Windows:main v1.0.0 Destination-owned Destination-owned Destination-owned Destination-owned Runtime judgment is independent of base release
flynn33/Aeostara-Mac-iOS:platform/macos v1.0.0 Destination-owned Destination-owned Destination-owned Destination-owned Runtime judgment is independent of base release
flynn33/Aeostara-Mac-iOS:platform/ios v1.0.0 Destination-owned Destination-owned Destination-owned Destination-owned Runtime judgment is independent of base release

A downstream repo may record platform limitations as caveats or deviations. It may not redefine Aeostara base semantics.

Clone this wiki locally