Raidiam
Book a working session

Films · Journey 1

We already have a catalogue and an approval process. Do we replace them?

Film: Find and trust Use case: Keep your catalogue. Govern the agent. 2 min 11 s 10 chapters Captions in English

Open the film file

Chapters 10

Transcript, read from the captions

Hello

Hi, I'm Ralph from Raidiam. You already approve the software your business runs, so let me show you how another organisation can trust it too.

Approved here. Unknown there.

Your organisation reviewed a piece of software, approved it and let it run. Now it needs to work with a service outside your organisation. The organisation on the other side has never seen it. So what does your approval mean over there?

Keep what already works

Before I answer that, here is what stays the same. Your catalogue decides what your organisation approves and runs. Raidiam Connect does not replace it. The new problem begins when that software must be understood somewhere else.

The agent can ask

The software can keep a record of what it wants. But asking for authority is not the same as having it. An appropriate authority governs what the agent actually holds. It removed one permission this agent asked for. It added another.

This is how the customer integrates

Let me show you that model running. This is an enterprise catalogue. It is not Raidiam Connect. We built it to stand in for the one you already run. When you are ready, that system calls Raidiam's APIs.

Now show Raidiam Connect

This is where Raidiam Connect comes in. Connect is the trust controller behind that call. With it, you govern the agent's identity and authority. Connect lets other organisations check the relationships behind them.

Now change perspective

Now look from the other side. This organisation holds no record of the agent. It does not have to take the agent's word. It can check those relationships for itself.

And this is real

It follows the signed relationships behind the identity to an authority it already trusts. This is not a drawing. This is Connect checking that path on the running system. You can inspect the signed statements and verify them yourself. The two parties did not need to meet first.

The payoff

Your approval stayed yours. Their decision stays theirs. What changed is what could travel between them. A governed identity. Bounded authority. And the relationships that let another party see why to trust them. So each party you add needs no bilateral integration of its own. We have built this for national ecosystems in Brazil, the UAE, Australia and New Zealand. What is new is that the pattern is now an open standard.

Thanks for watching

So you can keep the process you have, and let others resolve what you approved. If you'd like to see this running for your own business, please do get in touch.

The use case

Keep your catalogue. Govern the agent.

Find the agent, read the authority behind it, and see what it is allowed to do before you let it in.

Open the use case Read the evidence