Skip to main content
A.I. Commerce Studio

AI workflows and agents

Internal policy assistant (RAG)

Employees ask about policies and procedures and get an answer with its source, respecting access rights.

Fictional scenario. An example situation that illustrates the approach. It is not a client project and describes no measured results.

Business problem

A fictional company with a few hundred employees keeps policies in several systems. People ask colleagues or use outdated versions.

Assumptions

  • Documents are in one or two stores with APIs.
  • Access rights are managed centrally.
  • Each policy area has an owner.

Constraints

  • Answers only from approved documents.
  • Employees see only what they are allowed to.
  • Questions are not kept longer than needed.

Reference architecture

Components by stage — an illustration, not a running system and not a certified design.

  1. 01Input

    • Document stores
    • Metadata and permissions
  2. 02Indexing

    • Chunking and embeddings
    • Permission filters
  3. 03AI and rules

    • Retrieval
    • Instructed model
    • Source check
  4. 04Output

    • Answer with citation
    • Feedback
The diagram as a list
StageComponents
InputDocument stores, Metadata and permissions
IndexingChunking and embeddings, Permission filters
AI and rulesRetrieval, Instructed model, Source check
OutputAnswer with citation, Feedback

Interfaces

FromToVia
StoreIndexerRead-only API
PortalAnswer serviceSSO session
Answer serviceAI modelAdapter with masking

Data flow

  1. Documents are indexed with their permissions.
  2. The question is enriched with the employee's role.
  3. Retrieval returns only permitted passages.
  4. The model answers only from the passages and cites them.
  5. No source — no answer.

Security boundaries

  • Permission filtering happens before the model.
  • The index holds no documents without an owner.
  • Logs do not keep full questions.

Where a person approves

  • A new source enters the index after its owner approves.
  • A sample of answers is reviewed periodically.

Delivery phases

  1. 01 · Discovery

    Sources, permissions and sample questions.

  2. 02 · Pilot

    One department, a limited document set.

  3. 03 · Expansion

    More sources and feedback.

  4. 04 · Operation

    Evaluation set and index updates.

Limitations

  • Not a substitute for legal advice.
  • Owners must retire outdated documents.

Trade-offs

  • Strict permissions vs answer completeness.
  • Always citing — slower but verifiable.

Facing something similar?

We start with an assessment of where you are and propose a realistic first phase.