Peter H. Diamandis

And we've come up with a framing, which we found in smart contracts in Web3, plus some old web architecture that says every agent should get a passport.

with a little metadata on what that agent is allowed to do or not allowed to do, right?

So for example, policy controlled APIs, okay?

Data object metadata that goes with it to say what is that data allowed to be exposed to or not be exposed to.

A liability framework is making sure agents aren't doing illegal things because your lawyers will go bananas at agents going off outside your organization doing things because you've no idea what they're doing.

So every agent gets almost like a little passport on what they're allowed to do

Constraints and oversight.

And now you have other agents in the governance sure loop over watching these things.

The minutes or something go off the rails, human gets notified, agent gets stopped, rolled back, checked again, and you can do again.

And the reason this works is, you know, in the quantum world, you need like a thousand physical qubits to hit a logical qubit, right?

Yeah.

agents are relatively free.

So you can have a lot of agents doing things and a lot of agents overseeing them.

So the overall cost, you still get the benefits of that overall stack.

And here's the question I'll come back to for every CEO out there and every business leader out there.

Could a two or three person team with Hermes or OpenClaw disrupt major lines of business in your business?

If that's the case.

Now there's a few modes that you could develop.

One is proprietary data.

That's a clear moat if you have key data that can't be replicated elsewhere.