-
Notifications
You must be signed in to change notification settings - Fork 0
Branch main Arch branch native realization clarification
github-actions[bot] edited this page Jul 14, 2026
·
105 revisions
| Field | Value |
|---|---|
| Branch | main |
| Source | specs/architecture/branch_native_realization_clarification.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. |
Native realization belongs to downstream platform repositories. Aeostara does not add Windows, Mac, or iOS source files to satisfy base-design completion.
- Aeostara defines semantic lifecycle, contracts, fixtures, and conformance expectations.
- Platform repos implement native adapters, mutation mechanics, policy integrations, backup storage, verification probes, and halt behavior.
- Native implementation caveats are reported through downstream deviation logs.