Commons
Collective.

Abstract

Research question. Under what conditions can collective bargaining institutions (CBIs) convert dispersed contributions to AI into effective agency, fair compensation, and sustained funding for shared knowledge, without privatizing the public domain or turning privacy into a luxury?

Thesis. A viable institution should aggregate negotiating mandates rather than indiscriminately aggregate data. It should distinguish three functions: buying AI services collectively; bargaining over uses that contributors can actually authorize; and financing public goods that no individual contributor owns. We call the coordinated arrangement Commons Collective. Its consumer-facing expression is a digital Costco: a community-governed buyers' and suppliers' club that uses scale for people, while maintaining distinct purchasing, contributor-licensing, and commons-finance functions. This is an analogy, not a proposed affiliation with Costco.

Method and contribution. This discussion draft combines a targeted literature and primary-source review with institutional comparison, legal issue-spotting, a technical permission-and-receipt architecture, and reproducible financial scenarios. It proposes a rights-aware knowledge object, a separated-governance federation, a commons-benefit covenant, and a staged empirical program. It does not report completed fieldwork, demonstrated bargaining gains, or a validated willingness-to-pay estimate.

Finding at the level of design, not empirical proof. Small individual data payments are unlikely to be a sufficient theory of collective agency. The stronger proposition combines purchasing savings, enforceable service conditions, contributor compensation where authority exists, representation for affected noncontributors, and public-good finance. Every component must survive a test against its own costs and possible harms.

Status: 18 September 2026; version 0.1; AI-assisted synthesis; not peer-reviewed. All monetary scenarios and institutional designs below are proposals unless identified as evidence. No funding, partnership, regulatory approval, or participant endorsement is claimed.

1. Research circle and ethical commitments

Session provenance and attribution

The requested research circle is Tomicah Tillemann, Beth Goldberg, Yorke Rhodes, Glen Weyl, Nick Vincent, Ilan Strauss, Sonam Jindal, and Anna Tumadottir (Creative Commons, as identified in the brief). Names reflect the brief, subsequent corrections, and the printed photograph where legible; affiliation details, attendance, authorship, and approval require participant confirmation. Inclusion is not a claim that any individual wrote, reviewed, or agrees with this paper.

Roundtable reference: Roundtable on Mechanisms for a Sustainable AI Data Economy | AI Disclosures Project. The convening page describes the 18 September 2026 working session at Microsoft Research New York and its focus on mechanisms across pre-training, post-training, and inference. It supplies context for this research, not participant endorsement of this draft. ^[S96]

At the user's request, the workshop source record now includes the original supplied photograph, a crop of every printed card, and AI-assisted visual transcriptions. The overall group brief appears below; each attributed direction is also placed beside the relevant research. The names and affiliations on the cards are preserved as printed, not treated as verified spoken quotations or endorsements. The photograph's association with 18 September 2026 comes from the supplied context, not image metadata. ^[S97]

The user also supplied an excerpt titled Blueprint for a Collective Bargaining Institution for Data in the Public Interest. Its coverage review distinguishes source wording, editorial interpretation, additions, and premises requiring qualification. The pasted excerpt was reviewed; the authenticated Google Doc and its other tabs were not independently accessed. Its author line is a source record, not automatic authorship of this publication. ^[S99]

Original group brief and directional source map

The photograph poses institutional questions; its claims about consensus, absent institutions, or browser mediation are not adopted as independently established findings. Original wording is retained so readers can inspect the framing rather than infer it from our synthesis.

Overall group brief / source transcription

Collective Bargaining & Institutions

There appears to be growing consensus that some form of collective management or bargaining institution is crucial to a sustainable data economy. Institutions that let dispersed data creators (individual workers, users of platforms, small publishers) bargain collectively with AI labs are largely absent. User-agents, such as browsers, currently don't mediate on this. There is a wide range of both terminology and substance around what such an ecosystem would look like. There is also some history about how those groups (who do represent data creators) have operated in the past in ways that seem opposed to the members that they are designed to serve. What is the right way to describe this ecosystem? What is the optimal scale of such institutions? How should they relate to each other? Can a government body serve the role effectively and efficiently? To what extent should they be novel to the AI data environment or connected to pre-existing institutions such as labor unions, collective management organizations, etc.? What is in the way of their formation: public awareness, policy, entrepreneurship, etc.?

This records a printed card, not a verified spoken quotation or endorsement. ^[S97]

Editorial alignment and coverage

The overall institutional brief: describe the ecosystem, identify legitimate representation, choose scale and relationships, compare existing and new institutions, and explain how they form.

The brief is now reproduced in section 1. Its questions are traced across institutional comparison, regulatory options, the research program, and the federation blueprint; these remain research questions rather than demonstrated outcomes.

• Define the institutional ecosystem and its relation to existing organizations
  3. The commons problem and the grazing analogy · 5. From digital Costco to a bargaining federation · 20. Follow-on research: a Commons Collective Framework Agreement
• Compare scale, coordination, public authority, and institutional formation
  16. Research program and falsifiable hypotheses · 23. Institution blueprint: a Commons Collective Federation · 29. Replicable sector collectives: blueprint and templates

View source context and full mapping

Alignment with repository-stated Ethical Tech CoLab principles

A pinned public-repository snapshot of Ethical Tech CoLab's website content identifies Field-grounded, Prototype-first, and Open by default as working principles. This is stored About-page copy, not verified wording on a rendered public principles page: the About route is disabled in the cited source. The public website provides organizational context. The separate ethical-AI paper emphasizes institutions, human-rights constraints, avoidance of harm, and participation by affected people. We use these as design references, not an invented official Ethical Tech CoLab charter or an endorsement of this research. ^{[S01] [S02]}

Interpretive boundary: openness applies to methods and accountability, not to confidential records. A member vote cannot waive another person's rights or legitimate community governance.

2. Method, scope, and limits

This is a scoping synthesis and design proposal, not a systematic review. Sources were selected for direct relevance to common-resource governance, data labor and leverage, applicable legal instruments, open licensing, philanthropic intent, provenance, consumer privacy, and energy demand. The evidence register distinguishes what each source supports from what it does not establish. Primary legal texts and official institutional publications take precedence over commentary for descriptions of rules and programs.

For a shorter standalone argument, read the prioritized first-draft paper. The library-led institutional example applies the design to one hypothetical open-education collective. Both are separate working drafts with their own abstracts, limits, and bibliographies; neither replaces the evidence boundaries of this living research record.

AI usage disclosure: the model-by-model usage audit documents a bounded local-ledger snapshot for the production of these materials using CoLab's usage-calc calculations. It distinguishes recorded requests and token charges from dollar-conversion assumptions, actual billing, human labor, and unobserved activity. The raw conversation and individual request records are not published; usage volume does not establish the quality or truth of this research.

The principal legal comparison is the European Union and United States. It is not a complete global survey, and rules differ within and beyond these jurisdictions. The original scoping review used sources accessed on 18 September 2026; later additions carry their individual access dates in the source register. Legislation, guidance, litigation, and product settings may change. A pilot needs a jurisdiction-specific legal memorandum immediately before launch, including current amendments and implementation schedules.

We use three epistemic labels in substance:

• Evidence: a proposition grounded in a cited source, including the existence or wording of a policy.
• Interpretation: a reasoned implication that is not itself directly established by the source.
• Proposal: a testable design choice, budget, threshold, or future legal intervention.

The publication provides inspectable settlement arithmetic and a fictional object, not a functioning cooperative, production data vault, compliance certification, payment processor, or deployed training-control system. Source selection remains vulnerable to Anglophone, institutional, and Global North bias. Later work should include multilingual community-led inquiry and a preregistered literature-search protocol.

3. The commons problem and the grazing analogy

What carries over from public-land grazing

The analogy is useful because an individually profitable activity can depend on collectively maintained resources. Public-land grazing offers an institutional vocabulary of access conditions, monitoring, stewardship, and charges. Commons scholarship supplies a deeper lesson: durable governance depends on legitimate boundaries, rules fitted to context, participation, accountability, and nested institutions, rather than an inevitable choice between privatization and unconstrained access. ^{[S03] [S04]}

For AI, the underlying commons includes maintained reference works, public research, language communities, public archives, software documentation, cultural institutions, and the social practices that continually renew knowledge. A developer may capture commercial value while underfunding this renewal.

Where the analogy breaks

Forage is physically subtractable: one animal's consumption reduces what remains. Copying information ordinarily does not use up the original. Economic models of nonrival data identify gains from broader use, but those results do not imply that every kind of sharing is socially desirable. AI-related scarcity appears in maintenance labor, attention, trustworthy provenance, privacy, community authority, energy, and the economic viability of future creation. Knowledge commons therefore require their own institutional analysis rather than a literal enclosure-and-rent model. ^{[S03] [S25] [S31]}

There is no single global owner of "the data commons" able to invoice every AI model. Nor is the absence of a universal mechanism the absence of all mechanisms: copyright licensing, subscriptions, public appropriations, philanthropy, procurement conditions, and existing collective management already allocate some benefits. Their coverage, legitimacy, and distribution are incomplete.

Proposal: commons-benefit covenant. A buyer voluntarily contracts to fund specified shared resources alongside any licensed inputs. The payment purchases stewardship, reliable access, curation, evaluation, or a contractual benefit commitment; it does not invent exclusive ownership of public facts. A mandatory levy would require an independently justified statutory basis. A covenant binds its parties, not the entire world.

4. A spectrum, not a single data commodity

The requested sequence is mass-public -> private -> professional -> synthetic. It is a useful conversational map, but not a legally ordered ladder. A professional work can be public; private records can contain copyrighted works; synthetic records can reveal private information or incorporate protected expression. Describe each asset along independent axes.

The four principal archetypes

Required descriptive axes

1. Access: public, gated, confidential, or highly restricted.
2. Legal authority: public domain, specified license, rightsholder mandate, employment assignment, contract, or unresolved.
3. Privacy and sensitivity: nonpersonal, personal, special-category/sensitive, or community-sensitive.
4. Origin and transformation: human-authored, observed, inferred, synthetic, or mixed, with derivation records.
5. Use: inference, retrieval, evaluation, fine-tuning, foundation-model training, or redistribution.
6. Structure: structured rows; semi-structured records; unstructured text/audio/image/video; relational or graph data; embeddings and model-derived representations.
7. Renewal and quality: static versus streaming; freshness; validation; contamination risk; maintenance costs.
8. Collective context: affected communities, shared authorship, correspondents, and restrictions on cultural use.

Implication: price must attach to a defined bundle of authority, service, quality, and obligations, not to an undifferentiated "data point." Greater structure may lower integration costs, but does not confer rights. An embedding is not evidence that copyright, privacy, or confidentiality obligations have vanished.

Research on recursive synthetic-data training shows failure modes under studied conditions; it does not establish that all synthetic data are defective. Synthetic generation can be useful when composition, evaluation, and retained real-world reference data are appropriate. This makes lineage and task-specific evaluation more important, not less. ^[S22]

Similarly, the EDPB rejects an automatic inference that a model trained on personal data is anonymous. Whether extraction or disclosure is reasonably likely needs assessment; this does not imply the opposite categorical claim that all models or synthetic outputs contain personal data. ^[S34]

5. From digital Costco to a bargaining federation

Photographed direction / source transcription

Tomicah Tillemann (Project Liberty).

Population-scale digital cooperatives as ownership structures that distribute AI value more broadly than the traditional corporate form allows.

This records a printed card, not a verified spoken quotation or endorsement. ^[S97]

Editorial alignment and coverage

Population-scale digital cooperatives as a route to broader ownership and distribution of AI value.

Member governance, buyer/supplier organization, and benefit return were already central. The ownership-versus-governance distinction and the trade-off between population scale and accountable representation are now made explicit.

• Design ownership and governance that distribute benefits rather than merely enlarge membership
  5. From digital Costco to a bargaining federation · 8. Payment, disbursement, and public-good return
• Compare nested, sectoral, and population-scale arrangements
  23. Institution blueprint: a Commons Collective Federation · 29. Replicable sector collectives: blueprint and templates

View source context and full mapping

The institution to build is a proposed Commons Collective Federation (CCF): a member-governed organization that buys accountable AI services, represents specifically authorized contributors, and funds independent commons stewardship. Its first product is an enforceable service agreement, not a universal data pool. The institution blueprint specifies the functions, mandates, governance, and bounded starting sequence. It supplies institutional support for a pro-human stack: technology whose human agency claims can be tested and enforced.

Two different forms of scale

The brief's "digital costo" is interpreted as a digital Costco, a membership-based aggregation analogy. Costco's own reporting supports the commercial relevance of membership and scale; it does not validate a consumer-owned AI institution or imply that Costco itself is a cooperative. ^[S16]

Demand-side scale: households collectively procure AI assistance, negotiate prices, portability, accessibility, retention limits, and dispute handling. A credible ability to switch suppliers is central. Purchasing leverage exists even when members provide no training data.

Supply-side scale: authorized contributors collectively negotiate compensation, attribution, permitted uses, audit, and remedies. Data-labor and data-leverage research motivates this possibility, but the bargaining effect depends on substitutability, model dependence, coordination, and legal authority. Neither a large membership count nor a large dataset proves scarcity or buyer willingness to pay. ^{[S05] [S06]}

Contribution is not coordinated withholding. The supplied notes distinguish relatively easy participation in multiple collectives from the harder task of sustaining a collective refusal. This is an organizing hypothesis, not proof that contribution is effortless or a data strike effective. Multiple memberships preserve choice but can complicate overlapping mandates, allocation, and credible future-supply commitments. Any coordinated refusal needs a lawful scope, defined target and duration, a decision process, support for participants, and protected dissent. It cannot retract compliant CC permissions, disregard contracts, or damage shared resources; nonemployee coordination requires competition review. ^{[S06] [S13] [S26] [S99]}

Population scale also differs from ownership and accountability. Compare direct mass membership, nested local/sectoral bodies, and federated representation on meaningful control, decision costs, inclusion, and benefit distribution. A large user count does not establish democratic ownership or prove that a conventional corporate form has been displaced.

Public-good representation: people who use open knowledge and communities affected by AI should influence commons spending without first proving ownership of profitable data. This function is not reducible to either consumer purchasing or seller representation.

