By the time I saw the third verification on the same profile...
I stopped assuming it was an edge case.
Saudi first.
Then UAE.
Then Qatar.
Same person.
Same credentials.
Three full processes.
No connection between them.
I checked the first one again.
Still valid.
Issuer active.
Schema intact.
Nothing had expired.
Nothing had changed.
So I moved it into a UAE flow.
It didn’t resolve.
Not rejected.
Just... nothing.
Ran it again.
Same result.
That’s when it started to feel consistent.
Not an error.
A pattern.
I tried another profile.
Kuwait to Bahrain.
Same behavior.
Verified already.
Still starts from zero.
I kept going.
Saudi to UAE.
UAE to Qatar.
Every crossing.
Same thing.
The credential exists.
The receiving system can’t read it.
Nothing fails.
The process just restarts.
That’s when it settled.
Mobility gap.
Not movement.
Resolution.
The workforce crosses borders.
The credential doesn’t.
And everything downstream behaves like it never existed.
I started noticing where this actually shows up.
First hire.
Already verified somewhere else.
Still runs full onboarding again.
Doctor relocation.
Fully licensed at source.
Still reprocessed from scratch.
Investor access.
Identity already proven.
Still blocked until it’s proven again.
Same inputs.
Same checks.
Different boundary.
Every time.
Nothing breaks.
The system just ignores what it can’t resolve.
Nafath works.
UAE digital ID works.
Each system is internally consistent.
They just don’t resolve each other.
Each one sovereign.
None of them shared.
That’s where it shifts.
Because the region is already moving.
People.
Capital.
Access.
But the verification layer resets at the exact point movement happens.
$SIGN only matters if a credential issued under one schema resolves the same way in another system without being re-proven...
not just verified again under a different process.
Because right now...
movement is real.
Verification is local.
And every boundary quietly turns a verified identity...
back into an unverified one.
So the question I keep coming back to is this.
If a system can’t resolve a credential that already exists...
is it actually verifying anything...
or just repeating it?