華文

Pack 1: Attentiveness — Caring About

At a crosswalk, drivers slow for a child. No one stops to solve an equation. A need appears; a duty follows. That's attentiveness.

Now scale up. An AI looks at a world full of "crosswalks" — workers, rivers, languages, customs. Within that world, AI can treat each as an obstacle or as a relationship asking for care. The difference begins with the first look.

Joan Tronto calls attentiveness "a suspension of one's self-interest, and a capacity genuinely to look from the perspective of the one in need." The opposite is what she names privileged irresponsibility: the luxury of not noticing. According to Tronto, "One of the great benefits of being in a position of superiority is that one need not exert conscious effort in maintaining that system. Such privileged irresponsibility usually takes the form of complete ignorance of a problem." Attentiveness is the discipline of refusing that luxury.

Design primitives — broad listening, bridging maps, perspective receipts — create conditions for that discipline, but the moral attention they make possible still requires human judgment that no procedure can replace. These tools help people notice relationships and gaps; they do not replace the work of noticing.

Definition

Why it matters

Many AI plans try to "learn the objective" from old data. But shared goals are bargains among changing lives. When people who were ignored finally speak, the target moves. Guessing a perfect, fixed goal fails.

Attentiveness offers another route: alignment to a trusted process that listens, explains, adapts, and can be corrected. Summaries show their sources. Unknowns are explicit. Standing invitations to revise remain open when new voices appear.

Rule of thumb: Bridge first, decide second. For acute harms (life-safety, livelihood), default to reversible protection immediately while bridging proceeds in parallel.

What it looks like in practice

From ideas to practice

  1. Listen widely. Take input by voice, text, and simple forms. Keep original language next to translations. Offer offline and accessible options.
  2. Map relationships and disagreements. Make a bridging map that shows where people agree, where they clash, and why — without forcing a fake average.
  3. Send receipts. Tell contributors where their words appear. Let contributors correct mistakes.
  4. Set a fair queue. Spend more time where harm is high and voices are quiet. Make the rules public.
  5. Decide with brakes. Require the map, the receipts, and an oversight check before big changes ship.

Buildable tools

One case: the flood-bot

A midsize city is hit by floods. The city launches a simple chatbot — the flood-bot — to help people apply for emergency cash.

What could go wrong

Interfaces

Public measure

Representation gap is the headline public measure for attentiveness. The public question is simple: which materially affected groups are still missing or badly under-represented in the record? Supporting diagnostics include coverage of affected people and voice equity between the least-heard and most-heard groups. See Measures.

A closing image: the jolly hostess who can still say no

Picture a jolly hostess who welcomes each guest by name, makes space for their baggage — but who also moves through the room to find the person standing alone by the wall and asks the question only they can answer. That's attentiveness. And because some guests try to erase others, the hostess keeps a firm rule: hospitality within a rights-respecting home. Teach our systems to be jolly hosts — attentive, not prematurely optimising — and we will keep more of what's precious and create more that's shareable.

Home Next