AutoEvo Install Outcome State Machine

AutoEvo Install Outcome State Machine A lifecycle diagram generated by Archify. 01 / Install & verify 02 / Non-failure outcomes + Failure & recovery 03 / Terminal Provisional · unknown / pending · Install & verify · persisted first 01 Provisional unknown / pending persisted first Approve+install · allowed-once · Install & verify · DSH runs 02 Approve+install allowed-once DSH runs Host verify · layer by runtime surface · Install & verify · mechanical 03 Host verify layer by runtime surface mechanical verified · tool_roundtrip · Non-failure outcomes · functional verified tool_roundtrip functional activated · bundle_activation · Non-failure outcomes · no round trip activated bundle_activation no round trip awaiting_user_test · manual_runtime · Non-failure outcomes · manual test awaiting_user_test manual_runtime manual test failed_absent · target absent · Failure & recovery · diagnosable failed_absent target absent diagnosable recovery_required · state unsafe to judge · Failure & recovery · recover first recovery_required state unsafe to judge recover first removed · receipt-driven · Terminal · terminal removed receipt-driven terminal decision + re-check reconciled round trip passed load only no fixture install failed reconcile unclear retry after recovery plugin_remove all non-failure outcomes Legend start active state waiting decision terminal success failure / exit

Three outcomes are not equal

  • • Only verified claims functional verification
  • • activated / awaiting_user_test need one real try
  • • installed / loaded are progress signals, not verdicts

restartRequired

  • • A non-failure outcome exists, but hot-load was incomplete
  • • Restart the target profile, then verify again
  • • It is a flag on outcomes, not a fifth outcome

Failure paths stay distinct

  • • failed_absent: diagnose first, then decide whether to retry
  • • recovery_required: sealed recovery; never blind-reinstall or hand-delete
  • • Repeated failures exit to a human decision, never loop