A manifest for settling what a legacy codebase never decided

Bednarczyk, writing about his own projects, argues that coding agents degrade in legacy codebases not because the model needs more context but because the codebase itself never settled its own vocabulary: "the model invents a fourth spelling of a concept that already exists three times, because the codebase itself never decided which one was real." His fix is a .workflow.json manifest at each repository's root that declares the repository's bounded contexts, points to a living glossary file for each one, and names every edge to a neighboring context, including which side owns disputed terms and what integration pattern applies. A generator unions these manifests across repositories into a single derived context map, and a skill cross-checks both sides of every declared edge, filing a fingerprinted issue when the two sides disagree so a later fix updates the same issue instead of opening a duplicate.

Why it matters: A manifest and glossary turn "give the agent more context" into concrete artifacts, with a mechanical check for when the two sides of an integration disagree about who owns what. The system's generator and cross-check skill are described but not yet published, so the account should be read as one practitioner's own setup rather than a tool anyone else can run today.