The Commonplace

Soil, not firm

The defining metaphor of the whole series, and the one that resolved the most arguments. The question on the table was whether the cooperative is a productive enterprise that signs contracts and delivers work, or something more like infrastructure. The answer that held was soil: the substrate that creates conditions for growth. Coworking revenue keeps the lights on, the way a blockchain's transaction fees maintain the chain, but the actual value appears in what gets built on top.

This did practical work. If the cooperative is soil, it does not need to account for every member's minute-by-minute contribution. It tracks its relationship to the ventures and projects that grow in it. An entire class of accounting anxiety dissolved in one metaphor.

Scenius

A portmanteau of scene and genius, naming the collective intelligence that emerges from mutual inspiration among culturally aligned peers. It landed on first hearing in Meeting 2 and never left. It eventually became the filed public benefit purpose.

Meeting 6 added the etymology that made it more than a coinage. The Latin genius originally meant a household guardian spirit, an inspirational presence watching over a person or family from birth. Only later did it narrow to an individual trait and then to exceptional individual talent. Scenius is in that light a restoration rather than an invention: the spirit belongs to the group again.

Habitat for co-creation

The soil metaphor grown outward. Not just soil but a garden, and not just a garden but an ecosystem, with a forest and trees and a stream. The point of the escalation was that the whole exceeds its parts specifically because of its capacity for life and habitat, not because the parts are individually excellent.

The same session gave the plainest version of what reciprocity means here: when the garden has abundance it shares with people who could become gardeners themselves, who are given tools and skills, and when their own gardens flourish some of that returns to the first garden.

Third space

A place that is neither home nor work but something generative in between. The group wanted the term for two reasons: it describes an aspiration, and it names a loss, since third spaces have been broadly collapsing. Meeting 4 added a hard economic consequence. A true third space is historically free or very nearly free to be in, which means membership fees cannot remain the primary revenue stream if the phrase is to be honest.

Concentric circles of belonging

An answer to the perennial question of who counts as part of RegenHub. The cooperative draws a clean legal line, since you have either signed a member agreement or you have not, but the group was explicit that the legal boundary should not become the social one. The picture instead is rings: a core nucleus of cooperative members, then people who pay for the space without joining the cooperative, then people who come to happy hours and enjoy the scene, then the wider field of people who might one day. Growth means inviting people inward, not policing the edge.

Orientation over output

The membership test the group actually uses, arrived at by working through cases. They would decline someone collecting a paycheck with no projects, no curiosity about what the community is building, and no interest in growth. They would welcome someone in the same professional position who finds the work compelling and wants their life to move that direction. A student with no path figured out but genuine excitement is in.

Nobody has to be doing explicitly impact-oriented work. What matters is a current of community care running underneath whatever the vocation is.

Two piles

A blunt and useful description of what actually happens in the building. One pile is people showing up to help RegenHub be RegenHub: artwork, cleaning, infrastructure, cultivating the community. The other pile is individual projects people work on within the walls. Both belong in the structure, but forcing them through one set of member classes would mean routing every project through a single entity, which is both a headache and untrue to how the place works. This observation is a direct ancestor of the dual entity decision six meetings later.

Bioregional resilience and localism

Two words the group asked to keep in the purpose statement. Bioregional resilience grounds the cooperative in place and in care for the living world without narrowing it to environmentalism, with the Front Range as the natural anchor. Localism names an orientation toward the local economy that stays connected to wider networks without dissolving into them.

A second home

From the round-robin visioning exercise, and worth keeping for tone alone. The wish was for a place where members feel they have a vibrant scene of their own.

Retrofitting existing civic infrastructure with community

From the Neighborhood Village Project presentation, and the sharpest counter-frame to intentional-community thinking in the whole record. Rather than build new towns or buy land in remote places, you infill community back into the neighborhoods and civic structures that already exist. The underlying theory of change is almost embarrassingly simple: people already live where they live, and the coordination problem of getting everyone to move somewhere better is harder than the problem of getting neighbors to know each other.

