> Markdown is becoming source code, not documentation

> That Markdown should be checked in to /src

I've made a similar argument last June, although I made the point with a sample project rather than manifesto style

https://github.com/TZubiri/keyboard-transpositions-checker

> A Proof of Concept for LLM as source code. I am of the position that the "code" is now target code and not source code. My strongest source for this claim is Stallman's classical definition of Source Code which is the "preferred way to modify the program".

> Upload the conversation with ChatGPT as source code

Although this was pre-agents/markdown, the main way to generate code was just with user-interface conversations with the LLM.

And my position differs in which I argue against uploading the target code, just the source code. Which is an issue if the LLM is not deterministic, but it's workable.

That said I apparently did foreshadow solutions to these issues

> Since we are using a consumer interface, and not an api, (first we have no guarantees that the code will not be used for training, so there's no IP protection, but also), we don't have much reproducibility, robust publishing should use API access and publish exact model with revision as well as seed (and even then we are not guaranteed reproducibility.

I think in general we'll end up rewinding so much, the sloppers are recursing and building a ton of harnessing tools that will need to be trashed because they made a fundamental mistake at the very first steps. Those of us who are a bit more careful will probably only get back to agentic engineering once the slopper activity dies down, it's pretty much career suicide at this point to get into it. Anyone who is barely careful is just waiting it out.

Markdown in /src