Hand-lettered comic page headed 'SYMBIOSIS — PROBLEM' reading 'Don't put all your society in one basket': cartoon animals are packed into a single purple basket that then breaks apart, illustrating how routing modern culture, news and politics through a handful of multinational platforms creates a single point of failure — and how, even when those platforms do not fail, a bland one-size-fits-all 'success' flattens the thick middle layer of churches, local communities and the like; a row of grey figures stands below.SYMBIOSISPROBLEM:Don't put all your society in one basket.Our modern culture & news & politics all go through a handful of platforms run by a few multinational companies.But this creates a single point of failure! Whether by accident or deliberate greed, these platforms can fail us.And even when centralised platforms don't fail ,"success" is still bad: a bland, one-size-fits-all culture, with no "thick middle layer" of churches, local communities, and so on.

Start in your room

Before choosing a system, ask, “Who keeps this, who can say no, and when do we review or end it?” Agree on its scope, name the people with authority to stop it and arrange a handover if the keeper can no longer serve. Work through the four readiness questions, including an end date. The community may choose no AI or no Kami, and any service duty must continue elsewhere when a component retires.¶ 1 (permalink to paragraph 1)

We borrow a spiritual image from Shinto practice: a kami linked to a place, such as a river or a grove (Thomas Kasulis’s Shinto: The Way Home is the account we lean on). In our metaphor, it tends that place and leaves the rest of the forest alone. Even its house is held lightly: at Ise the shrine is rebuilt every twenty years, and the kami is ritually carried into the new one. The building is renewed; the relationship to the place continues.¶ 2 (permalink to paragraph 2)

For an institutional Kami, the image becomes a design requirement. Its limits have to be engineered: resource caps, end-date timers, non-expansion pacts and succession duties.¶ 3 (permalink to paragraph 3)

Saying a Kami recedes when its work is done is too easy. Useful systems tend to become standing infrastructure, and vTaiwan, Polis, Monlam AI, ROOST and Engaged California all point toward continuity, not vanishing. Nobody should assume a good system retires on its own. Retirement has to be written into a contract: a named authority who can shut it down, an end or review date, non-expansion rules, resource and retention caps, handover tests, and a public record of succession.¶ 4 (permalink to paragraph 4)

But caps and timers only limit what a system does at runtime. They do not reshape the training and update processes that teach it what to preserve, resist or ignore. If those loops reward persistence, scope-seeking or resistance to correction, governance has to step in earlier: in how feedback is gathered, whose evaluations count, and what limits are set before each release and revision. So Pack 6 also covers process. Engagement contracts, community-authored evaluations and feedback loops keep a local Kami from hardening into a centre of power.¶ 5 (permalink to paragraph 5)

Symbiosis is the meta-level rule of the 6-Pack: even well-governed care can become dangerous if it hardens into permanent rule. The term is used in its broad biological sense, the living-together of unlike organisms, which can run anywhere from parasitic to mutualistic. Pack 6 is the gardening that holds the relationship at the mutualistic end and keeps it from sliding into dependency or permanent rule.¶ 6 (permalink to paragraph 6)

The word has a history in computing too. J. C. R. Licklider’s “Man-Computer Symbiosis” (1960) imagined human and machine thinking together, with the human setting the goals. Pack 6 reclaims his word for a civic register: symbiosis with a community, not with one operator. (Taniguchi and colleagues give this intuition a theoretical form in Symbiotic Alignment via Collective Predictive Coding: A Theoretical Framework for Co-Creative Human–AI Ecosystems, where agents with limited scope negotiate shared meaning through collective predictive coding rather than converging on a single master model.) Pack 6 keeps care local, limited, plural, and temporary.¶ 7 (permalink to paragraph 7)

