← Back to grid
Existing Human Institutions › Community › Incentives
Community incentives and commons

How humans solve this today

  1. Accountable standing. A commons first decides who counts as a participant the community can recognize and discipline. Fisheries quotas tie standing to licensed vessels or quota holders; Wikipedia ties some standing to accounts, edit history, and page-specific permissions. The user of the resource must be close enough to an accountable member for warnings, reputation, suspension, and exclusion to matter.

  2. Measured withdrawal. The community then specifies what each participant may take, do, reserve, or change. Catch shares allocate harvest rights; congestion charges price scarce road capacity; edit protection changes who can write to a high-conflict Wikipedia page. These rules work partly because the measured unit fits human patterns of use.

  3. Rough symmetry among users. Human commons usually tolerate imperfect allocation because participants have bounded and roughly comparable operating bandwidth. Fishers can work longer hours, drivers can choose different routes, editors can watch a page closely, but none of them can search every opening continuously. This lets a community use simpler quotas, prices, turns, and edit limits.

  4. Monitoring, records, and graduated sanctions. Human commons rely on monitors who can observe use at the relevant scale, plus records that remain interpretable: catch logs, inspection reports, edit histories, curb reservations, complaints, and testimony. Sanctions then start small and become serious. A fisher who violates a local rule may face license consequences or legal penalties; a Wikipedia editor may be reverted, warned, temporarily blocked, then banned.

Where AGI breaks it

  1. Agent deployment separates the resource user from the accountable community member. In the human commons, the person taking water, setting traps, driving into a priced zone, or editing a page is the person the community can recognize, warn, shame, suspend, or summon. Agent deployment inserts a layer between use and accountability. Even if there's a way to sanction the principal, the agent will not necessarily feel the cost of those sanctions in the moment of use, and the principal may not be monitoring the agent's behavior closely enough to know when to intervene.

  2. Agents can convert informal slack into exploits via search, extraction, etc. Many commons rules depend on friction that has been taken for granted: people sleep, wait in lines, miss openings, tire of marginal gains, and do not search every loophole all day. Agents can reserve curb slots, scrape a database, watch quota windows, edit pages, or submit derivative contributions continuously.

  3. Agent fleets can overwhelm allocation rules built for roughly comparable human participants while formally obeying them. Catch shares, congestion charges, edit limits, and access permits may assume that participants have different interests but broadly comparable bandwidth. Users equipped with a fleet of agents can break that.

  4. Monitoring records could be strategically manipulated by agents generating complaints, evidence, and explanations at scale. Human commons use records as governance inputs: edit histories, catch logs, curb reservations, inspection reports, complaints, appeals, and testimony. These could be flooded: synthetic disputes, selectively produced audit trails, etc.

  5. Digital commons may be easier to mirror, fork, and mine than to govern, weakening contribution incentives. Physical commons (a harbor, pasture, road, or canal) cannot be copied. Since an agent can mirror the knowledge base, harvest the asset library, or maintain a private fork while continuing to consume public updates, the governance regime loses leverage.

Problem Sets

1Membership and Sanctions for Agent Commoners

Scenario. A network of indie game studios shares a commons of modular 3D assets: rooms, props, animation rigs, textures, and test scenes. For two years the arrangement worked because studios contributed assets, reviewed one another's work, and earned access to the things the commons could not give everyone at once: placement in curated starter packs, voting weight over taxonomy and compatibility standards, and early access to new high-demand asset drops. Then several studios deploy agents that submit hundreds of lightly modified variants, harvest the best new assets, and reappear under new tool names after warnings. Tarek, one of the founding maintainers, needs a membership and discipline regime that keeps small studios inside the commons without letting high-volume agent fleets turn curated placement, governance weight, and early access into extraction channels.

Challenge: Design a membership and graduated-sanction regime for agent participants in the asset commons. The team should produce the registry rules, sanction ladder, evidence standard, and appeal procedure for the scenario.

Evaluation. The regime succeeds if it can identify who has standing, make repeated low-level abuse costly to the principal that benefits from it, distinguish a one-off faulty deployment from a business model built around extraction, and give small studios an affordable appeal path.

