That makes a lot of sense. I think “structured where useful, plain Markdown everywhere else” is probably the right balance.
The source-link idea is especially strong to me. If the model can stay close enough to the implementation, it becomes less like traditional documentation and more like an interface to the architecture.
Curious to see how it holds up once the project gets much larger. I’ll definitely keep an eye on it.
Thanks — I really appreciate that.
I’m planning to keep developing Model Weave steadily, and one of the things I want to keep testing is exactly how well this approach holds up as the models and the project grow.
The goal is to keep the Markdown practical for humans while making the generated views, Source Links, diagnostics, and AI-assisted maintenance more useful over time.
There’s still a lot I want to explore, so I hope you’ll keep an eye on it. Thanks again for the encouragement.