• Home
  • Technology
  • Gaming
  • Entertainment
  • World & Business
  • Science
  • Sports
  • AI
HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • Home
    • Technology
    • Gaming
    • Entertainment
    • World & Business
    • Science
    • Sports
    • AI
    AI
    Report

    Bend 2 trial reportedly uncovered four false laws proposed by an AI agent

    A team testing Bend 2 says proving roughly 20 agent-proposed laws exposed counterexamples and changed its implementation.

    TA
    SU
    2 Sources, ,

    TLDR

    A team testing Bend 2 on real projects says an AI agent proposed roughly 20 laws for one project, but attempts to prove them showed four were false. The counterexamples led the team to revise its implementation. It says it also rewrote one correctness-critical part of a TypeScript project in Bend, compiled it to JavaScript and left the rest of the app alone. The team claims that part is now bug-free and four times faster, but says proving every part of an app can cost too much time and too many tokens.

    Combined views

    3.7K

    2 Sources, first seen 17h ago

    Combined views

    3.7K

    2 Sources, first seen 17h ago

    30 likes
    17h ago
    first seen 17h ago
    30 likes
    3 comments
    32 saves
    9 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Featured Source
    3 comments
    32 saves
    9 reposts

    2 Sources

    @superlinear_fmWe spent the last week building with @VictorTaelin’s @bendlang on real projects, and came away pretty impressed. Some takeaways: 1. Bend changes what the human needs to pay attention to. Instead of reviewing every implementation detail, you can spend more time getting the intent and laws right, then let the agent figure out the implementation and proof. You still need to make sure the laws actually express what you want. 2. Agents make formal verification much more practical. The annoying part used to be writing and maintaining the proofs. Now the agent can do that work. Basically: you don’t need deep math knowledge to start anymore; you can work through the problem in English and use the model to find the algebra/laws. 3. The proof is useful feedback for the agent, not just a safety certificate at the end. This was probably the most interesting thing we actually observed. In one of our projects using Bend, the agent proposed roughly 20 laws. When we made it prove all of them, 4 of the original laws were actually false. The proving process found counterexamples, forced the edge cases to be stated correctly, and changed the implementation. 4. Bend being a real general-purpose programming language with formal verification built-in matters a lot. Before Bend 2 existed, you might have your real program in Rust/TypeScript and separately model it in Lean/TLA+. Then you have to trust that the thing you proved still matches the real program. Bend lets the code you execute also be the thing whose laws you prove. No more worrying about the 'model of your code' drifting from the real code. 5. You probably shouldn’t formally prove everything. This was an important conclusion for us. Use it where correctness really matters, where the logic has a clear mathematical shape, where agents keep tripping up, or where there's a core that will evolve a lot. Proving every trivial piece of an app can be overkill and costs more tokens/time. 6. You don’t have to rewrite your whole app in Bend to use it. It's easy to get started. We took one correctness-critical part of one of our existing TypeScript projects, rewrote just that slice in Bend, compiled it to JavaScript, and left the rest of the application alone. It is now 100% bug-free (actually proven!) and 4x faster. We recorded our whole journey trying out Bend 2: 00:00 A new verification layer 00:47 Machine-checkable guardrails 10:11 Types, tests, and proofs 17:49 Find a problem worth proving 20:30 How algebraic laws enable optimization 25:03 Find the algebra 30:38 From exploration to self-contained spec 32:20 Laws that reflect your intent 37:33 Proofs and false laws 42:12 Bend in one part of an existing project 45:55 Costs and how much to prove17h
    @VictorTaelinRT @superlinear_fm: We spent the last week building with @VictorTaelin’s @bendlang on real projects, and came away pretty impressed. Some…5h

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Today's Rank

    —

    Not ranked yet

    Today's Rank

    —

    Not ranked yet

    2 Sources

    @superlinear_fmWe spent the last week building with @VictorTaelin’s @bendlang on real projects, and came away pretty impressed. Some takeaways: 1. Bend changes what the human needs to pay attention to. Instead of reviewing every implementation detail, you can spend more time getting the intent and laws right, then let the agent figure out the implementation and proof. You still need to make sure the laws actually express what you want. 2. Agents make formal verification much more practical. The annoying part used to be writing and maintaining the proofs. Now the agent can do that work. Basically: you don’t need deep math knowledge to start anymore; you can work through the problem in English and use the model to find the algebra/laws. 3. The proof is useful feedback for the agent, not just a safety certificate at the end. This was probably the most interesting thing we actually observed. In one of our projects using Bend, the agent proposed roughly 20 laws. When we made it prove all of them, 4 of the original laws were actually false. The proving process found counterexamples, forced the edge cases to be stated correctly, and changed the implementation. 4. Bend being a real general-purpose programming language with formal verification built-in matters a lot. Before Bend 2 existed, you might have your real program in Rust/TypeScript and separately model it in Lean/TLA+. Then you have to trust that the thing you proved still matches the real program. Bend lets the code you execute also be the thing whose laws you prove. No more worrying about the 'model of your code' drifting from the real code. 5. You probably shouldn’t formally prove everything. This was an important conclusion for us. Use it where correctness really matters, where the logic has a clear mathematical shape, where agents keep tripping up, or where there's a core that will evolve a lot. Proving every trivial piece of an app can be overkill and costs more tokens/time. 6. You don’t have to rewrite your whole app in Bend to use it. It's easy to get started. We took one correctness-critical part of one of our existing TypeScript projects, rewrote just that slice in Bend, compiled it to JavaScript, and left the rest of the application alone. It is now 100% bug-free (actually proven!) and 4x faster. We recorded our whole journey trying out Bend 2: 00:00 A new verification layer 00:47 Machine-checkable guardrails 10:11 Types, tests, and proofs 17:49 Find a problem worth proving 20:30 How algebraic laws enable optimization 25:03 Find the algebra 30:38 From exploration to self-contained spec 32:20 Laws that reflect your intent 37:33 Proofs and false laws 42:12 Bend in one part of an existing project 45:55 Costs and how much to prove17h
    @VictorTaelinRT @superlinear_fm: We spent the last week building with @VictorTaelin’s @bendlang on real projects, and came away pretty impressed. Some…5h