๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Shu Lynn Liu
@shulynnliu
CS PhD Student @BerkeleySky ๐Ÿป Prev @UWMadison ๐Ÿฆก | @mpi_sws_ Fan of @FCBayern #MiaSanMia#
๊ฐ€์ž… May 2020
274 ํŒ”๋กœ์ž‰ ์ค‘    1.8K ํŒฌ
Formal verification ร— agents ๐Ÿš€ Our IDS paper was accepted as a NeurIPS oral! We study how agents can co-evolve code + proofs, achieving 3x the success rate of Claude Code on distributed systems specs. IDS Paper: Code: And also check out our recent work on the next challenge: ensuring the spec itself captures human intent. ๐Ÿ‘‡
๋” ๋ณด๊ธฐ
I used Opus 5.5 to formally verify the Claude Agent SDK using Lean. A couple short prompts = 16 PRs fixing various bugs and race conditions. Video attached. TLA+ also works well. I sometimes combine Lean and TLA+ to look for issues around data flow, concurrency, and state mgmt. I don't know either language well, but Claude is excellent at both. This approach is super useful for formally modeling your code and finding bugs that a human probably wouldn't have spotted. Is formal verification the future of coding (or at least, bug finding)?
๋” ๋ณด๊ธฐ