Many instruments, one Library.
Unified is the perspective that makes the product thesis explicit. A user should not have to decide which isolated app owns the truth before asking a useful question. Requirements, graphs, messages, assignments, defects, team context, and repository state can all be presented through different instruments while remaining attached to one Library.
The unified work queue extends that idea into operations. A human or remote agent should be able to ask for actionable work without guessing whether it arrived as a dispatch message, an Execution assignment, or a Defect recovery. The queue contract should describe the work and return the right launch path, not force the operator to know the substrate first.
The same truth can look like a board, a graph, or a conversation.
This is why the perspective dropdown matters so much. It is not only navigation. It is a promise that changing the view changes the instrument, not the truth underneath it.