Dialogue as a field

The question

Ember Circles holds one question while people speak. Contributions return to each other, differ, and leave pauses. Most of that is gone as soon as it is said.

This study asks whether those relationships can stay available: something a group could look at together, and disagree with.

What I tried

The conversation here is authored. It has twelve events: ten contributions and two pauses, on the question When does choice become agency?

Each contribution takes a place in the field as it arrives. A line between two of them is a proposed reading. A dashed line is tentative. A rust line holds a difference. A pause adds no claim and draws no line.

You can select any mark to return to its exact words. Where a connection is proposed, you can keep it or let the two stand apart. The same conversation is also available as plain text, in order, so the two can be compared.

What it shows, and what it does not

It shows that a conversation can be held as structured state, with every relationship traceable to the words behind it and open to correction by the people in it.

It does not yet show that this helps. Nobody has compared the field with the same text to see whether a reader finds the question faster, recovers exact words, or corrects a connection more readily. That comparison is the next piece of work.

Corrections last for one visit. Nothing is saved.

How it is built

The conversation and its relationships live in a small data file, separate from anything that draws them. The browser reads that state and renders marks, lines and pauses. No microphone, transcript or AI service is running.

Because the state is separate, another renderer could read the same file. A TouchDesigner version is a later exploration. It has not been built.