Why streaming is architectural

It's tempting to think of streaming as "show the text as it arrives," a frontend concern. But to stream well, the whole pipeline must be built around incremental output:

• The orchestrator must emit events as things happen, not accumulate and return at the end.
• The transport must push those events to the client in real time.
• The client must render a timeline that updates live.
• And the durable record must capture the same events so a reload reproduces the experience.

If you build the agent to return one big response and bolt streaming on later, you'll fight it. Design for streaming from the start: an orchestrator whose fundamental operation is "write an event."