Commoning as Verb

Treating the Commons not as a static resource but as an ongoing social practice — the continuous acts of negotiation, contribution, maintenance, and re-negotiation that keep value creation resilient and vital.

[!NOTE] Confidence Rating: ★★★ (Established) This pattern draws on Commons Theory / David Bollier.

---

Section 1: Context

Most organizations, movements, and platforms treat their commons—whether knowledge, code, reputation, or collective capacity—as fixed inventory to be protected or harvested. The commons arrives already-formed, and the work is defensive: gatekeeping, policing boundaries, preventing depletion. This static framing works briefly but fractures under stress. When conditions shift, when new voices arrive, when maintenance needs spike, or when the commons itself must evolve, systems built on protection alone become brittle.

The living ecosystem we’re describing is one where the commons is actively being made through participation, disagreement, contribution, and repair. In organizations, this emerges as distributed stewardship replacing hierarchical control. In government, it surfaces in participatory policy-making that doesn’t end at voting. In activist movements, it manifests as non-extractive solidarity practices. In tech products, it shows up in how communities shape roadmaps, maintain documentation, and define success metrics.

The pattern arises precisely when a system recognizes it cannot be stewarded by decree—only by continuous practice. This recognition is growing. Organizations discovering that knowledge silos collapse under complexity. Platforms learning that community guidelines mean nothing without community authorship. Movements understanding that burnout signals a commons being extracted rather than regenerated. The domain is category-creation-positioning: we’re learning to name and articulate a fundamentally different way of relating to shared value.

---

Section 2: Problem

The core conflict is Commoning vs. Verb.

The noun-form “the commons” invites passive preservation: identify the resource, draw a boundary, manage decline. It’s static, defensive, legible to policy and audit. But living commons don’t work this way. They require active tending—negotiation of use, contribution of effort, maintenance of norms, renegotiation when conditions change.

The tension breaks into two worldviews:

Commoning as noun says: The commons exists. Protect it. Establish rules. Enforce them. This approach generates clarity and measurability (stakeholder_architecture: 4.5) but treats people as rule-followers rather than creators. When norms drift or contexts shift, the system can’t adapt. Resilience (3.0) suffers because the system has no feedback loop for renegotiation.

Commoning as verb says: The commons is made through practice. Rules emerge from participation. Maintenance is everyone’s responsibility. This generates vitality (4.8) and adaptive capacity but sacrifices initial clarity. It’s harder to audit, easier to misread as chaos, and requires a different kind of leadership.

The real cost of unresolved tension: organizations build commons they believe are self-sustaining, then watch them decay when participation stops. Movements extract value from their commons faster than members can regenerate it. Platforms design features that flatten community input into data points. Tech communities fork rather than negotiate.

The breaking point is always the same: when someone must choose between following a static rule or responding to a living need, the system loses either its integrity or its vitality.

---

Section 3: Solution

Therefore, design every commons-practice as a regenerating activity, not a protected state—making negotiation, contribution, and maintenance visible and rhythmic so that the commons is continuously remade by those who steward it.

This is Commons Engineering at its root. The shift is perceptual and operational: from “defend the commons” to “practice commoning.”

Think of a forest commons. The boundary is real (the forest exists), but the commons lives in the acts: harvesting timber sustainably, burning undergrowth to prevent catastrophic fire, resolving disputes over hunting rights, teaching youth forest ecology, adapting practices to climate change. The forest thrives not because rules exist but because the community continuously negotiates how to live with it.

The mechanism works through making visible and rhythmic the acts that regenerate. In a healthy commons, you can see:

• Who contributes and what they add (not hidden in systems)
• How decisions shift when conditions change (not locked in policy)
• Where maintenance work happens and who does it (not assumed or invisible)
• How newcomers learn to participate (not gatekept by insider knowledge)

This creates the richer feedback loops that Commons Theory emphasizes. When you treat commoning as verb, the system develops autopoietic capacity—it self-generates and self-corrects because the people in it are continuously sensing and responding, not blindly executing rules.

The pattern resolves the tension by reframing what “protecting the commons” means. It’s not about preventing change. It’s about ensuring that change happens through participation, negotiation, and transparency rather than extraction, drift, or coercion. The resilience score (3.0) lifts as people develop shared literacy about how they collectively sustain value. Ownership (3.0) becomes real because people are visibly making decisions, not receiving them. Vitality (4.8) emerges naturally because the system is alive with adjustment and creativity.

---

Section 4: Implementation

Begin by mapping where commoning is already happening in your system—invisible, often unrecognized. Look for the places where informal practices keep things alive: the Slack channel where knowledge actually gets documented, the community member who on-boards newcomers, the team that fixes broken processes without waiting for permission. Name these as commoning. Make them visible. This shifts energy from fighting breakdown to recognizing generative work.

For Corporate Contexts:

