A workspace map

01 / What it was

By mid-September the work ran through dozens of rooms in a chat server, each with its own agent or job. We asked an agent to draw a simple map of how it all fit together.

The first try was a flowchart. It was replaced by a set of three poster plates in the omo.sh style: the machine, the engine that feeds it, and the watch that guards it.

02 / How it worked

• Every number was read live from the chat server's API and the list of scheduled jobs, 'never from memory'.
• It counted 38 live rooms and 72 archived ones.
• Each plate has one filled black object for the single place a human decides, for example the approval gate.
• Drawing it found a real fault: two scheduled jobs were posting into a room that no longer existed.

03 / What we saw

Making the map was a kind of audit. A count on the first plate was wrong (it left out forum rooms), and a broken delivery showed up only because every room was checked.

04 / Where it led

The idea of one room per job came back later as real rooms in Omo Space.

Sources

1. Map manifest. workspace map notes, 22 Sep 2026 All figures were read live on 2026-09-22, never from memory.
2. Map manifest, plate III closing line. workspace map notes, 22 Sep 2026 A green room is not a green system. Only the receipt is.
3. Map manifest, plate I closing line. workspace map notes, 22 Sep 2026 Nothing merges itself. Nothing sends itself.