The front desk is not the worker

Some requests are conversational: explain a term, interpret a reference or summarize a visible state. Others are navigation commands: open a document, switch focus or show a table. A third class steers already-running work: pause, cancel, inspect or respond to an outstanding question. Still others create a new substantive investigation.

A good Front Desk recognizes which kind of interaction is needed and routes it accordingly. The point is not to create one omnipotent persona with every company system attached. It is to maintain a coherent entrance while preserving independent ownership of the work.

This separation also improves responsiveness. A status question should not routinely spin up a new multi-agent team, and opening a familiar surface should not require reconstructing a business workflow.

A substantial Execution may need procurement capabilities, compute, retrieval, policy checks, specialist expertise and a verified result. Those belong to the worker's governed assignment. The Front Desk needs enough visibility to start, steer and describe the work; it does not need to inherit all of the worker's permissions.

That avoids a common authority confusion: because a user can ask the front desk about every department, the front desk is assumed to have administrative access to every system. Knowing where work should go is different from being authorized to perform the underlying operation.

An architecture can support friendly natural-language interaction without allowing a chat entry point to become the single, unlimited credentialed operator of the business.

Business work frequently requires human participation. An approval is a governed decision tied to a specific proposed effect; a question may simply need missing information; a notification reports a change; an attention item is what the interface shows when the person should care.

These distinctions matter because presentation is not authority. Clicking through to an approval card cannot by itself grant the decision, and a notification saying 'Action needed' should not be confused with a recorded authorization.

A global attention surface can summarize important requests across many activities. It should let the user decide what deserves focus without constantly interrupting whichever work surface is currently open.

Imagine three independent Executions: an operational report is running, an invoice adjustment is blocked on finance, and a supplier investigation is waiting for a new file. The user should be able to understand each one's phase without opening three isolated conversations.

The interface needs stable task references, clear statuses and meaningful next actions. A completed model step is not necessarily a completed Execution. An explicit 'waiting for finance approval' is better than a fictional 92% progress meter.

Maintaining one input area while tasks move independently is a product challenge as much as a scheduling challenge. The Front Desk helps bridge that gap by resolving which work item the user's next sentence refers to.

The currently selected surface is useful context. If an invoice is open and the person asks, 'Can you explain this?', the invoice is an obvious candidate reference. But if the person explicitly mentions another order, that reference should take precedence.

Ambiguous cases need clarification, not guesswork. Nor can selection elevate permissions: opening a sensitive record does not authorize changing it. Focus, target resolution and action authority should remain distinct properties.

This is one reason a single global conversation is harder than simply attaching a chat pane to every tab. The runtime has to understand conversational continuity while respecting context and ownership boundaries.

The design goal is not to hide all software complexity behind a single chat bubble. It is to give people a stable place to express intent and supervise separately durable work, while preserving ordinary software controls wherever those controls work better.

Implemented Artemis already has conversational routing and orchestration foundations. The specific unified Front Desk / global conversation / independent Execution relationship remains part of the vNext target, not a demonstrated complete replacement for the current UI.

The underlying design is described in https://github.com/sarooo17/artemis-architecture/blob/main/docs/15-FRONT-DESK.md and https://github.com/sarooo17/artemis-architecture/blob/main/docs/16-MULTI-EXECUTION-ATTENTION.md.