華文

Pack 5: Solidarity — Caring With

Traffic is safer not because each driver is a saint, but because roads, signs, and rules make safe driving easier than reckless driving.

Even perfect local care fails in a hostile wider ecosystem. Solidarity equips the whole field so that civic behaviour wins by design.

Tronto's fifth phase — her new addition in Caring Democracy — demands that "caring needs and the ways in which they are met need to be consistent with democratic commitments to justice, equality, and freedom for all." This requires "plurality, communication, trust and respect." It is the political muscle of care: not just serving individuals, but ensuring the system itself is fair.

Collecting the passes

Solidarity means no one gets a structural exemption from caring. Tronto's metaphor captures this idea: "The first thing we need to do is collect all of those free passes out of taking care responsibilities seriously. No one automatically receives a pass out of caring because they are involved in protection, production, or taking care of their own, or are sufficiently wealthy to lift themselves by their own bootstraps or to give to charity."

For AI systems, the equivalent passes are: "we're too big to regulate," "users consented in the ToS," "we open-sourced the weights," and "we donated to safety research." The same logic of corporate irresponsibility — diffusing authority until no one is answerable — applies directly here.

Solidarity collects these passes by making cooperation structurally unavoidable. The "adopt-or-explain" mechanism (Pack 2) is one lever, but the "or-explain" clause has teeth only when the explanation is genuinely public and contestable. Without institutional culture to demand real accountability, explanation without binding consequence becomes a compliance gesture.

Core ideas

What good solidarity looks like

From ideas to practice

  1. Stand up an Agent ID custodian. Set up community orgs or public interest entities to issue/hold attestations; publish revocation and challenge endpoints.
  2. Mandate portability in procurement. Public buyers require protocol interop and exit-with-trust drills.
  3. Adopt bridge audits. Ensure platforms publish relational health metrics quarterly; have third parties verify.
  4. Join a safety federation. Contribute to and consume from a shared threat registry; localize enforcement.
  5. Default to bridge feeds. Make bridging-based ranking the default feed for civic contexts.

Tools (buildable today)

Flood-bot story: Part V

What could go wrong

Interfaces with other packs

A closing image: the well-marked interchange

Imagine a well-marked interchange — many lanes, clear signs, safe merges — where travel is smoother because the road is built for sharing.

Previous Next