build-implementation

To implement code from failing-test stubs using ATDD, read the architect-provided per-AC stubs, execute a batched RED phase, and write production code that passes the mutation gate and satisfies cohesion rules.

Mutation gating in a build workflow is a quality control step that scores code changes based on how effectively tests detect mutations, ensuring robust coverage and early defect detection before build completion.

Yes, the ATDD build protocol enforces cohesion-based shape rules to ensure that production code implemented from failing-test stubs remains clean, maintainable, and structurally cohesive throughout the delivery pipeline.

Yes, you can batch test rewrites during the ATDD build phase. The workflow automates batching test rewrites across typical build scenarios to streamline the transition from failing tests to implemented production code.

The best way to automate the build phase is to use an ATDD-driven orchestration workflow that converts architect-provided failing-test stubs into code, applies mutation scoring, and enforces runtime contract checks to produce auditable artifacts.

An ATDD build fails the mutation gate when implemented production code lacks sufficient test coverage to catch generated mutations, meaning tests must be strengthened to satisfy the required mutation score before passing the build.