-
Notifications
You must be signed in to change notification settings - Fork 0
Branch main Acceptance remediation acceptance targets
github-actions[bot] edited this page Jul 14, 2026
·
102 revisions
| Field | Value |
|---|---|
| Branch | main |
| Source | specs/acceptance/remediation_acceptance_targets.md |
| Commit | 774b981ef226 |
| Synced (UTC) | 2026-07-14T05:14:42Z |
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"]
| 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. |
Scenario 1: observed surface drift but semantic state remains stable. Scenario 2: no visible drift but semantic state is unstable. Scenario 3: correction blocked; fallback selected. Scenario 4: fallback unavailable; containment entered. Scenario 5: containment breach; safe halt entered. Scenario 6: verification failure triggers rollback/escalation. Scenario 7: policy gate blocks unsafe action before mutation.
All scenarios must include diagnostics, audit expectations, and schema-valid expected outputs.