How it works.
What Karmyq actually is.
A toolkit. An open-source platform that lets communities design their own cooperation systems — not one model handed down, but infrastructure flexible enough to hold mutual aid, skill sharing, tool lending, local services, or any combination a community needs. The platform doesn't decide what your community values. It gives your community the means to decide for itself, and to change its mind over time.
Reputation without the performance.
On Karmyq, your worth is not a public score. There are no leaderboards, no star ratings to optimize, no anxiety about your profile falling behind someone else's. Karma moves like ambient knowledge in a village: people remember who shows up, but nobody keeps a public spreadsheet on their neighbors.
Let's be honest: it feels good to be seen helping. Platforms know this — every like, every visible score is engineered to give you that hit and keep you chasing it. Karmyq deliberately doesn't. No applause, no public count. What you get instead is slower and harder to fake: over months, the people around you come to know who you are. The hit is pleasure. Being known is joy. We're built for the second.
Design essay · ReputationThe Problem with StarsWhy we hid the metrics
The problem with scores.
Every platform that has tried to build trust through reputation has converged on the same solution: a number. One to five stars. A score out of a hundred. The number is clean, portable, instantly legible. It is also, almost immediately, the thing people start to game.
This is not a character flaw. It is a predictable response to an incentive structure. When a visible number determines how much opportunity you get, optimizing for the number becomes rational. Drivers learn which behaviors produce five-star ratings. Sellers learn how to solicit reviews. The number, designed to represent trustworthiness, becomes a performance of trustworthiness — and the two quietly diverge.
In defense of gossip.
Gossip has a reputation problem. In contemporary usage it means malice. But anthropologists use the word differently, and more usefully: gossip is the informal circulation of social information through a community. Who helped whom. Who follows through. Who can be relied upon.
Robin Dunbar argues that gossip is the primary mechanism by which humans maintain relationships at the scale we live at. Physical grooming — the touch primates use to maintain bonds — doesn't scale beyond small groups. Language does. Gossip is social grooming at scale: the way communities stay current on each other, the way trust is built without requiring direct observation of every act. This is not a flaw of village life. It is the feature that made village life function.
The knowledge it produces doesn't live in any one person's head. It lives in the community — distributed, textured, contextual in ways no number can capture. Within roughly 150 people, we can hold genuine knowledge of each other. Above that, we reach for proxies. Karmyq's size limit is not arbitrary. It is the boundary within which ambient social knowledge remains possible.
Why you can't see anyone's karma.
In Karmyq, karma is not visible between members. You cannot look up another person's score. You must opt in even to see your own. This is the most counterintuitive design decision we made, and the one we are most confident about.
A karma score that members can see is a score that members will optimize for. Visible numbers create leaderboards, even when no leaderboard is intended. They shift attention from the act of helping to the reward for helping — and that shift changes the nature of the act. Sociologists distinguish between particularized trust, which develops through direct relationship, and generalized trust, which extends to strangers. Star ratings try to manufacture generalized trust through a shortcut. Karmyq builds particularized trust through practice. The opacity is not a workaround. It is the mechanism.
How karma is earned, and how it fades.
Every completed interaction generates karma for both people — the person who helped, and the person who asked. Asking for help is not passive. It is an act of vulnerability that makes the interaction possible. A community where only givers accumulate standing is a community that will run out of people willing to ask.
Karma records are never deleted, but they contribute less over time, using a six-month half-life. An interaction from three years ago is still in the record — it just carries a fraction of the weight it did when it was recent. What remains after the fading is a living picture of who someone is in this community, right now.
How reputation travels without broadcast.
Because karma is not visible as a number — and acts are never broadcast — reputation travels the way it does in any real community: through direct experience and its quiet consequences. The people you've helped know what they witnessed. The system knows the pattern. And the pattern shapes what happens next: whose requests reach you, how much trust you carry into a new community, how short the path runs between you and a stranger. No one is watching. But everything you do still matters.
What the platform does make visible is connection — not reputation, but relationship. Trust paths show how you're connected to someone you don't know directly: through whom, in how many steps, by what kind of tie. I trust Maria. Maria trusts David. I don't know David yet, but I know something about him I wouldn't know about a stranger.
And when you join a community where no one knows you, you don't start from zero. A portion of the trust you've built elsewhere — weighted and capped by what the new community accepts — travels with you. A letter of introduction, not a free pass.
Accuracy over direction.
None of this is static. The system is designed to calibrate toward what is actually true — not to push trust higher as a goal, but to reflect what a community's behavior actually shows over time. Trust that is earned looks different from trust that is performed. The system, over time, learns the difference.
How trust is measured.
Trust isn't a score. It's a pattern — how you show up, how reliably, with whom, how broadly. The platform reads the pattern. No one sees a number.
Trust paths show you how you're connected to a stranger. Through whom, in how many steps. Not a number. A map of actual human connection.
Cross-community trust travels with you. When you join somewhere new, a portion of what you've built elsewhere doesn't disappear. You don't start from zero.
The service layer.
Communities that choose to can enable a professional services layer — off by default, opted into deliberately. Providers must meet a minimum trust score before they can offer services. Karmyq never processes payment; it coordinates the connection and nothing more. A single identity carries both roles: the neighbor who helped you move last month and the electrician you hire this month are the same person, with the same trust history.
Design essay · Service layerThe Complete VillageHow commerce fits into community
The village economy was always complete.
There is a version of the community platform story that goes like this: money is the problem, markets are the disease, and the cure is a world where everything is freely given. It is a romantic vision. It is also, for most people in most circumstances, impossible to live inside.
The village economies that Karmyq draws on were never purely gift economies. The blacksmith charged for his work. The healer expected payment, in coin or in kind. What made these economies different from what we have now was not the absence of money — it was the presence of relationship. Commerce happened inside a web of mutual knowledge and ongoing obligation. That web is what we've lost. Not the commerce — the relationship that contained it. The service layer is not a concession. It is the honest completion of the model.
The tension, addressed directly.
Does enabling paid services inside a trust-based platform corrupt the trust culture it's trying to build? Research on motivation consistently shows that introducing payment into relationships that were previously gift-based can crowd out the intrinsic motivation that made those relationships function. This is why the service layer is opt-in at the community level. Some communities will keep everything gift-based. Some will want the full village model. The question is not resolved by us — it is held by each community, and answered through practice.
One identity. One history.
When a community enables professional services, members who choose to can activate a provider profile — a professional extension of their existing identity. Not a second account. Not a separate persona with a separate reputation. An additional layer on the same person, drawing on the same trust history.
The neighbor who helped three people move last year, who lent their van to someone they barely knew, who has been showing up consistently for eight months — that history is the context in which their professional services are offered. When you hire someone through Karmyq, you're extending trust into a web of actual human knowledge — not into a void filled by a star rating.
What communities configure.
Professional services are off by default. Communities that enable the layer control whether to allow it at all, which service types are permitted, and the minimum trust standing a member must hold before offering services. You cannot arrive and immediately offer paid work. You have to earn standing first. The service layer is not a shortcut to reputation. It is a reward for having built one.
Karmyq never touches money.
This is absolute and deliberate. Karmyq does not process payments, hold funds, or take a percentage. The moment money flows through a platform, the platform becomes a financial intermediary with the interests of a financial intermediary. Karmyq's role is to establish the conditions in which direct dealing is possible — and then step back.
The long arc.
The deepest hope for the service layer is that it eventually makes itself unnecessary. A community member discovers a local electrician through Karmyq. Trust develops. After a year, they call directly. That is not a failure. That is what success looks like. The measure of the service layer is not how many transactions flow through it. It is how many relationships it starts that eventually no longer need it.
How communities govern themselves.
Each community is sovereign — up to 150 members, the threshold at which genuine relationship becomes possible and beyond which it frays. It sets its own membership rules, configures how trust and karma flow, decides which kinds of help to enable. No platform override.
When a community is created, it goes through a short initialization process that sets its starting trust character — how it weights deep relationships over broad ones, how open it is to people beyond its immediate circle, what its default posture is toward other communities. These become the community's starting parameters. Not fixed permanently — the model evolves as the community actually behaves. The system calibrates toward what is actually true, not what was declared at founding.
Governance is gated by trust. To be nominated for a governance role, a member must first earn standing within the community — built through actual interactions, not assumed at entry. Nominations are made by members and ratified by existing role-holders. When contested decisions arise, votes are weighted by trust — the members the community has come to rely on most carry more weight in shaping its direction.
No role is permanent. A member whose trust has grown can be elevated. A role-holder whose presence has faded can be replaced. Governance reflects who the community currently trusts — not who it trusted at founding.
How communities grow and change.
Communities don't have to stay the same shape forever.
When a community approaches its natural size limit, its members can propose a split. The platform reads the existing patterns of interaction and suggests who belongs together — those who have helped each other most stay together. The proposed division goes to a vote weighted by standing. If it passes, two daughter communities form — each carrying the full trust history of its members, and each starting with a special relationship to the other. Sisters remember they share a past.
When two communities have built enough trust across their boundary to want to become one, they can propose a fusion. Both communities vote independently. If both pass, the merged community inherits the full karma history of both parents and carries forward the trust relationships built in each.
Neither process is automatic. Communities decide when the time is right. The platform provides the mechanics; the community provides the judgment.
Design essay · Governance & growthWhy No Role Is PermanentBinding power before it calcifies
The oldest failure mode.
Every cooperative structure in history has faced the same threat — not invasion, not scarcity, but calcification. Power accumulates. Roles harden. The people who once served the group begin to be served by it. By the time anyone names the problem, the people with the power to fix it are the ones benefiting from it.
This is not a story about bad people. It is a systems observation: power that cannot be displaced eventually destabilizes whatever holds it. Any structure without binding mechanisms — limits that constrain accumulation before it calcifies — will eventually concentrate power beyond what it can survive.
Binding mechanisms, by design.
Karmyq's architecture is a set of binding mechanisms, deliberately chosen.
The community size limit binds growth: at roughly 150 members, genuine mutual knowledge frays, so communities divide rather than swell. The karma half-life binds reputation: standing reflects who you are now, not who you were once. Trust-gated eligibility binds entry to power: you cannot hold a governance role before the community has reason to rely on you. And the impermanence of roles binds power itself: the nomination and ratification process runs in both directions. A member whose trust has grown can be elevated. A role-holder whose presence has faded can be replaced.
Elinor Ostrom documented communities that governed shared resources for centuries. The ones that lasted had this in common: rules made by the people bound by them, monitored by the community, adjustable over time. Karmyq's governance is that finding, made into software.
Growth without calcification.
Fission is a binding mechanism too — a pressure-relief valve. When a community approaches its natural limit, members can propose a split. The platform reads existing patterns of interaction and suggests who belongs together; the division goes to a vote weighted by standing; if it passes, two daughter communities form, each carrying the full trust history of its members, each holding a special relationship to the other. The community doesn't break. It reproduces.
Fusion runs the other way: two communities that have built enough trust across their boundary can choose to become one, each voting independently, the merged community inheriting the karma and trust built in both.
Neither is automatic. The platform provides the mechanics; the community provides the judgment.
What this buys.
A structure where power stays in motion. Where standing must be continuously earned. Where growth doesn't mean dilution and size doesn't mean distance. The same forces that hollowed out platforms and institutions — entrenchment, accumulation, the slow drift from serving to extracting — are bound here before they start.
No permanent thrones. No frozen hierarchies. Governance reflects who the community currently trusts — not who it trusted at founding.
Trust is a living thing, not a permanent record.
A neighbor who helped you last month matters more than one who helped three years ago. Karmyq works the same way. Old interactions fade, like memories. What remains is a living sense of trust — not an immutable score.