Recent ships.

Before this ship, asking DispatchDuck a research question could still produce a packet draft with approval framing, even when there was nothing to approve.

Now the Packet Writer classifies questions and work requests cleanly. Questions render as plain chat replies in the duck's voice. Work requests still produce dispatch packets with review gates, so the product feels like one conversation surface instead of two.

DispatchDuck now treats conversational answers as first-class messages. When a user asks a question, the reply lands as a normal assistant bubble instead of forcing the review UI into places it does not belong.

The dispatch path stays intact. Requests that create work still become packets with approval, evidence, and lifecycle state.

Personas are now built into the workspace. Scout, Architect, and Quant give DispatchDuck specialist modes for research, systems design, and analytical work.

Users can also create their own personas with dedicated prompts and model preferences. The point is simple: different AI jobs need different instincts, but they should still share the same memory.

The main app now opens into a unified chat-first shell. Threads, daily pulse, review state, and workspace navigation sit together instead of scattering the operator across separate surfaces.

This gave DispatchDuck the shape it needed for the public launch: one place to command the work, one place to approve what ships, and one memory layer underneath.