Branch main Arch platform implementation boundary

Platform Implementation Boundary

Back to Branch Overview

Field	Value
Branch	main
Source	specs/architecture/platform_implementation_boundary.md
Commit	5b2aac39fcf8
Synced (UTC)	2026-06-20T05:49: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

Platform Implementation Boundary

Aeostara specifies behavior; platform repos implement mechanics.

Concern	Aeostara base design	Platform repositories
ASH semantics	Bind to fixed upstream ASH sources	Consume without redefinition
JSON semantics	Define pointer addressing, canonicalization, preconditions	Implement parser/storage details
Diagnostics	Define envelopes, chains, rule references	Emit conforming records
Policy	Define decision contract and gate lifecycle	Connect native policy sources
Backup	Define backup record/result semantics	Create platform-native backup artifacts
Execution	Define approved-step lifecycle	Mutate platform resources safely
Verification	Define plan/result semantics	Run native checks and report results
Rollback	Define triggers and result semantics	Restore from backups
Fallback/containment/halt	Define deterministic escalation	Enforce native restrictions and halt behavior

No platform-native source code is required or accepted as an Aeostara base-design completion artifact.