---
session_id: "1333169"
title: "One team's path to trusting AI generated code"
phase: live
last_checked: 2026-11-12T13:24:21-08:00
render: 20261112-132421-c4d6ee
---

# Links: One team's path to trusting AI generated code

## Speaker

**Ankit Jain**, Founder and CEO, Aviator

- Site: [Ankit Jain, Author at Aviator Blog](https://www.aviator.co/blog/author/ankitjain/)
- X: [@ankitxg](https://x.com/ankitxg)
- GitHub: [jainankit](https://github.com/jainankit)

## Company

**[Aviator](https://www.aviator.co/)**: "Shared context, faster reviews,
deterministic verification, and merge-to-deploy automation built for the volume
AI creates." (from the site)

## Resources

- **Blog** · [We stopped reviewing code and started verifying intent](https://tessl.io/blog/we-stopped-reviewing-code-and-started-verifying-intent)
  (Tessl, 2026-10-20). The speaker's written version of this talk: four times
  the pull requests, intent instead of diff review, review comments mined into
  invariants.
- **Blog** · [How Verify Checks Code: Semantic Analysis, Runtime Previews, and Why It’s Not Just Another AI Review Tool](https://www.aviator.co/blog/how-verify-checks-code-semantic-analysis-runtime-previews-and-why-its-not-just-another-ai-review-tool/)
  (Aviator, 2026-07-21). The verification step the talk's Verify section
  describes.
- **Product** · [Verify | Aviator Documentation](https://docs.aviator.co/verify).
  The intent-and-acceptance-criteria workflow the talk walks through.
- **Product** · [Invariants | Aviator Documentation](https://docs.aviator.co/verify/concepts/invariants).
  Where the rules distilled from review comments live ("Now these become your
  invariants.").

## Gaps

- LinkedIn (`linkedin.com/in/ankitjaindce`, from the roster) answered 999 with
  no page title naming him, so it is not corroborated and is left out.
- No official recording or slides found yet. The dossier rechecks every 6 hours
  during the event.