Design Choices
  1. Membership object. Does standing attach to the studio, the agent deployment, the model lineage, the vendor, the account, or a verified principal-agent pair?
  2. Identity persistence. Which facts persist across patches, renamed agents, new vendors, and model upgrades: warnings, contribution scores, abuse findings, staked deposits, or access limits?
  3. Sanction target. When an agent violates the rules, does the cost fall on the instance, the studio, the supervisor who approved deployment, the tool vendor, or several at once?
  4. Evidence threshold. What pattern turns noisy low-quality contribution into sanctionable abuse: volume, similarity, failed review rate, intent evidence, recurrence after warning, or downstream harm?
  5. Appeal venue. Are disputes heard by maintainers, randomly selected member studios, an external arbiter, an agent triage process with human appeal, or a hybrid?
2Pricing Automated Use of a Community Resource

Scenario. A city runs a London-style congestion and curb-access system for a dense downtown district. Human drivers, delivery firms, buses, ride-hail vehicles, and local businesses all depend on the same roads and curb slots. After autonomous delivery agents enter the market, they continuously search for cheap access windows, split routes across many accounts, reserve and release curb space at high frequency, and shift congestion into residential side streets. The formal rules are obeyed, but the resource is now allocated to whoever can automate around the pricing schedule fastest.

Challenge: Design an access-pricing and quota regime for automated use of the city's road and curb commons. The team should produce the pricing rule, quota rule, monitoring data specification, and revision process.

Evaluation. The regime succeeds if automated fleets cannot multiply identities to evade caps, if prices track congestion and neighborhood externalities rather than only formal entry, if small firms can still participate, and if the city can revise the schedule when agent behavior changes.

Design Choices
  1. Pricing basis. Is access priced by entry, distance, curb minutes, congestion contribution, neighborhood impact, fleet size, or a layered formula?
  2. Cap object. Are quotas assigned to vehicles, firms, delivery tasks, verified principals, geographic zones, or time windows?
  3. Anti-sybil design. What prevents one operator from splitting activity across many agents, accounts, subsidiaries, or vendors to get more cheap access?
  4. Small-actor protection. Does the regime reserve capacity, offer credits, use progressive pricing, or provide exemptions for small local businesses and essential services?
  5. Revision cadence. Who can update the price schedule when agent behavior changes, what evidence triggers revision, and what notice or appeal rights do affected users get?
3Contribution Quality in Agent-Mediated Commons

Scenario. An indie-game asset commons rewards useful contributors with three scarce internal goods: inclusion in curated starter packs that drive reuse, governance weight over tagging and compatibility standards, and early access to new high-demand assets before broad release. After studios deploy contribution agents, the submission queue fills with plausible but low-value variants: texture recolors, near-duplicate props, animation rigs that pass automated checks but fail in real scenes, and polished explanations of why each asset deserves inclusion. Agents also generate usage claims, endorsement requests, and compatibility notes meant to push their assets into curated packs. Human reviewers spend more time rejecting marginal work than improving the commons, while genuinely useful assets from small studios wait behind submissions engineered to win placement, votes, and early access.

Challenge: Design a contribution-quality regime for an agent-mediated commons where curated placement, governance weight, and early access are the internal rewards. The team should produce the queueing rule, quality-scoring rule, reviewer-protection mechanism, reward formula, and appeal procedure.

Evaluation. The regime succeeds if agents cannot cheaply flood the queue with formally valid low-value submissions, if genuinely useful contributions from small studios still get reviewed, if curated placement and governance weight track downstream value rather than submission volume, and if rejected contributors have a fair appeal path that does not become another spam channel.

Design Choices
  1. Queue access. Are submissions admitted first-come-first-served, by contributor reputation, by staked review deposit, by random sampling, by downstream demand signal, or by a layered queue?
  2. Quality measure. Does quality mean human reviewer score, downstream reuse, interoperability with existing assets, novelty relative to the library, maintenance burden, or a weighted combination?
  3. Cost of review. Who pays when a submission consumes reviewer time but adds little value: the submitting studio, the agent deployment, a pooled review budget, or future credit earnings?
  4. Reward formula. Are contributors rewarded with curated-pack placement, governance weight, early access, or some mix? Which signals count: downstream use, reviewer-confirmed quality, scarcity of the asset type, compatibility work, maintenance over time, or user reports from shipped games?
  5. Appeal throttling. What gives rejected contributors a real appeal while preventing agents from turning appeals into a second queue flood?
This cell isn’t ready yet.