-
Notifications
You must be signed in to change notification settings - Fork 0
Branch main Arch branching strategy
github-actions[bot] edited this page Jul 14, 2026
·
106 revisions
| Field | Value |
|---|---|
| Branch | main |
| Source | specs/architecture/branching_strategy.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. |
Aeostara's base repository uses normal source-control branches for specification work. Platform implementation branches are not required for Aeostara base-design completion.
The base repository must keep these artifacts valid on its main integration branch:
- ASH baseline reference and bindings.
- Contract schemas and examples.
- Conformance fixtures with expected outputs.
- CI validators.
- Downstream handoff templates.
Windows, Mac, and iOS repositories manage their own implementation branches. They consume Aeostara by version pin and prove conformance with the downstream handoff templates.