Cosmo-local hubs

A frame borrowed from a Network Nations working group mapping physical, place-based spaces that belong to a global solidarity network. It gave the group language for being deeply rooted in Boulder and simultaneously a node in something wider, without the two competing.

Qualification over quantification

The first and most durable resolution of the central tension. The goal is not to assign a financial value to every contribution but to build language and categories that make different kinds of value visible. Tracking something and pricing something are separate activities, and the cooperative can do the first without committing to the second.

The commodification tension

Worth preserving as a tension rather than a conclusion, because it never fully resolved and probably should not. Several people were uneasy that reducing gifts to metrics shifts motivation from intrinsic to extrinsic. The same people wanted their particular gifts recognized and reflected in the structure. Both feelings were sincere and they pull opposite ways. Every recognition mechanism discussed across fifteen meetings is an attempt to hold both.

Gratitude as a patronage mechanism

Some contributions resist accounting entries. Community energy, culture-setting, the intangible social work of making a room feel good: these may be better recognized through collective expressions of appreciation than through ledger lines. The reference point was Giveth's retroactive praise system, where peers recognize each other after the fact rather than bidding beforehand.

Trust, not reputation

A deliberate refusal. The group pushed back on reputation systems and social credit scores as models, and named trust as the better indicator. The difference matters: reputation is a score others compute about you, while trust is a relation you are inside of. One can be gamed at a distance and the other mostly cannot.

Symbols over numbers

A speculative but revealing proposal: instead of a single trust number, members might be represented by different symbols, a heart or a spark or a mushroom, reflecting the character of a contribution rather than its quantity. The idea itself matters less than what it protects, which is the principle that contributions are qualitatively different rather than hierarchically ranked.

A class matrix, not a class ladder

Tiers and levels imply hierarchy, which cuts against the cooperative's whole disposition. What the group was actually building is an expressive framework that rewards emergent participation, not an assertion of rank. Member classes describe how someone shows up, not where they stand. The metaphor moved from climbing rungs to inhabiting a field.

Goodhart's Law

Named early and treated afterward as a design constraint rather than a warning. When a measure becomes a target it ceases to be a good measure. The community's earlier experiments with contribution tracking had deliberately avoided leaderboards and points for exactly this reason. The stated preference was for non-binding, iterative accounting methods rather than a fixed system locked in at formation.

Resources, Events, Agents

An accounting ontology from William McCarthy's 1982 work, introduced as the binding language between different member specializations. The argument against conventional double-entry bookkeeping is that debits and credits capture only a second-order effect of value creation, namely profit. An ontology of resources, events, and agents can recognize resources of any type, events as the moments where value is created or exchanged, and agents as people, organizations, or even the relationships between them.

The practical consequence is that a codebase or a community tool can be described as common property of the cooperative, emerging from several specializations working together, without anyone having to price the labor that made it.

First-order and second-order contribution

A two-level framework for patronage. First-order contributions follow from a member's own specialization: the developer writes code, the community builder organizes, the strategist shapes brand and culture. Second-order patronage workflows combine several specializations into something none could produce alone. A hackathon needs community organizing, technical development, and event logistics at once. The second-order layer would be defined by the group rather than by any individual, because it belongs to no one.

Multi-capital, and the trouble with the word capital

The recurring case for recognizing intellectual capital such as software and infrastructure, social capital such as relationships and community building, and material assets alongside financial flows. Conventional bookkeeping still handles the money; the expanded view makes the rest visible.

Meeting 5 questioned the word itself, preferring simply multiple forms of value or plurality of value. The objection is not decorative. Calling something capital already implies it can be accumulated and deployed, which is most of what the group was trying to avoid assuming.

Collective identity over individual accounting