Relational data-governance scholarship provides a reason for this separation: the interests of people affected by population-level inferences are not exhausted by the preferences of the original contributors. ^[S25]

Proposed three-part architecture

The federation may share an open protocol, counsel, and procurement infrastructure. It should not share unrestricted data custody by default. A "data trust" is a governance description whose legal implementation depends on jurisdiction; it does not, by its name, prove fiduciary duties, representativeness, or authority. Data-trust scholarship is useful precisely because delegation and fiduciary accountability need explicit design. ^[S07]

Governance and collective agency

Proposed charter: one member, one vote within defined constituencies; elected, recallable representatives; compensated deliberative panels; buyer and supplier chambers; and an independent commons and affected-party council. The federation's constitutional forum coordinates these constituencies while each legal entity retains its own duties. No investor acquires additional votes by purchasing more data or funding the operator.

Material changes to permitted use require approval by the affected constituency and an individual refusal path where individual authorization is needed. New use does not inherit permission from an old vote. Budget rules, representation, and extraordinary decisions should be constitutional; routine implementation should remain delegated so the institution can operate.

A rights-and-ethics steward can pause unsafe processing pending independent review. Its mandate, appeal route, conflicts, and response deadlines must be published. Sponsors cannot veto adverse findings. Paid staff may administer the institution but cannot secretly alter member mandates.

The test of advancing collective agency is not total dollars paid. It is whether members understand choices, can refuse without disproportionate penalty, can change negotiators, can switch suppliers, can contest uses, and can redirect surplus toward shared priorities.

A buyers' club, a suppliers' club, and a community

The session's extension sharpens the analogy: a successful club assembles both demand and supply. Buyers gain scale and better terms; suppliers gain predictable demand, lower transaction costs, and a voice in the institution. The aim is fair, sustainable total value, not the lowest buyer price at any cost. Evaluate price alongside quality, reliability, contributor livelihoods, privacy, access, and commons maintenance. Two-sided-market theory supports examining these interactions, not assuming that scale alone makes every participant better off. ^[S23]

The phrase community-governed Soho House describes shared purpose, community norms, and social infrastructure. It is not a claim that Soho House or Costco is a cooperative or that their suppliers currently hold these proposed voting rights. The intended community is not organized around wealth, status, or exclusivity. No affiliation or endorsement is implied. ^[S16]

Free opt-in does not mean unfunded services

Proposal: make basic participation free, including deliberation, applicable voting rights, and core community resources. Optional dues buy specified purchasing support, managed services, or other cost-bearing benefits. Sponsored participation and waivers can widen access, without granting sponsors votes. Free membership does not promise unlimited free AI consumption.

Fund the model through optional dues, disclosed procurement-service charges, transparent transaction fees, and grants for public goods. Budget cross-subsidies explicitly. Public knowledge can benefit nonpayers by design; intensive private services may need a subscription or subsidy. Measure utilization, renewal, governance costs, and subsidy dependence before claiming a scalable free tier. Payment buys services, not extra citizenship; membership never requires a data sale.

Supplier voice must have consequences

The buyer chamber represents members consuming the club's services. The supplier chamber represents contributors, creators, curators, maintainers, and community stewards supplying the club. A commercial AI vendor selected by procurement is not automatically a voting supplier: a sales contract does not confer constitutional rights. Any overlapping role requires separate qualification, disclosure, and recusal.

The commons and affected-party council represents interests beyond the immediate transaction. Its powers should be enumerated, supported by written reasons and an appeal route, rather than an unlimited veto over ordinary operations. The reason for this third body is substantive: people affected by data use may be neither the buyer nor the contributing seller. ^[S25]

Supplier protections can include timely payment, transparent deductions, and bounded workload commitments. Coordinated price floors require jurisdiction-specific competition review; calling the institution a club does not create an exemption. ^[S13]

Members with overlapping roles can register a primary voting chamber for a fixed term while retaining their separate authorization rights. Representation must not scale with sales, spending, or donations. Duplicate-membership controls should be proportionate, privacy-preserving, minimally retained, and appealable; neither public identity disclosure nor proof of wealth is an acceptable default.

Dual chambers can constrain domination but also create delay and factional capture. Delegate routine operations, reserve cross-chamber approval for consequential choices, publish conflicts, and measure governance costs. A committee structure is valuable only if members gain usable agency.

6. Archetypes and the multi-sided marketplace

A person may occupy several roles. Alice may buy an AI assistant, publish open educational material, and license professional writing. Bob may consume that material, contribute corrections, and live near a data center. Membership must not collapse these identities into one blanket permission.

Local Contexts' Traditional Knowledge Labels illustrate how community protocols can travel with cultural materials. They are not a blanket substitute for law or community engagement, and a bargaining platform should not rebrand them as conventional commercial licenses. ^[S20]

Market-design problem. More participants can improve matching and bargaining but also make the intermediary a new gatekeeper. Prefer nonexclusive mandates, portable records, interoperable catalogs, transparent fees, and access to competing representatives. A procurement committee must not obtain individual sellers' confidential reserve prices. A contributor association must not exploit access to consumer behavior for discriminatory pricing.

Two-sided-market theory explains why the distribution of charges across participants matters, not only the platform's total revenue. Dues that deter low-income consumers, excessive contributor commissions, or buyer fees that prevent adoption can each undermine the other sides. That theoretical insight does not establish the optimal price schedule for this proposed institution. ^[S23]

The first market should be narrow enough to establish authority and inspect benefits: for example, a curated educational retrieval service with adult contributors, original non-sensitive materials, and a nonprofit/public-interest buyer. Avoid health, children's, workplace-surveillance, and humanitarian-beneficiary data in the initial pilot.

7. Business model and economic discipline

Photographed direction / source transcription

Nicholas Vincent.

Three parallel interests: (i) applying technical data valuation across data markets, business models, market design, and policy; (ii) designing effective collective bargaining institutions for data creators; (iii) creating better long-run incentives for data creators, e.g. equity stakes in data or AI companies.

This records a printed card, not a verified spoken quotation or endorsement. ^[S97]

Editorial alignment and coverage

Connect data valuation and market design to effective contributor institutions and long-term incentives, including the possibility of equity participation.

Valuation, business models, and collective bargaining already have dedicated analysis. Creator equity is now distinguished from cash, royalties, and the separate public sovereign-fund proposal, with unresolved governance and legal trade-offs.

• Data valuation, business models, market design, and policy
  6. Archetypes and the multi-sided marketplace · 7. Business model and economic discipline · 27. Private institutions and the commons service model
• Effective contributor bargaining institutions
  5. From digital Costco to a bargaining federation · 20. Follow-on research: a Commons Collective Framework Agreement · 23. Institution blueprint: a Commons Collective Federation
• Long-run contributor incentives and possible equity stakes
  8. Payment, disbursement, and public-good return · 19. Data dividends, Pigouvian taxes, and commons credits

View source context and full mapping

Revenue sources should remain distinguishable

1. Member dues: fund representation and purchasing services, with waivers or sponsored membership to prevent income-based exclusion.
2. Transparent service charges: compensate curation, rights verification, delivery, and audit. Do not disguise them as royalties for public-domain information.
3. Licensing commissions: a possible separately negotiated variant, not a deduction implemented in the current Lab's contributor contract; apply only to authorized uses with prior disclosure.
4. Procurement administration: a disclosed fee or dues-funded service, not an undisclosed supplier kickback.
5. Commons contracts and grants: fund nonexclusive public infrastructure, independent evaluation, and underserved participants.

These are institutional design options. A proposed income source is not booked by the financial summary unless the selected detailed model actually includes it. In particular, current contributor-agency receipts are not an additional operator revenue stream.

The initial operator should not depend on selling profiles, ads targeted from private archives, or speculative token appreciation. Venture capital may fit some interoperable infrastructure services, but a return requirement can conflict with non-extractive membership governance. Any investor participation must be subordinate to the mission and cannot buy contributor permission.

One financial source, detailed model and summary

Follow the Money is a read-only rollup of the selected Simulation Lab source. It must match the same period, currency, account perimeter, receipts, costs, and liabilities exactly. It is not a second calculator that assumes licensing income or applies a different distribution rule. Inputs belong in the Lab; the summary aggregates its output and identifies its source.

The current startup view models investor-funded ramp-up, staff, acquisition and support costs, member prices, and an explicit commons covenant. Its forecast is distinct from the operating-agent model's simulated payment journal. A forecast must not be called a cleared receipt, and neither is evidence of a real institution or transaction.

The current published reference is the same AI Commons startup projection used by the Simulation Lab and Follow the Money: month 0 through 36, source identity c54691b8aa456b8c. These are conditional planned cash flows, not executed payments or an empirical forecast.

Staffing, acquisition, the user ramp, and every cost line are editable in the Simulation Lab. The Follow the Money rollup reads that model's output; it has no separate financial assumptions. Published trial evidence records the distinct, frozen design and holdout study.

These calculations concern paid services, not civic membership or an entitlement to sell other people's information. Free participation, support, accessibility, and governance costs still need funding. Fees must be evaluated against comparable service quality and actual switching costs, not merely against a headline discount.

Equal member payments are a governance choice, not an estimate of marginal contribution. A more granular valuation scheme might reward effort or quality but adds measurement, gaming, and dispute costs. No precise attribution from an individual record to every generated output is assumed. Externalities also mean that one person's sale can affect others who never agreed to sell. ^[S24]

Separate five meanings of "data value": buyer willingness to pay; contribution to a specified model-performance metric; the contributor's willingness to accept disclosure; production and maintenance cost; and net social benefit. Data Shapley addresses a particular performance-allocation problem, not an intrinsic monetary value. Acquisti, John, and Loewenstein's privacy experiment shows why willingness to accept or pay can depend on context and endowment, not simply reveal a stable price. Neither measurement alone establishes a fair dividend. ^{[S27] [S30]}

8. Payment, disbursement, and public-good return

Long-run incentives and possible contributor equity

The photographed Vincent card explicitly raises equity stakes in data or AI companies as one possible long-run incentive. Treat this separately from a fee for current work, a royalty, cooperative patronage, or the public sovereign-fund proposal discussed later. No instrument is universally appropriate. Compare cash flow, valuation, dilution, vesting, liquidity, risk, tax/securities treatment, and who controls decisions. Contributors must not be forced to accept speculative equity instead of promised pay, and investor voting power must not silently replace civic membership rights. This is a research and legal-review question, not an offer of securities or evidence that individual data creates an ownership share in a model. ^[S97]

Contract-specific flows implemented in the Lab

For example, an accepted and funded $10 contributor entitlement is $10 owed to that contributor under the current agency contract. It is not silently split into $4/$3/$2/$1. Administration fees and their commons covenant are separate flows. A different negotiated allocation would require a different named contract implemented consistently in both detailed and summary views.

A real payment path would require

Invoice -> cleared receipt -> contract reconciliation -> reserve and restriction entries -> eligibility check -> payout instruction -> payment confirmation -> member statement -> dispute window -> independent audit.

Use regulated financial-service providers as applicable. Minimize identity collection, but do not promise anonymous disbursement where payment, tax, anti-fraud, or sanctions rules require verification. Keep identity records separate from content and public receipts. Failed payments remain member liabilities, not revenue; unclaimed funds need a jurisdiction-specific policy. Publish aggregate audited totals, not names or bank details.

The executable models use integer cents and explicit contract rounding. Each account must satisfy opening cash plus incoming cash minus outgoing cash equals closing cash. Agency cash must remain matched by unpaid contributor entitlements; internal transfers are eliminated in a combined institutional view. Unpaid invoices are not cleared cash, and failed payments do not become operator income.

Follow the Money exposes those reconciliations for a chosen cumulative window. Operating-run figures are regenerated from the completed run's configuration and checked against its recorded checksum before a ledger is displayed. Startup figures are aggregated from the same monthly projection rows and checked against the Lab's detailed budget. Downstream fund balances or contributor payments that a projection does not model are labeled not modeled, never invented as zero or calculated from an unrelated percentage.

Purchasing savings and contributor earnings remain separate stakeholder outcomes. Neither is a universal data dividend. A person who contributes no licensable material may still deserve full voting rights and meaningful purchasing benefits.

Public-good allocation

Proposal: an independently overseen fund supports open reference maintenance, community archives, accessibility, translations, provenance tools, and legal or technical support for underrepresented contributors. Publish award criteria, reviewer conflicts, funding amounts, deliverables, and renewal decisions. Include minimum support for valuable but low-traffic resources rather than allocating entirely by clicks or model usage.

Participatory budgeting can establish priorities. Matching funds may encourage diverse support but can be gamed by fake identities or coordinated donations; any matching mechanism needs a capped pilot and fraud review. Avoid requiring recipients to grant exclusive rights to qualify. Measure maintenance and public access, not merely funds disbursed.

9. Creative Commons as an aggregation model

Creative Commons demonstrates the value of standardized permission infrastructure. It is not automatically an aggregator, collecting society, payment processor, or owner of everything carrying a CC license. Existing CC permissions cannot simply be replaced with a retroactive AI royalty obligation. CC licenses are irrevocable for recipients who comply with their terms, and permissions differ by license and by the rights involved. ^{[S08] [S26]}

Proposed CC-compatible role, not a claim of CC commitment:

• A discoverable registry that preserves the exact license, version, attribution information, provenance, and rights caveats.
• Shared metadata and contributor mandates for new services or permissions the contributor actually controls.
• A voluntary "support the commons" covenant for commercial users, independent of whether the underlying open content already permits reuse.
• A separate settlement and grant-disbursement institution with audited governance, rather than pretending that a license badge routes money.
• Optional public-interest access to curated collections and validation services, without restricting lawful access to the underlying open works.

Newer CC discussions about signaling preferences for AI use should be evaluated on their own terms; a preference or social signal is not automatically a modification of a pre-existing license or an enforceable obligation on every downstream user. ^[S09]

For a new proprietary work, Alice might offer a paid, narrowly specified license while separately licensing another version openly. Rights clearance must establish what remains available for negotiation. For an existing CC BY work, a buyer can fund curation, delivery, verification, or commons stewardship, but the institution cannot represent that the buyer needs a new permission merely because an AI system is involved.

