Questions

Operational questions about physical work: coverage, handover, incidents, checklists, client phrasing, and attachments you provide (images, many PDFs, spreadsheets, text). It uses scoped prompting for safety ordering and documentation habits — not open-ended consumer chat positioning.

It does not verify attendance, GPS, live telemetry, or the integrity of your tenant database. It does not rule on legal or contractual outcomes. It may tell you what to pull from your record system and how to describe it — the proof stays in DWERK (or your process) when you use those products.

No. The public /ask workspace is designed to try VORQON without a DWERK tenant. When your organisation uses DWERK, VORQON may reference record types and exports you should use for defensible truth — that is a product boundary, not a bundling requirement for a first try.

VORQON works in English, Hindi, Hinglish, and Kannada. You can switch language in the workspace at any time. No other languages are available today.

Photos, PDFs, spreadsheets, and text files as supported by the /ask surface. Attachments are interpreted for the current turn; they are not a compliance sign-off. Exact retention and storage rules follow the product you are using (public workspace vs tenant).

No. VORQON gives operational guidance. Legal, regulatory, and insurance interpretations belong to qualified people in your organisation. When uncertainty is high, replies bias toward documentation and escalation — not certainty.

Outputs are advisory: you remain responsible for actions in the field and for what gets recorded in your system of record. VORQON does not create verified truth; DWERK (when used) holds governed records and exports. See Trust for the posture in one place.

Supervisors, facility and security leads, housekeeping and field roles, vendor managers, and finance stakeholders who need clearer operational language — all in physical-work contexts. It is not positioned as a general-purpose consumer assistant.

On the public /ask workspace, conversation history and saved items are oriented around the device/browser experience described in that product — not a generic cloud “chat history” promise. Check in-product copy for the current retention statement; tenant deployments follow your organisation’s stack.

No. It complements judgment with structured steps and wording. Your approved procedures, training, and local law still win when they conflict with any suggestion here.