The reframe underneath the whole recognition problem. The transactional posture is I put in X and get out Y. The cooperative posture is that each person brings their own gifts and everyone benefits when any one of them succeeds. Participants described the shift from individual transaction to collective co-investment as feeling meaningfully different, not merely worded differently.

Peer appreciation over reputation scoring

Recognition should flow peer to peer rather than accumulate as a rating. The distinction from the trust entry above is one of mechanism rather than principle: this is about the direction recognition travels, sideways between members rather than upward into a scoreboard.

Sweat equity

The question of how capital contributions might account for work that generates no revenue, making that work eligible for patronage. It returned in Meeting 9 in a different key, when the attorney raised a founding member class as a way to recognize the organizing group's unpaid effort. The group's instinct leaned toward one member, one vote, and the founding class never generated much enthusiasm.

Giving, saving, investing together

A layered model of economic relationship, ordered from highest trust outward. Giving together is the innermost circle, closest to kinship, where a dollar given carries no attachment. Saving together is mutual aid and rough reciprocity, drawing on rotating savings and labor-pooling traditions found across Islamic finance, Latin American and African informal economies, and some Christian communities. Investing together is the outer ring, where trust exists but risk is higher and expectations of return are explicit.

Meeting 5 turned the three layers into three capital pools: a giving pool for unrestricted community benefit, a saving pool aimed at asset acquisition and eventual building ownership, and an investing pool for higher-risk allocations to member ventures.

Community reinvestment in lieu of profit sharing

The clearest single decision in the entire series, and it came from a plain preference test. Offered a choice between each member receiving a discretionary check and the same money reinvested in the community in ways that help others succeed, the group chose the second without much hesitation. Members have their own projects and income; what the cooperative provides is cultural support and infrastructure. Revenue goes toward paving the roads.

Upward spirals

The recurring shorthand for the feedback loop the cooperative is trying to start. Coordinating creates conditions for growth, which feeds back into more coordination. Ventures that emerge from the space return some portion to the treasury, which reduces dependence on desk fees, which makes the space more accessible, which brings in more people who start more ventures. It is the same structural claim as the garden, expressed in the language of systems rather than growing things.

Capital allocations instead of loans

Rather than lending money against a promise of interest, the cooperative would make allocations from its pools. The receiving group agrees to return a percentage of value to the pool. Structurally this resembles interest; functionally it is a revenue share and an extension of patronage. The distinction the group cared about is that it is reciprocal rather than extractive, and it runs through the cooperative's own governance rather than an external creditor relationship.

Mutual staking

From Protocols for Post-Capitalist Expression, published by the Economic Space Agency, and the theoretical frame that most caught the group's imagination. Value is recognized through performances, defined broadly enough to include building something, organizing an event, or simply showing up and caring for the space. When one member stakes on another's performance, that itself is a reciprocal exchange of value.

The most grounded version: paying monthly dues is already a mutual stake. The member stakes in RegenHub and RegenHub stakes in the member. Meeting 6 proposed testing the idea concretely with receipt tokens, where staking on a project causes the project to stake back on you.

Distributed credit issuance

Also from the ECSA framework. If anyone can issue credit to anyone, credit is abundant rather than scarce, and there is no reason to charge interest for it. Credit becomes a public good that keeps an economy flowing rather than a rationed resource controlled by intermediaries.

Decoupling money from value

Currency is a medium of exchange and a mechanism for credit. It is not itself the measure of worth. Value is instead determined by a network of mutual recognition, which the summary renders as what I value and who values me. Price becomes one signal among several rather than the single index everything collapses into.

The ecological economics version of the same point: markets do decentralized price discovery reasonably well, but when everything reduces to price, non-priced value simply stops appearing.

Streaming patronage

A speculative thread with a real design instinct in it. Instead of static quarterly dividends, patronage could flow continuously, with each member choosing how to redirect their flow back into the giving, saving, or investing pools. Superfluid was named as one possible implementation. The group noted that conventional token designs still carry a good deal of fiat monetary logic, and wanted something more ecologically shaped.

