Hey really appreciate that context! My thoughts:

1. Ledge's bet is it shouldn't feel like authoring at all. I've always had markdown docs chock full of commands and docs so making them runnable was the next logical step for me.

2. True. Keeping any kind of documentation up to date is difficult

3. Also true. I'm hoping Ledge's built-in agent support will bridge that gap and allow agents to help keep the docs up-to-date

And yes, a "Team" notebook is a challenge. Technically anyone with SSH access can all share a Ledge notebook. But that probably doesn't get us all the way there.

Thanks again for providing your thoughts. This by no means is a solved problem but I'm interested to see where it goes!

Thanks for answering. That's really interesting. Maybe agents flip this around. Instead of humans maintaining executable docs, the actual work generates the document. It could become something like a PR-style review layer for agent work. You don't necessarily need to understand the underlying code or tooling, but you can inspect what changed, why it changed, and approve or reject it. Do you think that would address any of the scaling problems you saw?