<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Semantic Layer on SoloSoft</title><link>https://www.solosoft.dev/tags/semantic-layer/</link><description>Recent content in Semantic Layer on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 07 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/semantic-layer/index.xml" rel="self" type="application/rss+xml"/><item><title>Auto-Ontology Audited: 9,026 Stars, 46 Watchers, and a SQLite Connector That Returns Ada Twice While Reporting No Error</title><link>https://www.solosoft.dev/post/nvidia-auto-ontology-audit-silent-duplicate-columns/</link><pubDate>Sat, 07 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/nvidia-auto-ontology-audit-silent-duplicate-columns/</guid><description>&lt;p&gt;The first sentence of NVIDIA&amp;rsquo;s Auto-Ontology README is a promise that indicts the project:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Agents can retrieve documents and query databases, but reliability gates agentic analytics: a revenue metric answered faster is worth nothing if the number is wrong.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I agree with that sentence. It is the correct diagnosis of why text-to-SQL demos do not survive contact with a finance team. The tool then goes on to build a semantic layer whose entire purpose is to make the number right, and ships three database connectors that — as I confirmed on this machine — return silently wrong numbers whenever a join produces two columns with the same name.&lt;/p&gt;</description></item></channel></rss>