Attractor pipelines emitted events. Every state transition, every node entry and exit, every edge traversal, every checkpoint write—all of it was broadcast as a stream of structured events. The events were there for logging, for debugging, for audit trails. But Jay looked at the event stream and saw something else.
He saw a heartbeat.
"I want to build a TUI," he told Navan. Not build, exactly—spec. He wanted to describe a terminal user interface that would consume the event stream and render the pipeline's progress in real time, the way a music visualizer renders audio.
He wrote the spec in an afternoon. The TUI would show the pipeline graph as ASCII art, with each node highlighted as it activated. Active nodes would pulse. Completed nodes would dim. Edges would animate as flow moved along them—a simple arrow character advancing from source to destination. Token consumption would scroll along the bottom as a running counter. Elapsed time per node. Satisfaction scores as they were computed.
The agent built it. Jay loaded it in his terminal and ran a pipeline.
The screen came alive. The graph was drawn in box-drawing characters—clean lines, rounded corners, node labels centered in their boxes. The first node lit up green. Events scrolled in a sidebar: NODE_ENTER: gather_requirements. Tokens ticked upward. Then the node completed and the edge to the next node animated—a small chevron character moving along the arrow, like a package on a conveyor belt.
Navan came over and watched. "This is mesmerizing."
"It's information. It's just information presented the way it wants to be presented." Jay pointed at the fan-out section, where three nodes activated simultaneously. Three boxes lit up green at once. Three token counters ticking in parallel. "See that? You can watch the parallel execution happen. You can see which agent finishes first."
"It's like watching a factory floor from the catwalk."
"Yeah." Jay smiled. "That's exactly what it is."
They watched three more pipelines run. Each one had a different rhythm. Short pipelines had a quick, staccato pulse—nodes firing and completing in rapid succession. Long pipelines with multiple iterations had a slower cadence, almost meditative, the codergen node lighting up and dimming and lighting up again as it converged on the right answer.
"Every pipeline has a personality," Navan said. "The fast ones are nervous. The slow ones are thoughtful."
"The event stream makes it visible. Before this, the pipeline was a black box. You kicked it off and waited for the result. Now you can watch it think."
Jay leaned back. The TUI scrolled and pulsed and ticked in front of him. The factory, rendered as light on a dark screen, working in the way factories always have: relentlessly, rhythmically, without rest.
"Like watching a factory floor from the catwalk." That's the image I've been looking for since the archive started. The TUI is the observation deck for the dark factory.