Imprint is a way to measure the changes we do in the World. The real changes based on events happen because of us.

Web Tree inside uses Imprint as a reward system. People with higher Imprint get priority over people with lower for getting access to limited resources. And Circles get more Impact for providing goods to people or Circles with higher Imprint.

Limited resources and limitless wants are the basic economic problems.

In the Web Tree, we split this one problem into two:

• Access limitation

• Reward system

Access limitation

When you create some goods and there is no way to give them to everyone who wants it, you need to decide who will get them and who don't.

In the financial system, the "winning strategy" is in increasing the price until the number of people who want the goods will be equal to your "capacity".

In Web Tree, we can use a similar strategy for limitation - set a minimum Imprint level. With one key difference - the only reason to create an access limitation is your limited capacity. There is no sense to set up any limitations if you have more "supply" than "demand" from people. Or if we're talking about intellectual property and there is no cost for you to provide access to any number of people.

Pressure

Pressure is the second way for limitation in Web Tree. It's a unique concept in Web Tree.

Each Circle defines the rules of pressure definition. But here is the main "formula": "Circle capacity" divided by "how hard to serve a concrete person in a concrete moment".

Let's show a couple of examples:

• We have a restaurant and it can serve a few people per hour. If the restaurant is empty, the pressure for people who eat there is pretty low. If there is a full restaurant and a queue outside, the pressure is higher. If you order a lot of complex dishes the pressure is higher than you order a cup of coffee. Another thing that is affecting the amount of Pressure is the uniqueness of the food we order. If there is more food accessible than people required, the pressure could be zero, because the food can just go bad if we won't eat it now. But if we want to eat truffles and marble beef, we should expect to get high Pressure for dinner.

• We have a few servers which have some memory, CPU, and disk space. And if you want to use it, the pressure every person gets depends on current usage. If the server will be switched on regardless of our usage and anyone else uses it for the moment you need it, you get no Pressure for the usage. But if at the moment you're using the server resources a lot of other people use it as well and, for example, CPU used on 100%, the amount of Pressure you get starts to rise.

In the cases when our supply is lower than demand, we start to see a queue for getting access to goods. The most reasonable for the Circle will be ordering the queue by higher Imprint to maximize the Circle's reward.

Reward system

Reward in Web Tree called Impact. In the same way as pressure, Impact distribution can be defined by each Circle. A Circle can define which actions give an Impact, how it will be calculated, and what you will get for the Impact inside the Circle. 

Imprint Circle

Imprint Circle, like all Circles in the Web Tree, has its own internal Impact and Pressure level.

Imprint determines Impact and Pressure between all Circles and people in the Web Tree and aggregates them all in a single value per Circle and person.

When Imprint calculates the Imprint of a Circle then it will distribute the Imprint between people and Sub-Circles. And make additional rewards to parent Circles.

The rules about the size and percentage of the rewards are dynamic and can be changed in the future. So, if someone will find a bug and start to abuse the system, it can bring a profit in short term but the future loss will be much bigger.