Appreciate the reply and thanks for the dialogue.

> 2. Git integration today is read-only by design. We intentionally avoid bidirectional mutation of source or models until we can guarantee determinism and auditability.

Our CI/CD regenerates our business and tech knowledge site with full business, product, system, and code docs on every build.

Lack of sync makes your product unusable for us, even though we're your most target market since we are entirely sold on, and practicing, the ethos that leads to this product.

We were among the first users/supporters of Structurizer. We were among the first users of icepanel.io, found it couldn't support our scope*, but ... paid for it anyway (!!!) just to support the concept.

[* Note: It only took them a couple quarters of work to be able to support our or anyone's, scope.]

Also support the work other teams are doing to make smarter (more humane) layouts, we even pay for commercial layout engines if they are drop-in for open source.

We do all this not just because this is the right way to do it even as a solo engineer, but anyone working in this space is contributing towards making architectural thinking and communication as common and portable as markdown, necessary to bridge the silos within most organizations of any scale.

OTOH, if the product doesn't squarely support an ecosystem rather than silo philosophy, we can't (won't) back it. Still, whatever your direction, we applaud working to make a business in this space.