# Planner Playbook

This note records how the planner should turn one business question into a structured response plan before any UI is rendered.

## Decision fields

- `mode`: text / single-block / workspace
- `tool`: which business view should be used
- `workspaceMode`: replace or merge
- `recipeId`: which presentation tone the response should use
- `density`: scan or deep dive

## Routing checks

1. First decide whether the request is a pure discussion, a single-view task, or a multi-view task.
2. Default to one useful block instead of composing multiple blocks too early.
3. Use workspace only when one block cannot carry the judgement.
4. The planner decides response form before visual rendering starts.

## Example

User request:

`这周整体经营先过一遍，再看看华东成本和诺瓦预算容忍度`

Expected plan:

- `mode`: workspace
- `tool`: operating overview + cost view + scenario view
- `workspaceMode`: replace
- `recipeId`: executive-brief
- `density`: scan