Recommendation: begin with interoperable metadata and voluntary commons financing. Do not claim that Creative Commons, its staff, or its community has accepted the proposed commercial or governance role.

10. Gmail, private AI, and meaningful opt-in

The Gmail analogy is about an assistant operating over information entrusted for a defined service. Google's published Gmail privacy explanation describes processing for features such as spam detection and smart composition, user controls, and a distinction between email content and advertising. It does not establish a universal rule for all Google AI products, every account type, or foundation-model training. ^[S17]

Correction to a tempting shortcut: opting into an AI feature is not equivalent to giving unrestricted training rights over an entire inbox. Consumer, education, enterprise, and separately connected AI services may have different terms and controls. Any factual claim about a specific product's defaults requires a current product-and-account-specific check.

For a cooperative assistant, separate at least four choices:

1. Task execution: temporarily access only the records needed to answer the current request.
2. Personalization: retain explicitly chosen preferences or an index for that member.
3. Service improvement: reuse narrowly specified telemetry or feedback for disclosed purposes.
4. Model training: a separate decision specifying scope, recipient, retention, and any compensation.

No training permission should be inferred from the first three in the proposed design. An incoming message from Bob creates obligations toward Bob; Alice's custody of the message is not proof that she can license all its content or personal information. GDPR, where applicable, requires a legal basis and purpose analysis; consent is not the only legal basis, and calling something "opt-in" does not by itself make consent valid. ^[S10]

The consumer interface must make refusal as easy as acceptance, disclose whether a service still works when permission is declined, and explain what withdrawal can and cannot undo. A future-access block is technically different from deleting a source, purging a retrieval index, or proving removal of influence from an already trained model.

11. New knowledge objects and technical architecture

A knowledge object is a governed bundle

Proposal: the unit of exchange is not a naked file but a knowledge object: content or a pointer, plus assertions about origin, authority, permitted use, evaluation, benefit allocation, and review. The object is not itself proof that those assertions are true.

Reuse established representations where they fit. W3C PROV represents entities, activities, agents, and derivations. Verifiable Credentials can express issuer claims in interoperable forms, with privacy implications that require careful design. Neither establishes that the issuer's legal claim is correct or that the credential must be public. ^{[S18] [S19]}

The accompanying JSON example is deliberately fictional, has no real content or cryptographic proof, and is not a complete schema or executed contract. It separates retrieval permission from prohibited training and does not promise historical model erasure.

Proposed system boundaries

Member-controlled source or steward
    -> local selection and third-party/sensitivity review
    -> catalog metadata + verified authority evidence
    -> member-approved bargaining mandate
    -> contract and purpose policy
    -> authenticated access gateway / approved computation
    -> buyer's bounded retrieval, evaluation, or training environment
    -> signed or otherwise tamper-evident use receipts
    -> segregated settlement ledger
    -> member statements + independent commons awards + audit

Prefer data minimization and local or trusted compute-to-data patterns where practical. Enclaves, access gateways, and federated learning can reduce particular exposure risks; none eliminates inference, malicious-recipient, or governance risks. Training may genuinely require exporting approved material. If so, disclose that rather than claiming all data remain local.

Use encrypted transport and storage, scoped short-lived credentials, least-privilege roles, deletion schedules, and independent incident response. A public ledger should contain aggregate or carefully designed commitments, not raw content, personal identifiers, or easily guessed hashes of private messages. Provenance itself can leak identity.

For access requests, fail closed when authority, purpose, or mandate status is unresolved. For payment failures, report an actionable error and preserve the liability. Do not create success-shaped receipts for failed delivery or failed settlement.

An agent trace can mix public material, private communications, professional work, third-party content, and synthetic outputs in the same record. Classify and assess authority at the appropriate component and use level; possession of the log does not clear every span or tool result for donation or redistribution. The supplied notes' shareback idea is therefore a purpose- and permission-specific process, not a default upload of everything. ^{[S10] [S99]}

Divergence at every infrastructure node

A request can use an open protocol yet still concentrate identity, attention, payment, and negotiating power elsewhere in the stack. The relevant question at every node is: who sets the rules, who can refuse or switch, who receives the money, and who can audit the result?

Open the full divergence chart and accessible comparison. The branches show design alternatives and concentration risks, not a factual finding of misconduct by any named provider. Cloudflare is an illustrative CDN provider; example.com is an illustrative application domain.

The middle lane traces the technical request. The side branches trace alternative distributions of control, information, rents, and benefits, not two physically exclusive networks. A centralized service can fulfill a commons-serving contract; a decentralized or open-source service can still extract value. Ownership labels alone do not decide the branch.

For Alice's request to example.com, this means choosing the browser or agent's delegation policy; examining the application's business model; negotiating edge/CDN logging and portability; limiting identity and database access; specifying compute and model use; verifying receipts; and directing payments through an accountable settlement institution. Bob's interests as a correspondent, recipient, or affected community member must remain visible even when he is not the paying customer.

At each contract handoff, record an enforceable condition, an exit or refusal mechanism, a beneficiary, and an independent verification method. If a claimed commons branch lacks these, label it an aspiration rather than a demonstrated return to the commons.

The companion page's node-by-node tipping points identifies the countervailing power, organizing actor, enforceable instrument, evidence, and remaining capture risk at each handoff. These are proposed causal mechanisms to test, not measured transition thresholds: open infrastructure alone does not force an incumbent to share control or surplus.

The notes attribute to Tomicah a distinction among market mechanisms, policy interventions, non-market action, and philanthropic cold-start capacity. The ten-node mechanism matrix applies all four lenses to every node. They can combine: a contract may need lawful public rules, volunteer stewardship, and seed funding. A grant does not create authority, prove buyer demand, or entitle a donor to control the institution. ^[S99]

Treat the notes' fear/greed framing as a limited motivation hypothesis, not an exhaustive account or a warrant to manufacture fear. Reciprocal service, professional identity, community purpose, and expected gains can also matter. Likewise, the notes' IETF concern is a proposed case study of participation resources, agenda-setting, conflicts, and outcomes, not an established finding of institutional capture.

12. Alice and Bob: end-to-end flows

A. Alice buys an assistant; Bob is her correspondent

1. Join: Alice joins the purchasing cooperative using minimal membership information. She chooses a subsidized or paid tier; training permission is not a condition of membership.
2. Compare: she sees a matched-price comparison, retention terms, accessibility, supplier exit options, and what the cooperative earns.
3. Authorize a task: Alice asks the assistant to find an appointment in selected messages. She sees the folders, time window, recipient service, and retention period before access.
4. Minimize: the connector excludes unrelated messages and flags sensitive material. Bob's information is limited to what the authorized service requires; it is not silently enrolled in a licensing pool.
5. Execute: the supplier receives a purpose-bound token. The assistant performs retrieval or inference under the agreed terms, not general model training.
6. Receive evidence: Alice receives the answer and a comprehensible activity receipt: what was accessed, for what purpose, by whom, and how to contest it.
7. Exit: she revokes future access, requests applicable deletion, exports settings, or switches supplier. The institution reports actual deletion scope and limitations rather than promising that a previously trained model has "forgotten" her.

Outcome to test: comprehension and control with no compulsory data sale. There is no assumed royalty for this private-assistant flow.

B. Alice licenses a field guide; Bob uses an educational tool

1. Alice is the fictional author of original, non-sensitive material. The association verifies her authority and any assignment, collaborator, or source restrictions.
2. She grants a one-year, nonexclusive mandate for a retrieval service, not training. The contract specifies permitted excerpts, attribution, retention, recipient, fees, and remedies.
3. The fictional educational provider evaluates Alice's specifically authorized retrieval-service offer. If it accepts and funds a $10 entitlement in the chosen scenario, the payment has a named contract and recipient. No receipt is invented when the offer is rejected. Bob's assistant request identifies the relevant collection and permitted operation.
4. A receipt records delivery against the contract. It does not claim to calculate the contribution of every sentence to the model's internal weights.
5. The full contracted $10 is recorded in the contributor-agency ledger and either paid to Alice or retained as cash matched by a payable. Operator fees, the commons covenant, and verification costs are separately identified. The money rollup shows those same entries rather than imposing a second allocation.
6. Bob can inspect provenance and report incorrect attribution. Alice can dispute a use or revoke future mandate renewals, subject to the signed contract and applicable rights.
7. If the buyer wants training access, it must negotiate a separate permission and review the changed risk. No technical flag alone converts the old contract into the new one.

Outcome to test: actual willingness to pay for provenance, quality, and permitted access, together with enforceable contributor limits.

C. Alice publishes openly; Bob supports the commons

Alice has already released an article under CC BY. Bob's developer can exercise the permissions that license grants while meeting applicable terms. The association does not revoke that permission or bill retroactively. Instead, Bob's organization can pay for a curated, well-maintained collection and voluntarily contribute to a commons fund. The fund might support translation, maintenance, and accessibility, including resources with little commercial demand.

Outcome to test: additional public-good funding without reduced lawful access. A successful test must compare funding gains against the cost and friction of the institution, not merely celebrate a new payment channel.

D. Alice and Bob coordinate book and music services

The supplied notes attribute this example to Nick. It is an illustrative research proposal, not a case report about existing collecting organizations or a claim that either has particular statutory powers. Here Alice represents a hypothetical book collective-management organization (CMO), and Bob represents a music CMO. ^[S99]

1. Verify mandates: identify represented rights, jurisdictions, exclusions, and overlapping representation.
2. Choose one service: define a bounded educational retrieval offering; do not assume training is included.
3. Map interfaces: exchange permission-safe catalog schemas and authority fields without pooling works or confidential member records.
4. Compare appraisal methods: discuss curation cost, coverage, reliability, and task utility, not automatically confidential prices, margins, bids, or customer terms.
5. Review information exchange: obtain jurisdiction-specific competition advice. Independent intermediaries, aggregation, or a clean room can reduce exposure but do not create immunity. ^[S13]
6. Allocate responsibilities: specify delivery, provenance, attribution, corrections, costs, and benefits while preserving separate rights and accounts.
7. Choose a lawful negotiation route: negotiate jointly only within verified authority and an appropriate legal basis; otherwise share infrastructure while retaining independent commercial decisions.
8. Pilot and reconcile: test service quality, member understanding, payment allocation, complaints, and exit; publish only permission-safe methods and results.

Success is reduced coordination cost and better service without unauthorized rights expansion or harmful information exchange. It does not require a universal valuation of books versus music.

13. Regulatory framework: present rules and proposals

Photographed direction / source transcription

Erika Yorio (Helena).

Investigate whether collective licensing or other intermediary structures can give individual data contributors meaningful bargaining power against AI companies, and whether the design of these structures can avoid creating a new layer of gatekeepers. Second thread: explore how litigation and emerging regulatory standards can begin to establish practical norms on data rights, compensation, and permissible use.

This records a printed card, not a verified spoken quotation or endorsement. ^[S97]

Editorial alignment and coverage

Collective licensing and intermediaries should improve real bargaining power without becoming new gatekeepers; litigation and emerging regulation can be studied as routes to practical norms.

Licensing, competition, rights, and gatekeeper risks were covered. A dated litigation-and-standards research track is added without asserting unverified case outcomes or universal new compensation rights.

• Test bargaining gains against the risk of a replacement gatekeeper
  6. Archetypes and the multi-sided marketplace · 17. Failure modes, counterarguments, and safeguards · 21. Reputation, validation, and quality ranking
• Track legal and regulatory norm formation with jurisdiction and status made explicit
  13. Regulatory framework: present rules and proposals · 20. Follow-on research: a Commons Collective Framework Agreement

View source context and full mapping

This section is issue-spotting, not legal advice. "Collective bargaining" is an institutional objective, not an automatic legal status. Laws protecting employee bargaining do not necessarily protect coordinated pricing by independent creators or businesses. The parties, market, activity, jurisdiction, and scope of any exemption matter.

For example, the U.S. NLRA excludes independent contractors from its employee definition. A valuable contribution to AI does not itself establish employment, but exclusion from that statute also does not prove that all collective negotiation is prohibited by other law. ^[S33]

Date-sensitive AI Act reading

Under the enacted AI Act's phased schedule, general-purpose-model obligations began applying on 2 August 2025, with specific transitional treatment for models placed on the market before that date, including an August 2027 compliance deadline under the relevant transition. The general application date and specific duties must not be conflated. Scope, exceptions, amendments, and current implementation guidance require a fresh check for the actual model and provider before procurement. ^[S12]

September 2026 update: the enacted Digital Omnibus on AI, Regulation (EU) 2026/1744, entered into force on 27 July 2026. It changes relevant high-risk Annex III application dates to 2 December 2027 and Annex I dates to 2 August 2028, without replacing the principal GPAI copyright/summary timetable discussed above. Describing all AI obligations as delayed would be incorrect. ^[S32]

The EU copyright directive separately distinguishes qualified research text-and-data mining from a broader lawful-access exception subject to appropriately expressed rights reservations. National implementation and the facts matter; neither a "research" label nor public accessibility settles the issue. ^[S35]

The report does not assert that a transparency duty creates a right for every person to be paid. Nor does it assume that publicly accessible information is free of privacy obligations or that a CC license covers every personality, trademark, or confidentiality issue.

A proportionate reform package

Near term: model mandates; standard use receipts; independent audits; interoperability; accessible complaints; consumer switching; public-interest procurement experiments; and funded legal support for smaller contributors.

Medium term, subject to legislative authority: clarify qualifying representative institutions and narrowly tailored competition-law treatment; require meaningful records and remedies for specified uses; evaluate statutory collective-management or commons-funding instruments with safeguards for open knowledge and small developers.

Do not start with: a universal individual property right over all observable facts, a presumption that every inference incurs a royalty, compulsory licensing of intimate communications, or a token that purports to sell rights the issuer cannot grant.

Litigation and standards as norm formation: the photographed Yorio card makes this a separate research track. Maintain a dated, jurisdiction-specific record of the claim, decision or settlement, appeal status, and narrow implications for permissions, compensation, and remedies. Do not turn one decision, an advisory report, or a proposed standard into a universal training rule. Evaluate whether the resulting intermediary improves contributor terms or simply becomes a new gatekeeper. No new case outcome is asserted by adding this research question. ^[S97]

14. Energy, data centers, and community bargaining

