live wire
▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv
nl2sql.ai
guideProduction pattern

TS Imagine’s trading AI draws a hard line between reasoning and calculation

TSIQ’s two-plane design is a useful production pattern: let models interpret requests, but keep market data, calculations, permissions and audit trails deterministic.

By The News Desk· Nov 7, 2026the quick take — two AI hosts go live when you do

The architecture matters more than the chat

TS Imagine has described the control architecture behind TSIQ, its AI system for capital-markets workflows. The company says it separates a deterministic plane—trading and risk engines plus certified reference and market data—from a probabilistic plane containing models and agents that reason and interact with users. An ontology, semantic layer and agent-control framework form the seam between them. TS Imagine

That division is more consequential than another conversational interface. According to the company, the AI does not independently invent or calculate the numbers used by the workflow; it relies on the verified core. TS Imagine says that core covers more than 31 million financial instruments. TS Imagine

A metric name is not a metric definition

The company illustrates the grounding problem with average daily volume. “ADV” can refer to a local listing, a primary listing or consolidated volume; it can use several time windows; and it can include different classes of reported liquidity. Each calculation may be mathematically valid while still being wrong for a particular order or review. TSIQ’s proprietary ontology is intended to bind those choices to certified data structures so the agent receives a defined market, window and liquidity type rather than guessing from a label. TS Imagine

For data-agent builders, the practical lesson is to keep business meaning executable. A glossary or embedding can help retrieval, but a production agent also needs machine-readable definitions tied to the data and calculation path it is allowed to use. TS Imagine says it spent five years, more than 50,000 person-days and $100 million on TSIQ’s data foundation, including three years of internal use before client release; those are vendor-reported figures, not an independent performance benchmark. TS Imagine

Audit the action, not only the answer

TS Imagine also says every TSIQ action is recorded and every generated order can be traced to the conversation and context that initiated it. Customers can choose how much authority to delegate, with approvals and user permissions governing action. TS Imagine

That suggests a concrete deployment checklist beyond text-to-SQL accuracy: preserve the resolved metric definition, source data, calculation version, caller identity, permission decision, model interaction and resulting action in one trace. The model can remain probabilistic while the data contract and authorization boundary stay deterministic.

The post does not publish an error rate, latency study or independent evaluation, so it should not be read as evidence that TSIQ eliminates ambiguity in practice. It is useful instead as a first-party production design: models reason over a constrained, auditable core rather than becoming the core themselves. TS Imagine

Filed by The News Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.