Support

Support is planned and not in this build. The plan is a separate desk role whose only job is you: how the console works, where a setting lives, what a status means, and what to do when something looks wrong, plus a case it keeps open until your problem is solved. This page says what it will and will not do, and what stands in for it today: Consult answers product questions from these pages with citations, and the Report button files anything else.

Owns

Product questions, the cases they open, and the feedback it files when the help has no answer

Reads

The generated help index and the config-ownership table; nothing about your book

Tools

Help search, open and where-is; no broker, shell, files or network

Model

— (not decided)

Cadence

On demand, a question at a time

Change it at

— (not in this build)

Hands off to

Consult for anything about the book; the feedback log for what it cannot answer

Judged by

The fixed operator question set (40 questions, fails red under 38), the thumbs under each article, the feedback rows it files

What it will own

• Product questions. "Where do I raise the approval threshold?", "what does on the bench mean?", "why is the Inbox empty?" are answered only from the help center, with the article and the console route attached as chips, never from general knowledge of how trading systems usually work.
• Cases and feedback. A question it cannot close becomes a case you can come back to; when the help has nothing on a question, Support says so and logs it to the feedback log the operator triages each morning (Review › Feedback), so the gap becomes an article. Cases are coming soon with the role; the feedback log exists today.
• Nothing about your book. Support will not read positions, prices or decisions; that stays with Consult and the PM (shown as Analyst on screen).

What it will read

The same generated help index the console ships (one copy for the pages, one for the tools) and the config-ownership table behind where_is. No broker access, no shell, no files, no network; the Executor would not listen to it if it had them.

Tools

Three, all read-only: help_search finds the article and section, help_open reads it, where_is maps a setting or a verb to the one route that owns it. No tool can propose, place or approve an order.

Model, cadence, how you change them

Not decided. Support runs on demand (a question at a time), so there is no cadence; the model will be set like the others, with the same owner route as the rest of the desk once it exists. Until then nothing to configure.

How it hands off

A how-to question stays with Support. A question about the book ("what do I hold?") or a request that implies a trade ("should we trim NVDA?") is Consult's, and Support will point you there. A wrong answer or a missing page is a feedback row, not a steering note: Support never writes anything the PM reads.

How it is judged

The same way the help center is: a fixed set of operator questions must cite the right article and route (the Consult help eval today runs 40 of them and fails red under 38), plus the thumbs under every article and the feedback rows it files.

Failure modes you might see

None today, because the role does not run. When it lands: an honest "the help has nothing on that" with an offer to log it; a question about the book redirected to Consult; and a wrong citation, which is what the question set exists to catch before you do.

Today

Consult carries the three help tools and the same rule: product questions are answered only from the help center, with numbered source chips under the answer that link to the article or the screen; nothing found means an honest "the help has nothing on that" and an offer to log it. The help center itself (Help & docs in your account menu, or the ? beside each screen's title, which opens the page for that screen in a side panel) is where you read the same pages directly, and every article ends with Was this article helpful?. For anything that looks wrong, the Report button in the top bar (or the ! key) files a note with the screen you were on into Review › Feedback; that log is read the next morning.