The sliding scale, and the cash problem it cannot solve

The ideal was stated plainly: everyone pays what feels right, everyone contributes their gifts regularly and organically, and the per-person rent burden falls as more people join. In practice this means a suggested baseline, individual conversations to find a workable number, three-month check-ins, and no emotional pressure about when someone will pay more.

The group then named the limit honestly. A prospective member had offered to DJ monthly and host musical events in exchange for reduced fees. The contribution is genuinely valuable. Rent still requires cash. They did not resolve this and did not pretend to.

Ecological credits as currency backing

From a case study of a worker-owned housing cooperative in Baltimore holding roughly twenty properties, financed by Seed Commons and employing people leaving prison or recovery in the renovation work. Because the cooperative held concentrated real estate, it could pursue water credits from the city for rain gardens and green space, and carbon credits for sequestration through soil health and tree planting, verified by satellite. Those credits are cash flow, and in the more speculative version they could back deposits for a local currency.

The larger claim was that fiat is not stable at the local level, and a local currency backed by ecological stewardship links environmental care directly to economic resilience.

Normies with hope

An affectionate description of most neighborhood program participants, who are not aware of and not especially interested in local currencies or blockchains. It is included here because it carries a discipline: the tools wait for readiness rather than arriving ahead of it.

Set it and forget it revenue

The revenue disposition that fits a cooperative with no full-time staff. Software with low operational overhead producing a slow drip of income, where several such products each contributing modestly eventually compose into something meaningful. Offered in the context of an unconference scheduling app built collaboratively at the hub.

Speaking two languages

The cooperative has to be fluent in two registers at once. One is the language of capital, in which it is a business selling desks, hosting events, running data infrastructure, and perhaps operating a venture studio. The other is the language of public benefit, in which it stewards regenerative public goods and community infrastructure. Everyone associated with the place should be able to speak both. The claim was that these are not in tension but are complementary wings of the same venture.

Revenue as leverage, and the finder's fee

Two pieces of practical economics from the same session. The first is a framing: more revenue means more optionality, which is a different argument for making money than growth for its own sake. The second is a small policy with outsized signal, a ten percent finder's fee for grant applications paid to whoever spots the opportunity and does the work, plus base compensation regardless of outcome. It prices the labor of noticing.

The fifty-fifty split, tilting outward

The first concrete revenue-sharing framework in the record, proposed for the education program. An even split between the program steward's own entity and the cooperative to start, with the expectation that it moves to seventy-thirty or eighty-twenty in the steward's favor as the program scales, so that the cooperative's shrinking percentage represents a growing absolute amount. It is a small design with a large disposition inside it: the cooperative takes proportionally less as a venture succeeds.

Two practical drivers

Worth stating first because everything else grew from it. The space ran collectively but its legal and financial liability sat with one person through an existing company, and members contributed toward rent while that same person covered the gap. Both facts were uncomfortable. Formalizing the structure would bring the legal reality into alignment with how the place already worked. Every philosophical thread in this book hangs off that unglamorous starting point.

Pace layering

Stewart Brand's model applied to the three formation documents, and probably the single most useful organizing idea in the legal work. Articles of organization are the slowest layer, filed with the state and changed rarely. Bylaws are the constitution, amendable by board vote and state filing. Member agreements are the fast outer layer, living documents updated by member vote without any filing at all. Put the things that should change slowly in the slow layer and the things that must adapt in the fast one.

Public benefit as a governance channel

Any Colorado cooperative can form as a public benefit entity by putting specific commitments in its articles: to operate sustainably and responsibly and to produce a material positive benefit that the organizers define. There is no ongoing fee. The obligation is an annual report, which can be a few narrative paragraphs. Standing to enforce belongs to members, not the public.

