part one of three
field note8.07.26

The loop was never the point

A loop is a shape, and by now everybody has the shape. Run the thing twice. If the second pass knows something the first one did not, you have something worth keeping. If not, you have automation with a nicer diagram.

I have written the word loop on this site more than any other word. I built the diagrams. I named a camp on the climb after it. So let me be the one to say it: the loop was never the point.

A loop is a shape. It says the work comes back around instead of running off a cliff. That is real, it was not obvious three years ago, and I still think it is the right way to build. But a shape is not an asset. Everybody has the shape now. You can buy the shape.

The test I use now

Run the thing twice. If the second run knows something the first run did not, you have a loop worth having. If it just does the same work again a little faster, you have automation with extra steps and a nicer diagram.

Most of what gets called a loop fails that test. It runs on a schedule, it produces output, somebody reads the output, and then nothing about the system changes. The next run starts exactly where the last one started. That is a very expensive scheduled job.

The difference is not the output. It is the deposit.

what it told me01the sourcewhere it came from02the datewhen it was true03the callwho agreed or overruled04the outcomewhat happened afterthe outcome changes what it believes next
the four things that have to survive a run for it to count

The deposit

Every time one of my systems makes a call, four things get written down and kept. Where the belief came from. When it was true, which is a different question from when it got written down. Whether I agreed with it or overruled it. And what actually happened afterward.

None of that is exotic. What is rare is keeping it. Almost nobody stores why the machine believed something, and almost nobody stores whether the human went along with it. That second one is the valuable half, and it is the half that gets thrown away, because disagreeing with your own agent feels like a failure instead of the most useful thing that happened all day.

The output is what the run produced. The deposit is what the next run inherits.

Why I am retiring my own word

I am not walking anything back. Building loops is the start, closing them is the unlock and The Loop Is the Product both still hold, and the mechanism on this site has not changed at all. What changed is which part I put in front.

Loop is a mechanism word. It belongs in the engineering conversation, and it stays there. What goes in front is what the mechanism produces: a record that is worth more every time it runs. That is the part I would actually fight somebody over.

The next two pieces are the argument. First, why evidence compounds and intelligence does not. Then, what happens when the record gets good enough that the system starts acting on it.

// working on something ghost should see?

Get in touch.

Share what you are building, and we can see if there is an opportunity to discuss further.

dave@rslvd.ai
Ghost / private build / running in the field / public home coming soon...
© 2026 RSLVD, LLCOperate with full control.