Downstream Handoff Guide

Downstream Handoff Guide

Home | Repository Overview | Branch and Platform Status

Windows, Mac, and iOS implementation repositories consume Aeostara. Aeostara does not depend on those repos to be base-design complete.

Handoff Direction

flowchart TB
  ASH["ASH Pattern System"] --> Aeostara["Aeostara base design"]
  Aeostara --> Requirements["implementation_handoff/"]
  Aeostara --> Templates["templates/platform_repo/"]
  Requirements --> Platform["Platform repository"]
  Templates --> Platform
  Platform --> Reports["Conformance reports"]
  Reports --> Judgment["Acceptance judgment"]

Loading

Required Downstream Reports

Report	Template	Purpose
Module mapping	module-mapping.template.md	Maps Aeostara interfaces/contracts to native modules
Verification report	verification-report.template.md	Records schema/fixture/check outputs
Diagnostics conformance	diagnostics-conformance.template.md	Proves envelope, rule ID, root/parent, and audit integrity
Materialization boundary	materialization-boundary.template.md	Proves planning has no side effects and emission invents no semantics
Deviation log	deviation-log.template.md	Records platform limitations without semantic changes
Acceptance judgment	acceptance-judgment.template.md	Uses only approved judgment language

Adapter Responsibility Map

flowchart LR
  Aeostara["Aeostara contracts"] --> Observation["Observation adapter"]
  Aeostara --> Mutation["Mutation adapter"]
  Aeostara --> Policy["Policy gate"]
  Aeostara --> Backup["Backup provider"]
  Aeostara --> Verify["Verification adapter"]
  Observation --> Native["Native platform mechanics"]
  Mutation --> Native
  Policy --> Native
  Backup --> Native
  Verify --> Native
  Native --> Reports["Conformance artifacts"]

Loading

Downstream Rules

1. Pin the Aeostara commit or release being implemented.
2. Preserve ASH and Aeostara semantics exactly.
3. Implement native mechanics behind Aeostara interfaces.
4. Run fixture vectors and schema validation.
5. Emit diagnostic and audit chains for every decision path.
6. Record limitations as deviations or caveats, never as base semantic changes.