What Becomes Visible Between Things?

Something can happen in one part of our lives and remain there for years: an idea, a conversation, something we learned, a feeling we could not quite understand, an experience that seemed significant without revealing why. Then something else happens, perhaps somewhere entirely different, and suddenly the first experience changes—not because anything inside it has changed, but because it has encountered something new. A relationship illuminates an old difficulty. Something understood intellectually becomes recognisable emotionally. An idea acquires meaning when it meets another idea. A creative experience gives language to something we had previously only felt. Sometimes neither experience contained the discovery.

It became possible through the relationship between them.

This raises an interesting question for the design of technology. What if digital systems were designed not only to remember the things we have encountered, but to help us explore what might become visible between them? That question led to Orbit.

From history to constellation

Most digital systems organise human activity by separating it. Chats become conversations. Files sit in folders. Memories become records. Projects become workspaces. Even when a system remembers us, its memory tends to remain organised around individual objects: this conversation, this preference, this project, this action.

This makes sense computationally. But human understanding does not necessarily develop in the same way.

Our experiences encounter one another. Something from the past acquires new significance in the present. Knowledge from one domain changes how we perceive another. An unresolved question follows us until it meets the experience through which it can finally be understood.

Meaning is not always contained inside the original event. Sometimes it develops through relation. Orbit begins from this relational premise. Rather than presenting someone’s activity only as a history of separate interactions, Orbit allows previous experiences to become visible as part of a wider relational landscape. The question is no longer simply, What happened before? It becomes:

What becomes visible when what happened before is brought into relationship with something else?

This changes the purpose of remembering. The past is no longer only something to retrieve; it can become something we encounter again.

<!-- orbit-interactive -->

The space between experiences

Orbit introduces a simple proposition: two experiences can be brought into relationship without assuming that a meaningful relationship necessarily exists between them. The purpose is not to declare, These things are connected. It is to ask:

What might become visible if we explored the space between them?

This distinction matters. Much of contemporary technology uses previous behaviour to determine what should happen next: you watched this, so perhaps you will want that; you searched for this, so perhaps this should be shown to you; you behaved this way, so perhaps the system can anticipate what you will do next. The relationship between past and present becomes a mechanism for prediction.

Orbit explores another possibility. Previous experience can become the beginning of inquiry. Instead of asking only, What is this person likely to want next?, we can ask:

What might this person discover by encountering their own experience differently?

This is a subtle change in technological orientation, but it changes the role of the system. The technology does not need to know the answer; it can create conditions in which a question becomes possible.

The Third Space

When previously separate experiences are brought together, another space becomes available. Within DIALOGIC, we call this the Third Space. It belongs entirely to neither experience. It exists through their encounter.

Imagine that someone has been exploring a question about relationships in one part of their life while encountering something apparently unrelated somewhere else. Neither experience needs to contain an explanation of the other. But bringing them into relation may reveal something that was not previously available.

Perhaps nothing happens. That possibility is important. Not every connection is meaningful, and not every pattern deserves interpretation. Sometimes two things are simply two things. But sometimes a relationship between them allows a person to perceive something neither experience had revealed independently: a contradiction, a pattern, a possibility, a question, a recognition. The discovery is not necessarily located inside either experience.

It emerges through relation.

When the relation becomes meaningful

Much of computing treats objects as the primary units of meaning: a user, a message, a document, a memory, a project, a piece of content. Relationships between these objects certainly exist within computational systems, but interfaces generally foreground the objects themselves.

Orbit reverses the emphasis.

Nodes are not always the primary unit of meaning. Relations can be.

A previous experience is therefore not valuable only because it can be remembered. Its relationship to another experience can itself become something worth exploring.

This suggests a distinction between personalisation and what we might call relationalisation. Personalisation asks:

How should the system adapt itself to this person?

Relationalisation asks something additional:

What relationships within this person’s experience could become available for exploration?

The distinction changes the purpose of accumulated context. The objective is no longer simply to build a system that knows increasingly more about the person; it is to create conditions through which the person can encounter their own experience differently.

The intelligence of relation

This leads to the proposition underlying Orbit:

Intelligence is not necessarily located only within either experience. Something can emerge through the relation between them.

The claim is not that every relationship contains hidden meaning, nor does it require us to imagine a mysterious intelligence existing independently between things. It is a simpler observation: bringing things into relationship can make information available that was not apparent when either was considered independently. We encounter this elsewhere. A metaphor creates meaning through the relationship between unlike things. Interdisciplinary thinking creates possibilities through encounters between different bodies of knowledge. A conversation can produce an idea neither participant arrived carrying. A musical interval exists through the relationship between notes. The relation changes what becomes perceptible. Orbit treats this as a design territory: technology can help make relationships available for human attention.

Meaning must remain open

There is also a danger.

