Inner-Loop Test-Driven Development with Autonomous Coding Agents

The Anti-Pattern: "Vibe Coding" & Tautological Tests#

When an AI assistant is asked to "write a feature and tests for it," it will often write the implementation first, and then construct tests tailored specifically to match whatever edge cases its implementation happened to handle.

If the implementation contains a subtle logic inversion, the test will assert that inverted logic. The test suite is green, but the feature is broken.

The 4-Phase TDD Verification Loop#

flowchart LR
    P1["1. PLAN Phase<br/>(Architecture Spec & Test Invariants)"] -->|"PO Approval"| P2["2. TEST_FIRST Phase<br/>(Author Failing Unit Tests)"]
    P2 -->|"Tests Confirmed Failing"| P3["3. EDIT Phase<br/>(Minimal Code Implementation)"]
    P3 -->|"Tests Turn Green"| P4["4. REVIEW Phase<br/>(39 AST Definition of Done Gates)"]
    P4 -->|"nomos task sync"| P5["5. Atomic Release<br/>(Pristine Master)"]

The TDD Phase Discipline Solution#

Under Nomos, task execution is broken down into deterministic, sequential phases:

Phase 1: PLAN#

The agent researches the codebase, inspects existing interfaces, and drafts an implementation_plan.md specifying the expected behavior and test boundaries. The human approves the plan before any code is touched.

Phase 2: TEST_FIRST#

Before modifying application source files, the agent must write failing unit tests asserting the new behavior. nomos verify checks that the test suite runs and fails for the expected reasons.

Phase 3: EDIT#

The agent writes the minimal implementation necessary to satisfy the failing tests.

Phase 4: REVIEW#

nomos verify runs all 39 Go-native Definition of Done verification checks spanning 8 core architectural dimensions:

1. Compilation & Static Typing: Zero syntax, vet, or type errors.
2. Test Suite & TDD Parity: 100% green test suite with test-first coverage parity.
3. AST Complexity Limits: Cyclomatic complexity < 15 and zero monolithic runaway functions.
4. Docstrings & Clean Code: Boy scout docstring checks and zero copy-pasted boilerplate comments.
5. Wire & Dead Code Detection: Zero severed UI wires, orphaned endpoints, or zombie agents.
6. Goroutine Lifecycle: Concurrency leak detection and clean goroutine termination paths.
7. Secret & Config Hygiene: Zero committed API keys, local config leaks, or branch contamination.
8. Phase Lock Security: Machine-enforced phase token and cryptographic DAG state.

Eliminating Silent Software Decay#

By requiring failing tests before implementation, we force autonomous agents into the same disciplined feedback loop used by senior human engineers.

The result is robust, self-verifying code that does not degrade over hundreds of automated cycles.