Intent
Build the shared resources neurodivergent life depends on as a commons — collectively made, openly available, and maintained — rather than as a product with a gate on it.
The Pattern
A commons is something people collectively build, maintain and benefit from. Historically they have taken many forms: shared grazing lands, community forests, open knowledge projects, open-source software.
Stimpunks is not only a website. It is a commons — a shared space where knowledge, tools, patterns and environments for neurodivergent life can grow. A design commons for neurodivergent life.
The reason this has to be a pattern rather than a preference is that the alternatives fail in a specific way. Knowledge about how to live and work as a neurodivergent person is mostly produced by neurodivergent people, at their own cost, and then either given away where it is hard to find or enclosed behind a price that the people who need it most cannot pay.
Enclosure is not only about money. A resource is effectively enclosed if it requires a diagnosis to access, a login to read, a professional to interpret, or membership of a network you have to already be inside to join.
A commons needs three things that a publication does not: it must be reachable without permission, contributable by the people it serves, and maintained, because an unmaintained commons decays into a monument.
That third one is where most attempts fail. Infrastructure is unglamorous, continuous and invisible when it is working — which makes it the first thing defunded and the last thing credited.
Why It Matters
Without commons infrastructure, people may:
- pay for knowledge that was produced by their own community
- need a diagnosis to reach information about their own life
- rediscover privately what somebody already worked out
- lose access to a resource when a project or a person stops
- be unable to contribute what they know back into the shared pool
- depend on a platform whose terms can change without them
The knowledge existed. The route to it was owned.
Forces
- Shared resources produce value that is hard to attribute and easy to overlook.
- Maintenance is continuous and invisible; creation is visible and funded.
- Open access removes the revenue that would sustain the work.
- Contribution requires trust, and trust requires moderation, which is labour.
- Enclosure is the default business model for anything useful.
- The people who most need the commons are least able to fund it.
Problem
How do we build shared resources that stay reachable, stay contributable, and stay maintained, without enclosing them to pay for it?
Solution
Default to open. Publish where it can be read without an account, licence it so it can be reused, and make the canonical copy the public one rather than an export of a private system.
Fund the maintenance explicitly, as its own line rather than as a residue of project work, because the failure mode of a commons is not collapse but neglect.
Let the people it serves contribute to it and be credited. This depends on Collaborative Niche Construction and is undermined wherever Administrative Burden gates the entrance.
What This Looks Like
In physical spaces
- Keep shared equipment, tools and materials genuinely available.
- Let people take what they need without an application.
- Maintain the shared thing on a schedule, not on failure.
- Make the space usable without membership.
- Never let a shared resource depend on one person’s goodwill.
In digital spaces
- Publish without a login wall.
- Licence for reuse and say so plainly.
- Keep the public version canonical, not a copy.
- Make contribution possible without insider access.
- Do not build the commons on a platform that can close it.
In social and organizational practice
- Fund maintenance as a named, recurring commitment.
- Credit the people whose knowledge the commons carries.
- Document how to contribute, and mean the invitation.
- Share what you learned, including what failed.
- Do not require a diagnosis to reach community knowledge.
- Never enclose something the community produced.
Implementation Notes
Take the most useful thing you hold and ask who can reach it.
- Can someone use this without an account, a diagnosis or an introduction?
- Who maintains it, and what happens when they stop?
- Can the people it serves add to it?
- Is the public copy the real one?
- What would it take for someone else to keep this going?
- Is maintenance funded, or is it absorbed?
A good test: if the resource would disappear when one person’s attention moves elsewhere, it is not infrastructure yet.
Signals of Misuse
This pattern is being violated when people hear:
- “You’ll need to create an account to read that.”
- “That’s members-only.”
- “We can’t fund maintenance, only new work.”
- “Do you have a diagnosis?”
- “It’s on the intranet.”
- “We’re the only ones who can update it.”
The last one describes a resource that is shared in name and owned in practice.
Consequences
When this pattern is honored:
- knowledge reaches the people who produced it
- work is not repeated privately across a whole community
- resources outlive the individuals who started them
- contribution is possible without insider standing
- access stops depending on diagnosis or money
- the community’s expertise accumulates instead of dispersing
When it is ignored, a community generates enormous knowledge and keeps having to buy it back.
Anti-Patterns
- Login walls on community knowledge
- Diagnosis as the price of access
- Maintenance funded only as new projects
- Canonical copy held privately
- Contribution restricted to staff
- Commons hosted where it can be closed
- Credit concentrated on the publisher
Design Moves
Strategies for building and keeping a commons.
See recipes:
Related Environments
Environments that are commons when they work:
- Neurodivergent Libraries
- Neurodivergent Community Spaces
- Neurodivergent Learning Ecosystems
- Collaborative Digital Spaces
Related Experiences
Experiences shaped by whether the commons exists:
Patterns Below
Patterns Above
Niche construction is a group reshaping its own environment. Commons infrastructure is what lets the results outlast the group that made them.
Related Patterns
- Pattern 41 — Administrative Burden
- Pattern 42 — Metric Fixation
- Pattern 36 — Cognitive Map Clarity
- Pattern 56 — Asynchronous Access
Related Principles
- Default to Open
- Care Is Infrastructure
- Everyone Can Contribute
- Free, Life-Changing, and Available to Everyone