Innomerc Learn
English is the default.
A worked example

AI demo production system

One exchange at a time. Read what changes, then explain it in your own words before moving on.

  1. Meet the components
  2. Follow the steps
  3. Compare an example
  4. Check your understanding
Interactive Lab

AI demo production system

Reveal the supporting controls around a model call. This is one illustrative architecture, not a universal stack.

Steps1. Prompt 2. Response
Click a box or choose its name to learn what it means.
User interfaceReadyPolicy gatewayReadyModelReadyRetrievalReadyTool executorReadyAudit +evaluationReadyUser interfaceReadyPolicy gatewayReadyModelReadyRetrievalReadyTool executorReadyAudit +evaluationReady
Ready to traceSmall demo
Before you start · 2 stepsSmall demo

A prompt and model response demonstrate capability but not operational readiness.

How to use this example

Select Next step to read at your own pace, or Animate step to watch one exchange. Nothing advances until you choose.

Inspect components & read every step
  • User interface

    The part of an application that people interact with.

    Example: A text box receives a question before the application processes it.

  • Policy gateway

    A control point that checks requests against application rules.

    Example: It may enforce access or usage limits before a model request proceeds.

  • Model

    An AI system that generates output from its input. Its answer can be wrong.

    Example: It drafts an answer using the question and supplied context.

  • Retrieval

    The process of finding relevant information to supply as context.

    Example: A system searches approved documents before asking a model to draft an answer.

  • Tool executor

    Application code that performs an allowed action requested through a tool interface.

    Example: It checks permissions before making an approved calendar lookup.

  • Audit + evaluation

    Records and checks used to examine how a system behaved and how well it performed.

    Example: A team reviews a failed tool call and evaluates whether answers meet its criteria.

Small demo

A prompt and model response demonstrate capability but not operational readiness.

  1. User interface Model: Prompt. The demo passes a prompt directly to a model.
  2. Model User interface: Response. A plausible response returns; production controls are not represented.

Controlled production flow

Independent policy checks protect data and tool actions; monitoring and evaluation support review.

  1. User interface Policy gateway: User request. Authenticate the caller and apply request limits.
  2. Policy gateway Retrieval: Authorized retrieval. Filter documents under the user’s access policy.
  3. Retrieval Model: Context + task. Retrieved text is evidence, not authority to change tool permissions.
  4. Model Policy gateway: Proposed action. The model proposes an action; policy decides whether it can execute.
  5. Policy gateway Tool executor: Approved action. A scoped executor performs only the approved action.
  6. Tool executor Audit + evaluation: Outcome + trace. Record outcomes with appropriate privacy and retention.
  7. Model User interface: Answer. Return the response; evaluation and monitoring remain ongoing.

Fictional teaching trace. One moving dot represents an exchange, not a measured network capture.