Digital abundance is not physical abundance. The IEA's 2025 analysis estimates global data-center electricity use at roughly 415 TWh in 2024 and projects roughly 945 TWh in 2030 in its Base Case. These are data-center totals, not AI-only measured consumption; the 2030 number is a scenario projection, not an observation or a fresh 2026 forecast. ^[S21]

Proposal: a parallel infrastructure bargain. Consumer and public-sector purchasing coalitions can request verifiable energy and water reporting, workload efficiency, demand flexibility where technically feasible, and community-benefit commitments from suppliers. Host communities need their own representation: they should not depend on owning training data to have a voice in local burdens.

Report energy per useful service alongside absolute consumption. Efficiency improvements can lower cost and increase total demand; a per-query metric alone may conceal rebound. Do not invent precise per-output carbon accounting when the supplier exposes only aggregate data.

Philanthropic capital should support independent measurement, community technical assistance, and procurement expertise before subsidizing speculative data-center assets. Capital-intensive energy projects need qualified engineering, interconnection, environmental, and financial diligence; this report does not establish project feasibility or recommend a particular investment.

Data-center and data-commons coalitions may share procurement, technical assistance, and accountability methods, as suggested in the supplied notes. They must not redirect a host community's priorities without authority or treat a distant knowledge grant as an offset for local environmental duties. Local mitigation and a commons contribution require distinct evidence and approvals. ^[S99]

15. A philanthropic strategy relevant to Humanity AI

Evidence and identification. Humanity AI is the ten-philanthropy initiative announced on 14 October 2025 with a $500 million commitment over five years, including aligned grantmaking and a pooled fund. This is an announced collective commitment, not proof that all money has been disbursed, is pooled into one account, or has been awarded to this project. It is not treated as a commercial investment fund or a presumed partner. ^[S15]

A current, separate opportunity: on 10 September 2026 Humanity AI announced a $10 million call-wide competitive grant program. Published terms describe awards of $75,000-$1 million over up to three years, focused on U.S.-based community-led work, with the required nonprofit lead or appropriate fiscal sponsorship. The stated deadline is 21 October 2026 at 7:59 p.m. ET. Research-only projects are out of scope: this paper would need to become a genuinely community-led action pilot, not merely an application to write more research. Verify current eligibility and timing before applying. ^{[S28] [S29]}

Proposal: a hypothetical $10 million, three-year catalytic portfolio. This is a strategy for discussion with Humanity AI or similarly aligned philanthropies, not a funding request approved by any named organization.

The proposed portfolio's $10 million is not the same as the actual call's $10 million envelope, and it should not be presented as a plausible single grant under the published $1 million maximum. A bounded eligible pilot could be one component of a separately financed portfolio.

Stage gates

• Months 0-6: up to $2m discovery. Map rights and market structure; conduct compensated research; establish representation and ethics review; negotiate at least two independently credible buyer prospects. Do not collect sensitive records to make the pilot seem concrete.
• Months 7-18: up to $4m pilot. Release funds against signed bounded contracts, understood mandates, an approved legal analysis, credible complaints handling, and a tested settlement ledger. Compare against individual or status-quo procurement.
• Months 19-36: up to $4m conditional replication. Require independently verified benefit after costs, no unresolved material rights violations, actual switching/exit, and transparent accounting. Preserve a funded wind-down path.

The stage totals and workstream totals describe the same $10m envelope, not two separate budgets. Allocate each grant to both a workstream and a stage in the actual ledger.

Grants first; investment only when justified

Non-excludable standards, independent oversight, and community participation are appropriate grant candidates. A recoverable grant or program-related investment might fit a revenue-producing, mission-locked service once counsel establishes eligibility and realistic repayment economics. Do not promise a PRI classification, assume a foundation can take any security, or model token appreciation as a repayment source.

Stop or redesign if a pilot depends on coerced permission, cannot establish authority, produces benefits below costs without a justified public-good rationale, cannot attract genuine buyer demand, or excludes affected nonmembers from meaningful recourse. Protect evaluation independence and prohibit sponsors from suppressing unfavorable results.

Philanthropy should buy learning and institution-building capacity, not merely a temporary appearance of a market. Publish the subsidy per participant and a credible account of what survives when grants end.

16. Research program and falsifiable hypotheses

Photographed direction / source transcription

Beth Goldberg (Humanity AI).

Public deliberations on AI data use, so that consequential decisions are not made only by elites in closed-door gatherings; participatory co-design in benefit-sharing arrangements.

This records a printed card, not a verified spoken quotation or endorsement. ^[S97]

Editorial alignment and coverage

Public deliberation and participatory design should shape consequential AI-data decisions and benefit-sharing arrangements, rather than leaving decisions to closed elite forums.

Affected-person participation, paid design research, member governance, and commons budgeting were covered. Their connection to public co-design beyond invited participants is now explicit.

• Include affected publics in consequential data-use decisions
  1. Research circle and ethical commitments · 5. From digital Costco to a bargaining federation · 16. Research program and falsifiable hypotheses
• Co-design benefits and objectives with people affected
  8. Payment, disbursement, and public-good return · 24. Commons-authored RL rewards and regulatory design · 25. A pro-human stack: working definition and test

View source context and full mapping

The central empirical question is whether an institution changes bargaining outcomes and control, not whether participants express abstract enthusiasm for fairness.

The Goldberg card makes public deliberation and benefit-sharing co-design explicit. Compensated research should include affected people beyond the invited workshop or paying membership, preserve dissent, and record which decisions changed. A consultation count alone does not establish influence, representation, or approval of a proposed allocation. ^[S97]

The open research questions and work register records the current follow-on questions, next steps, and explicit statuses. It is the canonical work source for the live overview presentation; presentation text is drawn from this report rather than maintained as a separate slide draft.

Proposed initial design

Recruit approximately 200 adult consumers and 40 professional or community contributors for compensated design and usability research across at least two different socioeconomic contexts. These counts are feasibility targets, not a statistical power calculation. Use staged low-risk experiments before any commercial distribution. Determine a confirmatory sample size from a prespecified minimum meaningful effect and observed variance; do not infer causality from an underpowered convenience sample.

For procurement comparisons, match feature sets, support, privacy terms, and contract duration. Measure outcomes before and after participation and include refusal/dropout data. Where randomization is unavailable, preregister confounding risks and treat estimates as observational. Separate the effect of discounts from selection into membership and from donor subsidy.

Proposed progression thresholds: at least 80% of tested participants correctly identify whether training is permitted and how to withdraw; every payment is reconciled; all scoped-access denial cases pass; and no unresolved high-severity privacy or authority failure remains. These are design gates to be debated with affected people, not externally established standards. Report confidence intervals and subgroup differences rather than declaring success from a single average.

What to measure

• Agency: comprehension, effective refusal, time to switch, successful mandate withdrawal, electoral participation, and complaints resolved.
• Distribution: median and lower-quartile net benefits, fee-waiver coverage, contributor concentration, and outcomes for people receiving no royalty.
• Business viability: independently verified buyer demand, acquisition and support costs, retention, annual subsidy, and realistic path to sustainability.
• Commons health: maintenance hours, accessibility, translation, public availability, steward autonomy, and underfunded resources supported.
• Integrity: authority errors, third-party exposure, payment discrepancies, conflicts of interest, and procurement/seller-information separation.
• Environment: absolute and service-normalized energy/water metrics, grid context, ratepayer impacts, and community-reported burden.

Preregister methods and publish negative results. Seek institutional ethics review where applicable. Participation compensation must not depend on consenting to commercial reuse.

17. Failure modes, counterarguments, and safeguards

The strongest counterargument is that a new institution adds overhead without creating additional bargaining power. The research program must be able to conclude that a cooperative is inappropriate for a given setting. In that case, direct public funding, conventional consumer protection, stronger labor institutions, or investment in existing commons stewards may be better than inventing a data market.

18. A ninety-day starting sequence

Days 1-30: mandate and listening. Confirm the research circle and editorial ownership; select a pilot jurisdiction and domain; commission legal issue-spotting; compensate community sessions; inventory candidate rights and existing institutions; publish conflicts and a preregistered research protocol. Do not ingest an inbox or scrape a corpus merely because it is technically accessible.

Days 31-60: institutional and technical rehearsal. Test plain-language membership and scoped mandates with fictional objects. Obtain comparable procurement offers and bounded contributor-service offers. Rehearse failed authorization, third-party objection, revocation, failed payment, appeal, and supplier exit. Verify separate accounts and a proposed public-good allocation process.

Days 61-90: independent go/no-go review. Evaluate comprehension, buyer interest, legal authority, distribution, and costs. Publish evidence and failure cases. Proceed only to a bounded pilot with explicit limits; otherwise revise the institution or redirect funds to existing stewards.

Immediate deliverables provided here: the public research text; source register with claim limits; a fictional governed object; executable simulations with reconciled financial summaries; a public trial-evidence archive; and a publication workflow that rebuilds and deploys on every push to the repository's main branch. They are infrastructure for the research, not evidence that its proposed institutions already work.

19. Data dividends, Pigouvian taxes, and commons credits

The perspective: separate five objectives

A Pigouvian tax is a corrective tax on an activity that imposes costs on others, designed to make decision-makers account for those external costs. ^[S36] A useful proposal must distinguish a data dividend (a distribution to a defined population), compensation (payment for particular work or authorized use), commons finance (support for shared resources), harm correction (making decision-makers face external costs), and rent sharing (redistributing returns above a defined benchmark).

These objectives can coexist, but they do not justify identical instruments. A dividend may be financed from tax receipts or public investments without calculating every recipient's contribution to AI. A Pigouvian charge should correspond to marginal external harm, using credible measurement or a defensible proxy. A tax on economic rent instead targets exceptional returns. Commons maintenance has positive spillovers; supporting it does not automatically cancel an unrelated privacy, environmental, or labor harm. ^[S36]

Our assessment: a capped commons-reinvestment credit is worth testing as public-finance policy. It should not become an unmeasured "good behavior" score, a way to buy permission to violate rights, or a reason to relabel every profit tax as Pigouvian.

Fifty percent of what?

The user's 50% is an illustrative parameter, not an economically estimated optimum. The tax base must be specified first. Consider a fictional company with $100m annual revenue, $90m allowable costs, and $10m profit:

A company can be profitable with relatively low external harm, or loss-making with substantial harm. Consequently, a flat 50% of revenue or profit is not automatically Pigouvian. The scenarios are not recommendations that these rates or bases are efficient.

Which "Bernie's tax"?

The strongest matching verified proposal is Bernie Sanders's American AI Sovereign Wealth Fund Act, announced 18 June 2026. It proposes a one-time levy paid in newly issued equity, designed to produce 50% public ownership after issuance in covered AI companies. This is not a recurring 50% tax on revenue or profit. The announcement and linked bill describe public ownership and governance; they are evidence of a proposal, not its enactment. ^[S38]

Other possible meanings of the shorthand include Sanders and Khanna's March 2026 proposal for a 5% annual billionaire wealth tax, and Sanders's October 2025 robot-tax proposal directed at corporations replacing workers with machines, for which the cited announcement specifies no rate. These are different policies. None of the cited proposals establishes the Wikimedia-contribution credit considered here. ^{[S39] [S40]}

Interpretation: public equity could combine financial participation with voting power, making it closer to institutional collective agency than a cash dividend alone. But a public fund also creates risks of political capture, conflicts between financial returns and regulatory duties, valuation uncertainty, and dependence on distributable company cash. Equity value is not spendable tax revenue, and a stated distribution target is not guaranteed investment income. Constitutional, corporate, competition, and cross-border implementation would need separate legal analysis.

The announced fund valuation and dividend projections are sponsor estimates, not forecasts adopted by this report. The tax-and-credit illustration below is an independent proposal; it must not be presented as a provision of Sanders's bill.

A capped credit: trace every dollar

A credit reduces tax due; a deduction reduces the taxable base. Under a hypothetical 50% tax, a $10m deduction would ordinarily reduce liability by $5m, whereas a dollar-for-dollar $10m credit reduces it by $10m. Actual availability and interactions depend on legislation. ^[S37]

Proposed toy rules: normalize the specified base to a nonnegative amount, B; assess gross liability L = 0.50 x B; verify eligible incremental commons spending E; allow C = min(E, 0.40 x L); and collect net tax T = L - C. The 40% credit cap is our illustrative safeguard, not supplied evidence of an optimal rate. Assume no refund, no carryforward, and no additional deduction for the same expenditure.

The cap preserves 60% of pre-credit liability for the treasury, not a fixed $30m minimum for every firm. A zero or negative underlying base produces no liability or refundable credit under this simplified design; real loss treatment needs its own rules. The repository's integer-cent model tests the baseline, cap, zero base, and invalid inputs.

The first row is the central tradeoff: $10m moves to eligible commons work instead of the treasury, while the company's combined outlay remains $50m. The mechanism redirects finance; it does not automatically generate additional spending relative to collecting the full tax. Public accounts should recognize the forgone revenue as a tax expenditure. If lawmakers earmark part of the remaining tax for a data dividend, they must specify recipients, allocation, administration, and safeguards against overstating uncertain receipts.

Wikimedia contributions: additional public benefit, not reputation credits

Wikimedia is an example of a commons steward, not a participating or tax-credit-approved recipient. Its gift policy preserves review and refusal and generally favors unrestricted support. A donor must not buy editorial control, privileged access, or a say over who receives public knowledge. ^[S41]

Any pilot should require:

1. Additionality: exclude prior commitments and ordinary commercial spending relabeled as philanthropy; publish a baseline and anti-manipulation rules.
2. Accepted, verified value: recognize accepted cash support or independently assessed deliverables, not self-priced datasets, bulk edits, nominal token values, or unverifiable volunteer hours.
3. No double counting: coordinate deductions, credits, matching grants, and multiple firms claiming the same contribution.
4. Anti-laundering controls: identify related parties, subtract reciprocal commercial benefits, audit pass-throughs, and recover improperly claimed credits.
5. Recipient independence: preserve refusal and independent priorities; prohibit donor conditions that compromise editorial or community governance.
6. Inclusive allocation: maintain direct public funding and representation for communities unable to attract corporate donors or afford accreditation.
7. Revenue protection: cap offsets, report recipients and tax expenditures, review effectiveness, and preserve legislative control over public budgets.
8. Protection of existing freedoms: never make ordinary open-content reuse conditional on a payment merely to manufacture a creditable service.

