MARKDOWN IN /SRC

Summary from the TLDR DevOps newsletter

Markdown can serve as the durable source of intent for agent-generated software, capturing architectural, data, API, and implementation decisions that would otherwise disappear in ephemeral prompt sessions. Keeping that Markdown alongside code in /src makes it diffable, reviewable, and available to both humans and agents, while tests can be derived from it to verify the resulting implementation.