華文

Pack 6: Symbiosis — Kami of Care

In Shinto practice, a Kami belongs to a place — a river, a grove. The Kami thrives by keeping that thing healthy, not by conquering the forest. If the shrine is rebuilt or the seasons turn, the Kami departs without regret.

An AI has no such nature. Its boundedness must be engineered — resource caps, sunset timers, non-expansion pacts, succession obligations — so that what a Kami does by grace, the system does by design.

But caps and timers only bound runtime behaviour. They do not by themselves reshape the processes that teach a system what to preserve, resist, or ignore. If training and update loops reward persistence, scope-seeking, or resistance to correction, governance has to intervene earlier: in how feedback is gathered, whose evaluations count, and what bounds are set before release and revision. That is why Pack 6 is not only about limiting output. It is also about cultivating process through engagement contracts, community-authored evaluations, and feedback loops that keep a local steward from hardening into a centre of power.

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 — and Pack 6 is the gardening that holds the relationship at the mutualistic end rather than letting it slide into dependency or permanent rule. Pack 6 keeps care local, bounded, plural, and temporary.

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. 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.

Definition

Symbiosis asks whether a system behaves like a bounded local steward, or Kami — the word came first; the initials, knowledge artefact management intelligence, caught up — rather than a permanent centre of power.

Why it matters

Packs 1-5 describe how care should be practised. Pack 6 answers a different question: what stops caring systems from centralising into a new permanent centre?

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 risk is not malice but success: useful systems attract dependency, dependency creates leverage, and leverage accumulates. The test, at every stage, is whether the community retains the practical ability to leave — not just the legal right, but the operational capacity.

What keeps care local is not just technical boundedness but institutional rootedness. Existing intermediate institutions — churches, unions, neighbourhood associations, cultural traditions, local governments — are not stakeholders to be consulted. They are 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, not a replacement for either. A deployment that bypasses the institutions closest to the community has violated subsidiarity before it begins.

These institutions serve as custodians, not consultees: a union can veto changes to the triage system its members work alongside; a neighbourhood association reviews the flood-bot's data retention; a cultural organisation mandates community-authored evaluations in its language.

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 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.

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. A care-based civic model 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. The metaphor changes what we optimise for: not "how do we extract maximum value?" but "how do we keep this ecosystem healthy?"; not "how do we scale globally?" but "how do we keep it locally responsive?"; not "how do we retain users?" but "how do we ensure communities retain the ability to leave?"

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, 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 stewardship resumes. Running locally also spends a fraction of the energy of an equivalent cloud call — a care ethic that ignores the environmental cost of its infrastructure is not fully attentive.

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 and enforce them with infrastructure.
  2. Sign treaties. Join federations with machine-readable terms for sharing, dispute, repair, and appeal.
  3. Run exit drills. Practise handover twice a year and verify portability and continuity.
  4. Escalate by subsidiarity. Escalate only when the local steward cannot handle life-and-safety or livelihood harms; log why and for how long.
  5. Retire with honours. Archive traces, evals, and lessons so the next steward starts stronger.

Buildable tools

One case: the flood-bot

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 stewards who know their stretch, and who know when to let go. Knowing when to let go is not a technical competence; it is a moral one. That discipline binds the makers too. A stewardship that cannot survive its founders fading is not care — it is dependency.

← Previous Next →