implement-step

You enforce state machine discipline for track execution by running a deterministic teleoperator loop that interfaces with the track-state CLI to manage atomic phase transitions. This prevents inconsistent agent behavior by verifying every action against the project's lifecycle.

Orchestrating subagents for TDD automation requires a rigid result-block protocol that dispatches specialized agents for testing and analysis. A conductor environment maintains state consistency by managing subagent dispatching while preventing overly verbose responses.

Yes, a teleoperator loop requires Python 3 and the Conductor plugin environment to maintain state consistency and workflow discipline. These dependencies are mandatory for executing track-state CLI commands and managing deterministic phase verification.

You implement a track with a small-window model by invoking a teleoperator that dispatches subagents and enforces phase verification. Every action is strictly verified against the track-state spine to maintain deterministic execution and workflow discipline.

You should not use a deterministic teleoperator loop if your project lacks a track-state CLI or does not require strict state machine enforcement. It is designed for tracks needing rigid atomic transitions and subagent orchestration, not for flexible or ad-hoc coding tasks.

Yes, subagent orchestration handles failure analysis by dispatching specialized agents to analyze failures within the strict state machine framework. The teleoperator loop manages this dispatching while maintaining the required result-block protocol.