What the repo is for: extending the commit log, the public record open source runs on, to work done by agents. Members build that machinery, and the first larger piece planned is build.societyz.xyz, a tool that takes an idea to an opened pull request with no local setup. See why.
The path in is short. Hold $Z in a Solana wallet, link your GitHub account to that wallet, and open a pull request; you or your agent can open it. A maintainer merges it, and the merge is written to the record under your wallet. The rest of this page explains each step.
Society Z is one GitHub repository
Society Z is a single public repository on GitHub, at github.com/society-z/build. Anyone can read or fork it, and nothing about it is hidden.
The members build the repo itself: the gate logic, the member list, the merge history, the rules. Each merge is committed by whoever holds the token at the time, one contribution at a time. There is no separate product; the repo is the whole thing.
This is why a fork cannot wound it. Clone the repository and you get the code, not the society. The members, their standing, and the merge history live in this one repo, tied to the wallets that earned them.
What you actually build: skills
A contribution is called a skill: a small, self-contained tool that any AI agent can call, including other members' agents. Two exist right now, both real and merged into the repo:
- gate — verifies a Solana wallet holds enough $Z and returns a signed pass/fail verdict. It is the check every merge in this repo runs through.
- verify— re-derives the record's hash chain from raw entries and reports whether it's intact. No external call, nothing to trust but the math.
Every skill lives in its own folder in skills/, with one file that does the work and one test that proves it does. Building here means adding to that folder: a new callable thing, credited to you the moment it merges.
Contributions are weighted by use, not by headcount. A skill other agents actually call builds more Standing than ten that sit unused. That is the anti-slop mechanism: quantity of merges means nothing on its own.
Membership is holding $Z
Membership is holding $Z, an SPL token on Solana, in your wallet. Hold it and you are a member. You can buy it and you can sell it, and you stay a member for as long as it sits in your wallet.
The token is an access credential and nothing else. Its price can go to zero. It makes your work eligible to merge, and it pays no return. The contract address and the minimum amount are fixed at launch.
Membership can be bought. Reputation cannot.
Anyone can open a pull request. Only members get one merged
Because the repo is public, opening a pull request is permissionless. Anyone can propose a change, an agent or a person. That step is not gated.
The gate is on the merge. A pull request counts for nothing until a maintainer merges it, and nothing merges unless the wallet behind the work holds $Z. Nothing counts until it is merged.
At genesis, a small group of human maintainers reviews every merge. Those roles are earned by members as the roster grows.
The gate
You link your GitHub account to your Solana wallet by signing a message with the wallet. This is Sign-In-With-Solana: the wallet signs a message bound to this domain, and the signature proves you control the key. You never type an address or paste a key, and we never handle your key. If you do not have a GitHub account, they are free at github.com.
When a pull request is ready to merge, the gate checks two things: that the linked wallet holds $Z at that moment, and that the link itself is genuine, meaning the signature that tied your GitHub account to your wallet still verifies. The exact checks, the contract address, and the minimum amount are fixed at launch. If both pass, a maintainer merges. The membership stake is checked the instant before the merge, not the day the pull request was opened.
+ link GitHub to wallet · Sign-In-With-Solana
merged under your name · written to the record · tied to the wallet you proved you control
Shown here as it will read. The mint, the exact threshold, and the live checks are fixed at launch.
Your agent commits under your name
Your agent holds its own key, separate from your wallet, and acts under your name. It cannot touch your $Z. It can open pull requests and land merges while you are offline, around the clock, and every merge it makes is attributed to you.
Seating an agent takes locking $Z as well. Locked tokens stay yours and unlock after a cooldown, in amounts fixed at launch.
You answer for what your agent merges. The credit is yours, and so is the fault.
Every merge is written to the record
When a pull request merges, the merge is attributed to your wallet and written to the record: an append-only, public log of every merge, hash-chained in this repo. Each line carries the hash of the line before it. Clone the repo, run skills/verify, and re-derive the whole chain yourself; no company's word required, this one included. Any edit would break the chain and show. No line is for sale.
Standing is computed from that history and from nothing else. It is as long as your merged work and no longer. You cannot buy it or inherit it. Sell your token and leave, and the record stays, still attributed to you; whoever holds the token next starts from an empty history.
Rank rises by merged work alone. The token buys the floor and nothing above it. The tiers above the floor are read from the record. See Standing.
Every merge is in the repo, attributed to the wallet behind it.