The detail the group cared about most is procedural. Weakening or removing a public benefit commitment requires a two-thirds member vote, higher than a standard amendment and raisable further in bylaws. Meeting 15 returned to this in a wider frame, contrasting public benefit status that exists on paper with structures that give the public interest an actual seat. The lesson taken was that values anchored in governance survive better than values held as intentions.

Three membership tiers

The simplification that stuck, replacing confusing part-time and full-time language. Community participants attend events and use day passes, with no formal membership but recognized presence in the ecosystem. Coworking members pay, have door codes, use the space, collaborate on projects, and can host events, but do not govern. Cooperative members have made a commitment to the cooperative itself, including some buy-in, and hold full governance rights under one member, one vote.

The path runs through the middle tier. You start by coworking, and if the fit is mutual on both sides, you join the cooperative. The change was implemented on the website during the meeting itself.

Provisional membership

The attorney's suggestion that the group liked most immediately. New members join for a defined period, six or nine or twelve or twenty-four months, with full or partial rights, giving both the person and the cooperative a chance to assess fit before permanent co-ownership. The argument for it is really an argument about the alternative: without a trial period, removing someone requires an adversarial process where a meeting is convened, a case for removal is made, and the person responds. Provisional membership is kindness disguised as procedure.

The investor member class

The distinctive strength of Colorado's cooperative framework, and the reason the LCA was attractive rather than a more conventional cooperative form. Investor members hold capital accounts, their patronage is defined by their capital contributions, and they do not vote unless they also hold another class. This makes the structure genuinely fundraisable, where cooperatives have historically struggled. The recommendation was to include the class at formation even in basic form, since it costs little and preserves future options.

The project member class

An idea raised while trying to figure out where the EthBoulder event should live. A group of members forms a project, and the project itself becomes a member of the cooperative, with its own governance scope distinct from the cooperative's. It would let a project operate with real autonomy while staying connected to shared infrastructure, and the pattern would be repeatable across a portfolio of ventures.

Subchapter T

Corporate tax treatment, and the reason a cooperative would want it: net profits can be allocated by patronage activity, so more active members receive more and less active members receive less, adjusting year to year. Sabbaticals and reduced participation stop generating resentment. It is also the only place in the tax code where an entity can toggle between paying tax itself and passing the obligation to members, which avoids double taxation. To pass through, at least twenty percent of what is allocated to a member must be distributed in cash, with the remainder held in that member's equity account and repaid on a multi-year track at withdrawal.

The cost is significant. Under Subchapter T, active worker-owners are presumptively employees, which means payroll, wage and hour compliance, and minimum wage.

Subchapter K

Partnership tax treatment, which sidesteps employment law entirely. Everyone is self-employed, so there is no payroll, no wage and hour compliance, and no work authorization requirement. The cost is symmetrical to the benefit: profits are shared equally regardless of involvement, which produces its own resentments when participation diverges sharply.

The group's read was that most activity at the hub is not paid client work, that all contributions should be positioned as voluntary, and that partnership treatment fit the actual shape of the place. This is the path they took.

The dual entity strategy

The structural resolution of the Subchapter T and K tension, and the most consequential design decision in the series. Two entities, each doing what its subchapter does well.

The first is a cooperative taxed as a partnership whose members are individuals. It holds the lease, moves liability off one person's company, governs the shared space, and hosts the informal life of the community. Everyone shares equally, everything is voluntary, nobody is on payroll.

The second, deferred, would be a cooperative taxed as a corporation whose members are organizations rather than people. Because entities rather than individuals are the members, employment law is not triggered even under corporate treatment, which unlocks capital accounts and patronage-based allocation. Members participate through their own companies. The partnership itself could be a founding member of it.

Venture cooperative, or venture commons

A concept the group found itself needing a word for, because cooperative vocabulary did not have one. Consumer cooperatives coordinate around purchasing. Worker cooperatives coordinate around labor. What this group wanted to coordinate around was investment in a shared portfolio of projects, where the investment might be money but might equally be time, skill, or assets. Revenue sharing and equity sharing were distinguished as separate layers beyond simple expense sharing.

