execution/

Package engine provides execution infrastructure: bounded concurrent fan-out, observer dispatch, job-group execution, and simple function steps.

Package gate composes AnyJobs into a Gate of ordered phases, run with stop-on-failure and error aggregation.

Package job is the job tier: a Base, one per job, decorates the job it builds with the job tier (recovery, logging, tracing, metrics, timeout), so a job is a function plus its name and group, never a hand-written AnyJob type.

Package ops is an operations registry: one set of typed operations that several front-ends run the same way, such as a CLI, an MCP server (transport/mcp) and a scheduled job (transport/cron).

Package runs is the background-run table a front-end uses for long_running operations: Start reserves the operations registry's working-tree slot under a new run id and runs the operation in a goroutine, and Status / Result / Cancel / List address the run by that id afterwards.