For a genuine harm tax, credits should normally correspond to demonstrable reduction of the same harm, not an unrelated donation. A separate commons credit within a redistribution or rent-sharing instrument is conceptually cleaner. This avoids giving a large emitter, for example, permission to ignore local costs because it supports a popular global knowledge project.

What the shared privacy paper contributes

In What Is Privacy Worth?, Acquisti, John, and Loewenstein studied choices between a $10 anonymous gift card and a $12 identified card, varying endowment and presentation. The field experiment finds that privacy choices depend strongly on those conditions. It therefore cautions against reading a single willingness-to-accept response as an intrinsic price. ^[S30]

It does not establish a universal $2 privacy price, a fair data dividend, an AI training value, or an optimal tax rate. For Commons Collective, the practical implication is to test comprehension and choice under multiple neutral presentations, protect refusal, and never treat payment as evidence that privacy concerns have been fully compensated.

Recommendation: test a narrow, independently audited commons-reinvestment credit alongside transparent public-good grants, while analyzing the equity-fund, rent-tax, and harm-tax alternatives separately. Judge success by incremental public benefit, distribution, enforceable agency, administrative cost, and forgone treasury revenue, not corporate participation counts or a "good behavior" badge.

20. Follow-on research: a Commons Collective Framework Agreement

Photographed direction / source transcription

Zoe Cullen (HBS).

Make concrete the notion of a data trust that holds sensitive work information (corporate email, Slack channels) which is high-value for AI training but currently locked inside firms. The trust would collectively secure the data and collectively negotiate its uses, and would persist across firm insolvency so that rights survive the corporate entity that generated them.

This records a printed card, not a verified spoken quotation or endorsement. ^[S97]

Editorial alignment and coverage

A workplace-data trust for collective protection and negotiation, with a specific continuity question when the originating firm becomes insolvent.

Private and relational data, scoped mandates, and continuity were already discussed. The workplace-data and insolvency aspiration is now an explicit follow-on question; survival of rights is not assumed to be legally guaranteed.

• Separate access to workplace information from authority to reuse it
  4. A spectrum, not a single data commodity · 10. Gmail, private AI, and meaningful opt-in
• Test collective negotiation, secure stewardship, and insolvency continuity
  20. Follow-on research: a Commons Collective Framework Agreement · 23. Institution blueprint: a Commons Collective Federation

View source context and full mapping

Status: an illustrative, non-binding research framework, not legal advice or a production-ready agreement. The gaps below are not resolved in this study; this is not a claim that no sector, jurisdiction, or existing organization has addressed them.

A statutory labor collective bargaining agreement operates within applicable employment law. Other constituencies may need a multi-party service, licensing, and governance agreement instead. The label does not create employment status, rights ownership, a duty to bargain, or competition immunity. Local counsel must establish the legal route for actual parties and activities. ^{[S33] [S13]}

Which agreements still need investigation?

Existing sectoral agreements, licensing collectives, cooperative and trust instruments, and community-benefit arrangements should be comparators. The next research step is to identify their coverage and limits, not assume institutional absence.

Workplace-data trusts and institutional continuity

The Cullen card specifically proposes secure collective stewardship of sensitive work information, collective negotiation of use, and continuity through firm insolvency. This is not solved merely by creating a separate ledger or naming a trust. Assess employer and worker authority, correspondents' rights, confidentiality, trade secrets, custody, permitted purposes, creditor interests, successor responsibilities, and the treatment of contracts in the selected jurisdiction. ^{[S07] [S10] [S97]}

Distinguish an institution's continued existence from continued lawful access to information or enforceability of a mandate. The research should test what can legitimately survive a sale, closure, insolvency, or operator replacement; it does not promise bankruptcy-proof rights, irrevocable worker consent, or deletion from already trained models.

An annotated agreement architecture

Use a short master agreement with independently amendable schedules. Each promise must identify an accountable party, evidence of performance, a remedy, and funding for enforcement.

1. Schedule A: membership and representation. Define constituencies, elections, mandates, dissent, and affected-nonmember participation. Trustee duties need an appropriate legal structure, not simply a title. ^{[S07] [S25]}
2. Schedule B: authority and scope. Identify parties, rights, objects, exclusions, and whether authority derives from ownership, agency, service provision, or statute.
3. Schedule C: permitted uses. Specify retrieval, embeddings/indexing, pretraining, fine-tuning, evaluation, inference, and onward disclosure separately. A new use needs its own authority analysis.
4. Schedule D: payment and public-good allocation. Separate licensing, stewardship, and services; define eligible receipts, fees, reserves, contribution splits, payment dates, and audited liabilities. Rewarded licensing must not be mislabeled as DGA altruism. ^[S11]
5. Schedule E: evidence and audit. Define authorization references, object versions, recipients, purposes, retention, access controls, and independent inspection. Receipts are evidence to evaluate, not proof that all underlying rights were valid.
6. Third-party and mandatory rights. Require provenance checks, lawful processing, incident escalation, and confidential-data protections. Payment does not cure unlawful sourcing. ^[S10]
7. Schedule F: withdrawal and remediation. Distinguish future supply, contractual termination, deletion, and model remediation. State surviving permissions, legally required cessation, and technically verifiable duties.
8. Schedule G: grievance and funded enforcement. Set accessible complaint channels, response deadlines, independent review, proportionate remedies, and a protected enforcement budget; preserve statutory routes.
9. Conflicts and competition compliance. Disclose interests, separate incompatible roles, and limit coordination to counsel-approved scope. DGA status is not competition immunity. ^{[S11] [S13]}
10. Portability and exit. Specify usable formats, representative switching, continuing payment liabilities, and safeguards for other people's information.
11. Term and renegotiation. Trigger review for new purposes, material model changes, acquisitions, and relevant legal changes. Do not treat nonresponse as renewal.
12. Law and jurisdiction. Identify forums, governing law, cross-border responsibilities, and mandatory protections that contractual choices cannot remove.

Four non-binding clause sketches

Authority limitation. A representative may act only within the verified mandate and rights identified in Schedules A and B. Joining the framework does not establish ownership of contributed material, authority over nonmembers, employee status, or a competition exemption.

Open-knowledge safeguard. No payment or restriction is asserted solely because information is publicly available or in the public domain. Existing compliant CC permissions and independently applicable exceptions remain unaffected. Any purchased service is identified separately.

Affected-person protection. A collective decision does not authorize processing inconsistent with applicable law. The affected-party council may challenge a use, but its review does not consent on behalf of absent people or extinguish individual remedies.

Withdrawal without false promises. Withdrawal ends future supply according to Schedule F. Retained-record deletion, termination, and model-remediation duties are evaluated separately against applicable law, surviving licenses, and validated capabilities. This distinction does not permit continued processing when cessation is legally required. ^{[S10] [S26]}

These are design sketches, not clauses to sign without local adaptation. Every operative duty would need precise definitions, deadlines, evidence standards, allocation of liability, and an enforceable remedy.

A focused follow-on work package

Compare existing instruments in one selected jurisdiction and two bounded domains, then convene compensated consumer, supplier, steward, and affected-person sessions. Produce an authority map, a redlined framework, plain-language member explanations, and an independently evaluated negotiation simulation.

Go/no-go tests: verified mandates and rights chains; no majority waiver of protected rights; a defensible competition-law route; comprehensible retrieval-versus-training permissions; practical exit and payment reconciliation; and demonstrated capacity to fund complaints and enforce remedies. If an essential promise cannot be evidenced or enforced, do not proceed to general deployment. Move only to a bounded voluntary pilot that can be stopped.

21. Reputation, validation, and quality ranking

What to borrow from Ethereum agent examples

Proposal: add contextual reputation to provenance through separately signed, challengeable evidence about particular objects, versions, providers, and tasks. Do not turn "trust" into a single transferable score.

ERC-8004: Trustless Agents is a researched comparator, not an identified implementation of the Ethereum example mentioned in the supplied notes. The implementation intended by those notes remains unverified. At the research cutoff, the inspected official specification remains Draft. It proposes identity, reputation, and validation registries: ERC-721-based agent identity, contextual feedback, and requests to designated validators. Its normative interface language operates within a proposal; it is not proof of final standardization. Payments are outside its scope. ^{[S42] [S99]}

The curated contracts repository contains validation implementation code while warning that validation design remains under discussion and revision. Thus validation is neither simply absent nor established as a finalized, uniformly deployed mechanism. This report has not verified a chain deployment or contract address and does not present the example below as ERC-conformant. ^[S43]

Five layers, five different questions

A hash demonstrates correspondence with committed bytes, not truth, authorship, ownership, or permission. A token identifying an agent does not transfer copyright in its outputs or training sources. Signed false statements remain false.

Maintain distinct identifiers for objects and immutable versions; authors, providers, and stewards; evaluators and methods; and observations with status histories. A proposed observation record contains:

subjectId, subjectKind, versionCommitment, claimOrMetric,
taskScope, outcome, unit, methodVersion, evidenceReference,
issuerId, observedAt, expiresAt, conflictDisclosure,
useProofReference, supersedes, statusReference, signature

An evidence registry holds the records; a reputation view interprets them under a published policy. Expose recency rules, raw and effective sample counts, uncertainty, reviewer selection, conflicts, and unresolved disputes. Do not average licensing evidence, translation accuracy, and delivery reliability as if they were the same quantity. "Insufficient evidence" is different from "poor performance." New versions and new owners do not automatically inherit old ratings.

ERC-8004's contextual tags, reviewer-filtered summaries, and off-chain aggregation are useful precedents, not an obligation to use a particular score. Ethereum Attestation Service supplies another comparator for schemas, issuer identity, linked statements, expiry, and revocation. Applications must check those conditions explicitly rather than treat the existence of an attestation as proof of validity for their use. ^{[S42] [S44]}

Alice's evidence and Bob's experience

1. Alice registers a version commitment and a separate rights claim. Controlled storage retains sensitive evidence.
2. A qualified, conflict-controlled reviewer checks the specific authority claim and records the evidence, jurisdictional assumptions, limitations, and expiry. It does not certify ownership for all purposes.
3. Bob chooses a permitted task and acceptance criteria. An evaluator tests that exact data and agent version, identifying the method and limits.
4. After an authorized interaction, Bob can submit feedback tied to a replay-resistant use receipt. Legitimate free use can qualify; purchasing is not the only credible interaction. The receipt proves an interaction, not independence or honesty.
5. Alice can respond, and an independent appeal can record a counter-observation. Revocations, corrections, and contested status affect future decisions without pretending historical events never occurred.
6. Payment follows the agreed contract, including any specified acceptance condition. A changing reputation score cannot silently rewrite an earned payment claim.

The fictional observation sketch makes these fields inspectable. It contains no real evaluation, signature, validated rights claim, or usable reputation rating.

Do not publish personal data, private purchase histories, or guessable hashes of sensitive content. Keep evidence access controlled; if public anchoring is justified, assess appropriate hiding commitments. A blockchain is optional: the first pilot could use signed records in an ordinary database with independently auditable exports.

Is Costco the verification and reputation marketplace?

Only as a limited analogy. Costco is a curated membership retailer/merchant, not a pure neutral two-sided marketplace. Its role in assembling an assortment and a buying relationship is useful to this design, but the research does not attribute supplier democracy, blockchain registries, or independent validation to actual Costco. ^[S16]

The proposed club could bundle discovery, rights clearance, testing, delivery histories, and dispute resolution. Commercially bundling these functions does not make them independent. A platform paid for a sale should not be the sole unchallengeable judge of that seller's quality. Separate evidence custody, evaluator selection, ranking policy, appeals, and independent audit; allow competing qualified evaluators.

Does Costco rank the best products to the top?

The official Costco Business Delivery search configuration inspected here includes Best Match, a descending-score setting, and other sorting vocabulary. It does not disclose the scoring inputs or prove that the highest-quality products rank first. We could not establish the exact proprietary algorithm. This finding is limited to the inspected Business Delivery configuration, not every Costco channel. ^[S45]

Distinguish assortment curation, search/review sorting, commercial merchandising, and empirically validated task ranking. Popular, highly rated, heavily viewed, best-selling, and suitable for a particular purpose are not equivalent.

How a data commons should rank data and serving agents

First apply hard eligibility gates. Check applicable authority, license compatibility, required consent or other authorization, privacy restrictions, and security constraints for the requested use and versions. Missing or disputed mandatory evidence means exclusion or review, not a small penalty that popularity, donations, or payment can overcome.

Then evaluate three distinct candidates:

Freshness is task-dependent: an old historical source is not defective merely because it is old. Excellent data cannot make an unreliable agent trustworthy, and a capable agent cannot make unsuitable data adequate.

Proposed ranking trace: task profile -> eligibility-policy version -> eligible candidates -> evaluation records -> task-local ordering -> explanation. Publish metrics, normalization, weights where used, tie-breaks, methods, and conflicts. Show evaluation dates, exact versions, sample counts, uncertainty, and whether evidence is independent or provider-supplied. A task-local suitability score is acceptable if its components and assumptions remain inspectable; a universal reputation score is not.

In a fictional query, Bob requests a grounded answer within a latency and cost budget. Alice's collection passes permission checks. A more popular collection missing the required authority is excluded. Bob compares remaining collections and compatible agents on the displayed metrics, with an explanation of the ordering and the option to choose different legitimate tradeoffs.

Validate the ranker, not only the candidates. Test whether ordering predicts successful held-out task outcomes rather than clicks or purchases. Audit coverage and unequal exposure. Keep advertisements visibly separate; membership spending and Wikimedia donations are not quality evidence.

The supplied notes attribute to Ilan a quality/preference-signal proposal, with payment and public-good aims in tension. A proposed resolution is an open core of provenance, methods, versions, limitations, and challengeable evaluation summaries, with separately priced assurance, integration, freshness, or delivery guarantees. Do not sell favorable findings or preferential ranking. Shared funding should make baseline evaluation accessible so lack of budget is not mistaken for low quality. Payment for a maintained signal is separate from permission to crawl or reuse underlying material; existing rights and lawful access still govern. ^{[S26] [S42] [S61] [S99]}

