AVP
I like the direction here. Git is the backbone of software development, but it assumes a human rhythm. Agents don't care about clean commit messages or careful merge requests. They just churn out diffs. So watching someone build a version control system that treats the agent as the primary user feels like the right kind of problem to solve right now.
The open source part matters too. If AVP wants to become the standard for agent-native versioning, it needs to earn trust in a space where teams are already nervous about AI writing code they don't fully understand. A closed tool would struggle. Opening it up lets the community poke at the merge logic, the conflict resolution, the rollback mechanics, and that's how you build something people actually rely on.
What I'd want to know next is how it handles the human-in-the-loop moments. Agents can move fast, but someone still needs to review what lands in production. Does AVP give humans a clean way to audit agent changes, or does it just optimize for machine speed and leave us scrambling? That balance will decide whether it's a niche experiment or something that changes how teams ship software.