Final draft Ratification: 18 September 2026, on the call, then a Telegram poll Term: From ratification until a new council is seated in 2027 Companions: Budget scope · Contributions and Retro · Infra Management · 2027 Election
What changed from Draft Two
-
A fifth initiative: Community Spotlights. Rotating spotlights of the work and tools across our orgs, inside the council call, with a forum category for async. This is instead of a third call, not as well as one.
-
Regen Commons enters as a partner, not a member org. Member orgs are Greenpill, ReFi DAO and Bloom.
-
CeloPG removed. Bread Co-op is our other active partner. Historical partners are handed to Sensemaking for learnings.
-
Linear is a three-month experiment and is not a prerequisite for contribution credit.
-
Active means executing something, not only attending and giving feedback.
-
No recruitment this period, other than Tricia joining as Bloom’s representative.
-
The council is finalized at the 2 October sync, not at the end of the month.
-
One decision mechanism. Polls, with quorum.
-
Contributions and retro moved to their own document, with the four balancing options set out in full.
Why now
Regen Coordination has been running on shared history and a group chat. That got us a long way. It stops working the moment the group grows, because there is nothing to point at when someone asks what joining means, what a steward does, or how a decision gets made.
We are past that point. The initiatives are real and sitting in Linear with nobody named against them. Bloom is changing who represents them. Regen Commons is regaining momentum and we have no formal relationship with them. And we have named this gap in almost every sync this year.
This is a maturation step, not a rescue. It is about three things:
-
Clarity. What a steward can decide alone, and what needs the group.
-
Autonomy. People holding initiatives should move without waiting on a call.
-
Accountability. Progress that shows up as something delivered, not as attendance.
This proposal covers the rest of 2026 only. Everything it leaves open is listed at the end.
Where we already are
What
Where
Council calls
Bi-weekly on Fridays, alternating with the Knowledge Commons call
Sensemaking
Telegram polls, pulling 20 to 30 responses
Forum
hub.regencoordination.xyz, moving to self-hosting at under $10 a month
Work tracking
Linear, on two week cycles. A three-month experiment
Fundraising
Regen Coordination Fund & Project on Artizen
Treasury
The Safe, USDGLO on Celo and BREAD on Gnosis, plus the Gardens pool
Budget
The budget scope, ratified alongside this
The initiatives
Five for the rest of the year. After that new initiatives run in three-month blocks so we stay focused on what we committed to.
Each has up to three stewards, one of whom is the lead. Stewards are named at the 2 October sync.
Regen Coordination Fund & Project
Curating the fund on Artizen down to a focused set of aligned projects. Holding boosts and spending them together on one drive rather than spreading them thin. Artifact and sponsorship transactions, the reimbursement process, and managing the payout when Season 7 closes in January.
Managing the project which is a direct way for capital to flow into the organization. Attracting donors and community members to support with capital or Artizen boost mechanics. Coordinating the community to support quests where the project or fund can win a cash prize either with boosts or sales.
Also decides when council capital can flow in, tracks it for reimbursement, and carries the criteria for how projects are admitted to the fund.
Knowledge Commons
The toolkit: an open, contributable resource for regen Web3, structured as foundations, then applied concepts, then playbooks and case studies. The playbooks carry the most weight, documenting working models rather than adding more general explainer content.
Repo stabilization and the contribution pathway. The ingestion pipeline and schema convergence. Deployment and federation across the networks, because a resource nobody finds or contributes to is not yet a commons. Its own infrastructure, hosting, domain and agents.
It submits its own budget request rather than receiving a top-down allocation.
Regen Hub and Ecosystem Sensemaking
The hub itself and the move to self-hosting. Telegram polls, and the published analysis that turns a poll from an output into an outcome.
Processing what we already have into learnings: previous round data, poll results, and the GG23 partnership documents. Several of those earlier partners are structurally close to a Greenpill chapter, a ReFi DAO node or a local Bloom, and that is worth understanding before we write anything new about partnership.
Also carries relaying what happens here back out to the networks.
Community Spotlights
New. A rotating spotlight of the work and tools across our orgs, held inside the council call. Not only demos: case studies and research apply as well.
We start with what the council already has, Green Goods, Gardens, Knowledge Commons, Bloom Network, Regen OS, then widen to associated projects. A forum category carries it, with a post before and after so people can take part without attending.
This replaces the need for a separate community call. We do not have the bandwidth for a third call, and the spotlight is the part that actually creates the visibility.
Governance and Resourcing
The council’s own work, held collectively rather than by an initiative team.
This proposal and its ratification. Re-consent and the steward roster. The budget scope, the four-bucket split, and the contribution epochs. Multisig signers across three chains. The custody register and handovers. Preparing the 2027 election decision.
The council
A council of stewards
You are on the council because you are doing something, not because you are here. There are two ways, and you need at least one.
You carry a network. You are genuinely active in Greenpill Network, ReFi DAO or Bloom Network. Your network knows you speak for them here. You bring what is moving there into the room, and you take what is decided here back out. This is the coordination itself, not overhead.
You hold an initiative. Stewards hold decision-making for that initiative. The lead holds continuity and is the person to ask.
Most stewards will do both. If you do neither, there is no role. Presence and feedback are genuinely useful, but on their own they are not enough right now.
Project contributors underneath the initiatives can be anyone, including people who are not stewards. That is how the Knowledge Commons already works.
Who the stewards come from
Member orgs: Greenpill Network, ReFi DAO, Bloom Network.
Every member org has at least one steward. Otherwise an org is a member in name and absent in practice. There is no cap on how many an org brings. At our size the binding constraint is people willing to steward, not seats.
The floor is five active stewards. Below that we pause and reopen rather than carry on.
Orgs name their own stewards and can change them. Tricia Stapleton joins as Bloom’s representative, replacing Magenta. She is the only addition this period. We have one quarter and the bandwidth to run it well or to onboard broadly, not both. Steward criteria and an onboarding protocol are for the next council.
Partners
Bread Co-op is an active partner.
Regen Commons is proposed as a partner for the rest of the year, pending a conversation with their council.
Earlier partnerships from the GG23 round were real and are now historical. Rather than tidy the list, Sensemaking pulls the learnings out of those documents.
What active means
An active steward:
-
Carries a network, holds an initiative, or both. You are executing something.
-
Joins one of the two monthly calls. If you cannot make it, say so in the chat and engage async on anything being decided.
-
Votes in council polls.
The evidence is what you bring, not the attendance. Two months with nothing from a network and nothing from an initiative means the seat has gone quiet, and that is visible without anyone having to raise it.
Past stewards
If you are not currently active, you are a past member. You leave the council chat and keep access to the council section of the hub, so updates and governance proposals stay visible. Credit for what you built sits on the hub and in the initiative history regardless of your status.
Stepping back, and being stepped back
You step back. Say so. Hand over anything you hold, including accounts. The seat opens and the signer comes off.
You go quiet. Two months with nothing to bring and no engagement triggers one message. If nothing changes, the move happens on its own. No vote, no removal ritual.
Removal for cause. Rare. Any steward can propose it with the reason written down, the person responds, and it carries on two thirds of active stewards. Signer removal is separate and immediate, because keys should not wait for a process.
An org leaves. Seats came through the org so they go with it. The council can invite an individual to stay.
What you keep. Retro and reimbursements already owed still get paid, whatever the reason for leaving. Nobody should be weighing their finances against an honest read of their own capacity.
Re-consent
A Telegram poll, straight after ratification. You indicate that you want to continue as a steward and that you agree to the commitments above. That is the whole process. Anyone who does not respond by the end of September is not continuing.
The timeline
-
18 September. Ratification on the call, then the poll.
-
End of September. Re-consent closes.
-
2 October. Quarterly call. Stewards named against initiatives and the council is finalized, with Tricia on the call. Q4 priorities and the capital ranking.
-
October. The four-bucket split is decided and locked. Then the first contribution epoch runs. Handovers completed and Safe signers updated across all three chains.
Silence resolves membership. It does not resolve custody. Anyone leaving who holds accounts still needs a real handover. See Infra Management.
How we work
What the council decides
Already on the calendar. Each quarter, priorities and the capital ranking. In October, the four-bucket split and the first contribution epoch. In January, how the two epochs balance and the election format.
When they come up. Money that is not in the approved budget. Admitting a member org or partner. Amending this document. Removal for cause.
Once stewardship is set for a period, the initiative runs itself, and it can raise and hold its own funding. Money from us is one input, not the only one, and given the size of our treasury it will often not be the largest.
Never a council decision. Anything inside an initiative’s mandate: scope, priorities, projects, contributors, and how its budget line gets spent. Spending against an approved budget line. Who an org sends as its steward.
How a decision gets made
One mechanism. A poll.
-
Post it with the options and a close date, at least five days out
-
Quorum is more than half the active stewards
-
Most votes carries
-
If you vote against, say what breaks. A preference is not an objection
Two venues. The council chat for what the council decides. The hub for anything binding on the wider group or that should be public, including ratification and amendments, with quorum published before it opens.
Poll Types
Type
Where
Used for
Council decision poll
Council chat, council only
Anything the council needs to settle around budgets, allocations, impromptu actions. Named options, close date, votes visible. Voting is part of being active.
Community pulse
Public Telegram, forwarded across the networks
One question, curated in the council before it goes out.
Hub decision poll
Discourse
Anything binding or structural. Quorum published before it opens.
Every poll ships with a published analysis. A poll on its own is an output. The analysis, and what it changes, is the outcome.
Removal for cause is the one exception and needs two thirds.
A call is where a proposal gets shaped, not another way to decide. If every active steward is in the room it closes there. Otherwise it posts and runs like anything else. A poll that misses quorum does not carry, and that is a signal about the council rather than about the proposal.
Work tracking
Linear holds the initiatives and their projects, on two-week cycles. We are running it as a three-month experiment and reviewing it at the January quarterly.
Linear is not a prerequisite for credit. It is one source of evidence among several. Work that happened elsewhere, or that does not fit a task shape at all, still counts and goes in your contribution statement.
Council Calls
Bi-weekly on Fridays, alternating with the Knowledge Commons call. Roughly an hour.
-
Open. Check in.
-
Network updates. What is moving in Greenpill, ReFi DAO and Bloom.
-
Initiative updates. Short.
-
Decisions. Things that need talking through before they settle.
-
Close. What was decided, who owns what, what is still open.
The quarterly call opens each quarter, and is longer, ninety minutes to two hours. It looks back at the quarter just gone: how the initiatives went and whether they carry on as they are, the structure and processes we are using including the tools, and the general sentiment in the room. Then priorities and the capital ranking for the quarter ahead. This is where something adopted three months ago gets looked at properly rather than becoming permanent by default.
The first is 2 October, covering Q3 and setting Q4.
Moderation rotates monthly. The moderator is expected to show up, picks what gets the most time, and can shelve something to the next call rather than letting it run.
Before a call, anyone can suggest something in the group chat. No agenda document needed.
How a decision closes. Confirmed on the call, then written up in the chat. If quorum was in the room it stands. Otherwise it posts and runs the normal window.
Meeting notes are AI-generated and garble names. Check any name before using it publicly.
Quarterly Updates
Each initiative posts an update on the hub once a quarter. That is two updates between now and early 2027, which is about right for what is actually happening.
Money and Treasury
The numbers live in the budget scope, ratified alongside this. This is the shape.
We start from what we hold, not a projection. All inflows for the rest of the year are what gets split across the four buckets.
The split is decided and locked before the first epoch. Percentages across the four buckets are agreed before anyone allocates anything, so nobody is adjusting a split after seeing what they received.
Bucket
What it covers
Networks
Greenpill, Bloom and ReFi DAO, split equally
Knowledge Commons
Infrastructure for the rest of the year, plus discretionary funds it can put into Artizen
2026 Retro
Paid against the contribution epoch points
Future council and initiatives
Held for whatever the next council scopes
If Regen Coordination winds down, the future council bucket disappears and splits equally between the other three.
February 2027 at the earliest. Artizen Season 7 funds land. The percentages are applied and retro points get a dollar value.
Council capital into Artizen
A steward puts their own money in only when doing so unlocks 3 to 4x matching. That is the test for whether the risk is worth taking.
The reimbursement model is tracked in the budget scope and is still to be decided. The proposal on the table is principal plus 20 percent for the assumed risk, repaid from Season 7 proceeds.
Multisig signers
The Safe at 0xFCb81c1B0e0D4FEa01e5A0fbf0aebb91e78A67E1 is 3 of 6 and the signer set no longer matches who is active. It is deployed on Celo, Gnosis and Arbitrum, and the Arbitrum owner set has already drifted from the other two.
-
Every active steward becomes a signer once re-consent settles
-
Past members are removed
-
All three chains get the same signer set
-
The threshold is set relative to the new signer count
Contributions and retro
Two epochs. October covers Q1 to Q3. January covers Q4. Everyone writes a statement, everyone gets the same points, and you allocate to others rather than yourself. Allocations stay private until the epoch closes.
The four-bucket split is locked first, the epochs run after, and points get a dollar value when Artizen funds land.
The flow, who takes part, and the four options for balancing the two epochs are set out in Contributions and Retro.
What ratifying this means
-
Five initiatives, a council of stewards, at least one per member org, a floor of five
-
Regen Commons as a partner, CeloPG removed, Tricia the only addition this quarter
-
One decision mechanism, polls with quorum
-
Re-consent closes end of September, council finalized 2 October
-
The four-bucket split is locked before the October epoch runs