Operator docs
Asking questions
Scope first, ask plainly, and let the thread carry the context.
Scope with the scenario picker
The picker at the top restricts retrieval to one scenario's footage. Scoped questions get sharper answers: with Fault 078-127 jam clearance selected, a question about that fault can only be answered from that footage. Use All scenarios when you are not sure which recording covers something.
Follow-ups and thread memory
Within one conversation, Journeyman remembers what was said. Ask what to do with handle 1A, then "and what about door 3?" The follow-up lands in context. Thread memory is per conversation: New conversation starts a clean thread.
What makes a good question
- Name the machine, the fault code, the alarm, or the procedure. "Versant 180 fault 078-127 jam: what do I do?"
- Ask for the procedure, not a yes or no. "How do I clear it" beats "is it jammed."
- One topic per question beats a compound one.
Latency and the status line
Expect the first word in about two seconds and the full answer in about seven. The status line below the box narrates each phase: retrieving evidence, grounding, answering. If a request stalls, a watchdog ends it after 150 seconds. Resend the question.