Perspectives

Kinship Before Family

What makes two systems kin: common ancestry, shared structure, exchanged parts, or the capacity to build something together?

We often imagine kinship beginning with a family tree: parents, children, grandparents, branches extending into the past. But life had a long history before anything resembling a human family could exist. Before there were parents in the familiar sense, there were molecules copied from earlier molecules, lineages of cells, and forms of inheritance whose history is written into every living organism.

Biological kinship has a powerful anchor: ancestry. Two organisms may resemble each other because they inherited traits from a common ancestor. They may also look alike because similar environments favoured similar solutions. Resemblance alone does not prove close relation, just as two machines built to solve the same problem need not share a design lineage.

Yet ancestry is not the only relationship that matters to living systems. Organisms can exchange genes, depend on other species, and become partners in associations that transform both sides. Mitochondria, the structures that help our cells use energy, descend from bacteria that entered into an ancient partnership with ancestral cells. Their history complicates the idea that every important biological boundary corresponds to a separate, independent lineage.

Could engineered systems have a comparable kind of kinship? Two software platforms might share a common codebase. Two others might use the same protocol without sharing ancestry. A third might incorporate a component developed by an entirely separate team. They are related in different ways, and confusing those relationships makes systems harder to understand.

A useful account of kinship therefore needs several labels. Genealogical kinship records shared descent. Structural kinship records shared architecture or conventions. Operational kinship describes systems that depend on one another. Compositional kinship describes systems that inherit or incorporate each other's components. These categories are not identical, but each reveals a different history.

Why does this matter? Because the kind of relationship determines what can safely be transferred. A component that worked in one system may carry hidden assumptions about timing, identity, resources or failure. Shared ancestry does not guarantee compatibility; superficial similarity guarantees even less. Provenance and testing matter.

Perhaps the deepest lesson is that kinship is not a vague feeling of likeness. It is a claim about history. To ask whether two systems are kin is to ask what they inherited, what they exchanged, and which relationships made their present forms possible. A system's family tree may be less like a tree than a landscape crossed by many paths.

Share this article
Facebook WhatsApp X LinkedIn Medium
Quick navigationEsc