Start with the map: Packs 1-4 form the care cycle, Pack 5 scales that cycle across organisations, and Pack 6 is the boundary condition that keeps every deployment local, plural, and sunset-ready. The map is the framework index — pack stations open their chapters, measure links land on the audit entries below, and handoffs show what each phase gives the next.

Framework map

Pack 6 · Symbiosis — the boundary in time
  • retired systems gift maps, evals, records
  • bounds and sunsets are contractual
5 · Solidarity

The field between deployments

The care cycle — Packs 1–4

who, what, why + rights flags

specs, SLAs, brakes

traces, incidents

new needs restart the cycleback to Pack 1

The field between deployments

Pack 6 keeps each pack from its negation — surveillance · contractual trap · indispensability · dependency-as-care · uncontrolled infrastructure — and guards itself: symbiosis without service continuity becomes abandonment.

Each pack descends in layers: closing image → pattern → buildable tools → named instruments → diagnostics → one headline measure.

Each pack then answers a distinct public audit question. To preserve the public promise of one headline public measure per pack, each pack has one headline public measure plus supporting diagnostics.

These metrics are designed for sufficiency, not maximisation. Each deployment context defines a threshold — "good enough" for that community. Crossing the threshold is the goal; score-chasing beyond it risks the same metric gaming the 6-Pack warns against. A headline measure is a public test, not a totalising score.

Headline public measures

Representation gap — the Attentiveness measure: Which materially affected groups are still missing or badly under-represented in the record?

Promise fidelity — the Responsibility measure: What share of material obligations are explicitly owned, properly authorised, and kept on their published terms?

Verified execution rate — the Competence measure: What share of audited decisions or releases pass guardrails, include a usable trace, and stay inside release bounds?

Trust-under-loss — the Responsiveness measure: After a bad outcome and attempted repair, do affected people report that the system became more trustworthy rather than less?

Uncommon-ground index — the Solidarity measure: Are shared decisions showing real cross-group participation and co-endorsement, rather than separate silos?

Exit readiness — the Symbiosis measure: Could this system hand over or shut down on schedule without rights loss, continuity failure, or recentralisation?

Supporting diagnostics

Named instruments

The book's Parts List catalogues every instrument a practitioner is asked to build or run. The ones the measures above depend on:

What each measure refuses to reward

Each headline measure names not only what it rewards but what it must refuse, so that a good number cannot be mistaken for good care.

How to read them

Before you call it Civic AI

The measures above audit a running deployment. These six questions gate whether a deployment should carry the name at all:

  1. Human standing (Pack 1) — can affected people prove standing without surrendering unnecessary identity?
  2. Adversarial load (Packs 1, 4, 5) — what stops synthetic publics, bots, or paid campaigns from flooding the channel?
  3. Decision force (Pack 2) — where does the output bind actual decisions, and where is it only advice?
  4. Repair path (Pack 4) — who can appeal, who pays for harm, and where is the repair logged?
  5. Exit capacity (Packs 5, 6) — can the community migrate, fork, pause, or shut down without losing service continuity?
  6. Boundary honesty (Pack 6) — what problem is out of scope, and who is carrying that problem instead?

If the answer to any of these is vague, the deployment is not ready. The point is not to defend the 6-Pack. The point is to make the room answerable.

Pack 6: SymbiosisFAQ

A research output of the Oxford Institute for Ethics in AI, Accelerator Fellowship Programme.

Audrey Tang and Caroline Green. CC0 (public domain). Illustration by Nicky Case. All comics. Glossary.

Co-written with jdd-kami, cultivated by Tenzin Yangtso — the GitHub commit log has full authorship details.