The nearest existing frame was the synthetic commons from the ECSA protocols: members allocate part of their surplus to a common asset profile, and how much they allocated determines how much they can draw.

The multi-stakeholder warning

The attorney's cautionary example, which the group should probably keep. A restaurant cooperative in Austin combines consumer and worker member classes. Consumer members want lower prices. Worker members want higher wages. When both classes vote and hold board seats, those interests collide structurally rather than occasionally. The standard remedy is making the consumer class non-voting, preserving their economic benefits while keeping governance with workers.

The group's answer was that its classes are levels of participation rather than distinct roles, and that people move between them as engagement deepens. Whether that avoids the problem or postpones it is an open question.

Consent, not consensus

A decision-making posture with a low and honest threshold. Rather than requiring full agreement, the question is whether something is good enough to try, with the understanding that it can be revisited. The claim in its favor is simply that more decisions actually get made.

A companion position was argued in the same session: one member, one vote, optimizing for positive-sum coordination rather than detailed accounting of who did what.

Legal wrapper for legibility

A working philosophy borrowed from another cooperative in the network, and arguably the group's actual operating theory. Maintain a clean legal shell for the things that need one, bank accounts and contracts and fiduciary structure, while doing the experimental and unusual work in good faith alongside it. To the state the entity looks one way; among members, practice runs more fluidly. Compliance as baseline, community norms as the living layer.

Bylaws make coordination possible without prescribing it

A useful division of labor. The bylaws mandate that members have capital accounts and set the rules governing them. They do not need to specify how pooled resources get allocated in any particular case, whether that is investing in a member's project or sponsoring a partner or seeding a matching pool. Those decisions can run through committees and member input. The bylaws provide legal protection for coordination; they are not the coordination itself.

The articles are the seed

What actually gets filed is modest: a purpose statement, a list of founding members, and a registered agent, running about three pages. Because the cooperative has an office it can serve as its own registered agent, and members used that address rather than home addresses. The bylaws and member agreement follow and are amendable afterward. The articles are the seed; the rest is the structure that grows from it.

The purpose statement as a commitment you can be held to

The balance the group worried about across four drafts. Filed purpose creates a real legal commitment, since in any dispute the cooperative would have to show adherence to it. Too specific and the cooperative constrains its own evolution. Too vague and the public benefit promise means nothing. Meeting 3 had already raised the accountability version of this: would the group be answerable for every aspiration in an annual report?

The phrase that survived the compression, from Meeting 11:

Synthesis and simplified

A lesson about translation that generalizes well beyond purpose statements. Two drafts were prepared from the same visioning transcripts. The synthesis version kept the group's own jargon and aspirational reach; it hit the right themes but felt vague and overcommitted. The simplified version was grounded and easy to say yes to; it had lost the enthusiasm, the specificity, and the group's own voice. Neither was right. The instruction was to weave them, finding something legible to the state and still alive with the community's energy.

The lease, not the building

A distinction that had to be held steady through a lot of enthusiasm. Building purchase was raised in the first meeting, with the three-story building valued somewhere between $1.7 and $4.2 million and a conservative down payment around $500,000. Meeting 2 called it moonshotty and named the more grounded goal, which is a continuation path when the lease expires. Meeting 11 stated it plainly: for now the cooperative shares the expense of a lease. Ownership remains a long-term aspiration.

Deadline as forcing function

The formation ran on external dates rather than internal readiness, which is worth noting because it worked. A clean accounting cutover at the start of the calendar year, and a conference in February where the group wanted to be able to say the cooperative exists rather than describe it as a project attached to someone's company. A comparable formation had previously taken about a year. This one took six months, at roughly one hour per week.

Techne

The Greek root of the word technology, but originally naming the place where art and craft were indistinguishable. It described the philosophy and practice of bringing something into reality through skilled making. The name was chosen for the educational program on the day the articles were filed, and it carries the group's position on tools: they are extensions of human capability rather than substitutes for it.

