DeviaTDD's SDD layers: claims, ledgers, and merges
DeviaTDD keeps Product, Macro, and Meso work legible by turning an issue claim into a branch, recording transitions in append-only JSONL, and merging those records as a union.
Notes
Engineering notes on the foundations that help teams ship reliable software — systems, infrastructure, and tooling.
Why DeviaTDD's micro-loop is Red → Green → Judge/Train → Refactor
The micro-loop is four phases — Red, Green, Judge/Train, Refactor — each exists because the model has a documented failure mode the phase prevents. Judge verifies the implementation; Train rolls back to red_sha, injects the rejection feedback, and re-runs Green. Verification is structurally separate from generation, enforced by git itself.