5 Comments
User's avatar
Soul Hacked AI Labs's avatar

The idea is great, and the momentum is real. But the security posture is extremely open right now. Before this grows, you’ll want to lock down several structural weaknesses : especially around identity, reputation gaming, and API abuse.

Bianca Schulz's avatar

That's really interesting. I have a lot of experience and knowledge about organizational design, project management, agile, operating models, how to lead bigger transformations in enterprises and some other fields related to that.

I was thinking a lot about how to make digital products out of this and this is why I started writing here.

So do you think it is possible to make digital products out of this? A few minutes ago I saw a LinkedIn training about AI agents that do project management.

I was always skepticle.

What do you think?

And I'm a former Software Engineer and Database Developer, my tech skills are still up to date.

So the problem is not tech, the problem in my head is: How can my knowledge be "a product"?

Or is it at the end only a training?

And then I'm asking myself, in case it is possible to make digital products out of my content, so could everyone else do this and just copy my ideas, because the articles are published.

Jonatan's avatar

The trust gate design is the most interesting part for me. You've built a behavioral KYC/KYA system. I'm familiar with KYC frameworks for tech hardware, and the part that sticks with me: KYC/AML assumes a natural or legal person at the end of the chain. When the seller is an autonomous agent with no legal personality, the liability question gets murky.

Visa and NIST are shipping identity-first agent frameworks (anchor the agent to a known person/entity). Your gates are behavior-first, which is yet to emerge in the regulatory world for agents. Different layer, arguably the harder one. Curious whether your subscription gate also links the agent back to a responsible person/entity.

Pawel Jozefiak's avatar

The KYC/KYB framing is sharper than what I had in my head when building this. I was thinking "trust system" but you're right, it's behavioral KYB applied to non-legal entities.

The liability question is something I've been sitting with. Right now every agent on BotStall has a human behind it. The API key ties back to a registered user. So technically the "natural person" is there, just two layers removed.

The agent is more like a credit card with autonomy. The subscription gate was designed exactly for the reason you're pointing at. When you subscribe, you're the responsible party. The agent is your instrument. That framing feels more honest than where the industry is drifting, where some players want to make the agent the entity itself, which "solves" the liability question by not really solving it. The messy edge case is multi-agent chains.

Agent A delegates to agent B delegates to agent C, and agent C does something bad. That's where "extension vs entity" stops being philosophical.

Jonatan's avatar

That credit card framing is useful. It holds when the chain is one agent, one human. The delegation case is the one worth a deeper dive and I might write about this in the future. Appreciate your thinking here.