Establish a “Commoning Cycle” around your core shared asset (code repository, knowledge base, customer insights, internal culture). Each quarter (or season appropriate to your pace):

• Harvest: Surface what’s been contributed. Celebrate contributors explicitly—name them, amplify their work.
• Tend: Hold structured conversations about what’s degrading. Don’t fix it top-down; create a working session where stewards identify needed repairs and negotiate who does what.
• Negotiate: When conflicts arise about resource use or direction, make these visible. Host forums where different needs are articulated, not settled by rank.
• Plan next planting: Collaboratively decide what new capacity needs seeding. This is not strategic planning—it’s gardeners discussing what the soil needs.

Document the cycle itself. Make it observable. People need to see that commoning is rhythmic and trustworthy.

For Government Contexts:

Move beyond “public comment periods” (listen-only) to structured re-negotiation practices. If a public service is commons-based (libraries, parks, data systems), create quarterly “stewardship convening”—not to inform the public of decisions, but to genuinely renegotiate how the commons will be tended in light of new conditions.

Concretely: A city’s housing data commons. Every quarter, bring residents, housing advocates, developers, and city staff to surface conflicts (affordability vs. development pace). Make visible how each group uses the data. Negotiate what new data should be collected. Renegotiate who gets access and on what terms. The practice itself teaches governance.

For Activist Contexts:

Institutionalize care practices alongside campaign work. Commoning breaks when extraction exceeds regeneration. Design explicit roles: not just strategists and organizers, but commons stewards—people accountable for noticing when people are burning out, when knowledge is being lost, when new voices aren’t being heard.

Create a “wisdom circle” rhythm (monthly or biweekly) where the movement reflects on its own health. What’s working? Where are we extracting faster than regenerating? Who isn’t present and why? This isn’t therapy; it’s commoning work. It regenerates the social fabric that makes campaigns possible.

For Tech Contexts:

Build stewardship ladders into your product. Not gamified achievement systems—real progression in how someone participates in shaping the product.

• Tier 1: User → Contributes feedback, reports bugs
• Tier 2: Contributor → Writes code, documentation
• Tier 3: Steward → Participates in roadmap negotiation, mentors new contributors, helps resolve conflicts about feature priority
• Tier 4: Gardener → Reflects on the health of the entire commons; proposes structural changes to how the community works together

Make the transitions real. Stewards get visibility, voice in governance, and responsibility for the commons’s vitality. Document how decisions are made. When a steward argues against a feature the founders want, show the negotiation happening, not the decree issued.

---

Section 5: Consequences

What Flourishes:

When commoning becomes visible and rhythmic, adaptive capacity emerges. The system can respond to new conditions because negotiation is normalized. Someone notices a new threat or opportunity; instead of waiting for permission, they surface it in the commoning cycle, and the collective quickly renegotiates. Organizations discover they’re faster at pivoting, not despite the extra “talking,” but because the talking is structured and real.

Shared ownership deepens. Not ownership of the commons (legally), but ownership of its regeneration. People develop what Bollier calls “stewardship consciousness”—they see themselves as responsible for keeping things alive, not just using them. This generates intrinsic motivation that no external incentive can replicate. Turnover drops. Contribution accelerates. Knowledge spreads faster because people want the commons to be healthy.

New forms of leadership emerge. Not from hiring new managers, but from people developing stewardship skills through practice. Someone becomes expert at helping groups negotiate conflict. Another develops gift for teaching newcomers. A third notices when the rhythm of commoning is breaking down and speaks up. Distributed leadership happens naturally.

What Risks Emerge:

Commoning-as-verb requires continuous relational work. If you’re used to rule-following, this feels chaotic. Meetings feel endless. Decisions take longer. Some organizations try commoning for two cycles, then revert to command-and-control because it “felt slower.” Guard against premature conclusion: adaptive systems often feel slower initially but accelerate once people develop fluency.

Resilience (3.0) and Ownership (3.0) both remain moderate risks. If commoning practices become hollow—meetings where decisions are already made, feedback that’s never acted on, stewardship roles without actual authority—the system decays fast. People become cynical. They stop participating. The commons reverts to static management, but now with added resentment. This is the failure mode: performative commoning.

Fractal value (4.0) is a known gap. If commoning practices don’t scale across nested levels (team → division → organization), the pattern breaks. A team practices commoning beautifully; the division doesn’t. The team’s autonomy becomes constrained by above. Be explicit about how commoning cascades or translates across scale.

---

Section 6: Known Uses

Free Software Commons (Linux kernel, Apache Foundation): The Linux kernel is stewarded through a visible, rhythmic commoning practice. Code review isn’t rule enforcement; it’s negotiation. When Linus Torvalds rejects a patch, he explains why. Contributors argue back. Eventually, a shared understanding emerges about what the kernel should do. When new use cases emerged (embedded systems, containers), the commons renegotiated its architecture. This is commoning as verb: the commons is made through continuous technical and social negotiation, visible in every patch thread. The result: a commons that’s survived 30 years and adapted to entirely new contexts.

