Universal eligibility. Unequal results.
Now we have to get less philosophical.
Because saying “everyone should have an opportunity to own things” is easy.
Actually designing a company around that idea is harder.
So let’s build one.
What is a Stoin?
In the broadest sense, a Stoin is a digital container for value.
That value might represent ownership in a company.
It might represent an interest in a physical asset.
It could eventually represent rights connected to intellectual property, information, reputation, or another economically useful resource.
A Stoin also carries rules.
Who can claim it?
Can it be transferred?
What rights come with it?
Does it vote?
Does it vest?
What created it?
Who contributed to it?
A dollar mostly tells you one thing:
I am worth a dollar.
A Stoin could potentially tell you much more:
Here is the value I represent, why it exists, the rights attached to it, and the rules governing it.
That’s the beginning.
Four tranches
Imagine a new Stoin company.
For simplicity, let’s divide its initial ownership into four tranches:
| Ownership class | Illustrative share |
|---|---|
| Investors | 30% |
| Workers / Builders | 30% |
| Users | 30% |
| Network / Overhead | 10% |
Those percentages are examples, not commandments.
A capital-intensive real estate project might need substantially more investor ownership.
A software network built primarily through user participation might weight users differently.
The important idea is not 30/30/30/10.
The important idea is that the ownership classes exist by design.
Before the company becomes valuable.
The investor tranche
This is familiar.
Investors risk capital.
They receive ownership.
If the business fails, they may lose it.
If it succeeds, they participate in the upside.
Stoinism doesn’t attack that mechanism.
It recognizes it as legitimate.
The worker tranche
Now add the builders.
Perhaps a portion is earned as compensation.
Perhaps some vests over time.
Perhaps exceptional contributions earn additional ownership.
Perhaps an employee can contribute both labor and capital and participate in two different tranches.
The point is that a worker doesn’t have to choose between:
I get paid
and
I own the thing I’m building.
They can do both.
The user tranche
This is where the model gets more unusual.
A customer can also create value.
Purchases matter.
But so can referrals.
Useful feedback.
Product testing.
Knowledge contributions.
Community support.
Creating content.
Improving the network.
Perhaps even allowing a privacy-preserving synthetic to contribute useful knowledge derived from that person’s experience.
Different contributions can earn different amounts.
The system doesn’t need to pretend every click is worth something.
But where real value is created, the architecture can recognize it.
The network tranche
Finally, there is a category for the infrastructure and shared resources that make the system possible.
The network itself may need maintenance.
Security.
Compute.
Common services.
Research.
Governance.
Insurance.
Perhaps public-good projects that benefit every participant.
Rather than pretending overhead doesn’t exist, the system can explicitly fund it.
The network tranche becomes the mechanism through which the ecosystem invests in itself.
People aren’t trapped in one box
This is important.
These aren’t castes.
I’m not forever a worker because I joined the company as an employee.
I might invest.
I might work.
I might also be a customer.
I may contribute intellectual property.
One person can participate through multiple pathways.
What changes is our ability to record those different forms of contribution without pretending they are all identical.
Why tranches?
Because interests differ.
An investor may care primarily about financial return.
A worker may care about compensation, working conditions, and long-term enterprise value.
A user may care about price, product quality, privacy, and durability.
The network may care about resilience and long-term ecosystem health.
Pretending all of those interests are identical doesn’t make them identical.
Tranches make the differences visible.
And once you can identify the different ownership communities, you can start asking the next question:
Who gets to make the decisions?
That’s where the DAO comes in.
