Branch main Acceptance base design completion gates

Acceptance: Base Design Completion Gates

Back to Branch Overview

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

Base Design Completion Gates

Aeostara base-design completion requires all gates to pass:

1. Authority and dependency direction.
2. ASH baseline traceability.
3. Contract/schema completeness and examples.
4. JSON Pointer semantics and canonicalization.
5. Semantic projection and ASH mapping.
6. Diagnostic chain integrity.
7. Recovery and safety lifecycle consistency.
8. Downstream platform handoff sufficiency.
9. Fixture-based conformance CI.

No gate may require native platform source files.