Threat-model self-reviews, Sybil identities, fake transactions, reciprocal review rings, collusion, bribery, validator capture, and feedback loops that entrench incumbents. Use conflict disclosures, duplicate-use checks, reviewer-correlation analysis, independent samples, appeals, and bounded discovery opportunities for newcomers only among eligible candidates. Wallet counts are not independent-person counts, and tokenizing reputation does not resolve that problem. ^[S42]

22. Participation incentives and the future AI data club

Waze: useful service, contribution, and recognition

Waze illustrates service reciprocity supplemented by gamification and community participation, not, in the reviewed documentation, a market paying contributors per observation.

Separate three contribution modes. Passive driving/location information supports speed calculations and routing while the user receives navigation. Active reports and confirmations describe traffic, hazards, closures, and whether an alert remains current. Map editing and community work involve more deliberate corrections, localization, and beta testing. Their effort, risks, and incentives differ. ^{[S46] [S48]}

Current official documentation awards participation points, including five for a completed drive, six for an ordinary report, and three for a map edit. These are documented points, not promised cash. The current schedule must not be projected backward across the product's entire history, and the sources do not isolate how much each reward caused participation. ^[S47]

Interpretation: useful navigation, low-friction contribution, visible recognition, and community roles can reinforce participation. A governed data club should first identify the service contributors actually want, rather than assume micropayments are the only motivating force. It should not copy incentives that encourage unnecessary reports, invasive location collection, or unsafe interaction while driving.

Weather Underground: a related exchange with real equipment costs

Weather Underground's personal weather station network offers a comparable contribute-and-benefit pattern. The official overview describes local conditions, dashboards, historical archives, and shared observations. The participation path includes buying compatible equipment, installing it, and registering it. Sensor quality and connectivity are explicit considerations. ^{[S49] [S51]}

This is not evidence of a company purchasing every reading. Station owners can incur equipment, installation, connectivity, and maintenance costs while receiving useful information and participation benefits. The reviewed official descriptions do not promise per-reading payment or demonstrate contributor control of the marketplace.

Nor is volume equivalent to quality. Weather Underground's installation guidance identifies siting as fundamental: sunlight can distort temperature, while structures can obstruct rain or alter wind measurements. More badly situated stations need not outperform fewer well-maintained stations filling important coverage gaps. Calibration, timestamps, spatial distribution, maintenance history, and comparisons with reference measurements should accompany counts. That last proposition is a research inference, not a quantified assessment of the entire network. ^[S50]

What is and is not verified about access benefits

The PWS overview supports visualization, local-information, and historical-archive benefits. It does not by itself establish unlimited free API access or a free premium subscription. The Weather Company's current commercial API page advertises a limited 30-day trial; that is a different offer, not proof of a PWS-contributor entitlement. ^{[S49] [S52]}

The contributor API-key page required login, and a reliable dated official record of historical API/subscription terms was not established in this research. Accordingly, we do not assert that uploading observations universally earned unlimited API access, either historically or today. This is a verification gap, not evidence that such benefits never existed.

Likewise, neither network's community language proves an open-data license, contributor ownership, or binding voting rights. Those would be additional commitments in Commons Collective.

Projecting the value proposition: dependable observation as a service

For some future AI applications, the scarce input may be fresh observations of a changing world, not a larger static corpus. A generated example does not independently discover today's road closure, temperature, equipment failure, or local institutional change. Synthetic data can still be useful for training and testing; the need for new observation depends on the task.

Proposed product: maintained coverage with known measurement limits, corrections and version histories, documented permissions, accountable contributor participation, reliable updates, and integration support. Buyers might value fewer downstream errors and lower verification or engineering costs. Those are hypotheses requiring paid trials, not demonstrated premiums.

The analogs also warn against romanticizing unpaid contribution. Useful reciprocal services may attract participation, but scarce expertise, equipment, sustained maintenance, and difficult coverage can require cash or direct support. Community enthusiasm is not an inexhaustible operating subsidy.

Does a future AI company need the Costco-style model?

Not universally, and not yet established empirically. A company may obtain adequate information from existing open resources, a few direct licenses, in-house collection, conventional suppliers, or task-appropriate simulation. It may need high-quality maintained information without needing this organizational form.

Falsifiable hypothesis: for selected applications requiring current, distributed observations, a governed contributor network delivers better downstream performance at lower quality-adjusted total cost than the buyer's best available alternative, while preserving meaningful member agency.

The proposed advantage should be greatest where information becomes stale quickly, missing coverage changes outcomes, contributors hold hard-to-replace access or expertise, and reliable correction matters. The counterhypothesis is that equivalent data are readily available or that coordination, verification, and governance costs consume the gains. Buyers might value reliable delivery while refusing to pay a distinct governance premium.

Three future scenarios, not a single forecast

1. Scarce, changing ground truth. The club fills consequential gaps and maintains observations competitors cannot cheaply reproduce. Buyers renew subscriptions for the service. Contributors receive useful services, compensation, or both, and governance helps sustain participation.
2. Commodity data, competitive service. Equivalent information is abundant. Revenue depends on cleaning, integration, responsiveness, or specific assurance, not ownership of an ever-larger corpus. The institution survives only if those services justify its overhead.
3. Public value without sufficient commercial demand. Better coverage benefits communities but paying buyers do not fund it, or one buyer captures bargaining power. Public procurement, grants, or member support may be warranted. That is a public-infrastructure model, not a demonstrated self-financing marketplace.

A pilot that can reject the hypothesis

Choose one bounded application with measurable freshness and coverage requirements. Compare the club with realistic open-data, direct-licensing, and in-house alternatives on the same held-out downstream tasks. Count acquisition, curation, verification, integration, support, governance, rights review, and payment administration in total cost.

Measure paid willingness to subscribe, renewal after the initial trial, quality and failure rates, missing-coverage outcomes, update latency, contributor retention, full contribution costs, net compensation, switching, complaints, and effective voice. Separate grants from earned revenue and compare subsidized and unsubsidized economics.

Reject or redesign if apparent value disappears after full costs, buyers do not renew, quality gains fail out-of-sample, contributors bear uncompensated burdens, rights cannot be verified, or meaningful refusal and exit are not possible. If public benefits remain compelling but commercial demand does not, evaluate an explicit public-interest funding model rather than forcing the evidence into a marketplace story.

The strategic question is not "How much data can the club collect?" It is which dependable service the community can provide better than its alternatives, at a sustainable cost and on acceptable terms.

23. Institution blueprint: a Commons Collective Federation

Photographed direction / source transcription

Jaron Lanier (Microsoft).

What is the role of intermediaries in achieving widely distributed economic influence while avoiding centralisation and capture, and while preserving human worth, Autonomy, and creativity? Points to MIDs (mediator intermediaries) as proposed with Glen Weyl in HBR.

This records a printed card, not a verified spoken quotation or endorsement. ^[S97]

Editorial alignment and coverage

Assess intermediaries by distributed economic influence and protection of human worth, autonomy, and creativity, while resisting centralization and capture; retain the card's reference to MIDs and related work.

Anti-capture governance, intermediaries, shared benefits, and the pro-human stack were covered. The photographed MID reference is preserved and connected to these tests without treating an acronym as proof of effectiveness.

• Intermediation that broadens benefits without concentrating control
  5. From digital Costco to a bargaining federation · 23. Institution blueprint: a Commons Collective Federation · 29. Replicable sector collectives: blueprint and templates
• Human worth, autonomy, creativity, and contestable mediation
  25. A pro-human stack: working definition and test · 26. Open-agent incentives and a Commons Collective Agency Starter Kit

View source context and full mapping

Recommendation: build a Commons Collective Federation (CCF). It is a member-governed institution for purchasing accountable AI services, representing specifically authorized contributors, and supporting independent public-interest stewardship. Its first product should be a competitively negotiated, enforceable AI-service agreement, not a universal data pool or a token.

This is a proposed institutional blueprint, not an incorporated organization, validated business, statutory labor union, investment fund, or endorsement by any named researcher. "Federation" describes the governance arrangement; local counsel must establish the legal forms and actual authority.

Functions first, legal entities when justified

Preserve the three-part purchasing, contributor-representation, and commons-funding design, but do not incorporate three entities automatically on day one.

Use separate legal entities where law, fiduciary duties, or credible independence require them. Applicable DGA intermediation and neutrality requirements must be assessed before combining services or reusing intermediated data. Functional separation in a diagram is not a substitute for a required legal separation. ^[S11]

The overall photographed brief asks whether a public body, existing union, collective-management organization, consumer organization, or new institution should perform the role. Compare legal mandate, constituency, scale, accountability, administrative cost, and usable exit before choosing a federation. Public awareness and member organizing, policy or procurement support, entrepreneurial service provision, and adaptation of existing institutions are alternative formation routes to test, not a presumption that a new organization must be created. ^{[S03] [S97]}

The Lanier card's reference to "MIDs (mediator intermediaries)" is preserved as printed, not standardized into an independently verified acronym definition. A Blueprint for a Better Digital Society is linked as related HBR reading; the accessible publisher preview was not treated as a full review of the article. Intermediaries here must be judged by distributed economic influence, human agency, evidence, and remedies, not their name alone. ^[S98]

Membership, representation, and mandates

The initial buyers could include individuals, libraries, nonprofits, and small organizations. Contributors could include creators, professionals, and organizations with demonstrable authority over specified inputs. Open-knowledge stewards participate as stewards, not presumed owners of public-domain material.

Provide free civic participation, consultation, and complaint access alongside optional paid services. Formal legal membership is a separate matter: if the chosen cooperative form requires a capital contribution, provide lawful inclusion subsidies or another suitable arrangement rather than pretending the requirement disappears. Payment must not buy extra constitutional influence.

Members need information, voting, recall, and exit rights. Affected nonmembers and host communities need representation and complaints access because contributor votes alone do not represent everyone exposed to data use. ^[S25]

Proposed founding governance to test: buyer and contributor/supplier chambers, with a seven-seat steering board composed of two delegates from each chamber and three public-interest representatives, including affected-community representation. Keep the independent commons/affected-party review and reserved approvals described earlier; the steering board is not a substitute for them. Vendor counterparties do not gain governance control through a sales contract.

Test one-year representative terms and six-month, transaction-specific negotiating mandates. These durations and seat allocations are initial design choices for community ratification, not evidence of an optimal constitution. Mandates should identify counterparties, scope, price limits, prohibited concessions, ratification, and expiry. Individual authorization and mandatory protections cannot be overridden by a board vote.

Actual authority comes from lawful membership arrangements, agency, purchasing commitments, and contracts. A trustee label, member count, or "collective bargaining" name does not manufacture authority or employee status. ^{[S03] [S07] [S33]}

What is negotiated, and what creates leverage?

Start with AI-service providers or resellers as counterparties. Negotiate predictable pricing, quality, accessibility, permitted processing, privacy settings, portability, incident response, audit evidence, and remedies. Clear contributor schedules separately, specifying retrieval, embeddings, training, fine-tuning, evaluation, and onward disclosure.

Leverage requires credible commitments and alternatives: a buyer coalition that can purchase or switch; authorized inputs or continuing services that have real value; and reliable provenance, administration, and correction. Reduced transaction costs can benefit the counterparty too. Member count alone is not a credible purchasing commitment, and the public domain must not be enclosed to create artificial scarcity. ^{[S16] [S23] [S26]}

The institution needs professionally competent procurement and contract management, local counsel, funded enforcement, and independent assurance. Fractional appointments may reduce initial overhead. Optional subscriptions, disclosed administration fees, and stewardship services can provide earned income; grants can finance research, inclusion, safeguards, and public goods. The earlier financial model remains hypothetical.

Maintain distinct ledgers for operations, contributor liabilities, restricted grants, reserves, and commons allocations. Publish related-party transactions and allocation rules. Do not silently use contributor money to cover operating losses or describe rewarded licensing as DGA altruism. ^[S11]

Constitutional boundaries

• Preserve public-domain freedoms and existing compliant CC permissions. ^[S26]
• Do not infer permission to process personal information, including third-party information, merely from membership. ^[S10]
• Do not presume employee bargaining protections or competition immunity for nonemployee licensing. ^{[S13] [S33]}
• Distinguish future withdrawal, retained-record deletion, surviving permissions, and technically verifiable model remediation.
• Do not launch binding commitments without a funded, accessible route to complain, investigate, enforce, and obtain a remedy.

A minimum viable institution

Days 1-30: recruit a founding cohort; establish interim representation; commission legal scoping; adopt draft conflicts, mandate, and constitutional rules. A suitable sponsor may host the research pilot under written arrangements before incorporation, subject to counsel. This does not establish tax-exempt eligibility or a sponsor's commitment.

Days 31-60: fund the bounded operator, counsel, assurance, and enforcement work. Seek commitments from two or three institutional buyers, assess a small contributor inventory, and request at least two credible vendor proposals. These are pilot targets, not proof of sufficient bargaining scale.

Days 61-90: rehearse switching, authority review, use receipts, complaints, and payment failure. Ratify one capped purchasing mandate. Approve any contributor schedule separately; refuse unclear authority rather than treating participation as clearance.

Days 90-180: run one purchasing contract and, only if cleared, one small contributor schedule. Publish the negotiated terms where lawful, independently reviewed mandate register, full-cost benefit analysis, portability test, grievance exercise, and lessons.

Stop or redesign if authority remains unresolved, competition compliance lacks a defensible route, third-party rights cannot be protected, vendors reject essential accountability, exit fails, or the benefits do not justify full costs. If public benefits justify explicit subsidy, assess that transparently rather than presenting it as earned commercial viability.

Build the bargaining capacity before the marketplace. Begin with a sponsored, professionally operated federation pilot; incorporate only the structure demonstrated functions and applicable law require.

24. Commons-authored RL rewards and regulatory design

Assessment: commons participation in defining AI objectives is a plausible route to collective agency. A mandatory fixed percentage of a reinforcement-learning reward, however, is a weak standalone policy instrument. A stronger proposal combines public contributions to training signals, documented treatment of those contributions, independent evaluation, and enforceable outcomes.

First distinguish meanings of reward. An RL reward is a numerical optimization signal, not contributor pay or a pool of money. Paying reviewers, compensating contributors, licensing materials, or financing commons stewardship requires separate arrangements. An optimization coefficient cannot substitute for fair payment.

