Scryer update 0.3: Model-driven development for coding agents

Previous post: https://www.reddit.com/r/softwarearchitecture/comments/1ri0c4o/modeldriven_development_tool_that_lets_ai_agents/

Hey guys, a lot of people are working with coding agents (Claude Code, Codex, etc.) now, and there still aren't great solutions for problems like:

• You stop understanding the codebase once the agent starts rapidly building things you've never done before.
• No awareness of dead code, stubs, etc.
• The plan/code loop feels like a slot machine: sometimes great, sometimes half-baked, broken, or just the wrong way.
• No visibility of what will actually change once you approve a plan.
• Specs in markdown are hard to keep in sync and drift from the code.

A few months ago I posted about Scryer, my attempt at solving these and making work with a coding agent less frustrating and more transparent. Originally it was a C4 diagram of your codebase with lifecycle tracking and contracts, meant to guide implementation through semantic intent.

I've since rebuilt it heavily, because I think diagrams are the wrong abstraction here: you get a bird's-eye view, but no real surface to plan features or refactors, and you can't see a node's intent or implementation from the diagram.

Some of the changes in the latest version:

• The C4 model is now mainly a tree, with each node as a wiki page.

• Contracts are now a list of "responsibilities" and directives on each node, creating a semantic intent layer that can model anything from a UI button to a whole service.

• Every edit to the model goes into a "planned" diff that has to be reconciled with the code; changes only commit to the model once they're implemented. Planning ends up looking like a git diff with a clear blast radius, instead of reading an essay and hoping for the best.

• Drift (code changes that weren't part of the model or any plan) is surfaced as proposed model changes you can approve or reject.

Link to the repo: https://github.com/aklos/scryer

I released 0.3 a few days ago and I'm curious whether this starts to address the issues people hit with coding agents.

People keep talking about spec-driven development, but it seems to boil down to managing markdown files with no meaningful system underneath. Does anyone know of more robust solutions in the SDD/MDD space?