runbook-solo

You can run a solo runbook workflow by initiating progression after the authority runbook converges and the user explicitly confirms entering solo mode. The Skill coordinates serial progression using the executor and acceptor sub-skills.

Solo mode is a runbook execution state using a single control point to coordinate serial progression. It enforces explicit role constraints, item-lock rules, and boundaries, limiting actions to execution and acceptance while deferring reconnaissance.

You need item locking during runbook coordination to ensure each item is completed before advancing to the next step. State validation aligns with authority runbook results to maintain stability and traceability.

No, you cannot perform reconnaissance during solo mode execution. The Skill enforces recon boundaries, deferring all reconnaissance activities until the workflow transitions back to the active planning state.

Yes, solo runbook execution requires explicit user confirmation before starting. Additionally, the authority runbook must be fully converged, and the system enforces solo role identity and post-action sign-offs for responsible conclusions.

Limitations of single-controller runbook coordination include strict boundaries that prevent cross-over into reconnaissance until the planning state becomes active again. It enforces serial progression, restricting execution and acceptance to sequential item completion.