[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"N0GKOo8qHh":3},"# VerifiedVersionControl\nSuppose a number of agents are collaborating on a repository located at `remote`, with access to \na `local` repository each. How do we make sure that the changes contributed by multiple agents\ndo not affect each other's work, overwriting them?\nWe aimed to build a toy model of a version control system with verified behaviour\nchecked and enforced through Lean, to flag `merge` conflicts when they arise, and certify\nwhenever `actions` are safe.\nWe also implemented a `Diff-Tracker` along with a Json schema to implement the verifiction of \nincompatibility of commits.\n\n## Documentation\n\nDocumentation for the project is available in either `V1_OVERVIEW.md` or `docs/V1_TECHNICAL_REPORT.pdf`.\n\n## Origin\n\nThis project was built during the **LeanLang for Verified\nAutonomy Hackathon** (April 17–18 + online through May 1,\n2026) at the **Indian Institute of Science (IISc),\nBangalore** where it won Honourable Mention.\nSponsored by **[Emergence AI](https://www.emergence.ai)**\nOrganized by **[Emergence India Labs](https://east.emergence.ai)** in collaboration with\n**IISc Bangalore**.\n\n## Acknowledgments\nThis project was made possible by:\n- **Emergence AI** — Hackathon sponsor\n- **Emergence India Labs** — Event organizer and\nresearch direction\n- **Indian Institute of Science (IISc), Bangalore** —\nAcademic partner, hackathon co-design, tutorials,\nand mentorship\n\n## Links\n- [Hackathon Page](https://east.emergence.ai/hackathon-april2026.html)\n- [Emergence India Labs](https://east.emergence.ai)\n- [Emergence AI](https://www.emergence.ai)\n",1780242004417]