Skip to main content

​
What this means

Context is the information assembled for a particular workflow step: the current request, relevant identifiers and records, applicable instructions, and any supported evidence retrieval. It is not automatically every document, message, or earlier interaction in your organization. Different workflows can assemble different context. Do not assume there is one universal script, one shared memory, or one set of sources used by every agent.

​
What to provide and check

  • State the task and desired output clearly.
  • Include the correct request, product, customer, or order identifiers.
  • Check which source evidence the workflow actually used and whether it is current.
  • Clarify missing units, dates, quantities, or contradictory instructions.
  • Limit information to what is necessary and authorized for the task.
These are checks on the task and evidence, not a universal context-settings form. If the workflow does not expose a needed source, ask the owner to resolve the gap rather than assuming hidden access.

​
How it connects

Sources supply facts; integrations supply scoped access; workflow instructions guide the task. The proposed action and its evidence must remain reviewable at an approval point.

​
Example

An order-status request needs the correct order reference and current order information. A customer name alone may match several orders. Ask for clarification rather than combining facts from different records.

​
Where lessons get their context

Lessons start with a saved answer, a verified correction, and cited source evidence—not automatic mining of every conversation. Reviewers check the correction and its source before creating a candidate. The lesson records guidance and a rule describing when it applies, rather than embedding changing business facts. At application time, supported steps can only use the inputs and scope they are designed to receive. Approval, testing, release, and workspace activation are distinct. Do not assume a saved lesson is being injected into every workflow. See Lessons learned and Results and evaluations.