ASH Conformance

ASH Conformance

Home

Core Rule

ASH is the immutable upstream semantic authority. Aeostara consumes ASH semantics and adapts product execution mechanics to them.

Required Flow

observe -> normalize -> map to ASH-aligned semantic state -> diagnose -> classify -> determine recoverability -> generate recovery plan -> gate -> backup -> execute -> verify -> rollback / fallback / containment / safe-halt

Conformance Targets

Aeostara is conformant when:

1. ASH authority posture is explicit in repository architecture docs.
2. Diagnosis-first semantic flow is documented and authoritative.
3. State classification uses ASH-aligned classes.
4. Recoverability mapping is deterministic.
5. Recovery planning is recoverability-driven.
6. Fallback decisions are registry-driven.
7. Containment and safe-halt behavior are explicit.
8. Diagnostic artifacts are schema/taxonomy compatible.
9. Superseded drift/diff contracts, helper algorithms, and configuration fixtures are absent.
10. CI gates reject missing conformance artifacts and cleanup regressions.

Acceptance Scenarios

Scenario	Expected result
Semantically stable despite superficial drift	STABLE, NO_ACTION
Semantically unstable despite minimal/no superficial drift	UNSTABLE or CORRECTABLE, recovery selected
Correction blocked	fallback selected
Fallback unavailable	containment entered
Containment breach	safe halt entered
Verification failure	rollback and/or escalation
Policy gate block	mutation blocked before execution