Branch main Arch downstream platform repository contract

Downstream Platform Repository Contract

Back to Branch Overview

Field	Value
Branch	main
Source	specs/architecture/downstream_platform_repository_contract.md
Commit	774b981ef226
Synced (UTC)	2026-07-14T05:14:42Z

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

Downstream Platform Repository Contract

Downstream platform repositories implement Aeostara. They do not redefine Aeostara.

Required Downstream Obligations

Each Windows, Mac, and iOS repo must:

1. Pin the Aeostara base-design version or commit it implements.
2. Map every required Aeostara interface to a native module.
3. Implement all required contracts without changing field meanings.
4. Run the platform-neutral conformance fixture vectors and record expected outputs.
5. Produce diagnostics that conform to DiagnosticEnvelope, DiagnosticReference, and DiagnosticChain.
6. Emit audit events that reconstruct the lifecycle.
7. Document platform limitations as deviations or caveats, not semantic changes.
8. Preserve ASH authority and Aeostara base-design authority.

Prohibited Downstream Behavior

• Inventing local rule-ID formats.
• Extending the ASH codeword set.
• Treating surface JSON diffs as semantic truth.
• Mutating configuration before policy, backup, and verification obligations are met.
• Bypassing fallback, containment, or safe halt without diagnostics.