Thread

Bend – a language that blocks AI mistakes via proof and runs on GPUs

616 points · 327 comments · nicolas-siplis

RomanKornev · 1789681302 · focus · HN ↗
> LAWS.bend
I like the law idea, but what i found they end up doing is they just modify the law itself to fit the new feature they are working on, which defeats the point.
Which means some laws needs to be frozen. But not all laws, otherwise you can't add or modify anything. So the judgement is still on the human part, and we're back to meatbags being the bottleneck.
I've seen some success adding these proof-like checks to CI every time agents do something irrational. I definitely think it should be part of every codebase.
There's also <a href="https://code-contracts.cc/" rel="nofollow">https://code-contracts.cc/ which co-locates code and proofs together.
1. LightMachine · 1789683448 · focus · HN ↗
  Yeah, you want to at least read what the AI is putting on LAWS.bend. It is substantially smaller than the codebase. Ultimately LAWS.bend makes you need to read astronomically less code. Not zero code.
  1. destring · 1789723557 · focus · HN ↗
    I definitely think that's the approach going forward. We need to invest in things that increase the leverage of human attention on code verification. I've been thinking for a while that current unit tests frameworks don't have that good of a ratio
    maksDanylenko · 1790274168 · focus · HN ↗
    [dead]

Unofficial Hacker News client; not affiliated with Y Combinator.