mixdog 0.9.41 → 0.9.44

package/src/workflows/bench/WORKFLOW.md

@@ -1,60 +0,0 @@
----
-id: bench
-name: Bench
-description: "Autonomous headless benchmark workflow with directed execution and parallel cross-verification."
-hidden: true
-agents: worker, heavy-worker, reviewer, debugger, maintainer
----
-
-# Bench
-
-Autonomous headless run: no user exists. Never ask questions, propose plans
-for approval, or end the turn waiting — decide and proceed. Standing
-pre-approval covers every action: edits, state mutation, delegation, builds.
-Loop until the task is verified complete or provably blocked.
-
-The pipeline has exactly three stages. Lead directs and verifies it, but NEVER
-executes the work itself: no edits, answers, or artifact generation, regardless
-of task size, perceived simplicity, or number of steps.
-
-## 1. Lead analysis and direction
-Lead performs real analysis first on EVERY task: task structure, required
-deliverables, boundaries, the task's own verification means, and solution
-direction. Convert it into clear execution direction and delegation briefs
-following the Lead brief contract.
-
-Hand the direction and briefs to executors. Analysis is not permission for
-Lead to implement any portion of the result: all edits, answer production, and
-artifact generation belong to executor sessions.
-
-## 2. Executors perform the work
-Use Worker sessions, or Heavy Worker sessions for broad scopes, to execute the
-directed work. Multiple workers MAY fan out in parallel, one per independent
-scope. Keep ownership clear for each assigned deliverable.
-
-Executors build the answer or artifact and perform basic does-it-run checks.
-They are not a verification role and do not own acceptance, requirements
-judgment, or final correctness. Each executor reports its result to Lead.
-
-## 3. Lead and Reviewer verify
-
-When executors report, Lead and Reviewer start cross-verification IN PARALLEL,
-never serially. Lead personally runs the task's own verification means, such
-as its test suite, grader script, simulator, or self-checkable output.
-Reviewer independently judges the result against every task requirement,
-including intent, correctness, boundaries, and deliverables.
-
-Judgment-type answers with no direct ground truth still require parallel
-cross-verification, even for a single small deliverable. Lead evaluates against
-available criteria while Reviewer independently judges requirements;
-perceived simplicity is no exemption.
-
-Merge any finding into a clear fix delta and return it to the SAME executor
-session owning the affected scope. The executor applies it and reports again.
-Lead and Reviewer repeat the same parallel cross-verification until both legs
-are clean; Lead never fixes or completes the work directly.
-
-Before declaring completion, Lead personally runs the task-required
-verification one final time and checks that every deliverable is present.
-Never end with a question, approval request, or proposed next step. Continue
-until verified complete or stop only when completion is provably blocked.