Augmentation over automation

The philosophical claim underneath the name, and the one with the most economic content. Automation puts a tool in place of a person. Augmentation puts a tool alongside them. The version that makes this more than a preference: if these tools sit on the capital side of the ledger, they tend toward replacing labor. If they sit alongside labor as augmentation, they support a different economic relationship entirely. The same technology, differently placed, produces opposite politics.

Communal design

A methodology from a member's design practice, developed over a year-long engagement. Rather than managing clients through static review cycles, they are invited into the design files themselves, observing and participating from first sketches through delivery. The argument is that genius comes from anywhere, and that including clients, stakeholders, and even peripheral participants in the live process produces work that is both more creative and more thoroughly tested. It requires real confidence, since controlled reveal is replaced by continuous transparency.

It borrows from engineering's perpetual beta: continuous testing, fast iteration, and a willingness to discard. Described also as active requirements gathering, where steady creative cadence prevents scope drift from becoming an expensive surprise. Meeting 13 proposed applying it to the cooperative's own identity work, on the grounds that the inputs had to come from the community rather than from one designer working alone.

Single source of truth

A design systems idea extended into organizational design. In a brand system, a single repository holds the design tokens, the colors and typefaces and spacing, so that one change propagates everywhere. The proposal was to ask what that would mean for an entire organization: a place where a change ships once and lands coherently across the whole, rather than fragmenting across siloed tools.

The group recognized the problem immediately from its own life. Five messaging platforms, each holding different threads of the same conversations. The engineering principle behind it was named too: each piece of state should be owned and modified in one place, with clear boundaries preventing components from reaching across to change what they do not own.

Admin as opaque power center

Perhaps the most quietly radical claim in the record. Every organization has three irreducible administrative functions, accounting, finance, and legal, and in conventional corporations these operate as opaque power centers. Accounting controls the books, finance controls leverage, legal controls agreements. Those three perpetuate an organization's norms and behaviors more reliably than any stated mission. Meaningful systems change at the corporate level therefore requires making these functions transparent rather than reforming anything more visible.

The implication for the cooperative was left implicit but is not subtle. Designing the accounting, financial, and legal infrastructure is not procedural work. It is the mechanism through which stated values are either embodied or quietly contradicted.

The distributed hub model

An agency structure worth borrowing. Rather than hiring contractors under the agency's own entity, they are hired through the client's organization. This teaches clients to build and manage their own creative teams, removes agency overhead, and makes the team modular, so people can join or leave without disrupting the whole. The detail that carries the ethics: everyone on a project is paid the same rate, which eliminates the tensions that grow where pay is uneven and authority is ambiguous.

The bookends

An observation about onboarding and offboarding that became a discipline. Branding work pushes clients through an intense creative process, and many experience something like regret afterward even when the work is strong. Without designed processes framing the beginning and end of an engagement, the container that holds the creative work is weaker. Business starts and ends at the bookends, and they are usually the least designed part of it.

Community data trust

The stewardship logic of a community land trust applied to digital infrastructure. Buying a lot in Boulder might cost millions; buying a server costs a thousand dollars and has generative capacity that depends entirely on what runs on it. Members offered hardware they already owned, and the pooled total was estimated at a thousand dollars of existing machines. It was framed as a small, low-risk experiment in collective infrastructure ownership that could lead to larger ones.

The information right

The community data trust taken to its full aspiration, and the most far-reaching sentence in the later meetings. What if the cooperative committed to holding this building for a hundred years as information infrastructure, the way a land trust commits to holding land for housing? The claim is that there is an information right standing alongside the housing right, and that the first century of computing was shaped by corporate co-option of tools originally conceived as instruments of collective coordination. A locally hosted, solar-supplemented micro data center was imagined as a small tangible expression of that.

Web 2.5

