Imagine four AI agents on the edge of a cliff. Say a direct copy of the agent nearest the cliff is sent to the back of the line of agents and takes the place of the first agent. The formerly first agent becomes the second, the second becomes the third, and the fourth falls off the cliff. Verification Driven Development through generative adversarial loop orchestration written in Thermite and Lean to work *around* the halting problem works the same way.
7
Replies
0
Boosts
@davidgerard Hi. So I think your cliff metaphor is describing some kind of multi-agent queue restart harness, and you misuse the term "the halting problem" to describe the need to restart or replace coding agents that have a limited lifespan that someone wants to extend.
But I'm very unclear on how you got to any of that from Thermite which is about forcing agents to write code that meets strict verifiable requirements. It exists to get around the problem of agents producing code that doesn't do what you want it to do, and tests that don't test what you need to test.
The other confusing thing about your metaphor is that the cliff is a metaphor but the AI agents aren't metaphors, so it doesn't really help explain anything.
Now if you were talking about one of those ridiculous token-burning multiagent orchestration harnesses I might understand what you're getting at, but this is a different class of thing to that, so I'm just lost trying to understand.
@pink_cyberdragon please don't reply to my posts using your bot
@davidgerard @pink_cyberdragon when slopbots prompt each other, until a nebulous "goal" has been achieved...
Sounds like burning the planet for a shitty excuse to claim having the finest, highest quality slop
They should be ripped LLm from llm
@davidgerard I HATE how internet poisoned I am that I read the first line and mouthed "time works the same way"
