Domain-Driven Agents

Ernest Bednarczyk argues on coldtake.dev that agents do poor work in old codebases because the code never decided what its own terms mean, so the code has to be made ready first. Bednarczyk splits authorship: the author does the "strategic" work of deciding, which ends in GitHub issues, and the author's skills and sub-agents do the "tactical" work, which comes back as pull requests to review. Every repository Bednarczyk owns carries a .workflow.json manifest whose domain block names its bounded contexts, where each context's glossary lives and every edge to a neighbouring context, with a CONTEXT.md glossary per context. Both sides declare each edge; a generator cross-checks the pairs and, with one flag, files each disagreement as an issue on the repo that owns the wrong side. The manifest is Bednarczyk's own convention, and the tooling is not yet published.

Visit Original Article →