SELECTED WORK / 03 / OPERATOR KNOWLEDGE ASSISTANT

An answer you can trace.

Find relevant information quickly, with the supporting passage always within reach.

GUIDED EXAMPLES / FICTIONAL SOURCES

What belongs in a shift handover?

EXAMPLE RESPONSE

Supported answer

Include equipment status, open work, unresolved observations, and references. Keep observation times and make follow-up items explicit.

Supporting sources

Why this response?

A relevant passage supports this answer.

Prepared example · No live model or private document access

Explore how a source-grounded assistant should respond, including when it cannot provide an answer.

The problem

Useful information can be buried in documents and shift records. A confident answer is not enough: the operator needs its source, revision, and a clear indication of missing information.

My contribution

I apply lessons from building and diagnosing secretary retrieval workflows: trace the source, distinguish missing information from failed access, and make uncertainty visible.

How it works

The intended RAG flow is question → retrieval → source checks → grounded answer. This public demo uses curated questions and authored, cited examples. It does not run a live language model or search a private knowledge base.

Project evidence

The existing operator prototype uses TF-IDF retrieval and templated answers. Secretary retrieval code distinguishes source-service errors from valid empty results. This demo illustrates the richer operator experience being proposed.

Context & limitations

Guided examples over fictional study documents. Source freshness is scenario metadata, not a live verification. No free-form generation, live operating advice, or measured response-time claim.