Branch main Acceptance compliance checklist

Acceptance: Compliance Checklist

Back to Branch Overview

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

Compliance Checklist

• Aeostara is platform-agnostic.
• ASH is upstream authority.
• Platform repos consume Aeostara.
• Base CI does not require native platform source.
• Schemas and examples are validated.
• Fixtures encode expected outputs.
• Diagnostic-chain integrity is enforceable.
• Recovery consistency is validated.