Product · Architecture
Spotonix is the AI analyst that interprets before it queries. This page is for the people who have to sign off on that. It separates the stable product path—interpretation, query generation, validation, and execution—from deployment choices such as hosting, warehouse credentials, model credentials, identity, network routing, and retained artifacts.
The product behavior can be demonstrated. The infrastructure boundary must be documented for the selected deployment; this page does not turn engagement-specific choices into universal claims.
How it works
A production evaluation should separate the system's responsibilities clearly: represent the intended analysis, generate and validate a query, and execute through a configured warehouse connection. Each boundary has a different control owner.
01 · Interpretation
Intent Algebra binds business terms to the Context Graph and represents the intended Segments, Calculations, filters, grain, and scope as a plan. In Copilot mode, the workflow pauses for plan acceptance before query generation continues.
02 · Generation
The current implementation supports configurable Anthropic and OpenAI model backends. The query generator receives the question and the analysis plan. Provider, model, key ownership, and network path are confirmed for the deployment.
03 · Validation & execution
Semantic checks compare material query bindings to the accepted plan before execution. SQL then runs through the configured database connection. Whether that connection uses a service identity, delegated user identity, or another credential mode is deployment-specific.
The path a question takes
Configure the Context Graph, model backend & warehouse
Connect your warehouse & your model
Ask · Intent Algebra resolves a visible plan
Generate SQL · validate material bindings
Execute through the configured database connection
The interpretation and closure steps are the product; see Intent Algebra for how the plan is bound, grounded, and exposed before SQL executes.
What is fixed and what is selected
The product path is stable; the deployment topology is not universal. Use this table to drive the architecture review and record the selected boundary for the actual engagement.
Component
Current behavior
Deployment decision
Your warehouse
Queried through a configured database adapter
Credential mode, network path, and warehouse controls
The model
Anthropic or OpenAI backend can be configured
Provider, model, key ownership, endpoint, and retention terms
The Context Graph
Provides explicit domain context to interpretation
Storage location, backup, access, and export requirements
The accepted plan
Visible before execution in the analysis workflow
Retention, stable identity, audit export, and access policy
The defensible claim is the visible interpretation and binding validation. Spotonix does not currently claim deterministic plan-to-query compilation or a universal logged-in-user execution model.
Where the boundary is
An evaluation is easier when unknowns are explicit. Confirm these items in the architecture packet for your deployment instead of inheriting them from generic website language.
Controls & assurance
Confirm application identity, warehouse credential mode, provisioning, and the enforcement point for table, row, and column restrictions. Runs-as-user is not a universal live claim.
Confirm where the application, Context Graph, logs, caches, and query results are stored, processed, backed up, and deleted for the selected topology.
Anthropic and OpenAI backends are configurable. Confirm provider, model, credential owner, endpoint, regional availability, retention terms, and model-change procedure.
The analysis plan is visible in the workflow. Stable plan identity, retention, query-to-plan linkage, and export requirements are confirmed during evaluation rather than assumed.
The Context Graph is your asset. Open export of the graph in a standard, non-proprietary format so it leaves with you is in development — we will confirm the format and scope with design partners rather than overstate it here.
Spotonix does not currently claim a completed SOC 2 attestation. Any compliance or contractual requirement must be reviewed directly before production use.
Deployment topology and control specifics are confirmed per engagement. We work these through with design partners against your real environment, not a reference diagram.
Keep reading