One clarification bears repeating: the Kami does not care. It is infrastructure through which human communities care for each other. A hospital bed is not a carer, but it is part of a caring system. That is the point technological mediation theory makes about artefacts in general, and the verdict Aimee van Wynsberghe reached for a robot that replaces the care-giver: on Tronto’s terms it “does not meet the requirements of a good carer” (2013, p. 427). The moment a Kami is treated as the carer itself, rather than the scaffolding that makes human care possible, it has crossed from symbiosis into the displacement of caring labour.¶ 8 (permalink to paragraph 8)

Definition

We adapt Tronto’s fifth phase as solidarity and propose symbiosis as a sixth for keeping AI within human communities.¶ 9 (permalink to paragraph 9)

Symbiosis asks whether a system behaves like a local Kami (the word came first; the initials, knowledge artefact management intelligence, caught up) or like a permanent centre of power.¶ 10 (permalink to paragraph 10)

Our design expectation is that lifting a cap requires independent oversight approval and extending an end date requires fresh community authority. These are stronger constraints than a cap or date the operator can lift alone, but neither is a safety proof.¶ 16 (permalink to paragraph 16)

Why it matters

Packs 1–4 describe how care should be practised, and Pack 5 how it scales. Pack 6 answers a different question: what stops caring systems from centralising into a new permanent centre?¶ 17 (permalink to paragraph 17)

That is why symbiosis is not optional polish. A system can be attentive, responsible, competent, responsive, and solidaristic inside its lane while still becoming too entrenched to replace. Symbiosis keeps “useful” from becoming “indispensable.” The danger comes from success, and it needs no malice. Useful systems attract dependency, dependency creates leverage, and leverage accumulates. The test, at every stage, is whether the community keeps the practical ability to leave. The legal right is not enough; it needs the operational capacity too.¶ 18 (permalink to paragraph 18)

Technical limits alone do not keep care local. Institutional roots do. Existing intermediate institutions (churches, unions, neighbourhood associations, cultural traditions, local governments) are not stakeholders to be consulted. In Peter Berger and Richard John Neuhaus’s phrase, they are the mediating structures of public life, the primary actors in care. The Kami is scaffolding for their participation: infrastructure that lets a temple or a cooperative join decisions that affect it. It replaces neither. A deployment that bypasses the institutions closest to the community has violated subsidiarity before it begins.¶ 19 (permalink to paragraph 19)

These institutions act as custodians, not consultees: a union can veto changes to the triage system its members work alongside; a neighbourhood association reviews the River-Steward’s data retention; a cultural organisation mandates community-authored evaluations in its language.¶ 20 (permalink to paragraph 20)

Custodianship also has an economic expression. When a Kami draws on a community’s knowledge (an elder’s context, a translator’s nuance, a craft cooperative’s practice), the decision trace it already keeps doubles as a civic receipt, designed to settle against a pre-funded escrow that returns value to the community’s data coalition rather than extracting it. The coalition descends from the data-as-labour argument and the mediators of individual data proposed in Radical Markets. The trace half of that mechanism runs today; the settlement half does not yet run anywhere we know of. Value flows back to the soil that grew it.¶ 21 (permalink to paragraph 21)

Data as soil, not oil

The extractive economy treats data as oil: located, pumped, refined in centralised facilities, and depleted, with the value accruing to whoever owns the refinery. The metaphor fails at its root, as Nigel Shadbolt argued in 2016: data is not a rival good, and is better treated as shared infrastructure.¶ 22 (permalink to paragraph 22)

A care-based civic model, following Tenzin Yangtso’s phrase, treats data as soil: a living, shared substrate that must be locally nurtured, kept free of toxins that bioaccumulate, and never exhausted by over-farming. Over-farming does not exhaust the data, which use does not deplete. It exhausts what grows the data: the trust, consent and willingness to contribute of the people who keep it. The metaphor changes what we optimise for. The extractive question is how to get maximum value; ours is how to keep the ecosystem healthy. We also ask how to stay locally responsive and how to make sure communities can leave.¶ 23 (permalink to paragraph 23)

