GoKawiilCarson Gross argues Markdown files are becoming software's true source code
In an essay, Montana State University professor and consultant Carson Gross describes a shift he has observed in client organizations adopting agentic coding: Markdown documents are increasingly the source of truth for systems, with LLM-generated code treated as a derived, low-level artifact. He cites Hartley Brody's earlier essay 'Markdown is the new source code' to support the observation, and argues that Markdown specs should be checked into /src alongside the code and tests they generate, rather than living only in transient prompt sessions.
GoKawiil's interpretation of the reporting above, not reported fact.
If Markdown specifications become the primary artifact developers write and review, code review and version control practices could shift toward auditing prose specs rather than diffs of implementation code. Gross frames this as an emerging practice he's witnessing 'at terrific speed' in consulting engagements, though he says he remains personally ambivalent about AI-generated code overall. The idea suggests LLMs are increasingly treated like compilers, converting specifications into implementations, which could change how teams document, test, and maintain software.
- Carson Gross says Markdown is functioning as source code, not just documentation, in agentic-coding workflows.
- He recommends storing Markdown specs in /src alongside the code and tests they generate, rather than in ephemeral prompt sessions.
- Gross draws on Hartley Brody's essay to support the view that LLMs act like compilers turning high-level Markdown specs into low-level code.
Source: htmx.org, 2026-09-21
Published there as: “Markdown in /src”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.