The Database Condition

We are no longer represented as whole things. We are increasingly assembled from attributes.

The Database Condition describes a world in which selves, brands and culture are represented through relationships between data points, attributes and signals, rather than as singular, unified entities.

A database is not simply a databank. It is not just a store of information. What makes it a database is the structure of relationships between its elements.

That changes how identity, brands and even cultural moments work.

They become plural and programmable.

Different attributes can be selected, combined and interpreted in different ways, producing different versions of the same underlying person, brand or event.

In simple terms:

The same thing can become different things depending on which bits are selected, assembled, mixed and remixed and who they are shown to.

That is the Database Condition.

Three levels of the Database Condition

1. The Database Self

A person is increasingly represented not as one coherent identity, but through distributed attributes, behaviours, records and signals.

Different systems assemble those attributes differently.

The result: multiple machine-readable versions of the same self.

2. The Database Brand

A brand is no longer defined solely by the identity it broadcasts.

Search engines, platforms, marketplaces, AI systems, reviews, creators and consumers continually reconstruct the brand from distributed signals.

The result: the brand becomes platformed, searchable, P2P and dynamic.

3.Database Culture

Cultural moments increasingly operate in the same way.

The event may be shared, but its component parts can be clipped, selected, recombined and fed differently to different groups.

The result: we can share the same moment without sharing the same meaning.

Database, not databank

The Database Condition is not primarily about the accumulation of information.

It is about relationships.

A databank stores things. A database relates them.

The significance lies in the coordinates between attributes: what is connected to what, which elements are selected, which are ignored, and how those relationships are interpreted by a particular system.

This is why the Database Self, Database Brand and Database Culture can all be plural and programmable. Their apparent identity depends upon the reconfiguration through which they are assembled.

Why it matters

The Database Condition helps explain a central question running through my' work:

What happens to the self when systems can continually reconstruct who or what something is?

It connects earlier work on the Database Self and Database Brand with current work on Selfhood in the Synthetic Age, System & Self and Me:chine.