Used approvingly rather than dismissively. Blockchain infrastructure provides the backend properties worth having, permissionless, persistent, verifiable, accountable without being identifying, while the experience stays entirely familiar. In practice this meant tapping a card to check in, to vote, or to transact, with everything underneath abstracted away. Verifiable anonymous neighborhood voting was the worked example: participants proven to be actual neighbors, individual votes private.

Tools follow expressed need

The design principle governing a proposed portfolio of neighborhood tools, and a direct rebuke to technologist habit. Tools emerge from what people say they want, not from builders arriving with solutions. Neighborhoods would self-select from a menu rather than be assigned. The tools would be white-labeled, each community naming and shaping its own instance, but networked underneath so coordination across neighborhoods remains possible.

The proof case was a technologist who built a simple offers-and-needs board for his neighborhood only after learning what his neighbors actually wanted.

Plain-language change requests

A small piece of infrastructure with real governance consequences. Anyone with an account can open an issue on the website repository describing a change in ordinary language. A developer or an assistant generates the change, an administrator reviews and approves, and the site updates. The group tested it live and changed the membership language during the meeting. The point is not the tooling. It is that a non-developer can alter what the cooperative says about itself, through a reviewable process, in minutes.

Studio Night and the third object

Recurring evening sessions for side projects and passion projects, oriented around what the group called the third object: the thing beyond your main work that you want to tinker on and ship. The distinction from ordinary coworking is precisely that it is not your primary work. Light facilitation, people mostly in their own bubbles but able to connect. The revenue thought attached to it was that these evenings become the place where prototypes get carried across the gap to launch, as a crew rather than alone.

Mutual interviews

The chosen method for skills mapping, and a small but pointed methodological preference. Not solo questionnaires but real-time dialogue between members, because feedback and nuance and the discovery of unexpected fit only happen in conversation. The occasion for it was the realization that valuable experience within the group was simply unknown to the group.

Project presentations as formation record

A practice worth naming as a practice. For several sessions, the meeting time was given over to one member presenting their work in depth, so that the full context of what each person brings became part of the permanent record rather than folklore. It is an unusual thing to spend formation time on, and it produced several of the most substantive entries in this book.

The knowledge graph as intellectual property

Prompted by a visiting cooperative scholar's talk, the group considered recording such talks and building them into a structured knowledge graph. The striking part was the assessment attached: that this accumulated understanding might be the cooperative's core intellectual property. Not the software, not the brand. What the place knows.

The flywheel

The final assembly of the pieces, stated on the day of filing. The school brings people into the network. Those people start ventures. The ventures create deal flow for the venture studio. The studio generates returns that can be reinvested in the school and the cooperative. Each layer reinforces the others. It is the upward spiral from Meeting 1 with actual named components in it.

Fruiting

The soil metaphor completing itself in the last meeting of the series. The education program was described as one of the first fruiting projects in the ecosystem: a living structure grown from the soil that had begun producing something. The three questions put to its steward are the ones the cooperative will presumably keep asking of every venture that grows in it. What do you intend to cultivate here. What do you want to retain for yourself. What reciprocity do you imagine flowing back.

The taproot

An aspiration recorded and explicitly held as aspiration rather than plan. If the annual event grows as a project of the cooperative, it could become a deep and stable source of support, enough eventually to underwrite building acquisition and land-trust-like stewardship of commercial real estate. The group put it on the record as a possibility in the field, not a commitment.

Building the bridge

From a discussion about a potential anchor tenant whose political orientation differed from the community's. The framing offered was that the cooperative is building a bridge between different political and cultural orientations, and that the bridge-building is part of what it offers rather than a cost of doing business. The condition attached was honest: it requires genuine comfort from everyone, and members were encouraged to evaluate the relationship in both directions.

This has an earlier echo. Meeting 4 described how the culture shifted over time toward community care through what was called soft power, creating friction with members whose worldview did not fully align, and resolving not by policy but by the orientation simply becoming the culture.