Sevenoir changed form several times. One problem kept surviving: physical things move, context fragments, responsibility changes, and their identity and history should not disappear between systems.
A change of hands should not mean a loss of context.
An item can be found in one building, logged at another desk and returned by someone who never saw it arrive. Each person needs a clear account of what the item is, where it has been and who is responsible for the next step.
Sevenoir is being built around that continuity. The record should stay with the item through a change of desk, a change of shift and the moment it is returned. No one should have to reconstruct the whole story simply because responsibility moved.
University recovery is the starting point. The larger ambition is a shared way for institutions to preserve identity and history when physical belongings move between them.
Global ambition means nothing without precise execution.
The road to Sevenoir
Sevenoir began with a sticker. The idea grew to include a token, a proposed blockchain and an unusual way of paying for access. There was a team, then a period of continuing without it. Aviation brought a different problem into focus: what happens to the record when responsibility changes hands? The current product came out of that sequence, not a straight line drawn in advance.
The first idea was practical: give a belonging a QR code and an NFC connection so that a stranger who found it had a way to help. They should not need to know the owner or install the same app.
The sticker was a small object, but it opened a larger question. What information should remain connected to a belonging as it moves? The idea expanded from helping someone make contact to giving the object a record that could last beyond a single interaction.
Blockchain became part of that exploration. The attraction was an identity that did not depend entirely on one company's database. The ambition eventually reached a proposed Layer 1 of our own and a broader idea of an identity layer for physical assets.
That architecture was larger than the first product needed. It raised questions about what was technically possible before the more immediate question had been settled: what would make the recovery of an ordinary belonging meaningfully better? The lasting-record idea stayed. The proposed protocol did not become the current product.
One of the early experiments was called Hold-to-Use. Instead of paying a recurring subscription, a user would hold a minimum balance of Sevenoir's token to access the service. The balance would remain theirs. If they withdrew it below the required level, access would pause.
It was an attempt to separate access from spending the balance. It also meant that using a recovery service would involve holding a token. That trade-off is part of Sevenoir's history. The company is now being developed around institutional software, not token-based access.
Hold minimum token balance → Service access
Withdraw below threshold → Access pauses
Sevenoir was not always a solo project. There was an early team, and we later went our separate ways. I continued with the company. That chapter belongs in the story, even though the way the work is organized has changed.
The early research record includes 386 survey responses and 27 interviews. It belongs to those earlier product questions, not a claim that the current university workflow already has buyers. Conversations and research helped make the problem more specific as the idea evolved.
Lost-and-found operations at GYD made the handoff problem concrete. The aviation version of Sevenoir focused on baggage custody, evidence and disputed responsibility. The work moved into handlers, claims and the systems already used to track what had happened.
That version took time to understand and explain. Stepping back meant letting go of an approach that had already shaped the product and its presentation. The useful part was what it revealed about the handoff itself: a record can exist, and responsibility can still become unclear.
Across the different versions, the same need kept returning. An item arrives. Someone takes responsibility. It moves to another person or place. A claim is checked, and the item is released or returned. The history should not start over each time.
That is the basis of Sevenoir today. University workflows are the first setting for building and testing it. The ambition remains broader, but it begins with a product people can use to complete an actual return.
Sevenoir is built and led by Ruhlan Jafarli, across product direction, research, design and the development of the company.
What should exist, and why.
Talk to operators. Observe the workflow. Kill weak assumptions.
Turn the thesis into something testable.
Decide what deserves more time, capital, and people.
Sevenoir is founder-led today. Product direction, field discovery, system design and validation are led directly by Ruhlan.
Founder of Sevenoir, with education and experience spanning business management, innovation, and entrepreneurship across the UK, Germany, and the U.S. He leads product direction, research, design, validation, and company building.
A factual record of contribution from an earlier chapter of the company.
Stuart provided strategic guidance during Sevenoir's early formation, particularly around fundraising readiness, founder execution, and go-to-market. His contribution belongs to an earlier chapter of the company; he is not involved in Sevenoir's current operation.