Branch main Arch native target architecture

Native Target Architecture

Back to Branch Overview

Field	Value
Branch	main
Source	specs/architecture/native_target_architecture.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

Native Target Architecture

Architecture Layers

1. Upstream semantic authority (ASH)
2. Downstream conformance/orchestration (Aeostara)
3. Platform-native realization (Windows/macOS/iOS)

Aeostara Layer Responsibilities

• Observe runtime/product state
• Normalize and map to ASH-aligned state representation
• Evaluate diagnostics/classification/recoverability using ASH semantics
• Build recovery plans with deterministic gating
• Execute and verify actuator steps with backup/rollback/audit
• Escalate via fallback, containment, and safe-halt pathways

Platform Layer Responsibilities

• Implement adapters/services using native frameworks/toolchains
• Preserve deterministic behavior and interface contracts
• Provide platform-specific observability and operations integration

Semantic Constraint

Platform differences may change implementation details but cannot change state-class meaning, recovery category semantics, or escalation rules.