Thanks! KSON is very focused on facilitating a better interface for a user managing config data, so one concrete example of the embed block's purpose is to help anywhere folks are directly editing important/complex multi-line strings in their config (think sql in dbt files, or bash snippets in GitHub Actions, etc).
By making the content type of the embed a first-class citizen of the syntax, together with clear boundaries for the embedded content, editors and IDEs can hook in all their great tooling to the embed blocks. So, you nailed it: being great for devex is exactly the idea.
By making the content type of the embed a first-class citizen of the syntax, together with clear boundaries for the embedded content, editors and IDEs can hook in all their great tooling to the embed blocks. So, you nailed it: being great for devex is exactly the idea.