A governance proposal inside Poimandres was merged in seventeen minutes.
Not a figure of speech. Pull request #7 on pmndrs/org opened at 09:07 on October 22, 2026, and merged at 09:24. The body ends with a sentence that made me stop scrolling: "Per Charter §4, these are accepted if no member objects within five days."
Seventeen minutes is not five days.
i went into this looking for a fight. What i found was a rulebook that had already decided everything was fine, sitting on top of 92 million weekly downloads.
Zustand alone did 92,760,094 installs in the week ending November 15. That is one library. The same person wrote four more of them.
Then he posted six words.
"From today on @pmndrs is dead to me."
That went up on November 16, from an account with 59,000 followers. It picked up a few hundred likes. Not a lot, considering what it meant.
What he gave away
Paul Henschel started the org in December 2018. It has 105 public repos and 10,021 followers. Zustand, react-spring, react-three-fiber, drei, and a long tail of smaller tools.
The pitch was unusual. Not a company. Not a foundation.
A place to park your repo so other people would find it.
His own description of the deal, from the follow-up post:
"Pmndrs was a platform of mutual trust, that lifts up good ideas and developers. We promised devs never to take ownership of repos, transfers, manage your funds."
Read that again:
- no ownership
- no transfers
- no control of money
He handed owner permissions to people on the strength of that promise, and the promise was the only thing holding it together.
There is no legal entity in that sentence. There is no contract. Just a norm.
The charter showed up in September
Two commits tell the story better than any thread. On September 6, 2026, a maintainer named Kris Baumgartner pushed "Update core principles to include open, remove quality." Four days later, "Title changes."
By October there was a CHARTER.md. Status line: Draft.
It is a decent document, honestly. Membership defined as a working role. Decisions made "as close as possible to the work they affect."
Project leads keep autonomy over their repos, including project status. Disputes go to lazy consensus, five days, and any objection pauses things.
Which is the strange part. On paper, the charter protects exactly what Henschel says he lost.
| pmndrs | pmndre | |
|---|---|---|
| Created | Dec 2018 | Nov 13, 2026 |
| Public repos | 105 | 3 |
| Followers | 10,021 | 62 |
So either the charter got ignored when it mattered, or the fight was never about the repos.
He says the org became "some kind of committee," the mission statement was rewritten, and people he trusted used the permissions he gave them to remove him without a conversation.
The current mission statement is one paragraph about craft, joy, and shared effort. It does not say who owns what. That is the hole.
The half of the story nobody has
Here is what i could not find.
No statement from pmndrs. No thread from any current maintainer explaining their side. The GitHub org updated on November 14 and then went quiet.
He says he tried to negotiate a split and got no reply.
Maybe there is one and i missed it. But a 92-million-download-a-week ecosystem just had its founder walk out the door, and the public record is one man's posts plus a draft charter.
That is not enough to convict anyone.
i keep thinking about the pull request though. The governance work carried a footer saying it was generated by Claude Code. A document about human trust and mutual obligation, written by a model, merged seventeen minutes later under a rule that asks for five days of silence.
So he started over
The new org is github.com/pmndre. Three repos. 62 followers.
Created November 13, three days before the announcement.
Same description as the old one, word for word: "Open source developer collective."
The main project is PINE. Its README opens with a claim i have not seen elsewhere: "PINE makes AI reactive."
The distinction it draws is sharp. Most agent tools do chat, or chat plus a scheduler. PINE agents subscribe to event sources instead:
- folders
- webhooks
- MQTT
- FTP endpoints
- web addresses
- command output
You tell the main agent what you want watched, and it writes the integration itself. No config files. The agent builds its own setup through tool calls, and a built-in search tool lets it look up its own API on demand.
Six days old. 258 stars. Zero open issues.
It ships as npm install -g @pmndre/pine, runs a terminal UI with tabs and inline images, and drives a Flipper Zero through an MCP server in the demo screenshots.
i have not run it. Six days is six days.
Nobody on Hacker News noticed
This is the detail i cannot get past.
i searched Hacker News for pmndrs, poimandres, pmndre, and the man's handle. Nothing. Not one submission about the split.
Then r/threejs and r/reactjs on old reddit. The newest posts are people debugging raycast collisions and asking about state management.
Zustand did 92 million downloads last week. React Three Fiber did 9.2 million. And the founder's exit produced no thread.
Compare that to any framework drama you remember. The attention is not proportional to usage anymore. It goes to whoever is loudest on the timeline.
And the 3D corner of React has never been loud. It ships, people import it, nobody argues about it.
My bookmarks folder has 41 react-three-fiber demos in it.
Little orbital mechanics toys. A shader that makes water look wet. Someone's recreation of a Game Boy.
i have opened exactly two of them and built nothing.
i keep saving them like i am going to get a quiet weekend where i finally learn quaternions.
The people who wrote those demos are the actual community this whole thing is about. Not the charter. Not the org.
Not whoever holds the owner bit. A folder of links to things strangers made because they were excited.
The real talk
If you use zustand, none of this changes your code.
That is the honest version. The license is MIT. The repo is not going anywhere.
Ninety-two million weekly installs means someone will maintain it, because too many companies depend on it for it to die.
But if you are building a business on top of a GitHub org, read the charter before you transfer anything. "Project leads retain autonomy" is a sentence. It is not a mechanism.
The mechanism is who holds the owner permission and who can revoke it.
Those are different things, and the gap between them is where this whole fight lives.
And if you are the person handing out permissions on trust, ask what happens the first time the group disagrees with you. Not hypothetically. Ask for the actual procedure and get it in a file, signed by everyone.
The ending
i still think the seventeen minutes is the tell.
Not because a merge was fast. Because a group that had just written down "five days of silence means yes" found a way to move in under twenty. Rules like that only bind people who want to be bound.
Henschel named his new org after the same 2,000-year-old text. Poimandre, the vision. Same name, same description, same mission paragraph he says was rewritten out from under him.
i hope this time he keeps the keys.
