Or to steel-man it, it could also end up as a prototype that forced the end user to deal with decision points, and can serve as a framework for a much more specific requirements discussion.

Exactly -- vibe coded PoC becomes a living spec for prod

That's a good point

classic "Midwest Goodbye" when trying to leave grandma's house

love it, will definitely be using it for sketching documentation in comments for SQL sprocs, etc.

One request: support for self-reference, i.e. "A --> A", "A --> A & B"

Thanks, that's a good suggestion. I'm also noticing that's not working as intended.

Fixed in 0.5.0. Give it a try!

Interesting. Looks very similar to CSound score notation, with CSound being oriented towards rendering audio files, rather than printable documents. CSound is also FOSS, and has a sound generation side that is incredibly deep and detailed.

https://csound.com/

Easier said than done, but if you can manage to set up the metric to align the business and the employee, life becomes very easy for management. Working on designing and implementing production-based pay systems in warehouses, when it goes right the department runs itself with barebones management as a little profit generating machine that fairly pays workers a very good wage. When it goes wrong though...

Yeah, the problem comes in when the dynamic changes and you’ve overoptimized for the old dynamic and don’t have any ability to flex within the systems without totally overhauling them. Hence the current supply chain problems…