Collective Intelligence NetworkResearch & design project
← All notes Coordination

Why trust multiplies

Hard problems need many people working together, and the chance that a large group can all rely on each other usually falls as the group grows. Records anyone can check change that arithmetic.

14 October 2026 · 6 min read · Our current thinking, open to correction

1. FLAT CLOUD SOCIAL GRAPHS & BOT SWARMS • Strangers, scrapers & deepfake bots have equal reach • Sharing context leaks raw PII to central servers • Zero cryptographic proof of real-world trust Outcome: Social trust collapses under bot floods 2. CIN 4-RING CONCENTRIC TRUST ROUTING ✓ Ring 0 Device -> Ring 1 Kin -> Ring 2 Guild -> Ring 3 Mesh ✓ Progressive disclosure: less data leaves at each ring ✓ 2-of-2 hardware attestation blocks Sybil farms Outcome: High-bandwidth trust without surveillance
Interactive D3.js v7 Mechanism & Impact Explorer
Initializing D3.js v7 Mechanism & Impact Explorer (trust-multiplies)...

The arithmetic of trust

Inspect technical derivation, proofs & citations ▾

Take a simple model. A task needs a group of people, and each pair in the group must be able to rely on each other. If any two people trust each other with probability t, a group of k people has k×(k−1)/2 pairs, and the whole group holds together only if every pair does. That number of pairs grows with the square of the group’s size, which is why large cooperation is rare.

Inspect full technical derivation & primary sources ▾

Now suppose people do not need to trust each other one by one. Each only needs to rely on a shared record of signed commitments, verified deliveries and checkable observations. Then the group holds when each member can rely on the record, and the exponent grows only with the group’s size.

Chance the group holds, trusting pair by pair–
Chance the group holds, relying on a shared record–

Inspect fallback comparison table ▾
Without the calculator: chance a group holds together
5 people10 people20 people
Pair by pair, trust 0.9035%1%almost 0
Pair by pair, trust 0.9774%25%0.3%
Shared record, reliance 0.9786%74%54%
Raising trust between pairs from 0.90 to 0.97 makes a ten-person task about 29 times more likely to hold together. A shared record people can rely on at 0.97 lets a group of twenty hold together more than half the time.
Inspect full technical derivation & primary sources ▾

The model is deliberately crude. Real trust is not the same between every pair, groups do not simply hold or break, and records can themselves be forged. It is a hypothesis to test in simulation, not a law. But the direction fits the evidence: countries where people trust each other more have tended to grow faster, and studies of small groups have found a measurable collective intelligence that depends more on how evenly members take part than on how clever each one is.

1. Multiplicative Trust Dynamics Hard to earn (+2%), catastrophic to betray (-65%) Verified Honest Delivery: τ(t+1) = τ(t) · 1.02 Bounded in [0, 1] · requires sustained functional proof Caught Deception / Backdoor: τ(t+1) = τ(t) · 0.35 Two violations drop trust from 0.90 -> 0.11 (quarantined) 2. Inverse Transparency Curve Privacy for citizens, sunlight for concentrated power Tier 0 Everyday Citizen: 100% Local Privacy Zero public telemetry; only voluntary ZK capability proofs Tier 3–4 Public & Grid Roles: 100% Audit Log Every high-impact agent instruction is publicly co-signed Because every verified human has exactly 1 hardware-rooted identity, an attacker cannot reset a burned trust score by spinning up new accounts.
Why multiplicative trust and inverse transparency stop.

Transparency where power is, privacy where people are

“Transparency” here has a strict…

“Transparency” here has a strict meaning: what an agent agreed to, what an organisation holds, what a device reported.

Inspect technical derivation, proofs & citations ▾

It does not mean that people’s lives are visible. A community that tried to raise trust by watching its members would destroy the thing it is trying to build, because people would stop being honest with it.

Every person brings computing

We treat access to computing…

We treat access to computing as part of what every person is owed: a personal agent needs somewhere to run.

Inspect technical derivation, proofs & citations ▾

If every member brings their judgement and a share of computing, the problems a group can take on grow with the size of the group that can hold together, and trust sets that size. A community with checkable records can pool more people and more computing on one problem, solve harder problems, and prove its improvements sooner.

Communities that copy and change each other

Communities will disagree about how…

Communities will disagree about how to run their records: how much to reveal, how fast recognition should fade, who may observe what.

Inspect full technical derivation & primary sources ▾

The answer is not one rule for everyone. Any community can copy the shared rules, change one, and run. Open-source software shows this working: LibreOffice split from OpenOffice in 2010 and MariaDB from MySQL in 2009 when their communities lost confidence, and both are still maintained. The economist Albert Hirschman argued in 1970 that the freedom to leave keeps institutions honest.

Each community’s results would be recorded in a form others can compare: which rules hold larger groups together, which protect people with the least, which get the most done. Rules that work spread by being copied. Rules that fail are dropped. No one is forced onto a rule, and anyone can move to a community that suits them.

What could happen

Key architectural rules, failure boundaries…

Key architectural rules, failure boundaries, and verification steps for what could happen.

Inspect full technical derivation & primary sources ▾
  • We want thisLarge groups work together

    Communities with shared, checkable records routinely run projects with dozens of members.

    For example: forty households and their agents design, fund and install a neighbourhood heating network, each checking the others’ commitments on the shared record rather than vetting forty strangers.

  • We want to avoid thisA forged record is trusted everywhere

    High reliance on a record that can be falsified multiplies harm instead of output.

    For example: a batch of forged delivery records lets one supplier claim hundreds of rewards before independent observers notice.

  • We want to avoid thisTransparency turns into surveillance

    Communities try to raise trust by watching their members.

    For example: a housing co-operative asks members’ agents to share location history “for trust”, and half the members quietly stop using their agents.

  • We want thisBetter rules spread

    Communities copy and change the rules, compare results openly, and what works spreads.

    For example: a community that slows how fast recognition for care work fades sees more people take part after a year, and nine others copy the change.

What comes next

Inspect technical derivation, proofs & citations ▾

A simulation comparing trust pair by pair with a shared record, for groups of 5 to 100, with noise, forged records and members free to leave.

Inspect technical derivation, proofs & citations ▾

If a shared record does not at least double the largest group that holds together, we will say so and drop the claim.