Conversations

Polychrome ties each conversation to where it lives — a chat thread, a channel, an email chain. Picking that thread back up continues the same conversation, with the same memory and the same history, rather than starting over. Everything below is what that one thread is made of.

It moves in turns

You send something; the agent goes to work. Often it does more than answer — it reads a file, fetches a page, drafts a message, checks a result — several steps in a row, deciding the next from what the last one returned. When it has what it needs, it replies. That whole round, from your message to its answer, is a turn. A conversation is a run of turns, each building on the ones before it. If a turn does work but has nothing to say yet, Polychrome still closes it with a plain reply, so a turn never ends in silence. The machinery of a single turn is in Architecture.

It is written down as it happens

Every turn is recorded the moment it happens, in a log that only ever grows — nothing is edited, nothing is erased. That record is the source of truth: the conversation is not kept somewhere and copied to the log, it is the log, rebuilt from it exactly whenever it is needed. So a restart loses nothing, two parts of the system can never disagree about what was said, and the history you scroll back through is the same history the agent acts on. How the log stays tamper-evident and who is allowed to write to it are covered in Architecture.

It can stop and ask you

When an action needs your say-so — spending from a wallet, sending something outside the chat, anything Polychrome will not do on its own — the conversation pauses in the middle of a turn and waits. It is not canceled and not restarted: your answer resumes the very same turn from the exact point it stopped, and the approved action runs with the arguments you saw. Reading anything from outside your conversation is what most often triggers this, because it takes away the powers that could leak your data. The full safety model — one check on every action, and why it asks rarely — is in Trust, and spending uses the same step in Payments.

It remembers across turns

A conversation carries what matters forward. Facts worth keeping — who you are, what you decided, where you left off — travel from turn to turn without you saying them again, and a long thread is kept readable rather than growing without bound. What is remembered, and how you can see or clear it, is in Memory.

Each one has its own space

Every conversation runs in its own sealed workspace, kept apart from every other. One conversation cannot see another's files, history, or in-progress work, so a busy or untrusted thread cannot reach into yours. That isolation is also what lets many conversations run at once without stepping on each other.

Who is in a conversation

A conversation starts wherever you reach Polychrome — the surfaces that carry it in and out are in Edges. It can be one-on-one or shared with other people, and the agent can take on a named identity for the thread; that is Personas. Whoever is in it, it stays the single continuous thread described here — one that turns, remembers, pauses for you, and keeps an honest record of everything it did.