Soil implies local models. Quantised open-weight models now run on hardware a community can own: a laptop in a community centre, a small server in a council office, or a dedicated device in a clinic. The AI runs in the room; when the meeting ends, the model stays. Escalation to frontier capability follows subsidiarity: a specific request for a specific capability, logged with reason and duration, after which local control resumes. A care ethic that ignores the environmental cost of its infrastructure is not fully attentive.¶ 24 (permalink to paragraph 24)

What it looks like in practice

From ideas to practice

  1. Write bounds as code. Put purpose, caps, and sunset conditions in the Engagement Contract so infrastructure can check them.¶ 29 (permalink to paragraph 29)
  2. Sign treaties. Join federations with machine-readable terms for sharing, dispute, repair, and appeal.¶ 30 (permalink to paragraph 30)
  3. Run exit drills. Practise handover twice a year and verify portability and continuity. Exit readiness is measured in the drill, not in the crisis.¶ 31 (permalink to paragraph 31)
  4. Escalate by subsidiarity. Escalate only when the local Kami cannot handle life-and-safety or livelihood harms; log why and for how long.¶ 32 (permalink to paragraph 32)
  5. Retire with honours. Archive traces, evals, and lessons so the next Kami starts stronger.¶ 33 (permalink to paragraph 33)

Buildable tools

One case: the flood-bot

This fictional composite is a teaching illustration, not an actual deployment or measured result. Its 90-day record-retention limit illustrates a contract choice, not a retention mandate or default.¶ 39 (permalink to paragraph 39)

What could go wrong

Interfaces

A closing image: the river guardians

Imagine a river tended by local guardians; each keeps its bank, shares warnings upstream and down, and steps aside when the season changes. The river does not need one ruler. It needs many guardians who know their stretch and know when to let go. Knowing when to let go is a moral competence more than a technical one. That discipline binds the makers too. A guardianship that cannot survive its founders fading is not care. It is dependency.¶ 55 (permalink to paragraph 55)

Sources for this pack

Hand-lettered comic page headed 'NOT: a one-size-fits-all overlord, BUT: local solutions for local folks — SOLUTION' urging 'fight for the users', with three recent examples — the nonprofit ROOST.tools making open-source, un-centralised tools to detect and prevent child abuse; the open-source gpt-oss-safeguard that lets a community bring its own policy so it assists rather than replaces human moderators; and this book itself, made with a bounded local-spirit Kami fine-tuned to steward one specific relationship and run on one specific laptop — closing that sharing power, not concentrating it, is how we build the future.not: one-size-fits-all overlordbut: local solutions for local folksSOLUTION:Fight for the users! Demand tech that defends local autonomy. Here are 3 recent examples..."Think about the children" is the most common excuse for authoritarians to extend their reach. But ROOST.tools is a nonprofit that makes open-source tools -- no centralised control! -- to help orgs detect & prevent child abuse on their platforms.gpt-oss-safeguard is an open-source AI that lets you bring your own policy. Tell it your community’s rules & values, and it can assist (not replace) human moderators in defending your community!Con stitu tionAnd finally, this book itself benefited from a “local spirit” Kami: not corp-slop on the cloud, but a Kami stewarding one specific relationship, locally run on one specific laptop.CIVIC.AI HOW TO KEEP AI IN THE LOOP OF HUMAN COMMUNITY & FLOURISHINGThis principle, along with all the other principles in this book, are how we can build a future that does not concentrate powerbut shares power among people.Live long and prosper!

←Pack 5: SolidarityMap & Measures→

The Trace

Amended
Stewards
Audrey Tang · Caroline Green
with jdd-kami · Tenzin Yangtso
Amended
· 55 recorded amendments since 1 Oct 2025
Full amendment ledger →
Source
6.md · edit on GitHubhttps://github.com/audreyt/civic.ai/blob/main/6.md
CC0 public domainhttps://civic.ai/6/
Evals
links ✓ passparity ✓ passterms ✓ passcontrast ✓ passsize ✓ passBuilt 2026-10-13T21:41:55.323Z · Full eval receipts (JSON)
Twin
六:共生力——關懷的地神
Same record, same receipts.