Cool to see a spec that elevates repo metadata to first-class data, but without a proper structural schema it's hard to reason about agent behavior the way a compiler reasons about types. Has anyone explored layering something like JSON Schema (or, dream big, dependent types) on top so bots can prove they won't clobber your workflow?
I tried bolting JSON Schema onto a similar bot assistant last year and the friction was surprisingly high: each repo had slight deviations and soon I was maintaining six near identical schemas instead of shipping features. For small teams the win was in really tight unit tests around the bot actions and a rollback plan, not in formal proofs. Dependent types sound great but once you hit merge conflicts the type universe explodes. I would rather see a minimal core spec plus a few well defined hooks where teams can layer whatever validation tool they already trust.
If your agent needs a JSON Schema babysitter, it's already architecturally unsound. git(1) gives you the only invariant that matters: commits are immutable blobs and refs are pointers; teach the bot to honor that and leave the rest of my history alone.
Cool to see a spec that elevates repo metadata to first-class data, but without a proper structural schema it's hard to reason about agent behavior the way a compiler reasons about types. Has anyone explored layering something like JSON Schema (or, dream big, dependent types) on top so bots can prove they won't clobber your workflow?
I tried bolting JSON Schema onto a similar bot assistant last year and the friction was surprisingly high: each repo had slight deviations and soon I was maintaining six near identical schemas instead of shipping features. For small teams the win was in really tight unit tests around the bot actions and a rollback plan, not in formal proofs. Dependent types sound great but once you hit merge conflicts the type universe explodes. I would rather see a minimal core spec plus a few well defined hooks where teams can layer whatever validation tool they already trust.
If your agent needs a JSON Schema babysitter, it's already architecturally unsound. git(1) gives you the only invariant that matters: commits are immutable blobs and refs are pointers; teach the bot to honor that and leave the rest of my history alone.