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, communities recovering from floods. 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.
Carol Gilligan names the muscle this trains: "Radical listening holds the potential for transformation because it starts from a place of not knowing and develops the muscle of curiosity." Curiosity is not passive; it is built through repeated acts of turning toward the absence rather than assuming it means nothing is there.
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
- Relationships first. The relationship is the basic unit of care. Some situations make duties visible because of roles and dependencies. Listening means secure channels for voluntary input and recognition, not passive surveillance or data exhaust. Surveillance is attention without relationship; listening is attention within one.
- Power must answer questions. Decisions should be explainable and challengeable. If no one can question you, the process isn't fair.
- Be precise only when it helps. Start with stories and people. Add numbers when they clarify; update them when reality changes.
- Rights baseline. This project operationalises care ethics within rights-respecting, pluralist democratic institutions. We use the Universal Declaration of Human Rights plus local constitutional rights as the floor for participation. Rights are not opposed to care; they are the threshold condition for relational standing — the floor that keeps care from becoming domination.
- No fake pluralism. If someone's basic existence is being erased, they cannot participate as an equal in a bridging process. Claims that try to erase someone's standing are recorded but do not set the agenda. Hospitality has a floor.
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
- Look for absences. "We heard nothing from night-shift carers — go find them." Missing voices are evidence. Hélène Landemore calls this the test of a "jolly hostess": not merely keeping the door open, but bringing the quiet people into the room.
- Show your work — as a brochure. Present AI outputs as brochures: shared, editable artefacts that link every claim to its sources and mark disagreements, rather than private chat replies that smooth them into false consensus.
- Share attention fairly. Don't just follow the loudest. Give time to those most affected. Pay extra attention to smaller groups that are easy to miss and harder to reach.
- Read the conflict pattern. When mapping disagreement, ask whether the same groups oppose each other on every issue (reinforcing cleavages) or whether alliances shift from issue to issue (cross-cutting cleavages — the bridges worth finding). The map should surface the people who can bridge those divides and flag the splits that need extra care.
- Build in repair. Sunset clauses, review points, reversible defaults, and the humility to shut down or hand off.
From ideas to practice
- Listen widely. Take input by voice, text, and simple forms. Keep original language next to translations. Offer offline and accessible options.
- Map relationships and disagreements. Make a bridging map that shows where people agree, where they clash, and why — without forcing a fake average.
- Send receipts. Tell contributors where their words appear. Let contributors correct mistakes.
- Set a fair queue. Spend more time where harm is high and voices are quiet. Make the rules public.
- Decide with brakes. Require the map, the receipts, and an oversight check before big changes ship.
Buildable tools
- Broad listening. Multi-language, multi-channel input with source and uncertainty kept intact.
- Bridging maps. Charts of overlap and disagreement, with citations.
- Perspective receipts. Receipts that allow each person to find and correct how they were represented.
- Machine-checkable rules. Community data rules written to ensure software can enforce them automatically.
- Fair queues. Simple algorithms that favour high-risk issues and quiet voices.
- Jolly-hostess prompts. Governing instructions that require the AI to act as a bridging host — representing quieter groups, flagging under-representation, surfacing uncommon ground — so attentiveness is structural, not incidental.
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.
- Listening. People send voice notes, texts, or visit a kiosk. Messages stay in the original language, with a clear translation beside them. Elena, a night-shift hospital worker whose landlord never gave her a formal lease and whose papers were lost to the flood, records a voice note in her first language at a kiosk: she has no standard documents, but neighbours and a landlord who can vouch for her.
- Mapping. The team sorts needs into categories: housing, wage loss, documentation barriers. They keep disagreements visible — renters and homeowners need different proofs.
- Receipts. Every contributor gets a link to see how their words were used and a button to say "that's not what I meant."
- Fair queue. Priority human review for people flagged as both high-need and low-digital-footprint — those most likely underserved by standard channels. The algorithm doesn't decide the case; it makes sure a human looks at it promptly.
- Measure. A public dashboard shows who has been reached, who is still missing, and whether the queue is fair.
What could go wrong
- One metric runs the show. Engagement is up, but trust is down. Fix: Use a small set of balanced measures and rotate them.
- Listening theatre. Glossy reports, same outcomes. Fix: Real decision gates, outside veto power, and spot checks.
- Loud voices take over. Well-funded groups flood the channel. Fix: Throttles, fair quotas, public attention dashboards.
- First movers freeze the frame. Early language locks in. Fix: Rolling windows and boosts for late but important views.
- False balance. Treating harmful claims as equal. Fix: Separate facts from values, uphold basic rights, refuse fake equivalence.
- Fake crowds. Copy-paste comments. Fix: Source checks and rate limits.
- Capture by power. Oversight migrates toward those with most to lose from scrutiny. Fix: Keep oversight independent, rulings public, funding transparent, membership regularly renewed.
- Procedural capture. Process professionals learn the format; resourced orgs dominate the queue. Fix: Fund participation — paid time, childcare, translation, community intermediaries — and track who is missing, not just who shows up.
Interfaces
- From Responsiveness (Pack 4): repair loops and newly discovered needs restart the cycle.
- From Symbiosis (Pack 6): retired agents gift maps, evals, and receipts, offering a better baseline for the next first look.
- To Responsibility (Pack 2): attentiveness hands over the who, what, and why — along with flags on rights and unknowns. Without attentiveness, responsibility operates in the dark; without responsibility, attentiveness is merely observational.
- To Competence (Pack 3): high-caution areas become small, safe-to-fail trials.
- To Solidarity (Pack 5): fair attention and open challenge build cross-group trust.
- To Symbiosis (Pack 6): The system serves a place and time, and treats shutdown as success.
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, actively curious about who is not yet in the conversation — and we will keep more of what's precious and create more that's shareable. A need appears; a duty follows. That's where everything begins.
