ultrawork

Parallel task execution runs independent high-throughput work streams concurrently to improve throughput, while enforcing evidence-first completion. It requires explicit acceptance criteria and concrete verification evidence before wrapping up any task.

Evidence-first completion in workflow orchestration enforces explicit pass/fail acceptance criteria and requires concrete verification proof before finishing. This prevents "vibes-only" completion and ensures tasks meet strict state activation and closure protocols.

To enforce verification evidence for multi-lane work, apply explicit pass/fail acceptance criteria and require concrete proof before wrap-up. The runtime state must be activated and closed correctly via Omagy CLI with evidence-bound final reporting.

Yes, preflight workflow status gating is required for parallel execution. It acts as protocol guardrails to prevent unsafe workflow overlap and ensures the runtime state is activated and closed correctly via the Omagy CLI.

Parallel execution with state management applies to multi-lane work without persistence guarantees. It requires strict state activation and closure via Omagy CLI, providing lightweight proof and evidence-bound final reporting for concurrent tasks.

You should not use parallel execution for workflow orchestration when tasks are dependent rather than independent, or when persistence guarantees are required. It is designed specifically for high-throughput independent work streams needing lightweight verification proof.