Use case 02
Resolved, not registered.
The platform trusts a federation, not a list of clients. Every agent the federation governs arrives already described.
The agent
Records Assistant
Known to its authority, not to this platform.
Step 1First call
Step 2Resolves the chain
Signed statements
The authority
Tarnbrook Financial Group
Governs the agent and vouches for it.
The API platform
Reference implementationClient records
No record for this agent.
Step 3Built from the answer
authorization_details_types- records.readrecords.annotatetransfer.initiatetransfer.status
token_endpoint_auth_method- private_key_jwt
Tarnbrook federation anchor key, pinned in configuration
Step 4A token for the types it asks for
Step 5The agent presents the token
The resource
The records resource
Acts within the token's types.
No registration step
Nobody registers the agent on this platform first.
One federation recognised
Pin its anchor once, and every agent it governs resolves.
Bounded at issue
Never wider than the ceiling its authority registered.
A person still decides
Moving value waits on a person's grant.
Watch
Resolved, not registered
Which of your platforms would resolve first, and what would it pin?
Ninety minutes, on the shape of your estate: which systems resolve first, which anchor each pins, and which key each party holds.