Loop Sdd Cycle

Loop: SDD Cycle

Advance one approved spec slice through spec, tests, implementation, and verification in bounded iterations. Each iteration takes the smallest slice that keeps the spec and its tests in step.

Loop Steps

1. Confirm the slice against the approved spec; run sdd-change for the spec-first discipline.
2. Add or update a focused failing test for the slice; run tdd-change for the red/green discipline.
3. Implement the smallest change that satisfies the failing test and the spec.
4. Verify the slice against the spec and acceptance criteria; run final-review before handoff.

Max Iterations

The loop runs at most 3 iterations. When it reaches 3 iterations without meeting a stop condition, it stops unconditionally and reports the unfinished state and the outstanding work; it never raises the bound to keep going.

Stop Conditions

Stop the loop as soon as any of these holds:

• The relevant tests and checks are green.
• An iteration produces no diff.
• The same failure repeats identically across two consecutive iterations.

Approval Gate

• Get explicit human approval before any write, commit, or destructive step in each iteration.
• The loop never self-approves, never continues past the iteration bound, and never runs destructive commands on its own authority.
• Pause and surface the state whenever approval is missing.

Safety

• Do not upload source code.
• Do not read or print secrets.
• APC does not run this loop; a human or agent follows these instructions and remains in control.