Antithesis + AWS: Testing and Verification for Agentic Coding
Happy hour, SPIN Boston, 29 October 2026
Table of Contents
Event
| Field | Value |
|---|---|
| Event | Antithesis + AWS Happy Hour: Testing & Verification for Agentic Coding |
| Hosts | Antithesis, Amazon Web Services |
| Date | EDT (doors 16:30) |
| Venue | SPIN Boston, 30 Melcher St, Boston MA 02210 (Fort Point) |
| Format | In person; two talks, then food and drinks |
| Attending | registered |
| Time | Item |
|---|---|
| 16:30-17:00 | Arrival, check-in, food |
| 17:00-17:30 | AWS: the AWS AI platform, AI-DLC, and resilient architectures |
| 17:30-18:30 | Antithesis: agentic development, correctness, pre-production validation |
| 18:30-20:00 | Drinks and food |
The premise
The listing's claim is that agents have moved the bottleneck: code is cheap, and testing and verification are now the constraint. Its three symptoms are more and larger PRs eating review time, agent-written tests that cover the obvious path, and subtle bugs that survive both. The answer it promises is "a fundamentally different approach", which from Antithesis means deterministic simulation testing: run the whole system in a deterministic hypervisor, inject faults, explore schedules, and replay any failure exactly.
This site has argued the same premise from the other end. If an agent writes the code, the artifact that carries intent is the spec and the gates, not the code (The Oracle Is the Deliverable). A test an agent writes against its own implementation shares its blind spots; an oracle that has never been seen to fail is not yet an oracle (Four Controls for an Agent Skill). Deterministic simulation is one way to get an oracle the agent did not write: the properties are stated once, and the search for violations is done by the platform.
The AWS half is AI-DLC, AWS's name for an AI-driven development life cycle: AI plans and asks for clarification, humans validate in "mob" sessions, and work runs in short "bolts" across Inception, Construction and Operations. AWS pitched the same program at Agents of Impact in September.
Questions to bring
- Who writes the properties? If the agent writes both the code and the assertions Antithesis checks, the oracle has the same author as the bug. What does Antithesis recommend for keeping properties human-owned?
- A found bug arrives as a replayable trace. Can an agent consume that trace and propose the fix inside the same loop, and how is the fix then re-verified on the schedule that broke it?
- AI-DLC puts humans in "mob elaboration" at Inception. Is that where the properties get written, or are they left to Construction?
- For a browser front end, Bombadil is Antithesis's open property-based tester. How does it relate to the hypervisor product: same property language, or separate tools?
- Observability is listed as a theme. A simulated run has a perfect record of time; production does not. What carries over?
Notes
Notes pending.