Branch main Acceptance acceptance targets

Acceptance: Acceptance Targets

Back to Branch Overview

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

Required fixture scenario families include semantically stable despite superficial drift, semantically unstable despite minimal/no superficial drift, correction blocked; fallback selected, fallback unavailable; containment entered, containment breach; safe halt entered, verification failure triggers rollback/escalation, and policy gate blocks unsafe action before mutation.

Acceptance is based on expected fixture outputs, not keywords alone.