Users
How to ask, and when not to trust a tidy sentence.
People and maintenance
People who can check an answer come first.
A model without training becomes another browser tab. We teach people how to ask, how to check the source excerpt, and what must not be pasted into a prompt. Maintenance is written into the contract, not into a slide with a response time.
Administrators
Accounts, restart, refreshing the collection, swapping weights.
Contract
Response times, if any, are written down after we know the environment.
Training
Separately for the people who ask and the people who keep the server.
- Users: how to ask a question, how to open the cited excerpt, when an answer has to be rejected.
- What not to paste: data that is not in the approved collection, and contract text the assistant should not see.
- Administrators: who creates accounts, how to refresh the index after a new procedure, how to roll back a model version.
- We do not issue public certificates of attendance. If the organisation wants its own training record, we agree that with the order.
Maintenance
After go-live, the document collection ages, not only the software. Maintenance means refreshing the index, reviewing accounts, patching the system and a deliberate swap of the model.
Care terms — including how quickly we react to a failure — are written into the contract once we know the installation site and who on your side has access. This page has no SLA numbers, because they would be invented.
What maintenance does not include by default
We do not decide whether a new procedure is lawful. We do not monitor employees through the content of their questions. If logs are to be used for anything beyond diagnostics, that is a separate decision described under compliance.