You keep other people's gold.
Your clients are starting to ask what software could do with metal that today only sits. The design would let them delegate without your custody, your licence or your books changing.
Phi Klobos Technologies Ltd is a research and development company in the Dubai International Financial Centre.
This work is not addressed to the public. It is written for a small number of institutions and people, and each of them meets it from a different side.
Your clients are starting to ask what software could do with metal that today only sits. The design would let them delegate without your custody, your licence or your books changing.
Your unit is held more than it is used. The design is meant to sit on top of an existing gold token and give it a use beyond holding.
Gold on your books is collateral that moves at the speed of people. The design describes how an agent could post it, release it or exchange it in one step, within limits your risk function sets.
You want software to act for you and never to be able to act against you. A mandate with a named beneficiary is the design's answer to that.
Your agents settle in a unit that someone issues. The research asks what changes when the unit is a weight of metal.
You would rather read a specification and run a prototype than sit through a pitch. Both exist, and a conversation can start from them.
If one of these is you, write.
info@phiklobos.comThe company's research programme concerns settlement architecture: what a settlement layer would require in order to be sovereign-neutral rather than domiciled in any national unit of account, to be denominated in physical units rather than in fiat, and to be operable by autonomous software agents under structurally constrained delegation.
The programme is conducted as design research. What follows describes a design and the software written to prove it.
Klōbos is the Greek word for cage. In this design the cage is a mandate: four limits, signed once by the person who owns the gold.
A holder of vaulted gold would sign a mandate that says how much, until when, with whom, and who receives the result.
A software agent could then carry out an operation in a single step, a treasury move or a pledge of collateral, without coming back to ask.
A request beyond any of the four limits would simply not execute. There would be nothing for the agent to override.
Whatever is received would go to the beneficiary named in the mandate, and never to the agent.
As of
Ten chapters and an annex.
The settlement step, with automated tests and formal checks.
In operation.
A first analysis by an external adviser.
Registered in the DIFC under an Innovation Licence.
The specification is larger than the part that has been built. Further components are designed and reviewed, ready for whoever takes the work forward.
Public writing from the company’s research programme. Each note argues one structural question in settlement architecture at the level of design criteria — what a settlement layer would require, not what any instrument does. The notes are published on LinkedIn under the author’s personal profile; every one of them is listed here.