Branch main Acceptance acceptance execution model

Acceptance: Acceptance Execution Model

Back to Branch Overview

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

Acceptance Execution Model

Acceptance runners execute static conformance checks over schemas, schema examples, fixture vectors, ASH traceability, diagnostic chains, JSON semantics, recovery consistency, and downstream handoff artifacts. They do not execute platform-native implementation code.