# One side chat per topic

The chat list is the org chart: each side chat owns one project, device, program, or chore, and the main chat stays a desk, not an archive.

From the [Guides](../index.md#guides) section of [The Muse Field Guide](../index.md).

## The problem

A chat that tries to own three topics ends up serving none of them, because every new instruction has to fight the residue of the other two. And a main chat that receives everything, direction and bookkeeping alike, stops meaning anything when it speaks.

## The arrangement

Each side chat owns one thing: a project, a device, a program, a trip, a standing chore. Its history becomes the working record for that topic, searchable and resumable weeks later; when the topic ends, that chat is what gets archived and nothing else is disturbed. The main chat keeps the opposite discipline: direction, escalations, and review land there, and routine output never does. Decisions that cross chats travel as explicit messages that say what they supersede, and handovers are confirmed at both ends.

## What it costs to run

Hygiene. A list this size stays usable only with a naming system, status markers, periodic re-grounding of stale threads, and archive checks before anything is closed.

## Template (copy and adapt)

```
Chat charter
Topic: <one sentence, or it is two chats>
Owns: <the work this chat is responsible for>
Out of scope: <what belongs to another chat>
Decisions: travel as messages; handovers confirmed at both ends
```

## Where this came from

The household runs 93 chats in total, and the count is not sprawl. It is what one chat per topic looks like after months of daily use.

Deep dive: [Chats as an operating model](../deep-dives/chats.md)

Related resources: [where-were-we: re-ground a stale chat](where-were-we.md), [baton-pass: hand a chat to a successor](baton-pass.md), [The Engine Room: one chat for noise](the-engine-room.md)

Canonical page: https://www.niclydon.io/muse/items/one-chat-per-topic.html