# Product Vision

Friday should feel like a single operating console for getting work done, not a loose collection of tools.

Core product stance:
- the main experience is one persistent conversation that can see the current page, current object, and current runtime state
- users should never have to guess where a capability lives
- simple flows stay visible first; advanced control opens progressively inside the same console
- page actions and chat actions must resolve into the same visible state

What the product should make obvious:
- what is running now
- what is blocked on the user
- what Friday knows
- what Friday can connect to
- what Friday is costing
- what is unhealthy or risky
- what distributed runtime nodes are doing

What this console is optimizing for:
- a new user can start a task, review output, and approve a blocked action in three steps
- a power user can reach workflow design, runtime routing, memory controls, observability, and fleet health in three steps
- support, ops, product, and engineering all see the same system model instead of separate admin products

Non-goals for this delivery:
- redesigning the production router
- creating a Marketplace information architecture
- shipping a new branded marketing site
