Branch main Arch branch alignment contract

Branch Alignment Contract

Back to Branch Overview

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

Visual Context

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"]

Loading

Reading Checklist

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.

---

Source Content

Branch Alignment Contract - Superseded for Base Completion

This document is retained as a historical note and downstream handoff concept. Branch alignment is not an active Aeostara base-design completion gate.

Superseding Rule

Aeostara completion is validated by base-design contracts, ASH traceability, fixture outputs, diagnostic chains, recovery consistency, JSON semantics, and downstream handoff sufficiency. It is not validated by requiring platform branches or native implementation source files.

Current Use

Downstream repos may adapt the platform-repo templates under templates/platform_repo/ to report their own branch/module mapping. Those reports belong to platform repositories and do not make Aeostara depend on them.