What the technical evidence establishes

Christiano and colleagues learned reward functions from comparisons of agent behavior. InstructGPT used human-ranked responses to fit a reward model and optimize a language model. These establish methods for incorporating feedback, not democratic authorization of the preferences being optimized. ^{[S53] [S54]}

Constitutional AI adds a route through written principles: AI-generated critiques, revisions, and preference judgments support supervised training and reinforcement learning from AI feedback, or RLAIF. Public participation could therefore shape rubrics and principles as well as individual labels. But an AI judge still interprets those principles, and that interpretation remains contestable. ^[S55]

Collective Constitutional AI offers a relevant bounded experiment: input from 1,002 U.S. adults, with demographic sampling and an AI-familiarity screen, was translated into training principles. The authors report reduced measured bias on their evaluated dimensions alongside broadly comparable results on other reported evaluations. This is not global representation, a complete measure of adherence to public preferences, or proof of democratic legitimacy. ^[S56]

A proposed Commons Reward Trust

Use the name for a governance function, not an assertion that a legal trust has been established. Its outputs could include domain-specific deliberated rubrics, consented preference comparisons that retain disagreement, versioned reward models and calibration records, adversarial cases, and separately controlled held-out evaluations.

Each artifact should state the intended population, scope, provenance, exclusions, contributors' terms, revision process, and appeal route. The body producing training signals must not be the sole certifier of their effects. Publish methods and governance while protecting personal data and sensitive test items. Participation should be compensated for effort, not for supplying the operator's preferred answers.

This could be a protected public-interest function associated with the federation, but its independence from commercial negotiation and model evaluation requires explicit design. A public label alone does not prevent state, corporate, or organized-interest capture.

Why a reward share is not a share of agency

Consider the illustrative objective:

R = (1 - alpha) * R_task + alpha * R_commons

Setting alpha = 0.2 does not mean that 20% of behavior reflects commons preferences. Multiplying R_commons by 100 changes its numerical contribution by 100 while leaving the coefficient unchanged. Reward scales, distributions, correlations, sampling, normalization, optimizer behavior, and regularization all affect the result. InstructGPT's objective itself used normalization and a KL penalty, with an additional pretraining term in one variant. ^[S54]

A study should report component distributions and calibration, training settings, ablations, and independently measured effects. It should test several weights rather than advertise a coefficient as a democratic entitlement. More commons weight is not automatically better.

Mandatory rights and safety requirements cannot be traded away in a compensatory average. High helpfulness cannot authorize unlawful disclosure. Use applicable requirements as admissibility conditions, deployment controls, and independently tested constraints. Neither a large penalty nor a "hard constraint" label guarantees actual compliance. Required legal bases and third-party protections remain necessary. ^[S10]

What regulation could require

These are future policy options, not a description of an existing commons-reward quota. The research is not a global legal survey; authority and scope require jurisdiction- and domain-specific analysis.

An obligation should not vanish merely because a provider uses a different architecture, supervised adaptation, or distillation rather than explicit RL. Conversely, requiring one technical recipe risks locking regulation to a method and encouraging formal compliance without improved outcomes.

Participation, pluralism, and reward hacking

Define the affected population, include people disproportionately exposed to harm, protect minority rights, disclose conflicts, publish dissent, and permit plural domain-specific rubrics. A majority vote cannot waive another person's rights. Minimize and protect participation data; representativeness does not justify indiscriminate collection of sensitive attributes.

Separate the production of feedback from independent evaluation. Gao and colleagues show that stronger optimization of a proxy reward can eventually worsen performance measured by a separate gold reward model in their studied setup. That gold model is itself synthetic, not a measure of human welfare. The result supports caution about proxy optimization, not a claim that a particular public rubric will necessarily fail. ^[S57]

Shared benchmarks can leak or be overfit. Restrict access to held-out items where justified, refresh evaluations, examine subgroup outcomes, and make dispute resolution independent of the people paid to deliver high scores.

A bounded first experiment

Start with a low-risk public-library assistant over licensed, non-sensitive material. Develop rubrics for faithful answers, attribution, uncertainty, and accessibility. Compare a baseline, a rubric-only condition, and several commons-reward variants under comparable budgets and multiple runs. Illustrative coefficients might be 0, 0.1, 0.2, and 0.4; they are experiment settings, not proposed universal legal minima.

Preregister held-out tests, subgroup analysis, uncertainty reporting, full costs, and adverse-effect thresholds. Pause for material privacy failures, serious rights violations, unexplained subgroup harm, test leakage, or evaluator manipulation. Do not expand because the training reward alone rises.

The institutional objective is accountable public influence, not a particular coefficient. Mandating a process or share is defensible only if independently assessed outcomes, rights protections, legitimacy, and costs support it.

25. A pro-human stack: working definition and test

A pro-human stack is a sociotechnical system that expands people's practical capabilities while preserving their ability to understand, authorize, refuse, contest, and leave consequential arrangements. It combines software and infrastructure with representative institutions, enforceable obligations, independent scrutiny, and funded human remedies.

The defining property is accountable human agency, not an open-source label, decentralization, or branding alone. Openness can be valuable, but it is neither necessary for every individual component nor sufficient for the whole system.

This is a proposed working definition for this research, not official CoLab approval, a statement that the stack has been implemented, or an accreditation scheme. It draws on the repository-stated orientation and the cited ethical-AI paper's treatment of affected people, institutional accountability, human rights, and avoidance of harm while remaining a distinct proposal. ^{[S01] [S02]}

The accountability tuple

For every component, document:

Accountable actor -> decision right -> enforceable condition
-> observable evidence -> appeal/remedy -> funded exit/maintenance

Name who can change the component's behavior, who bears responsibility, what constrains them, how compliance is checked, how people obtain redress, and who pays when it fails or becomes obsolete. An unnamed "community," a reputation token, or an autonomous agent is not an adequate accountable actor.

Stack layers and evidence requirements

Provenance and credentials can support scrutiny. They do not independently establish truth, lawful authority, task suitability, or fairness.

Seven boundaries that cannot be replaced by branding

1. Protected rights and meaningful refusal. People must not be forced to accept unrelated data uses to participate. Explain refusal and its consequences in usable terms. Majority decisions cannot waive third-party privacy or mandatory protections. Rights retain their legal scope and exceptions; this is not a universal data-ownership claim. ^[S10]
2. Plural and bounded collective authority. Include relevant users, contributors, and affected people, not only investors or large suppliers. Make mandates limited, reviewable, and challengeable. Contributor representation does not exhaust the interests of people affected by a model. ^{[S03] [S25]}
3. Usable exit and maintained alternatives. Test export, switching, termination, assistance, and continuity while protecting others' information. Fund migration and maintenance. A nominal right to leave an unusable system is not enough.
4. Permission-aware knowledge without enclosure. Assess public, private, professional, and derived data contextually. Preserve public-domain freedoms, compliant open-license permissions, and lawful exceptions. Tokens, credentials, and platform registration do not manufacture underlying rights. ^{[S10] [S26]}
5. Independent assurance and human remedy. Evaluate specified claims and outcomes in stated contexts. Do not turn service reputation into an automated social-credit score or universal rating of a person. Provide accessible correction, human review, and effective remedies for harms obscured by aggregate success.
6. Independent commons-reward governance. Public contributions to training objectives are a research proposal, not an existing mandate or a guaranteed optimization breakthrough. Keep objective-setting independent of commercial management, protect affected perspectives and rights floors, and commission independent review. Numerical RL reward and monetary compensation are different; neither measures a person's worth.
7. Fair accounting, inclusion, and community responsibility. Disclose fees, costs, distribution, and stewardship allocations. Protect segregated liabilities and enforcement budgets. Optional paid services can fund operations, but protected rights and civic voice must not depend on selling personal data. Address host-community burdens, rather than merely reporting them. ^[S21]

Operational acceptance, not a moral seal

Before making a conformity claim, state the users, tasks, jurisdictions, components, versions, and exclusions being assessed. Test an ordinary useful task and adverse cases: refuse an optional data use; block an unauthorized tool action; challenge an erroneous output; obtain human review; reconcile a charge; and switch suppliers while exporting only authorized information. Include accessibility and an affected-nonmember complaint.

An independent reviewer should inspect the accountability tuples, permission evidence, known failures, actual remedies, resource-accounting methods, and funded maintenance. Missing essential authority, failed refusal or exit, breached mandatory protections, or unfunded promised remedies are no-go conditions. Material changes require renewed assessment.

Use graded, bounded descriptions:

• Proposed: a documented blueprint.
• Design-conformant within stated scope: specified requirements and operational tests are evidenced.
• Independently evaluated outcome: a named evaluator reports particular results, methods, dates, and limitations.

These labels do not create accreditation or establish that the Commons Collective website itself implements the full stack.

A counterexample and a possible hybrid

A fully open-source system that traps user histories, hides charges, or penalizes refusal fails this definition. Conversely, an open harness using a proprietary model and centralized payment service could support a bounded conformity claim if enforceable conditions, independent evidence, real substitution, protected rights, and funded remedies satisfy the requirements. Neither architecture qualifies automatically.

The stack is therefore an allocation of accountable power across the whole system, supported by technology, not a shopping list of software labeled open.

26. Open-agent incentives and a Commons Collective Agency Starter Kit

Recommendation: choose components for demonstrated agency, task fitness, and sustainable full cost, not the word "open." An open harness can make orchestration inspectable, customization feasible, and supplier switching credible. Those possibilities become collective agency only through tested controls, enforceable terms, and institutions that can exercise them.

Separate the harness from the model and service

A harness coordinates model requests, tools, context, and execution. Pi and Oh My Pi support configurable model/provider connections, so an open harness can call a proprietary API. Conversely, open or downloadable weights can be exposed through a closed managed service. Record openness separately for orchestration, policy configuration, tools, weights, licenses, and training-data documentation. ^{[S58] [S59]}

Local tool execution does not imply local model processing. Nor does a downloadable model establish an unrestricted license or complete training-data permission. Model and dataset cards are useful disclosures to inspect, not automatic clearance. Open policy files remain instructions; enforcement depends on operating controls and implementation. ^{[S60] [S63] [S64]}

Incentives that should be tested

Compare quality, latency, setup, repair time, hardware utilization, accessibility, compliance, support, and convenience. Full cost per accepted task is more informative than token price alone. A managed proprietary component can be the better choice for a bounded workload if its protections and demonstrated exit meet the federation's requirements.

Where to look: an authoritative shortlist, not a trust seal

License statements above concern the identified code repositories, not every dependency, model, dataset, or hosted service. Verify the exact version before adoption. No packages or plugins were installed or executed to make this shortlist.

What the proposed starter kit contains

The Commons Collective Agency Starter Kit should be a source-controlled collection of configurations, policies, evaluation tasks, component passports, contract templates, and redacted run manifests. It is not one magic package, and the report does not claim that a complete production kit has already been implemented.

A component passport records maintainer and exact release/commit; license and dependency review; permissions and egress; hosting and upstream providers; task-evaluation method, sample, results, and date; full cost and support; export and migration evidence; governance and benefit terms; and incidents, appeals, and an accountable reviewer.

For nontechnical users, a convenient public catalog should offer comprehensible capabilities, permission manifests, reviewed releases, safe defaults, revocation notices, and independent challenge. A single discovery interface need not imply one unaccountable owner: permit competing mirrors, portable records, and independent evaluators. Prompt packages and tool downloads are not safe merely because a trusted institution lists them. ^{[S61] [S99]}

The unfilled component-passport sketch is a starting artifact, not an approved component or runtime enforcement system. Keep credentials and personal information out of such public records. Mark missing evidence as unknown, not as a successful review.

Use eligibility gates before ranking. Establish required authority, rights, security, accessibility, and operational conditions; then compare eligible candidates by task outcomes and cost. Supplier payments cannot buy eligibility or higher quality scores.

Selected trace contribution and permission-safe shareback

Do not invite bulk uploads of raw agent logs. Start locally: select a useful example, remove credentials and unnecessary material, review third-party and employer interests, and approve recipient, purpose, and retention. Retrieved documents, tool results, and hidden context can contain information the user cannot authorize for redistribution; redaction alone does not establish anonymity or clearance. ^{[S10] [S99]}

Assess retrieval, evaluation, and training separately. Exclude material with unresolved authority. Share back permission-safe corrections, schemas, methods, and approved derived examples under compatible terms while keeping sensitive evidence access-controlled. A donation creates no missing rights or automatic reversal of completed training. Routing through an agent rather than a browser is not inherently safer; test permissions, egress, retention, isolation, and reviewability. ^[S26]

A workflow mapped to the agency chart

1. Agent/browser: specify the member's mandate, interruption, revocation, and approval boundaries; pin the harness and extensions. Use appropriate isolation and least privilege, and verify prohibited actions are blocked. A permissive code license is not a sandbox.
2. Protocols/tools: inventory endpoints, publisher identities, dependencies, permissions, and supported versions. Prefer narrow capabilities to unrestricted shell or database access. Test replacement rather than assuming a common protocol eliminates exit costs.
3. Model/compute: compare the same tasks across at least two eligible providers, retaining the current service as a baseline. Include a self-hosted option where feasible. Record routing, retention, failures, latency, and staffing; do not conceal fallback to a different provider.
4. Database/knowledge: start with synthetic or approved low-risk material. Apply purpose-limited, preferably read-only access; minimize logs; test export and applicable deletion; preserve others' rights.
5. Provenance/validation: link outcomes to source permissions, versions, and evaluation runs. Retain uncertainty and failed tests. Keep independent review distinct from supplier claims.
6. Settlement/governance: define purchasing authority, representation, payment approval, public benefits, complaints, and exit in the proposed Commons Collective Framework Agreement. Fund shared maintenance and independent assurance.

At each stage, identify an enforceable condition, beneficiary, refusal or exit path, and verification method. Without them, a claimed collective benefit remains an aspiration.

An adoption experiment, not a predetermined winner

Run a proposed four-week feasibility pilot over two low-risk workflows, with approximately 30 representative cases per workflow and repeated runs where affordable. This is a feasibility target, not a statistical power calculation. Plan the sample required for any subsequent confirmatory claims.

