if, as @sgrove proposes, specs are the code of the future, then what is debugging? 1) spec compilation is the process of a coding agent turning specs into code 2) more and more “compilation” will be unattended, less watching the agent work diff by diff, more spec in, code out 3) type errors -> truth errors : most debugging will be digging through research and implementation plans in markdown to find the one line of incorrect context that makes the coding agent fail to succeed when implementing. Test suites will, among other things, check for truth and logical consistency. 4) there is a new higher order flavor of “attaching a step debugger” which is watching the agent implement a plan step by step to pinpoint the logic error in the spec. When you find an error when stepping through a program line by line, you change the code, restart the process, and repeat until it’s working. When you find an error in a *spec* while stepping through an implementation, you go upstream, fix the spec, and restart the *implementation*