Once technology becomes capable of recognising relationships across someone’s experiences, it becomes tempting to allow the system to explain those relationships.

This happened because of that. These experiences reveal this pattern. This is what your behaviour means.

Some interpretations may be useful, but a system that continually completes meaning on our behalf risks becoming the primary interpreter of the very life it is supposed to support.

Orbit takes a different position. Its orientation is closer to:

There may be something here.

The person can explore the possibility, reject it, modify it, remain uncertain, or discover something entirely different. This continues a principle developed elsewhere in DIALOGIC Research:

A relational system can know enough to support recognition while remaining incomplete enough that the human remains necessary to meaning.

The technology can make a relation perceptible.

The human remains necessary to what that relation becomes.

From personalisation to relational architecture

Orbit provides a concrete expression of what DIALOGIC means by Relational Technology:

Technology designed around relationship as a medium through which human understanding, agency, creativity and capacity can develop over time.

Orbit is DIALOGIC’s first reference implementation of Relational Architecture: an attempt to make relation itself part of the interface through which human experience can be explored.

But Orbit extends the proposition. Relational Technology does not need to concern only the relationship between a human and artificial intelligence. The relevant relationship might also be between:

• experience and experience
• idea and idea
• past and present
• self and relationship
• inner recognition and lived situation
• one form of intelligence and another

This suggests a broader design territory. We call it Relational Architecture.

Relational Architecture designs conditions through which relationships can become perceivable and explorable without determining in advance what those relationships mean.

This is different from designing primarily for prediction and from designing primarily for content. The relationship itself becomes part of the interface territory. The system does not necessarily need to resolve uncertainty; sometimes it can preserve uncertainty long enough for something else to emerge.

An interface for between-ness

There is a larger question underneath Orbit:

What would interfaces look like if they were designed not only to show us things, but also to help us perceive between things?

Contemporary interfaces have become extraordinarily sophisticated at presenting objects. Feeds present content. Search returns information. Dashboards present metrics. Chat interfaces present conversations. Knowledge systems retrieve records. Generative systems produce new material. But the spaces between experiences remain comparatively invisible.

Orbit treats this between-ness as interface territory—not because every space contains something waiting to be found, but because sometimes the relationship changes what becomes possible to perceive.

That possibility matters beyond Orbit. As technology develops increasingly sophisticated forms of continuity, we face a choice about what continuity is for. It can be used to know us more completely, predict us more accurately, optimise what appears next and reduce uncertainty. Or some of that capacity can be used differently: to return something without explaining it; to place experiences into relationship without declaring a pattern; to create a question rather than an answer; to preserve enough openness that the person can still surprise the system, and perhaps themselves.

What becomes possible between things?

Orbit began with a practical problem. DIALOGIC contains many different territories of exploration. How could someone begin to perceive what was happening across them without reducing their experience to analytics, progress indicators or an increasingly comprehensive profile?

The answer was not simply to build a better dashboard. It was to begin thinking relationally.

That decision points toward something larger than Orbit itself. The dominant trajectory of computational systems has been extraordinarily effective at identifying, storing, retrieving, generating and predicting things.

Relational Technology introduces another possibility. Technology can also create conditions through which relationships become available to perception.

Some of those relationships will lead nowhere. Others may allow someone to understand an experience differently. Some may reveal questions rather than answers. Some may remain unresolved for years.

And occasionally, bringing two things together may make something possible that neither could have produced alone.

We cannot always know beforehand. That is precisely why the space must remain open.

Relational Technology does not need to eliminate uncertainty. Sometimes its task is to create somewhere uncertainty can become generative.

Orbit is one expression of that possibility: not an interface that tells us what our experiences mean, but an interface that allows us to encounter them relationally.

Because sometimes the important thing is not hidden inside either experience. Sometimes it only becomes visible when we place them in relation.

Conventional technology asks what something is. Relational Technology also asks what becomes possible between things.

Orbit makes that question visible.

---

DIALOGIC Propositions

Relationalisation

The use of technology not only to adapt to an individual, but to make relationships within and across experience available for exploration.

The Third Space

The exploratory space that becomes possible when previously separate experiences are brought into relationship without determining in advance what that relationship means.

Relational Emergence

Something can become perceivable or articulable through the relationship between experiences that was not available through either experience independently.

Relational Architecture

The design of conditions through which relationships can become perceivable and explorable while preserving human interpretive agency.

Productive Uncertainty

A relational system does not always need to resolve ambiguity. Uncertainty can remain open long enough for human recognition, interpretation or new possibility to emerge.

---

Governing Proposition

Relational Technology does not only design relationships between humans and technology. It designs for what can emerge through relationships between experiences, ideas, people, contexts and forms of intelligence.

The technology can make relationship available to attention. It can create conditions for inquiry. It can preserve the space between things.

But what becomes meaningful there does not need to be known in advance.

That remains part of the human encounter.