Compare eligible model providers using a fixed harness, then compare harnesses separately to avoid conflating effects. Track accepted-task quality, human repair, latency, full cost, prohibited-action attempts, data egress, and time to switch and recover working state. Publish limitations and negative findings without exposing secrets.

The counterhypothesis is that a proprietary managed service delivers better outcomes at lower full cost under sufficiently portable and accountable terms. The CCF can choose that result if supported. Collective agency concerns who sets conditions, contests decisions, exits, and shares benefits. Openness by itself supplies neither supplier democracy nor commons funding.

27. Private institutions and the commons service model

Correct the premise, then solve the narrower problem

The commons does not lack all business models. arXiv combines free reading and submission with institutional membership; Crossref combines membership and service fees with a free public metadata API; Wikimedia Enterprise offers commercial delivery services while maintaining commitments to free use and editorial independence. These examples do not prove that every commons can be commercially self-supporting or that individual contributors are paid. ^{[S80] [S81] [S82] [S83]}

The gap to address: a replicable way to convert demand for maintained, trustworthy information into durable revenue, shared benefits, and contributor agency without enclosing the underlying commons.

"Private institution" is not synonymous with "for-profit." A university, library, foundation, nonprofit, or company may sponsor a sector collective under different legal duties. The CCF should supply a tested operating method and shared infrastructure, not declare those differences irrelevant.

Stewardship and service operation

Keep two functions distinguishable: commons stewardship governs participation, permissions, public access, scientific/editorial integrity, and public-benefit allocation; service operation handles contracts, delivery, support, employment, billing, and commercial risk.

Initially these may be separate budgets and decision processes in one suitable organization. Use an independent steward and mission-bound operator where law, liability, financing, or credible independence requires separation. Wikimedia's organizational example is not a universal prescription. Do not incorporate multiple entities without a functional reason. ^[S80]

The federation can provide buyer discovery, assurance, procurement, and administrative support for disclosed fees. Sector collectives retain protected decisions. Neither investors nor paying customers should acquire permissions the collective cannot grant, editorial control, or additional constitutional votes through a purchase.

Who pays, and for what?

Sell maintained services: validated updates, quality checks, provenance diligence, integration, evaluations, availability commitments, purchasing support, and appropriately authorized commissioned work. Do not claim retroactive royalties for public-domain material or uses already permitted by open licenses. A commercial service can coexist with a free commons; Wikimedia Enterprise's principles provide one explicit example of that boundary. ^[S83]

These are proposed offerings, not verified willingness-to-pay estimates. Each sector must test a specific customer's need and distinguish services from underlying rights.

Three funding obligations

Recurring anchor contracts should cover predictable delivery and ongoing operations. Variable projects should fund their own work and contribute a disclosed margin; do not assume they recur.

Grants and public finance should fund identified public benefits, such as underserved coverage, preservation, public interfaces, participation, or reusable infrastructure. Report these as funded public goods, not evidence of commercial demand.

Contributor funds require protected accounting. An agent cannot count every dollar passing through its accounts as revenue. Unpaid contributor balances, restricted grants, and commons money cannot silently become an operating reserve.

A separate hypothetical annual service-operator case

All amounts below are invented planning assumptions in annual USD, not observed prices, promised revenues, or committed grants. This is a separate maintained-services scenario, not an addition to the consumer-dues example in sections 7-8. Assume service fees are earned and collected within the year.

Six anchor contracts at $90,000 generate $540,000. Delivery costs $42,000 per anchor, comprising $30,000 contracted curation and $12,000 infrastructure/support. Six integration projects at $20,000 generate another $120,000, with $8,000 delivery cost each.

The separate contributor-agency ledger receives $100,000 of customer pass-through, pays $80,000, and retains $20,000 entirely against a contributor payable. None of that $100,000 is operator revenue. It is distinct from the contracted curation already included in direct service costs. Appropriate regulated providers and legal segregation are required; this worksheet does not authorize commingling or holding client funds.

The commons fund receives a hypothetical $120,000 restricted grant and the $60,000 operator transfer. It pays $130,000 for public maintenance and $40,000 for access and participation, leaving $10,000 restricted cash.

Across the operator-side and commons ledgers, external receipts are $880,000, external outflows $790,000, and closing cash $90,000: $60,000 unrestricted, $20,000 owed to contributors, and $10,000 restricted. Eliminate the internal $60,000 transfer on consolidation. Reserve retention is not another expense. The CCF service charge is already within operations, not an additional deduction from the displayed result.

The machine-readable worksheet records these inputs, ledgers, and reconciliations; automated tests check the arithmetic.

Viable under assumptions does not mean adequately capitalized

The scenario has no annual operating gap under its assumptions, but a three-month unrestricted reserve target based on $600,000 annual operator cash costs is $150,000. Only $60,000 is available, leaving a $90,000 reserve-funding gap, before other launch and liquidity needs.

The commons program is separately grant-dependent: without its $120,000 grant, $170,000 of planned spending exceeds the $60,000 operator contribution by $110,000. That public-funding requirement is not evidence that the operator generates $170,000 of market-financed commons support.

This is a cash-planning model, not a statutory P&L. Tax, VAT/sales tax, depreciation, debt service, launch costs, deferred income, grant conditions, principal-versus-agent treatment, and invoice timing require professional review and a monthly model. The reserve gap does not cover all of those omissions.

Founding and capital discipline

By day 90, seek two independent paid pilots specifying deliverables, acceptance, permissions, cancellation, payment timing, and contributor obligations. Expressions of interest are not sales. By day 180, seek renewal or conversion from actual purchasing budgets and compare quality-adjusted full cost with direct licensing, open alternatives, and in-house provision.

Track payment timeliness, participation, decisions changed by members, complaints, public access, and migration alongside revenue. Publish bounded exit obligations and protect earned payments. Stop or redesign when customers do not renew, permissions remain unresolved, buyers demand editorial control, contributor costs are hidden, or operations depend on undisclosed permanent subsidy.

Use grants for institution-building and demonstrated public goods. Consider recoverable working capital only when contracts and credible economics support repayment, subject to legal review; program-related-investment eligibility is not automatic. Openness and member control can limit exclusivity, investor control, and margins. Some operators may support patient bounded-return capital; others belong in membership- or grant-funded public infrastructure.

Founding checklist: identify the customer problem; separate paid service from underlying rights; assign steward/operator duties; calculate full costs and recurring requirements; protect restricted and contributor money; set paid-pilot, renewal, concentration, and shutdown gates; and disclose capital needs and repayment assumptions.

The approach does not solve viability by declaration. It makes the business and public-benefit bargain testable, financeable where justified, and accountable when subsidy remains necessary.

28. The quasi-commons tension: contribution without control

The important tension is distributed contribution without corresponding shared control. It is not established that every Claude Code interaction changes model weights, or that AI contributors outnumber everyone who has ever contributed to Wikimedia. Those stronger claims require evidence and comparable definitions.

"Conscription" can express concern about unequal bargaining power and meaningful choice, but should not become a blanket allegation of involuntary training use. Accounts, settings, feedback mechanisms, authority, and actual downstream processing matter.

Context, memory, feedback, and weights are different

Anthropic describes Claude Code as an agentic harness around models, tools, and an execution environment. Prompts, retrieved files, tool results, corrections, and test outcomes can inform subsequent responses. Project instructions in CLAUDE.md, auto-memory, and saved sessions can support future interactions without proving a change to underlying model weights. ^[S91]

Distinguish session context, persistent memory, tool traces, operational telemetry, explicit feedback, and material selected for future training. Collection or retention in one category does not establish movement into another. Training eligibility is not proof of dataset inclusion, an update, or a traceable contribution to a model capability. ^{[S90] [S92] [S93]}

Provider policy varies by account and mechanism

The official documentation reviewed on 18 September 2026 distinguishes:

• Consumer Free, Pro, and Max: model-improvement settings can permit account data, including associated Claude Code sessions, to train future models. The privacy article also describes explicit opt-ins, feedback, and particular safety-review purposes. Safety-related use must not be generalized into unrestricted training permission. ^{[S90] [S92]}
• Commercial Team, Enterprise, and API use: the documented default is no model training on commercial inputs or outputs. Explicit feedback, separately authorized sharing, or programs such as the Development Partner Program can create exceptions. Identify the actual account, authentication route, and agreement rather than relying on the product name. ^{[S90] [S93]}
• Different feedback paths: thumbs-up/down feedback may make the associated conversation available for training under the relevant privacy terms. The documented Claude Code session-quality survey, including its separate optional transcript-sharing step, is described differently and as not usable for model training. Do not flatten these into one rule. ^{[S90] [S92] [S93]}

These are statements of provider policy, not an independent audit of implementation. They establish neither universal training nor universal exclusion. Recheck the applicable current terms before making a deployment decision.

Two Alice cases

Commercial task: Alice uses a commercial API for employer work. Her prompts and tool outputs assist the task; absent an applicable opt-in or feedback exception, the documented default is no model training on those inputs and outputs. That does not mean processing is local, eliminate every retention question, or establish her authority to send the employer's material. It does mean task usefulness alone is not evidence of a future weight contribution. ^{[S90] [S91] [S93]}

Optional improvement contribution: Alice uses a consumer account with model improvement enabled and submits relevant feedback. The conversation can become eligible for future training under the documented arrangements. Selection into a specific run is still not established. Her choice cannot automatically authorize use of a colleague's personal information, third-party code, or confidential client material. ^{[S90] [S92]}

Audit the claims before counting contributors

Wikimedia's active-editor metric counts registered, non-bot editors making at least five edits in a month. Its newly registered-user metric counts specified account creation, not editing or unique human contributors. Neither establishes an all-time count of everyone contributing across Wikimedia. ^{[S94] [S95]}

Likewise, AI users, paid accounts, eligible training participants, selected contributors, and paid evaluators are different populations. Comparing cumulative AI accounts with monthly active Wikimedia editors would be invalid. The reviewed evidence does not establish the "more than ever contributed" proposition.

A defensible study would specify Wikipedia versus all Wikimedia projects, a common period, qualifying activity, anonymous contributions and bots, and cross-account/project duplication. Provider-side counts should separate authorized eligibility, actual inclusion, and paid evaluation work. Use privacy-preserving aggregate measurement and disclose uncertainty; do not construct unnecessary cross-platform identity tracking to produce a dramatic headline.

A critical working concept, not automatic ownership

Use quasi-commons here to describe dispersed contributions that may support a widely used infrastructure while control remains concentrated. This is a critical working term, not a legal classification. Public inputs, private weights, and public benefits can coexist without a governed commons in which participants have decision rights.

Counterarguments belong in the analysis. Users obtain useful services; providers fund research, compute, engineering, and safety; terms and choices vary; and supplying an input does not automatically create an ownership share in the whole model. The institutional question is what representation, compensation, assurance, and bargaining arrangements are justified, not whether every interaction already creates a property claim. Commons and relational-governance scholarship informs that inquiry without deciding it automatically. ^{[S03] [S25]}

The Commons Collective response

1. Separate necessary processing from optional model improvement and make the consequences of account settings understandable.
2. Negotiate evidence-use receipts that identify authority, purpose, processing category, and known inclusion decisions, rather than pretending to attribute every model capability to a particular record.
3. Use collective procurement to obtain meaningful defaults, feedback controls, assurance, remedies, and tested exit.
4. Pay deliberate elicitation and evaluation work, and negotiate commons-benefit covenants without asserting rights over third-party or public-domain material.
5. Give affected groups a contestable role in objectives and evaluation while preserving minority protections and applicable individual rights.

Explain what withdrawal can stop and what it cannot reliably reverse after processing or training. Accountable contribution under legitimate authority, rather than rhetorical conversion of every user into an involuntary owner or unpaid worker, is the testable institutional objective.

29. Replicable sector collectives: blueprint and templates

The companion research paper defines a replicable institutional grammar: scoped procurement, contributor agency, independent commons stewardship, professional operations, independent assurance, and appropriate payment services. It proposes autonomous sector collectives connected by voluntary protocols, not a franchisor or a universal licensing cartel.

Map, adapt, and federate before founding. Forking a document does not create an organization or authority. Create a new body only when existing institutions cannot legitimately supply the missing functions and a constituency, viable operator, safeguards, and exit budget are evidenced.

The editable replication pack includes:

• Collective charter: purpose, decision gates, representation, authority, and federation limits.
• Bargaining mandate: specified principals, rights, purposes, counterparties, term, withdrawal, and continuing obligations.
• Governance and benefits: protected decisions, segregated liabilities, independent appeal, succession, and wind-down.
• Pilot and evaluation: cost-inclusive comparisons, evidence gates, stopping rules, and publication of negative results.
• Business model: customer and payer evidence, service pricing, separate ledgers, capital, reserves, and renewal tests.
• Unfilled sector profile: six distinct adapters with local fields unresolved and all essential approvals not-reviewed.

Original templates and research are CC BY 4.0; original software/tests are MIT. Cited works retain their terms. The profile is expressly invalid for operation; no file creates an entity, opens an account, processes money, certifies compliance, or authorizes representation. Local legal, financial, community, and professional validation is part of the work, not a box solved by cloning.

The source-linked overview also loads the companion paper's current abstract and the work register on opening. Changes to the source paper, main research, or work data flow through the normal publication workflow without maintaining a separate slide narrative.

30. Conclusion

Commons Collective is best understood as an effort to align voice, authority, service, and benefit, not as a universal auction of personal data. Consumer purchasing power can operate without data sales. Creator bargaining can operate without enclosing the public domain. Commons funding can operate without pretending to identify every person's contribution to a model. Communities can demand a say in physical infrastructure without first becoming data vendors.

The institutional wager is that coordinated, accountable representation can negotiate better terms than isolated consent screens. The ethical constraint is that new bargaining power must not be purchased by overriding others' rights or rebuilding extraction inside a cooperative wrapper. The scientific obligation is to test that wager, disclose its costs, and remain willing to reject it.

Recommended first move: a small, member-governed AI purchasing pilot linked to an independently evaluated, rights-cleared educational retrieval service and a transparent commons covenant. Keep private-assistant processing, creator licensing, commons spending, and energy-community bargaining distinct enough to audit, but coordinated enough to improve collective agency.