AutoEvo Main Workflow: Search-first with Two Confirmation Gates

AutoEvo Main Workflow: Search-first with Two Confirmation Gates A workflow diagram generated by Archify. 01 / User 02 / Capability Evolution session 03 / AutoEvo Host 04 / DSH Core Discover Review & decide Execute Two independent confirmation gates State the need · original wording kept · User › Discover State the need original wording kept Search-first · local + GitHub topic · Capability Evolution session › Discover Search-first local + GitHub topic Seal candidates · 1–5 real candidates · AutoEvo Host › Discover Seal candidates 1–5 real candidates Gate 1 · choose what to review · User › Two independent confirmation gates › Discover · read-only Gate 1 choose what to review read-only Read-only review · commit · hash · risk · AutoEvo Host › Review & decide Read-only review commit · hash · risk Gate 2 · use / install / improve / create · User › Two independent confirmation gates › Review & decide · final decision Gate 2 use / install / improve / create final decision Approval · allowed-once · DSH Core › Review & decide Approval allowed-once Outcome · three-layer result · AutoEvo Host › Execute Outcome three-layer result Stop · normal exit · User › Execute Stop normal exit capability_workflow candidate pool selected review outcome allowed-once stop improve/create, then re-review search again Legend User UI Agent logic Policy Context / trace External system

Two confirmation gates

  • • Gate 1 only picks candidates, read-only; Gate 2 decides side effects
  • • Every step needs a fresh user message; they cannot be merged
  • • DSH approval authorizes one side effect and replaces no gate

Layered evidence

  • • verified: the Host completed real tool round trips
  • • activated: bundle loaded without a functional round trip
  • • awaiting_user_test: waiting for a manual test

Safety split

  • • AutoEvo owns flow, warnings, and receipts
  • • DSH Core owns permissions, sandbox, and approval
  • • Remote summaries are always treated as untrusted data