Browse the documentation
AI-Soda Brain

Follow the data behind a question

Trace how AI-Soda Brain connects identity, business meaning, data and knowledge. During a deployment review, identify what each stage processes, which resources it accesses and how to test its boundaries.

Technical guide · November 20263 min read
Business databases
Company documents
Collaboration tools
Ontology · Metric definitions · Knowledge index
Enterprise Brain
Data Q&A
Text and image retrieval
Reporting and collaboration
Access controls and source checks apply at every layer.

From a question to its evidence

One reference flow begins when a business application receives a question. Identity and authorization determine scope, planning selects a query or retrieval, connectors read the approved material, and validation organizes the answer and its sources. These responsibilities can be implemented by different components in different deployments.

Structured queries and knowledge retrieval can work together. A database supplies records from a particular snapshot, while documents explain rules and context. Preserve the provenance and date of each when combining them.

Assign responsibility at each layer

Logical layerWhat to evaluate
Entry pointIdentity, session, cancellation and error feedback
Task planningBusiness meaning, context and available tools
Semantics and knowledgeMetric definitions, document versions and citations
Execution and connectorsRead-only scope, query limits and failure states
Results and deliveryAnswers, charts, files and access control

Map where information actually travels

Mark question text, query results, document excerpts, credentials, caches, logs and backups on the deployment diagram. Add the location of inference and required external connections. Together, these flows show where processing takes place and which network or organizational boundaries it crosses.

Validate the diagram with one execution

  1. Ask for last month’s sales as a regional manager. Note which regions you can see, the reporting period and how sales are defined.
  2. Use the run history to find the order records behind the answer. If a result was reused, check its period before requesting a fresh query.
  3. Make a test reference unavailable and ask again. Check whether the answer identifies the missing evidence.
  4. Test retrying and cancelling a query, and exporting its results. Check that each action respects that user’s permissions.
Consult the architecture and delivery documentation for the deployed release for its actual component topology, network connections and supported capabilities.

Trace an answer to its sources in the diagram

Try “permissions,” “data source,” “manufacturing” or “API.”