-
Notifications
You must be signed in to change notification settings - Fork 0
Branch main Arch base to platform versioning
github-actions[bot] edited this page Jul 14, 2026
·
75 revisions
| Field | Value |
|---|---|
| Branch | main |
| Source | specs/architecture/base_to_platform_versioning.md |
| Commit | 774b981ef226 |
| Synced (UTC) | 2026-07-14T05:14:42Z |
Architecture pages define ownership, authority, and dependency direction for the base design.
flowchart TB
ASH["ASH fixed authority"] --> Aeostara["Aeostara base design"]
Aeostara --> Contracts["Contracts and algorithms"]
Aeostara --> Handoff["Downstream handoff"]
Handoff --> Platforms["Windows / Mac / iOS repos"]
| Question | Where to look |
|---|---|
| Who owns the semantic decision? | Check the authority and boundary language. |
| What is platform-neutral? | Find Aeostara-owned obligations. |
| What moves downstream? | Find adapter, implementation, and deviation rules. |
Downstream platform repos must explicitly pin the Aeostara base design they implement.
A downstream conformance report must include:
- Aeostara repository URL.
- Aeostara commit SHA or released tag.
- ASH baseline commit recorded by Aeostara.
- Conformance manifest version.
- Schema example set version.
- Fixture manifest version.
A downstream repo is compatible with an Aeostara version only when it passes that version's schema, fixture, traceability, diagnostic-chain, recovery, JSON semantics, and handoff gates.
When Aeostara changes a contract or fixture expectation, downstream repos must rerun all affected conformance vectors and update their deviation log before claiming compatibility.