Branch main Acceptance platform repo handoff acceptance

Acceptance: Platform Repo Handoff Acceptance

Back to Branch Overview

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

Visual Context

Acceptance pages define the evidence needed before Aeostara or a downstream repo may claim conformance.

flowchart LR
  Artifact["Spec artifact"] --> Fixture["Expected-output fixture"]
  Fixture --> Validator["CI checker"]
  Validator --> Report["Audit report"]
  Report --> Judgment["Acceptance judgment"]

Loading

Reading Checklist

Question	Where to look
What evidence is required?	Read the gate table or scenario list.
What must fail when broken?	Check negative fixture and diagnostic-chain requirements.
What judgment is allowed?	Use only the documented final judgment values.

---

Source Content

Platform Repository Handoff Acceptance

A downstream platform repo is acceptable when it pins Aeostara, maps every required contract/interface, runs all fixture vectors, emits diagnostic/audit records, records deviations, and uses one final judgment: CONFORMANT, CONFORMANT WITH CAVEATS, or NON-CONFORMANT.