Civic knowledge rarely accumulates in a durable way. Movements build understanding, identify patterns, develop language for explaining a problem — then the moment passes, the organization dissolves, the platform shifts its algorithm, or the grant cycle ends. The next wave of people arrives and starts nearly from scratch. The institutions they are trying to change do not work that way. That asymmetry is one of the most underappreciated advantages that entrenched power holds over civic effort.
This piece develops the argument introduced in Core Ideas #8 of this project. The first part examines why civic knowledge fails to accumulate and what it costs when it doesn’t. The second part takes up a related but distinct question: even when civic work does produce lasting knowledge, who owns it? The platforms and organizations that hold civic labor as an asset are reproducing a version of the same extractive dynamic that civic work is often trying to address.
The reset problem
Civic engagement is episodic by nature. It spikes during crises, elections, regulatory windows, and moments when public attention briefly converges on a particular failure. Then the moment passes. Attention moves. The organization that formed around the issue loses its funding, its staff, or its urgency. Participants return to the rest of their lives.
What dissipates along with the energy is the knowledge built during the active period. Which arguments landed and which didn’t. What the institutional counterarguments were — the specific ways that agencies, lobbying groups, and legislative staff deflected pressure. Who the key actors were and how they behaved under scrutiny. What was tried, what worked, and what failed, and why. None of this is obvious to someone arriving at the issue fresh. All of it is perishable if there is no structure to preserve it.
The result is that each new wave of engagement rediscovers patterns that prior participants already mapped. The questions asked in one legislative cycle are asked again in the next. The arguments made in one decade’s public comment period are reconstructed from scratch in the next decade’s. This is not because the later participants are less capable. It is because the knowledge produced by the earlier participants was not organized for retrieval by the people who came after them.
This problem is not unique to civic life, and its solution is not a mystery. The early labor movement was episodic and fragmented; over time, federations built institutional infrastructure — training programs, legal research, legislative tracking, model contracts — that meant each new organizing campaign did not have to reinvent the underlying framework from first principles. The civil rights movement developed systematic legal strategies through organizations like the NAACP Legal Defense Fund, which maintained continuity across decades and built case law deliberately rather than opportunistically. The environmental movement developed institutional expertise that persisted across multiple political cycles. None of this eliminated setbacks, but it changed what was possible. When movements failed to build comparable infrastructure, they paid for it repeatedly: the same lessons relearned, the same institutional counter-strategies succeeding again.
What civic amnesia actually costs
The clearest illustration of the reset problem may be the history of prescription drug pricing advocacy. As NPR reported in 2019{target=”_blank”}, Senate hearings on pharmaceutical prices in 2019 were essentially identical in substance to hearings held in 1959 and 1960 — the same arguments about transparency, the same executive defenses citing research and development costs, the same proposals for generic competition. As Johns Hopkins drug-industry historian Dr. Jeremy Greene told NPR, “Every decade since the Kefauver hearings has seen at least one set of congressional hearings into the increasing prices of prescription drugs.” The industry’s primary counter-argument — price controls threaten innovation — has been deployed successfully since at least 1959. Advocates, working without an accumulated record of what had already been tried, encountered the same institutional resistance without the benefit of the full prior history.
This pattern repeats in local governance, where it is even less visible. Community knowledge about how a particular city agency behaves — which commitments it has broken, what pressure worked in the past, which officials respond to which forms of accountability — is rarely documented and rarely survives the departure of the individuals who held it. When those people leave, move away, or disengage, the knowledge leaves with them. The next round of civic engagement begins from a vague sense that something is wrong, with no systematic record of what was already established.
Legislative cycles compound the problem. Bills that fail in one Congress are routinely reintroduced in the next with limited institutional memory of why they failed or what changed the political calculation the last time. The staff who managed a bill’s prior effort may be gone. The advocacy organizations that pushed it may have restructured. The documentation of what happened — the negotiating history, the amendments that were considered and rejected, the specific objections that killed it — exists in scattered form, if at all, and is rarely organized for use by the next group of people who need it.
Meanwhile, the institutional actors who benefit from the status quo maintain continuity with considerable sophistication. Industry associations, lobbying firms, and institutional legal teams keep records, track legislative history across decades, and maintain relationships through staff and personnel changes. They know what was tried before and which arguments worked against it. This is not a conspiracy — it is just good organizational practice. The striking fact is that civic groups, working against far greater resource constraints, so rarely develop comparable institutional memory. The result is an asymmetry that compounds over time. The conversation about what makes civic engagement ineffective focuses on organization, resources, and access. Institutional memory rarely gets its own category. It should.
Why knowledge doesn’t accumulate — the structural reasons
Civic knowledge fails to accumulate for structural reasons, not personal ones. Four of them recur consistently.
First, most civic organizations are built around campaigns, not infrastructure. They have a goal, they pursue it, they win or lose, and then the organization either dissolves or redirects its attention to the next urgent thing. The knowledge generated during the campaign is instrumental to the campaign — it serves the immediate fight. Preserving it as a public resource for the next round of engagement is not the mission, and so it is not done.
Second, funding structures do not support maintenance. Grants fund projects and deliverables, not infrastructure. Maintaining a repository of accumulated knowledge — updating it, organizing it, keeping it accessible as the underlying situation changes — is exactly the kind of work that is structurally hard to fund. It produces no visible deliverable at the end of a grant cycle. It is not a campaign. It does not generate the kinds of outcomes that go in a funder report. And so it does not get funded.
Third, platforms own the output. The majority of civic work that happens online — analysis, organizing, documentation, argument development, network-building — takes place on infrastructure owned by someone else. Social media platforms hold the posts, threads, and communities where this work happened. When a platform changes its policies, restricts access to old content, sunsets a feature, or simply degrades, the work is gone. The people who produced it have no claim on it. This is not an incidental risk. It is the default structure of civic work in the digital era.
Fourth, there is no common format and no common place. Even when civic organizations do preserve their work, it is scattered across incompatible repositories, institutional websites, personal drives, discontinued platforms, and PDF archives that are not searchable or cross-referenced. The fragmentation makes retrieval nearly impossible for anyone who did not produce the original work. Knowledge that exists but cannot be found is functionally equivalent to knowledge that was lost.
These four structural conditions interact. An organization built around a campaign has no incentive to invest in infrastructure. Without infrastructure, work goes onto platforms that own it. When those platforms change, the work disappears. And even the work that survives is scattered so completely that the next person who needs it cannot find it.
The commons model — what it means here
A commons is a resource that is collectively produced, collectively maintained, and openly accessible. The classic examples are physical: shared pastures, fisheries, irrigation systems. Elinor Ostrom’s Nobel-winning research{target=”_blank”} on how communities manage shared resources without either state control or private enclosure showed that commons are not inherently unstable. With the right governance structure, communities can sustain shared resources over long periods. The insight extends, as Ostrom and Charlotte Hess argued in Understanding Knowledge as a Commons{target=”_blank”}, to knowledge itself: knowledge produced by many can be governed and maintained as a shared resource available to all.
Wikipedia is the most visible working example of a knowledge commons in practice. It is collectively produced, openly licensed, free to access and reuse, owned by no single organization, and maintained through a governance structure that has evolved over more than two decades. The model has real limitations — coverage is uneven, editorial power is unevenly distributed, and maintaining quality across millions of articles is an ongoing governance challenge. But the structural principle is sound: knowledge produced through collective effort should be accessible to everyone who might need it, without a toll gate and without a single organization’s interests determining what is preserved and what is discarded.
Applied to civic work, a commons layer means the knowledge produced through civic engagement — the issue definitions, the argument maps, the documented history of what was tried, the policy analysis, the accountability records — is preserved in a format that is openly accessible, reusable, and not controlled by any single organization. This is a different thing from hosting conversations. A platform captures engagement. A commons preserves outputs. The distinction matters enormously for what is actually available to the next person who arrives at an issue and needs to understand what has already happened.
The difference is not just technical. It reflects a choice about who the knowledge is for. A platform that hosts civic engagement and holds the outputs is serving its own continuity. A commons that holds civic knowledge and makes it openly retrievable is serving the people who do civic work.
Why ownership matters — the extraction problem
When civic work happens on platforms that own the output, there is a structural dynamic worth naming plainly: the participants provide the labor, the platform holds the asset.
This is most visible in social media. The analysis, documentation, argument development, and network-building that activists do on Twitter/X, Facebook, or Instagram increases the value of those platforms. When a platform changes its policies, restricts access to historical content, collapses under new ownership, or simply makes it technically difficult to retrieve old material, the work is gone. The participants have no claim to it. The platform captured the value of their labor and retains it or discards it according to its own interests. The civic actors who produced it are left with nothing they can point to, retrieve, or build on.
But the same dynamic appears in less obvious places. Civic organizations that produce research and analysis and then restrict access to it through paywalls or membership requirements are making a version of the same choice — knowledge produced with civic intent is held as an institutional asset rather than returned to the public. Government processes that solicit public comment and then make that comment inaccessible or functionally unretrievable reproduce the same pattern. Foundation-funded projects that generate knowledge and then leave it in an unmaintained repository that nobody is paid to keep accessible are, in practice, capturing knowledge and then letting it disappear.
In each case, civic labor produces knowledge that does not return to the public that produced it. This is worth naming as a structural dynamic analogous to the broader power problems that civic work is often trying to address. The extraction of value from people who have little formal claim to the outputs of their own work is not only a labor market problem — it is a feature of how civic engagement is organized online and institutionally.
The commons principle is a direct response to this. The work belongs to the people who contributed it, and the structure should be designed to return it to them and to the public — not to capture it for institutional benefit, and not to let it disappear when an organization’s funding ends or a platform’s business model changes.
What accumulation actually looks like in practice
Accumulation is not a warehouse of documents. Knowledge that exists but is not organized for retrieval is not meaningfully different from knowledge that was never preserved. The test is whether someone arriving at an issue for the first time can find relevant prior work without already knowing it exists.
That requires specific things. Issue definitions that can be updated and contested, not just archived as artifacts of a particular moment. Argument maps that capture the range of positions and the evidence and reasoning behind each of them. Institutional histories that document what was tried, when, and by whom, and what the outcome was. Accountability records that track specific commitments against documented outcomes over time. Templates and resources that can be adapted rather than rebuilt from scratch each cycle. And contribution pathways that make it clear how new knowledge enters the system and how it is maintained as circumstances change.
Open-source software communities solved a closely related problem. In mature open-source projects, documentation is treated as a first-class output alongside the code itself — written for newcomers, not just for people who already know how the project works. Contribution models are structured so that partial engagement is productive. Version history preserves not just what decisions were made but the reasoning behind them. The README and CONTRIBUTING documents exist precisely to lower the cost of entry for someone arriving without context. The civic application is not identical, but the structural principle is the same: make it easy to find what exists, understand the history of why it looks the way it does, and contribute without starting over.
What America’s Plan is trying to build
To be direct about the current state of things: the commons and wiki layer described in this project’s design is not yet built. What exists now is a set of issue hub pages and background material that can be updated, linked, and built on. That is a partial version of what a civic knowledge commons would need to be, and it is worth describing honestly as a direction rather than a completed feature.
The intention is to develop a publicly accessible layer where the outputs of civic engagement are preserved, organized for retrieval, openly licensed, and maintained as a common resource — not locked inside a platform, not owned by this project, and not lost if this platform changes. The knowledge produced through organized civic work on specific issues — the definitions, the accountability records, the argument history, the documented experience of what was tried — would persist in a form that anyone could access and build on, whether or not they were part of the original effort that produced it.
The issue hub structure visible on this site is the beginning of that. Background material on specific issues can be referenced, updated, and used as a shared starting point rather than rebuilt each time a new person arrives. The full commons layer would extend this to include participant-generated knowledge, accountability records, and the accumulated output of issue-specific organizing over time. That is a longer-term goal, and it will require technical work and governance decisions about how knowledge enters, who can update it, and how disputes are handled.
For more on how this connects to the broader project model, see Core Ideas and Theory of Change.
The underlying logic is not complicated. Civic work that doesn’t accumulate has to be redone — the same arguments reconstructed, the same patterns rediscovered, the same institutional resistance encountered without the benefit of knowing it was already mapped. Civic work that accumulates but is held by platforms or organizations as an asset is still effectively lost to the public that produced it. The structure has to do both things: preserve the work and return it to the people and the public interest it was meant to serve. Those are not the same requirement, and meeting only one of them is not enough.
This article was researched and drafted with AI assistance under human review. See our full AI and editorial practices.