-
Notifications
You must be signed in to change notification settings - Fork 0
Branch main Acceptance diagnostic chain conformance
github-actions[bot] edited this page Jul 14, 2026
·
75 revisions
| Field | Value |
|---|---|
| Branch | main |
| Source | specs/acceptance/diagnostic_chain_conformance.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. |
A conformant lifecycle has no orphan diagnostics. Root diagnostics reference themselves through chainRootReference and have no parent. Non-root diagnostics must reference an earlier parent. Every decision and audit event must link to a diagnostic reference.
Negative fixture cases must fail for missing parent, missing root, missing rule ID, decision without diagnostic, recovery step without diagnostic, and unreconstructable audit chain.