Core Concepts

RKVST Core Concepts


A Tenancy is an Organization’s private area within RKVST, containing Asset and Event data. The user who created the Tenancy is the Root User and has full administrative control over everything in that tenancy. A Root User can also create granular Access Policies which allow data from their Tenancy to be shared to other Tenancies; for example, Organization A would share Asset data from their Tenancy to Organization B’s Tenancy.

Root Users may invite other user accounts into their Tenancy. The invited user needs to have signed up for RKVST with the same email address as the invite, they will then be added to the tenancy as a Non-Root User. Non-Root Users start off with no permissions but can be given specific permissions (including being upgraded to a Root User) by any existing Root User in that Tenancy.


Assets are central to RKVST. Each Asset Record represents a thing; this could be a physical object, a smart device, or even a business process.

An RKVST Asset has a collection of attributes that describes its current state and a complete life history of Events that brought it to that state. RKVST Asset attributes track anything deemed important. For example, a Shipping Container as an asset might have the attributes of Height, Width and Depth, and have a handling history of movements through ports.

Each Asset has a fixed identity across all stakeholders, ensuring that all relevant parties are collaborating on the same object and see the same history of the Asset at any given time when shared through Access Policies.


Events are things that happen during an Asset’s lifecycle. Each Event Record contributes to the ‘Golden Thread’ of supply chain evidence by enriching the Asset’s history. Events can be used to add or update Asset information if they change the Asset’s state, but they also have their own attributes to add process detail and rich evidence.

Events can never be deleted or modified. Events provide details on Asset attributes, such as updating the weight of a shipment, and/or details about the event itself, such as a recording a shipment inspection.

Access Policies

Sharing the right amount of information with your value chain partners is critical to creating a trustworthy shared history for any Asset. It is important that every participant be able to see and contribute to the management of those Assets without compromising security and private information. To ensure stakeholders can access only the Assets and attributes relevant to them, transactions are private by default. A Root User may share as much or as little access to Assets as the needs of the value chain partners dictate through Access Policies.

An Attribute-Based Access Control (ABAC) policy is used to share with Non-Root Users within a Tenancy. An Organization-Based Access Control (OBAC) policy is used to share with the Root Users of another Tenancy. The Root User of the external Tenancy may then use an ABAC policy to grant permissions to the relevant Non-Root Users of their Tenancy. In both cases, attribute-specific read and write access can be granted using fine-grained controls.

The Golden Thread

Using the four concepts of Tenancy, Assets, Events and Access Policies it is possible to create a Golden Thread of evidence that underpins supply chain integrity, transparencey and trust for all relevant stakeholders.

The Golden Thread

Edit this page on GitHub