Branch main Arch roadmap separation

Roadmap Separation

Back to Branch Overview

Field	Value
Branch	main
Source	specs/architecture/roadmap_separation.md
Commit	774b981ef226
Synced (UTC)	2026-06-29T06:00: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

Roadmap Separation

This roadmap separates semantic authority work from platform implementation work.

Track A: Downstream ASH Conformance (current)

Scope:

• Reset architecture authority language
• Replace drift-first contracts/algorithms with ASH-aligned artifacts
• Rebuild acceptance and traceability around ASH conformance
• Update CI gates to prevent semantic-authority regression

Exit criteria:

• ASH is explicit upstream semantic authority
• Observation, intent, encoding, evidence, actuator, repair, policy, and fixture artifacts are current ASH-built downstream specifications
• Conformance artifacts and CI checks are in place

Track B: Platform Realization and Release Verification

Scope:

• Platform-specific build/test/release validation in platform repos
• Native runtime integration and production hardening

Dependency:

Track B must consume the conformance surface produced by Track A.

Track C: Future Upstream Evolution (out of scope here)

Any semantic evolution of ASH belongs upstream and is not performed in this repository during Aeostara remediation.