How developers earn
A membership, not an app store
Software is cheap to copy and hard to protect, so the design intent is that you shouldn't have to compete on locking it down. People pay one NAOMS membership. What they pay flows toward the packages they actually use. A payout tapers off over time and the package becomes part of the commons — until someone makes a real improvement to it and gets paid again for that specific improvement.
This membership split is design intent — it is not built yet
What exists today, plainly
Here is the honest state of each piece this model depends on.
Seven separate payment integrations are already wired into the ledger, so value can move in and out through real, named rails rather than a placeholder.
A working payout mechanism already shares value among the people who contributed inside a single Hive. It's real and shipped, but it operates inside one Hive at a time — it isn't yet a platform-wide split across every package someone uses.
A price list and a checkout screen already exist in the wallet. The checkout asks for value; it doesn't yet charge anything, because no payment rail is connected to it yet.
The platform-wide membership flow itself — one payment, split automatically across every package a person uses — is the team's stated design, held separate on purpose from the capital-raising flows that already exist. It is not built yet.