Occupy Wall Street Movement (2011): At its best, OWS practiced commoning as verb. General Assemblies were structured negotiation spaces where decisions emerged from collective voice, not delegation. The “people’s microphone” made invisible thinking visible (everyone heard every voice). Working groups were stewardship units; people moved between them, learning how to tend different aspects of the movement’s commons (food, safety, messaging, protest planning). The movement fractured partly because commoning practices depended on continuous physical presence—they didn’t scale when the occupation ended. But the pattern was real: the movement regenerated itself daily through visible, rhythmic acts of negotiation.

Wikimedia Commons: The visual and media commons stewarded by Wikipedians isn’t just a database. It’s maintained through weekly edit-a-thons, clearly visible governance discussions (where should images be categorized? who can delete?), and rotating stewardship of high-value assets. New photographers learn commoning by watching how experienced Wikipedians negotiate metadata standards, resolve disputes about image licensing, and welcome contribution. The commons thrives because tending it is visible and rhythmic, not hidden in database management.

---

Section 7: Cognitive Era

In an age of algorithmic mediation and AI-assisted decision-making, commoning-as-verb faces new pressure and new possibility.

The Risk: AI systems can accelerate extraction. Recommendation algorithms optimize for engagement, not community health. Automation can make commoning invisible again—rules applied at machine speed, leaving humans passive. A platform using AI to “optimize governance” might make faster decisions but lose the negotiation space where people learn to steward collectively. The commons reverts to static, just now administered by neural networks instead of executives.

The Leverage: But AI can also make commoning more visible. Dashboards can surface contribution patterns, highlight maintenance work others don’t see, flag when someone’s burned out based on participation patterns. AI can transcribe meetings, surface key decision moments, and help newcomers see how decisions are made. This supports what Commoning as Verb requires: transparency about the acts that regenerate.

In tech products (context translation), this is critical. Communities stewarding open-source projects increasingly use AI for routine code review (style checking, security scanning). This frees humans to focus on the negotiation work—the discussions about architectural direction, about trade-offs between features, about whether a contribution aligns with the project’s values. The pattern shifts: AI handles the rule-checking; humans handle the renegotiation.

New risk emerges: If AI becomes the arbiter of what counts as “valid contribution” (filtering issues, pre-sorting pull requests), the commons can’t renegotiate. The community stops seeing itself as making decisions; it’s optimizing for algorithmic approval. Guard against this by making explicit: AI is a tool for surfacing information and handling routine work, not for replacing the spaces where commoning happens.

---

Section 8: Vitality

Signs of Life:

• Visible, celebrated contribution. When you ask a community member why they maintain a particular practice, they can tell you a story about negotiating it with others, not just following a rule. Stewards are named, their work is surfaced, not invisible.
• Renegotiation happens openly. Conflicts about resource use or direction are surfaced in shared spaces, not resolved in private. Disagreement is expected and worked through collectively. People can point to moments when a practice changed because someone raised a need.
• Maintenance work is rhythmic and transparent. There’s a regular cycle where the community explicitly attends to the commons’s health. In quarterly reviews, harvests, or working sessions, people talk about what’s decaying and who’s caring for it. This isn’t optional work done in spare time; it’s integrated into how the system operates.
• Newcomers learn through participation, not just rules. New members aren’t handed a handbook. They join a working session, see how decisions get made, and gradually develop stewardship literacy. They can articulate why the community does things, not just what they’re supposed to do.

Signs of Decay:

• Commoning becomes a ritual without negotiation. Meetings happen, but decisions are pre-made. Feedback is collected but never acted on. People sense the hollowness; participation drops. This is performative commoning, and it spreads cynicism faster than no commoning at all.
• Stewardship becomes invisible again. The work that keeps the commons alive gets absorbed into someone’s personal bandwidth (often uncompensated). When that person leaves, the commons collapses. No one else knew what they were doing.
• Conflicts stop surfacing. People have disputes about use or direction but resolve them in private conversations, side channels, or by leaving. The commons can’t renegotiate because the renegotiation isn’t happening where collective sense-making can occur.
• The rhythm breaks. There’s no regular cycle for reflection and renewal. Commoning becomes sporadic, reactive. When conditions change, the community can’t collectively adapt because there’s no structured space for that conversation.

When to Replant:

Replant when you notice the commons is being treated as fixed inventory again—when people stop seeing their participation as making the system and start seeing it as using it. This is the moment to surface what commoning was actually happening, name it explicitly, and rebuild the rhythmic practices that make it visible. The right moment is often after a crisis (someone burns out, a conflict explodes, the system fails to adapt)—these signal that static management isn’t sufficient. That’s when the organization is ready to commit to commoning as continuous practice.