Programming as theory building
Peter Naur's argument that a program is the team's theory of the problem, and the code captures only the part that runs in the machine. The value is delivered outside the computer, so reading only the code shows only part of the program; in Naur's terms, code is lossy.
michael-carducci uses it to explain the value of openspec: its Markdown proposals, designs and specs hold the reasons behind decisions, the kind of tribal knowledge that doesn't fit in comments (Michael's example is a load-bearing bug in a class nobody touches). Some records become architectural decision records, so the next agent doesn't undo a decision because it is inconvenient, and a decision that no longer holds goes to a human. Related: spec-driven-development.
Source: report