Your business has a memory.
Give it references.

Define what the memory must contain

Keep three things apart: the documents that serve as a reference, the decisions made by an authorized person and the current state of cases. A signed contract, a commercial exception and a pending quote carry neither the same authority nor the same period of validity.

This memory belongs to the document and application system. It can feed an assistant without training a model on everything the company holds. Buying or adapting a model does not, on its own, build this organization.

Turn an experience into a verifiable record

For each reusable piece of information, keep its source, scope, effective date, version and the person who validated it. Add the roles allowed to view it and its status: proposed, validated, replaced or withdrawn.

Fictional example: an exceptional discount is granted to a customer for one order. The memory keeps the decision and its justification, but its scope remains that order. The assistant must not infer a new general price from it.

Plan for correction, not just accumulation

A corrected answer can become a candidate for the memory; it must not silently overwrite an approved procedure. When a rule changes, keep the link between the old and the new version and remove the old one from current answers. Authorized archives stay separate from active references.

Withdrawal must cover the copies and indexes used by the assistant, not only the original document. Permissions and the retention period call for an identified owner.

Start with a single business workflow

Choose a recurring case and a few representative questions. Compare the current search with a structured memory: source found, right version, correct access, absence of an answer recognized. Then have a decision corrected and run the questions again. Saphan can scope this first end-to-end flow and the update responsibilities before the corpus is extended.