[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"portal-settings:stajic:en":3,"public-menus:all":38,"post:source-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from:en":205,"related:post:source-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from:en:1":1869},{"statusCode":4,"data":5,"message":37},200,{"tenantId":6,"lang":7,"defaultLang":8,"siteUrl":9,"contactEmail":10,"brandName":11,"logoUrl":12,"siteName":11,"siteDescription":13,"ogImage":10,"robotsIndex":14,"socialLinks":10,"reservedSlugs":10,"seoPolicy":15},"stajic","en","de","https:\u002F\u002Fstajic.de",null,"Stajic Platform","\u002FLogo_Planet.svg","Stajic Portal",true,{"branding":16,"relatedContent":17,"crossDomainLinks":18},{"logoUrl":12},{"enabled":14},[19,22,25,28,31,34],{"url":20,"label":21,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Ffigure.rocks","figure.rocks",{"url":23,"label":24,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Floving.rocks","loving.rocks",{"url":26,"label":27,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.com","bazify.com",{"url":29,"label":30,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.de","bazify.de",{"url":32,"label":33,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.at","bazify.at",{"url":35,"label":36,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.ba","bazify.ba","Portal settings resolved",[39,45],{"id":40,"name":41,"location":42,"isActive":14,"isDefault":43,"items":44},1,"main-navigation","header",false,[],{"id":46,"name":47,"location":48,"isActive":14,"isDefault":14,"items":49},4,"main-menu","sidebar",[50,66,79,93,103,118,133],{"id":51,"title":52,"url":60,"target":61,"icon":62,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":64,"portfolioId":10,"children":65},"item-18",{"de":53,"en":54,"es":55,"fr":56,"it":54,"ru":57,"sr":58,"zh":59},"Startseite","Home","Inicio","Accueil","Главная","Почетна","首页","\u002Ffull-stack-web-developer-munich-performance-seo-and-maintainable-builds","_self","i-lucide-home","page",111,[],{"id":67,"title":68,"url":75,"target":61,"icon":76,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":77,"portfolioId":10,"children":78},"item-22",{"de":69,"en":69,"es":70,"fr":69,"it":71,"ru":72,"sr":73,"zh":74},"Vision","Visión","Visione","Видение","Визија","想象","\u002Fueber-uns-webdesign-muenchen-webaplikation","i-lucide-eye",113,[],{"id":80,"title":81,"url":89,"target":61,"icon":90,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":91,"portfolioId":10,"children":92},"item-19",{"de":82,"en":83,"es":84,"fr":83,"it":85,"ru":86,"sr":87,"zh":88},"Leistungen","Services","Servicios","Servizi","Услуги","Услуге","服务","\u002Fservices-dienstleistungen-muenchen","i-lucide-wrench",116,[],{"id":94,"title":95,"url":99,"target":61,"icon":100,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":101,"portfolioId":10,"children":102},"item-23",{"de":96,"en":96,"es":96,"fr":96,"it":96,"ru":97,"sr":97,"zh":98},"Blog","Блог","博客","\u002Fblog","i-lucide-book-open",112,[],{"id":104,"title":105,"url":114,"target":61,"icon":115,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":116,"portfolioId":10,"children":117},"item-32",{"de":106,"en":107,"es":108,"fr":109,"it":110,"ru":111,"sr":112,"zh":113},"Neue Technologien","New Technologies","Nuevas tecnologías","Nouvelles technologies","Nuove tecnologie","Новые технологии","Нове технологије","新技术！","\u002Fneue-webtechnologien","i-lucide-sparkles",122,[],{"id":119,"title":120,"url":129,"target":61,"icon":130,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":131,"portfolioId":10,"children":132},"item-20",{"de":121,"en":122,"es":123,"fr":124,"it":125,"ru":126,"sr":127,"zh":128},"Kontakt","Contact us!","Contacto","Contact","Contatto","Контакт","Контактирајте нас","联系我们！","\u002Fcontact","i-lucide-mail",115,[],{"id":134,"title":135,"url":144,"target":61,"icon":145,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":146,"portfolioId":10,"children":147},"item-21",{"de":136,"en":137,"es":138,"fr":139,"it":140,"ru":141,"sr":142,"zh":143},"Unsere Arbeit","Our Work","Nuestro trabajo","Nos réalisations","I nostri lavori","Наши работы","Наши радови","文件夹","\u002Fportfolio","i-lucide-briefcase",114,[148,161,175,181,193],{"id":149,"title":150,"url":144,"target":61,"icon":159,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":146,"portfolioId":10,"children":160},"item-24",{"de":151,"en":152,"es":153,"fr":154,"it":155,"ru":156,"sr":157,"zh":158},"Alle Projekte","All Projects","Todos los proyectos","Tous les projets","Tutti i progetti","Все проекты","Сви пројекти","所有项目","i-lucide-grid-3x3",[],{"id":162,"title":163,"url":171,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":174},"item-29",{"de":164,"en":165,"es":166,"fr":167,"it":168,"ru":169,"sr":170,"zh":143},"Local Roots, Global Reach","Local Roots - Global Reach","Empresa local ","Entreprise locale","Azienda locale","Местная компания","Локално предузеће глобално тржиште","\u002Fportfolio\u002Flocal-roots-global-reach-communication-media-systems-for-modern-business","i-lucide-folder","custom",[],{"id":176,"title":177,"url":179,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":180},"item-28",{"de":178,"en":178,"es":178,"fr":178,"it":178,"ru":178,"sr":178,"zh":178},"Solr Suggester","\u002Fportfolio\u002Fsolr-fuzzy-suggester-und-solr-infix-suggester-abfrage-ueber-ajax-und-filterung",[],{"id":182,"title":183,"url":191,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":192},"item-27",{"de":184,"en":185,"es":186,"fr":187,"it":188,"ru":189,"sr":190,"zh":185},"Firmenwebseite SEO","Company Website SEO","Sitio web corporativo SEO","Site web d’entreprise SEO","Sito web aziendale SEO","Корпоративный сайт SEO","Пословна веб-страница SEO","\u002Fportfolio\u002Fseo-sem-branding-mobile-webseite-muenchen",[],{"id":194,"title":195,"url":203,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":204},"item-31",{"de":196,"en":197,"es":198,"fr":199,"it":200,"ru":201,"sr":202,"zh":197},"Digitalisierungsportal","Digitalization Portal","Portal de digitalización","Portail de numérisation","Portale di digitalizzazione","Портал цифровизации","Портал за дигитализацију","\u002Fportfolio\u002Fdigitalisierungsportal-archiv-museum-bibliothek-ead-lido-mets-mods",[],{"statusCode":4,"data":206,"message":1868},{"id":207,"title":208,"slug":209,"content":210,"contentJson":211,"excerpt":1297,"featuredImage":1298,"featuredImageAlt":1299,"featuredImageCaption":10,"featuredImageTitle":10,"featuredImageCopyright":10,"featuredImageAuthor":10,"featuredImageSourceUrl":10,"featuredImageLicense":10,"featuredImageIsAiGenerated":43,"status":1300,"publishedAt":1301,"createdAt":1302,"updatedAt":1303,"seoLocalePaths":1304,"categories":1313,"author":1326,"translations":1331},"486","Source of Truth in AI Systems: Where Reliable Knowledge Actually Comes From","source-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from","{\"time\":1791479104597,\"blocks\":[{\"id\":\"intro\",\"type\":\"paragraph\",\"data\":{\"text\":\"A Source of Truth in an AI system is the authoritative source allowed to define whether a specific fact, state or rule should be treated as true for a particular scope, version and time. It is not automatically the language model, the vector database, the top-ranked retrieved document, agent memory or the latest message in context. Reliable AI architecture must preserve which source has authority for which claim, then keep provenance, retrieval and validation connected to that authority.\"},\"tunes\":{}},{\"id\":\"direct\",\"type\":\"callout\",\"data\":{\"variant\":\"info\",\"title\":\"Direct answer\",\"body\":\"\u003Cstrong>The Source of Truth is an authority rule, not an AI component.\u003C\u002Fstrong> An AI system can search many sources, but only some sources are authoritative for a given question. The correct source may be an application database for current account state, an approved policy document for a rule, source code for implemented behavior, an official specification for a protocol, or a primary research artifact for an observed claim. Good architecture makes that authority explicit instead of asking the model to infer it from relevance.\"},\"tunes\":{}},{\"id\":\"terminology\",\"type\":\"callout\",\"data\":{\"variant\":\"note\",\"title\":\"Terminology boundary\",\"body\":\"“Source of Truth” is widely used in software, data and organizational practice, but it is not a standardized AI component with one universal formal definition. This article uses it as an architecture concept: \u003Cstrong>the source or authority mapping that determines which evidence is allowed to establish a particular fact or state\u003C\u002Fstrong>. Provenance standards such as W3C PROV describe origin and derivation; they do not automatically decide which source your application should treat as authoritative.\"},\"tunes\":{}},{\"id\":\"current\",\"type\":\"callout\",\"data\":{\"variant\":\"note\",\"title\":\"Current-source note — 8 October 2026\",\"body\":\"The core distinction between authority, provenance, retrieval and model context is stable. NIST AI RMF 1.0 is currently being revised, but the current NIST Playbook still explicitly recommends documenting data provenance, including sources, origins, transformations, dependencies, constraints and metadata. W3C PROV remains a W3C Recommendation for interoperable provenance descriptions.\"},\"tunes\":{}},{\"id\":\"toc\",\"type\":\"tableOfContents\",\"data\":{\"title\":\"Contents\",\"minLevel\":2,\"maxLevel\":3},\"tunes\":{}},{\"id\":\"h-meaning\",\"type\":\"header\",\"data\":{\"text\":\"What “Source of Truth” really means\",\"level\":2},\"tunes\":{}},{\"id\":\"p-meaning-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The phrase is often misunderstood as “the one database that contains everything.” That can be true in a narrow system, but it is usually too simplistic for AI. A real AI application can combine operational databases, documents, APIs, vector indexes, user input, model memory, external web sources and generated summaries.\"},\"tunes\":{}},{\"id\":\"p-meaning-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"Those sources do not have equal authority. A customer-support manual may define policy but not a customer's current balance. A CRM may define the current account owner but not the legal meaning of a regulation. A source-code repository may define implemented behavior while a product specification defines intended behavior. The architecture must therefore answer a more precise question: which source is authoritative for this specific claim?\"},\"tunes\":{}},{\"id\":\"p-meaning-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"This makes Source of Truth a relationship between a claim and an authority, not merely a property of a storage technology.\"},\"tunes\":{}},{\"id\":\"principle\",\"type\":\"callout\",\"data\":{\"variant\":\"success\",\"title\":\"Core principle\",\"body\":\"\u003Cstrong>One system can have many Sources of Truth because authority is fact-specific.\u003C\u002Fstrong> The important architectural property is not that one database wins globally, but that each important fact or state has an explicit authoritative owner.\"},\"tunes\":{}},{\"id\":\"h-simple\",\"type\":\"header\",\"data\":{\"text\":\"The simplest example\",\"level\":2},\"tunes\":{}},{\"id\":\"p-simple-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"A user asks an AI assistant: “What is my current subscription plan?” The assistant has three possible inputs: last month's support transcript, an indexed help-center document describing plan types, and the live billing database.\"},\"tunes\":{}},{\"id\":\"p-simple-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"The support transcript may mention that the user had a Pro plan. The help-center document explains what Pro means. But the live billing record is the authoritative source for the user's current subscription state.\"},\"tunes\":{}},{\"id\":\"p-simple-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"A semantic search engine could rank the support transcript above the billing record because it contains language closer to the question. That ranking would still not make the transcript authoritative. Relevance and authority are different dimensions.\"},\"tunes\":{}},{\"id\":\"simple-comparison\",\"type\":\"comparison\",\"data\":{\"title\":\"The same question can involve different source roles\",\"layout\":\"table\",\"columns\":[{\"id\":\"source\",\"label\":\"Source\"},{\"id\":\"role\",\"label\":\"Role\"},{\"id\":\"authority\",\"label\":\"Authority for current plan?\"}],\"rows\":[{\"id\":\"billing\",\"label\":\"Billing database\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"help\",\"label\":\"Help-center documentation\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"transcript\",\"label\":\"Old support transcript\",\"values\":[\"\",\"\",\"\"]},{\"id\":\"model\",\"label\":\"Model memory\",\"values\":[\"\",\"\",\"\"]}]},\"tunes\":{}},{\"id\":\"h-stops\",\"type\":\"header\",\"data\":{\"text\":\"Where the simple example stops\",\"level\":2},\"tunes\":{}},{\"id\":\"p-stops-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Not every domain has one unquestioned authority. Historical research can contain conflicting primary sources. Scientific claims can evolve as new studies appear. Legal interpretation can depend on jurisdiction, date and court authority. Product behavior can differ between documentation and deployed code.\"},\"tunes\":{}},{\"id\":\"p-stops-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"In these cases the correct architecture is not to invent a single winner. It is to preserve the competing sources, their provenance, their authority class, their applicable scope and the unresolved contradiction. A reliable Source-of-Truth system must be able to represent uncertainty and disagreement.\"},\"tunes\":{}},{\"id\":\"h-authority\",\"type\":\"header\",\"data\":{\"text\":\"Authority is scoped by claim, version and time\",\"level\":2},\"tunes\":{}},{\"id\":\"authority-table\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Question\",\"Possible authoritative source\",\"Why scope matters\"],[\"What is the user's current account balance?\",\"Ledger \u002F accounting system of record\",\"Historical exports may be accurate for an earlier time but not current state.\"],[\"What does company policy currently allow?\",\"Approved current policy version\",\"An older policy may remain valid evidence of past rules but not present rules.\"],[\"What code is actually deployed?\",\"Deployment artifact \u002F commit \u002F release record\",\"Main branch may differ from production.\"],[\"What did a contract state when signed?\",\"Executed contract version\",\"A draft or later template is not authoritative for the signed agreement.\"],[\"What does a technical protocol specify?\",\"Current official specification for the relevant version\",\"A blog explanation may be useful but is secondary evidence.\"],[\"What happened in a historical event?\",\"Relevant primary evidence plus explicit source criticism\",\"There may be no single authority; conflicting evidence must remain visible.\"],[\"What does a user prefer?\",\"Current explicit user setting or confirmed preference\",\"Old conversation memory may be stale or superseded.\"]]},\"tunes\":{}},{\"id\":\"p-authority-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The word “truth” can therefore be misleading unless its boundary is stated. In architecture, the Source of Truth is usually better understood as the source authorized to determine a specific proposition under defined conditions.\"},\"tunes\":{}},{\"id\":\"h-what-is-not\",\"type\":\"header\",\"data\":{\"text\":\"What a Source of Truth is not\",\"level\":2},\"tunes\":{}},{\"id\":\"h-vs-sor\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs system of record\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-sor-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"A system of record is typically the authoritative operational system for a class of records: for example, a billing ledger, HR master record or order database. It is one common implementation of Source-of-Truth authority.\"},\"tunes\":{}},{\"id\":\"p-vs-sor-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"But Source of Truth is broader. A signed PDF contract, an official standard, a deployment artifact or a primary archival document may be authoritative without being a transactional system of record.\"},\"tunes\":{}},{\"id\":\"h-vs-prov\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs provenance\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-prov-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Provenance answers questions such as: Where did this data come from? Who or what produced it? Which transformation created this derivative? Which prior entity was used? W3C PROV models entities, activities, agents and derivations so origin and responsibility can be represented.\"},\"tunes\":{}},{\"id\":\"p-vs-prov-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"Provenance does not by itself establish authority. Knowing that a value came from a spreadsheet written by a specific employee helps evaluate it, but the application still needs a rule saying whether that spreadsheet is authoritative for the claim.\"},\"tunes\":{}},{\"id\":\"h-vs-evidence\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs evidence\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-evidence-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Evidence supports or contradicts a claim. A Source of Truth defines which source has the authority to settle or strongly constrain that claim in the current application context.\"},\"tunes\":{}},{\"id\":\"p-vs-evidence-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"A source can be valuable evidence without being authoritative. Five customer emails may be evidence that users dislike a workflow, but they are not the system of record for current product configuration.\"},\"tunes\":{}},{\"id\":\"h-vs-rag\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs RAG\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-rag-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"RAG is a retrieval pattern. It finds information and supplies selected content to the model. RAG does not automatically know which source deserves authority.\"},\"tunes\":{}},{\"id\":\"p-vs-rag-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"A RAG pipeline can retrieve a stale document, a secondary summary or a highly similar but non-authoritative source. Source authority must be encoded through corpus design, metadata, filters, ranking policy, validation or post-retrieval checks.\"},\"tunes\":{}},{\"id\":\"h-vs-vector\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs vector database\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-vector-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"A vector database stores or indexes representations used for semantic retrieval. It is an access layer, not automatically a truth layer.\"},\"tunes\":{}},{\"id\":\"p-vs-vector-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"The same authoritative document may be chunked, embedded, copied and re-indexed many times. The vector record should retain a reference back to the authoritative source and version rather than becoming an untraceable new authority.\"},\"tunes\":{}},{\"id\":\"h-vs-memory\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs memory\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-memory-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Agent or application memory stores information that may be useful later. Memory can preserve a prior decision, preference or observation, but it can become stale.\"},\"tunes\":{}},{\"id\":\"p-vs-memory-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"For volatile or consequential state, a reliable agent should normally re-read the authoritative current source rather than assume that remembered state is still true.\"},\"tunes\":{}},{\"id\":\"h-vs-context\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs context\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-context-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Context is what the model receives during the current inference. Authoritative information can be absent from context, while non-authoritative information can be present.\"},\"tunes\":{}},{\"id\":\"p-vs-context-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"Context construction therefore needs an authority-aware policy: retrieve or read the source that is allowed to define the claim, then preserve enough metadata for the model or validator to understand its scope.\"},\"tunes\":{}},{\"id\":\"h-vs-ground-truth\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs evaluation ground truth\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-ground-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Evaluation ground truth is the reference answer, label or outcome against which a system is scored. It can be derived from authoritative sources, expert adjudication or curated test data.\"},\"tunes\":{}},{\"id\":\"p-vs-ground-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"Ground truth is therefore an evaluation construct. A Source of Truth is an application\u002Fdomain authority construct. They can overlap, but they are not interchangeable.\"},\"tunes\":{}},{\"id\":\"h-vs-quality\",\"type\":\"header\",\"data\":{\"text\":\"Source of Truth vs data quality\",\"level\":3},\"tunes\":{}},{\"id\":\"p-vs-quality-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"An authoritative source can still contain errors. Authority says which source officially governs the fact; data quality asks whether that source is accurate, complete, timely, consistent and fit for purpose.\"},\"tunes\":{}},{\"id\":\"p-vs-quality-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"When an authoritative system is known to be wrong, architecture should record the defect, correction process or exception instead of silently substituting an unofficial source and hiding the discrepancy.\"},\"tunes\":{}},{\"id\":\"h-model\",\"type\":\"header\",\"data\":{\"text\":\"A practical Source-of-Truth architecture model\",\"level\":2},\"tunes\":{}},{\"id\":\"model-note\",\"type\":\"callout\",\"data\":{\"variant\":\"note\",\"title\":\"Proposed architecture model\",\"body\":\"The model below is a practical synthesis for AI systems. It is not a W3C, NIST or ISO standard. It separates authority, provenance, retrieval and model-facing context because those responsibilities are often incorrectly collapsed.\"},\"tunes\":{}},{\"id\":\"sot-flow\",\"type\":\"processFlow\",\"data\":{\"title\":\"Authority-aware AI answer path\",\"orientation\":\"auto\",\"steps\":[{\"label\":\"1. Define the claim type\",\"description\":\"Identify what the user is actually asking: current state, policy, historical fact, technical specification, user preference, calculation or interpretation.\"},{\"label\":\"2. Resolve authority\",\"description\":\"Determine which source or authority class is permitted to define that type of claim for the required scope, version and time.\"},{\"label\":\"3. Acquire evidence\",\"description\":\"Read or retrieve the authoritative source and any necessary supporting or conflicting evidence.\"},{\"label\":\"4. Preserve provenance\",\"description\":\"Carry source identity, version, timestamp, locator, transformation history and responsibility metadata.\"},{\"label\":\"5. Build model context\",\"description\":\"Supply the relevant evidence to the model without discarding authority and applicability metadata.\"},{\"label\":\"6. Generate or compute\",\"description\":\"The model may summarize, compare, reason or transform the evidence, but it does not inherit source authority merely by processing it.\"},{\"label\":\"7. Validate the claim\",\"description\":\"Check that the answer is supported by the right source and remains inside its scope and validity boundary.\"},{\"label\":\"8. Preserve contradictions\",\"description\":\"If authoritative or relevant sources disagree, expose the conflict rather than fabricating false certainty.\"}]},\"tunes\":{}},{\"id\":\"h-registry\",\"type\":\"header\",\"data\":{\"text\":\"Authority should be explicit, not inferred from similarity\",\"level\":2},\"tunes\":{}},{\"id\":\"p-registry-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"One robust implementation pattern is an authority registry or equivalent policy layer that maps claim classes to authoritative source classes. The implementation can be code, metadata, configuration or domain rules; the important property is that authority is deliberate.\"},\"tunes\":{}},{\"id\":\"registry-table\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Claim class\",\"Authority rule\",\"Fallback behavior\"],[\"Current account state\",\"Read live account service \u002F system of record\",\"If unavailable, report that current state cannot be verified.\"],[\"Product documentation\",\"Current approved documentation version\",\"Older version may be shown only with version warning.\"],[\"Implemented software behavior\",\"Relevant deployed release \u002F source artifact\",\"Documentation alone cannot prove deployed behavior.\"],[\"Internal policy\",\"Approved policy repository and active version\",\"Drafts are supporting material, not current authority.\"],[\"External technical standard\",\"Official standards body publication for relevant version\",\"Secondary explanations can clarify but not override the specification.\"],[\"Research claim\",\"Evidence policy appropriate to the domain\",\"Preserve conflicting evidence and confidence rather than force one source.\"]]},\"tunes\":{}},{\"id\":\"h-retrieval\",\"type\":\"header\",\"data\":{\"text\":\"Retrieval should use authority as a ranking constraint\",\"level\":2},\"tunes\":{}},{\"id\":\"p-retrieval-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Semantic relevance answers “Which candidate looks related to this query?” Authority answers “Which candidate is allowed to establish this fact?” A production retrieval system often needs both.\"},\"tunes\":{}},{\"id\":\"p-retrieval-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"A useful sequence is to first constrain the candidate space by identity, tenant, source class, status, version or date, then rank relevant evidence inside the permitted space. If relevance is calculated before critical authorization or authority filters, the pipeline can return a convincing but invalid result.\"},\"tunes\":{}},{\"id\":\"relevance-authority\",\"type\":\"callout\",\"data\":{\"variant\":\"warning\",\"title\":\"Highest similarity is not highest authority\",\"body\":\"A search engine can rank a stale summary above the current primary source. A language model can prefer the better-written explanation over the official record. Neither behavior changes which source owns the fact.\"},\"tunes\":{}},{\"id\":\"h-freshness\",\"type\":\"header\",\"data\":{\"text\":\"Freshness is part of authority\",\"level\":2},\"tunes\":{}},{\"id\":\"p-freshness-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Many Source-of-Truth failures are actually time failures. The correct source was known, but the system used an old snapshot, stale embedding, cached API response or superseded document.\"},\"tunes\":{}},{\"id\":\"p-freshness-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"An authority rule should therefore include invalidation or refresh semantics where the fact can change. “CRM is authoritative” is incomplete when the application reads a week-old replicated export.\"},\"tunes\":{}},{\"id\":\"h-derivation\",\"type\":\"header\",\"data\":{\"text\":\"Derived values need a trace back to authoritative inputs\",\"level\":2},\"tunes\":{}},{\"id\":\"p-derivation-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Some important facts are not stored directly. They are computed from authoritative inputs: a risk score, account total, eligibility status or aggregate metric.\"},\"tunes\":{}},{\"id\":\"p-derivation-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"For derived values, Source-of-Truth architecture should preserve the input authorities, transformation or calculation version and execution time. W3C PROV's distinction between entities, activities and derivations is useful here because it models how one entity was produced from others.\"},\"tunes\":{}},{\"id\":\"derived-rule\",\"type\":\"callout\",\"data\":{\"variant\":\"success\",\"title\":\"Derived truth is conditional\",\"body\":\"A calculated value is only as current and authoritative as its inputs, transformation and validity conditions. Store the lineage needed to recompute or audit it.\"},\"tunes\":{}},{\"id\":\"h-conflict\",\"type\":\"header\",\"data\":{\"text\":\"What happens when authoritative sources disagree?\",\"level\":2},\"tunes\":{}},{\"id\":\"p-conflict-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Conflicts are not edge cases in serious knowledge systems. A signed contract may disagree with a CRM field. Production behavior may disagree with documentation. Two primary historical sources may contradict each other. A current policy can conflict with an outdated local copy.\"},\"tunes\":{}},{\"id\":\"p-conflict-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"The system needs a resolution policy appropriate to the domain. Sometimes one authority clearly outranks the other. Sometimes the newer version supersedes the old one. Sometimes an expert or business owner must adjudicate. And sometimes the correct result is simply: the evidence is unresolved.\"},\"tunes\":{}},{\"id\":\"conflict-table\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Conflict type\",\"Typical handling\"],[\"Current vs superseded version\",\"Use current version for present state; retain older version as historical evidence.\"],[\"System of record vs stale replica\",\"Use system of record; flag replication freshness issue.\"],[\"Contract vs CRM transcription\",\"Executed contract governs contractual wording; CRM discrepancy becomes a correction task.\"],[\"Documentation vs deployed behavior\",\"Distinguish intended behavior from observed\u002Fdeployed behavior; do not silently merge them.\"],[\"Two credible primary sources\",\"Preserve both, assess provenance and scope, and represent unresolved disagreement if no governing authority exists.\"],[\"User memory vs current user setting\",\"Use current explicit setting; mark memory as superseded where appropriate.\"]]},\"tunes\":{}},{\"id\":\"h-web\",\"type\":\"header\",\"data\":{\"text\":\"Web search is discovery, not automatically evidence\",\"level\":2},\"tunes\":{}},{\"id\":\"p-web-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Search engines are excellent discovery systems. Search snippets, result ranking and generated summaries are not automatically primary evidence.\"},\"tunes\":{}},{\"id\":\"p-web-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"For claims that require authority, the search result should lead to the original publication, official record, source document, dataset or other appropriate artifact. The result page helps locate the source; it does not inherit the source's authority.\"},\"tunes\":{}},{\"id\":\"h-ai\",\"type\":\"header\",\"data\":{\"text\":\"The language model should not decide authority by itself\",\"level\":2},\"tunes\":{}},{\"id\":\"p-ai-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"A model can help classify a question, extract claims or compare evidence, but authority should not depend only on the model's preference. Models optimize generation from context; they do not possess a guaranteed domain-specific registry of which database, document or organization owns each fact.\"},\"tunes\":{}},{\"id\":\"p-ai-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"This is why application architecture should encode critical authority rules deterministically where practical. The model may reason within the boundary, but the boundary itself should not be recreated from scratch for every prompt.\"},\"tunes\":{}},{\"id\":\"h-observability\",\"type\":\"header\",\"data\":{\"text\":\"Authority must survive the execution trace\",\"level\":2},\"tunes\":{}},{\"id\":\"p-observability-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"If a production answer is important enough to audit, the trace should make it possible to reconstruct which sources were consulted, which version was used, which passage or record supported the claim, which transformations occurred and whether conflicting evidence was available.\"},\"tunes\":{}},{\"id\":\"p-observability-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"This aligns with the broader provenance principle in W3C PROV and with NIST AI RMF Playbook guidance to document sources, origins, transformations, dependencies, constraints and metadata.\"},\"tunes\":{}},{\"id\":\"h-implementation\",\"type\":\"header\",\"data\":{\"text\":\"Original implementation evidence: Source of Truth Research Engine\",\"level\":2},\"tunes\":{}},{\"id\":\"implementation-note\",\"type\":\"callout\",\"data\":{\"variant\":\"note\",\"title\":\"Original implementation evidence\",\"body\":\"The Source of Truth Research Engine is my own implementation evidence for an evidence-first architecture. It demonstrates one concrete way to separate discovery, source acquisition, provenance, claims, evidence classes, contradictions and conclusions. It is an implementation pattern, not a universal industry standard.\"},\"tunes\":{}},{\"id\":\"p-impl-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The engine is designed around a traceable pipeline rather than direct AI summarization: research task → search → original source or digital artifact → local snapshot → SHA-256 → source ID → claim → evidence class → relation or contradiction → interpretation → conclusion.\"},\"tunes\":{}},{\"id\":\"p-impl-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"Its shared evidence core stores Sources, Artifacts, provenance, Claims, Relations, Contradictions, a Reference Model and an audit trail. Different research modes can share that core while applying different domain methodologies.\"},\"tunes\":{}},{\"id\":\"p-impl-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"The architecture deliberately separates discovery from evidence. Search snippets are not treated as evidence, filenames are not treated as content, AI summaries are not treated as primary sources, and semantic similarity is only a discovery signal until a result is traced back to a concrete source and locator.\"},\"tunes\":{}},{\"id\":\"p-impl-4\",\"type\":\"paragraph\",\"data\":{\"text\":\"Original files are preserved and local bytes receive SHA-256 identifiers. Contradictions and rejected hypotheses are not silently deleted. New evidence is allowed to change the current reference model while the prior evidence path remains auditable.\"},\"tunes\":{}},{\"id\":\"implementation-table\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Implemented rule\",\"Why it matters for Source-of-Truth architecture\"],[\"Search ≠ evidence\",\"Discovery ranking cannot silently become authority.\"],[\"Filename ≠ content\",\"Metadata clues cannot substitute for reading the actual artifact.\"],[\"Local snapshot + SHA-256\",\"Evidence can be tied to exact bytes rather than a mutable remote label.\"],[\"Source ID + exact locator\",\"Claims can be traced back to the concrete evidence location.\"],[\"Claim\u002Fevidence separation\",\"The assertion is not confused with the material supporting it.\"],[\"Contradictions preserved\",\"The system can represent unresolved disagreement rather than overwrite history.\"],[\"Semantic similarity is discovery only\",\"Retrieval relevance is explicitly separated from evidentiary authority.\"],[\"New evidence may update the model\",\"Source-of-Truth state is versioned and revisable rather than treated as immutable dogma.\"]]},\"tunes\":{}},{\"id\":\"h-document-engine\",\"type\":\"header\",\"data\":{\"text\":\"Aaasaasa Document & Knowledge Engine: applying the same boundary to enterprise documents\",\"level\":2},\"tunes\":{}},{\"id\":\"p-doc-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The Aaasaasa Document & Knowledge Engine concept extends the same design principle to enterprise documentation: users should be able to search documents, ask source-grounded questions and review collections against explicit criteria while preserving the distinction between what a document states and what the system infers.\"},\"tunes\":{}},{\"id\":\"p-doc-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"The important architecture rule is that a universal retrieval core does not make every collection equally authoritative. Contract documents, maintenance records, financial documents and research material need different authority, validation and coverage rules even when they share ingestion and search infrastructure.\"},\"tunes\":{}},{\"id\":\"h-failures\",\"type\":\"header\",\"data\":{\"text\":\"Common Source-of-Truth failure modes\",\"level\":2},\"tunes\":{}},{\"id\":\"failures-table\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Failure mode\",\"What goes wrong\"],[\"The model is treated as the source of truth\",\"Parametric knowledge can be stale, incomplete, unverifiable or outside the application's authoritative scope.\"],[\"Top retrieval result wins automatically\",\"Similarity is mistaken for authority.\"],[\"Vector database becomes authoritative\",\"Derived index records lose the identity and version of the original source.\"],[\"Everything is copied into one knowledge base\",\"Copies obscure ownership, freshness and correction paths.\"],[\"Memory is reused as current state\",\"Old observations silently override the current system of record.\"],[\"No version metadata\",\"The right document is used for the wrong time period.\"],[\"No source locator\",\"A citation exists but the supporting passage or record cannot be verified.\"],[\"Conflicts are overwritten\",\"The system appears consistent by destroying evidence of disagreement.\"],[\"Generated summaries replace originals\",\"A lossy transformation becomes the apparent authority.\"],[\"Authority is global instead of claim-specific\",\"One source is trusted beyond the domain or fact class it actually owns.\"],[\"Web snippet is treated as evidence\",\"Discovery metadata replaces the original publication.\"],[\"Authoritative data is wrong but exceptions are hidden\",\"Operational defects become invisible and cannot be corrected transparently.\"]]},\"tunes\":{}},{\"id\":\"h-decision\",\"type\":\"header\",\"data\":{\"text\":\"A practical Source-of-Truth decision framework\",\"level\":2},\"tunes\":{}},{\"id\":\"decision-flow\",\"type\":\"processFlow\",\"data\":{\"title\":\"How to decide what should define a claim\",\"orientation\":\"auto\",\"steps\":[{\"label\":\"1. State the claim precisely\",\"description\":\"Separate current state, historical state, policy, interpretation, prediction and derived calculation.\"},{\"label\":\"2. Identify the authority owner\",\"description\":\"Determine the system, document, institution, person or evidence class responsible for that claim type.\"},{\"label\":\"3. Define scope\",\"description\":\"Specify tenant, jurisdiction, product, environment, user, document set or other applicability boundary.\"},{\"label\":\"4. Define time and version\",\"description\":\"Determine whether the claim requires current state, a historical snapshot or a specific standard\u002Frelease version.\"},{\"label\":\"5. Preserve provenance\",\"description\":\"Record source identity, origin, locator, transformations and responsible agents or processes.\"},{\"label\":\"6. Define retrieval\u002Faccess path\",\"description\":\"Make sure the application can actually obtain the authoritative information under the correct identity and permissions.\"},{\"label\":\"7. Define conflict policy\",\"description\":\"Decide precedence, supersession, adjudication or explicit unresolved-state behavior.\"},{\"label\":\"8. Define invalidation\",\"description\":\"Specify when cached, indexed, remembered or derived representations must be refreshed.\"},{\"label\":\"9. Validate the answer path\",\"description\":\"Verify that important generated claims can be traced to the intended authority, not merely to a plausible source.\"}]},\"tunes\":{}},{\"id\":\"h-checklist\",\"type\":\"header\",\"data\":{\"text\":\"Source-of-Truth architecture checklist\",\"level\":2},\"tunes\":{}},{\"id\":\"checklist-table\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Question\",\"Expected answer\"],[\"What exact fact or state is being established?\",\"A claim precise enough to assign authority.\"],[\"Who or what owns that fact?\",\"Named authoritative system, source class or adjudication rule.\"],[\"Is the authority current for this scope?\",\"Tenant, jurisdiction, environment, user or domain boundary is explicit.\"],[\"Is the version\u002Ftime correct?\",\"Current, historical or version-specific applicability is known.\"],[\"Can the source be verified?\",\"Stable identifier, locator or record reference exists.\"],[\"Is provenance preserved?\",\"Origin, transformation and responsibility metadata survive ingestion and retrieval.\"],[\"Can retrieval return non-authoritative material?\",\"If yes, filters or validation distinguish relevance from authority.\"],[\"Can the source change?\",\"Refresh, invalidation or supersession rules exist.\"],[\"Can sources disagree?\",\"Conflict and adjudication behavior is explicit.\"],[\"Can memory become stale?\",\"Volatile state is re-read from the current authority before consequential use.\"],[\"Can a derived answer be reproduced?\",\"Inputs, transformation version and execution conditions are traceable.\"],[\"Can an auditor reconstruct the answer?\",\"Execution evidence preserves the source path for important claims.\"]]},\"tunes\":{}},{\"id\":\"h-misconceptions\",\"type\":\"header\",\"data\":{\"text\":\"Common misconceptions\",\"level\":2},\"tunes\":{}},{\"id\":\"misconceptions-table\",\"type\":\"table\",\"data\":{\"withHeadings\":true,\"stretched\":false,\"content\":[[\"Misconception\",\"Correction\"],[\"“Source of Truth means one database.”\",\"One database can be authoritative for one domain; complex systems usually have multiple fact-specific authorities.\"],[\"“The newest document is automatically authoritative.”\",\"Recency helps only when the newer artifact is approved and actually supersedes the older one.\"],[\"“RAG solves truth.”\",\"RAG solves retrieval. Authority, provenance, evidence quality and validity remain separate problems.\"],[\"“A citation proves the answer.”\",\"The cited source must actually support the claim, have the right authority and apply to the current scope.\"],[\"“Provenance tells us what is true.”\",\"Provenance tells us origin and derivation; authority and correctness still require domain rules and evaluation.\"],[\"“The system of record is always correct.”\",\"It is authoritative for the operational record, but data-quality defects can still exist and require visible correction.\"],[\"“If several sources agree, the claim is authoritative.”\",\"Agreement increases evidence but does not necessarily establish ownership or applicability.\"],[\"“AI memory can replace repeated reads.”\",\"Only for information whose staleness risk is acceptable; volatile or consequential state should be refreshed from authority.\"]]},\"tunes\":{}},{\"id\":\"h-edge\",\"type\":\"header\",\"data\":{\"text\":\"Edge cases\",\"level\":2},\"tunes\":{}},{\"id\":\"p-edge-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Some questions are interpretive rather than factual. “Which architecture is best?” has no single Source of Truth. The system can retrieve authoritative constraints and evidence, but the final judgment is an inference that should expose assumptions and trade-offs.\"},\"tunes\":{}},{\"id\":\"p-edge-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"Some domains use distributed authority. A scientific conclusion can depend on multiple studies, datasets and replications. A historical conclusion can depend on conflicting primary and secondary evidence. The architecture should represent evidence structure rather than invent a central database that supposedly owns truth.\"},\"tunes\":{}},{\"id\":\"p-edge-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"A user can also be the authority for subjective personal information: preferences, goals, chosen settings or explicit instructions. Even then, newer explicit input can supersede older memory.\"},\"tunes\":{}},{\"id\":\"p-edge-4\",\"type\":\"paragraph\",\"data\":{\"text\":\"External events can invalidate previously authoritative data. A price feed, inventory system or security policy may have been correct when captured but no longer valid. Snapshot provenance preserves what was true then; it does not make the snapshot current forever.\"},\"tunes\":{}},{\"id\":\"h-limit\",\"type\":\"header\",\"data\":{\"text\":\"Limitations\",\"level\":2},\"tunes\":{}},{\"id\":\"p-limit-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Source-of-Truth architecture cannot guarantee that an authoritative source is factually correct. It provides accountability, provenance and deterministic ownership boundaries; data-quality and domain-verification processes remain necessary.\"},\"tunes\":{}},{\"id\":\"p-limit-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"Authority can also be contested. Different institutions can legitimately claim authority in different jurisdictions or methodologies. In those situations the system should expose the authority model and disagreement rather than hide it behind a universal “truth score.”\"},\"tunes\":{}},{\"id\":\"p-limit-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"Finally, authority rules require maintenance. Systems, owners, policies, versions and regulations change. A stale authority registry can be as dangerous as no registry at all.\"},\"tunes\":{}},{\"id\":\"h-change\",\"type\":\"header\",\"data\":{\"text\":\"What would change this answer?\",\"level\":2},\"tunes\":{}},{\"id\":\"p-change-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"The specific authority mapping changes with the domain. Banking, healthcare, software delivery, scientific research and historical analysis have different systems of record, evidentiary rules and regulatory obligations.\"},\"tunes\":{}},{\"id\":\"p-change-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"The implementation also changes with architecture. A small application can encode authority directly in service calls. A larger platform may need registries, source metadata, policy engines, lineage systems or data contracts. The core principle remains the same: do not let retrieval order or model preference silently decide what counts as authoritative.\"},\"tunes\":{}},{\"id\":\"h-related\",\"type\":\"header\",\"data\":{\"text\":\"Related canonical knowledge\",\"level\":2},\"tunes\":{}},{\"id\":\"p-related-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Source-of-Truth architecture is a prerequisite for later retrieval and governance concepts because retrieval quality alone cannot determine whether evidence is allowed to define the answer.\"},\"tunes\":{}},{\"id\":\"ref-rag\",\"type\":\"referralArticle\",\"data\":{\"url\":\"https:\u002F\u002Fstajic.de\u002Fblog\u002Fwhat-is-rag-the-simplest-explanation-of-how-it-works\",\"title\":\"What Is RAG? The Simplest Explanation of How It Works\",\"excerpt\":\"RAG retrieves external knowledge for a model. This foundation explains why retrieval and authoritative truth are separate responsibilities.\",\"ctaLabel\":\"Read the RAG foundation\"},\"tunes\":{}},{\"id\":\"p-related-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"Memory is another adjacent concept. A reliable agent separates remembered information from current authoritative application state.\"},\"tunes\":{}},{\"id\":\"ref-memory\",\"type\":\"referralArticle\",\"data\":{\"url\":\"https:\u002F\u002Fstajic.de\u002Fblog\u002Fai-agent-memory-is-not-rag-how-to-separate-memory-retrieval-state-and-context\",\"title\":\"AI Agent Memory Is Not RAG: How to Separate Memory, Retrieval, State and Context\",\"excerpt\":\"A four-layer architecture separating persistent memory, authoritative state, retrieval and the context actually supplied to the model.\",\"ctaLabel\":\"Read the memory architecture article\"},\"tunes\":{}},{\"id\":\"p-related-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"Authority also connects directly to answer validity. Even an authoritative source supports only claims inside its version, date, scope and evidence boundary.\"},\"tunes\":{}},{\"id\":\"ref-avb\",\"type\":\"referralArticle\",\"data\":{\"url\":\"https:\u002F\u002Fstajic.de\u002Fblog\u002Fthe-answer-validity-boundary-the-missing-layer-between-relevance-and-reliable-ai-answers\",\"title\":\"The Answer Validity Boundary: The Missing Layer Between Relevance and Reliable AI Answers\",\"excerpt\":\"A framework for making explicit where an AI answer remains supported by evidence and which changed conditions invalidate that support.\",\"ctaLabel\":\"Read the Answer Validity Boundary\"},\"tunes\":{}},{\"id\":\"h-faq\",\"type\":\"header\",\"data\":{\"text\":\"Frequently asked questions\",\"level\":2},\"tunes\":{}},{\"id\":\"faq\",\"type\":\"faq\",\"data\":{\"title\":\"Source of Truth in AI systems\",\"items\":[{\"id\":\"faq1\",\"question\":\"What is a Source of Truth in an AI system?\",\"answer\":\"It is the authoritative source or authority rule that determines which source is allowed to establish a specific fact, state or rule for a defined scope, version and time.\"},{\"id\":\"faq2\",\"question\":\"Is the language model a Source of Truth?\",\"answer\":\"Normally no. A language model can generate, summarize and reason, but its parametric knowledge is not automatically authoritative for current application state, company policy, a specific document version or a regulated domain fact.\"},{\"id\":\"faq3\",\"question\":\"Is a vector database the Source of Truth for RAG?\",\"answer\":\"Not automatically. A vector database is usually an index or retrieval store. It should preserve references to the authoritative original source and version rather than silently replacing them.\"},{\"id\":\"faq4\",\"question\":\"What is the difference between provenance and Source of Truth?\",\"answer\":\"Provenance describes where data came from, how it was produced or transformed and who or what was involved. Source-of-Truth rules determine whether that source has authority for the specific claim.\"},{\"id\":\"faq5\",\"question\":\"Can an AI system have multiple Sources of Truth?\",\"answer\":\"Yes. In complex systems this is normal because different facts belong to different authoritative systems or source classes.\"},{\"id\":\"faq6\",\"question\":\"What happens when two authoritative sources disagree?\",\"answer\":\"The system needs a domain-specific conflict rule: precedence, version supersession, expert adjudication or an explicit unresolved state. It should not silently choose the source the model prefers.\"},{\"id\":\"faq7\",\"question\":\"Does RAG guarantee that an AI answer uses the Source of Truth?\",\"answer\":\"No. RAG retrieves candidates. Authority-aware metadata, filters, source policy and validation are needed to ensure that important claims use the correct source.\"},{\"id\":\"faq8\",\"question\":\"Can the Source of Truth be wrong?\",\"answer\":\"Yes. Authority and correctness are different properties. An authoritative system can contain a data-quality defect, which should be corrected transparently rather than hidden by substituting an unofficial source.\"}]},\"tunes\":{}},{\"id\":\"h-glossary\",\"type\":\"header\",\"data\":{\"text\":\"Glossary\",\"level\":2},\"tunes\":{}},{\"id\":\"glossary\",\"type\":\"glossary\",\"data\":{\"title\":\"Key Source-of-Truth terms\",\"entries\":[{\"term\":\"Source of Truth\",\"definition\":\"The authoritative source or rule permitted to establish a particular fact, state or rule for a defined scope, version and time.\",\"anchor\":\"source-of-truth\"},{\"term\":\"System of record\",\"definition\":\"The authoritative operational system responsible for a defined class of records or current business state.\",\"anchor\":\"system-of-record\"},{\"term\":\"Provenance\",\"definition\":\"Information describing the origin, derivation, transformations, responsible agents and history of data or another entity.\",\"anchor\":\"provenance\"},{\"term\":\"Evidence\",\"definition\":\"Information or an artifact that supports, contradicts or constrains a claim.\",\"anchor\":\"evidence\"},{\"term\":\"Authority\",\"definition\":\"The application or domain rule determining which source is entitled to define a specific claim.\",\"anchor\":\"authority\"},{\"term\":\"Freshness\",\"definition\":\"Whether a representation remains current enough for the claim or operation in which it is used.\",\"anchor\":\"freshness\"},{\"term\":\"Supersession\",\"definition\":\"The explicit replacement of an older authoritative version by a newer one while preserving historical traceability.\",\"anchor\":\"supersession\"},{\"term\":\"Ground truth\",\"definition\":\"A reference answer, label or outcome used to evaluate a system; it is an evaluation construct rather than automatically the application's Source of Truth.\",\"anchor\":\"ground-truth\"},{\"term\":\"Lineage\",\"definition\":\"The trace of how data or derived values flow and transform across sources and processing steps.\",\"anchor\":\"lineage\"},{\"term\":\"Validity boundary\",\"definition\":\"The conditions of scope, time, version, evidence and assumptions inside which a claim remains supported.\",\"anchor\":\"validity-boundary\"}]},\"tunes\":{}},{\"id\":\"h-conclusion\",\"type\":\"header\",\"data\":{\"text\":\"Conclusion\",\"level\":2},\"tunes\":{}},{\"id\":\"p-conclusion-1\",\"type\":\"paragraph\",\"data\":{\"text\":\"Reliable AI does not come from giving the model more information. It comes from knowing which information is allowed to define the claim, preserving where that information came from, retrieving the correct version and keeping the final answer inside the source's scope.\"},\"tunes\":{}},{\"id\":\"p-conclusion-2\",\"type\":\"paragraph\",\"data\":{\"text\":\"That is why Source of Truth, provenance, retrieval, memory and context must remain separate concepts. The Source of Truth defines authority. Provenance explains origin. Retrieval finds candidates. Memory preserves selected past information. Context is what the model sees. Generation turns those inputs into an output.\"},\"tunes\":{}},{\"id\":\"p-conclusion-3\",\"type\":\"paragraph\",\"data\":{\"text\":\"When those layers remain explicit, an AI system can do more than sound plausible: important claims can be traced back to the source that actually had the right to establish them.\"},\"tunes\":{}},{\"id\":\"h-sources\",\"type\":\"header\",\"data\":{\"text\":\"Primary sources and implementation evidence\",\"level\":2},\"tunes\":{}},{\"id\":\"p-sources-note\",\"type\":\"paragraph\",\"data\":{\"text\":\"The external sources below support provenance and AI risk-management claims. The Source of Truth Research Engine section is original implementation evidence and is explicitly presented as one implementation pattern rather than a universal standard.\"},\"tunes\":{}},{\"id\":\"src-w3c-prov\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fwww.w3.org\u002FTR\u002Fprov-dm\u002F\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"W3C PROV-DM — The PROV Data Model\",\"description\":\"W3C Recommendation defining a domain-agnostic provenance model around entities, activities, agents, derivations and responsibility.\"}},\"tunes\":{}},{\"id\":\"src-w3c-publications\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fwww.w3.org\u002Fgroups\u002Fwg\u002Fprov\u002Fpublications\u002F\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"W3C Provenance Working Group — Publications\",\"description\":\"Official index of W3C PROV Recommendations and related specifications for provenance interchange and constraints.\"}},\"tunes\":{}},{\"id\":\"src-nist-rmf\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fwww.nist.gov\u002Fitl\u002Fai-risk-management-framework\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"NIST AI Risk Management Framework\",\"description\":\"NIST's voluntary framework for incorporating trustworthiness and risk-management considerations across the AI lifecycle; AI RMF 1.0 is currently being revised.\"}},\"tunes\":{}},{\"id\":\"src-nist-playbook\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fairc.nist.gov\u002Fairmf-resources\u002Fplaybook\u002F\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"NIST AI RMF Playbook\",\"description\":\"Operational guidance aligned to the AI RMF, including documentation practices for data provenance, sources, origins, transformations, dependencies, constraints and metadata.\"}},\"tunes\":{}},{\"id\":\"src-nist-measure\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fairc.nist.gov\u002Fairmf-resources\u002Fplaybook\u002Fmeasure\u002F\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"NIST AI RMF Playbook — Measure\",\"description\":\"Guidance on documenting measurement, data provenance and contextual interpretation of AI system outputs.\"}},\"tunes\":{}},{\"id\":\"src-nist-genai\",\"type\":\"linkTool\",\"data\":{\"link\":\"https:\u002F\u002Fwww.nist.gov\u002Fpublications\u002Fartificial-intelligence-risk-management-framework-generative-artificial-intelligence\",\"meta\":{\"image\":{\"url\":\"\"},\"title\":\"NIST AI 600-1 — Generative AI Profile\",\"description\":\"NIST generative-AI profile, including provenance and information-integrity considerations for generative AI systems.\"}},\"tunes\":{}}],\"version\":\"2.31.6\"}",{"time":212,"blocks":213,"version":1296},1791479104597,[214,220,228,235,241,249,254,259,264,269,276,281,286,291,296,331,336,341,346,351,388,393,398,403,408,413,418,423,428,433,438,443,448,453,458,463,468,473,478,483,488,493,498,503,508,513,518,523,528,533,538,544,576,581,586,619,624,629,634,641,646,651,656,661,666,671,677,682,687,692,718,723,728,733,738,743,748,753,758,763,768,774,779,784,789,794,826,831,836,841,846,890,895,928,933,976,981,1013,1018,1023,1028,1033,1038,1043,1048,1053,1058,1063,1068,1073,1078,1083,1092,1097,1105,1110,1118,1123,1161,1166,1211,1216,1221,1226,1231,1236,1241,1251,1260,1269,1278,1287],{"id":215,"data":216,"type":218,"tunes":219},"intro",{"text":217},"A Source of Truth in an AI system is the authoritative source allowed to define whether a specific fact, state or rule should be treated as true for a particular scope, version and time. It is not automatically the language model, the vector database, the top-ranked retrieved document, agent memory or the latest message in context. Reliable AI architecture must preserve which source has authority for which claim, then keep provenance, retrieval and validation connected to that authority.","paragraph",{},{"id":221,"data":222,"type":226,"tunes":227},"direct",{"body":223,"title":224,"variant":225},"\u003Cstrong>The Source of Truth is an authority rule, not an AI component.\u003C\u002Fstrong> An AI system can search many sources, but only some sources are authoritative for a given question. The correct source may be an application database for current account state, an approved policy document for a rule, source code for implemented behavior, an official specification for a protocol, or a primary research artifact for an observed claim. Good architecture makes that authority explicit instead of asking the model to infer it from relevance.","Direct answer","info","callout",{},{"id":229,"data":230,"type":226,"tunes":234},"terminology",{"body":231,"title":232,"variant":233},"“Source of Truth” is widely used in software, data and organizational practice, but it is not a standardized AI component with one universal formal definition. This article uses it as an architecture concept: \u003Cstrong>the source or authority mapping that determines which evidence is allowed to establish a particular fact or state\u003C\u002Fstrong>. Provenance standards such as W3C PROV describe origin and derivation; they do not automatically decide which source your application should treat as authoritative.","Terminology boundary","note",{},{"id":236,"data":237,"type":226,"tunes":240},"current",{"body":238,"title":239,"variant":233},"The core distinction between authority, provenance, retrieval and model context is stable. NIST AI RMF 1.0 is currently being revised, but the current NIST Playbook still explicitly recommends documenting data provenance, including sources, origins, transformations, dependencies, constraints and metadata. W3C PROV remains a W3C Recommendation for interoperable provenance descriptions.","Current-source note — 8 October 2026",{},{"id":242,"data":243,"type":247,"tunes":248},"toc",{"title":244,"maxLevel":245,"minLevel":246},"Contents",3,2,"tableOfContents",{},{"id":250,"data":251,"type":42,"tunes":253},"h-meaning",{"text":252,"level":246},"What “Source of Truth” really means",{},{"id":255,"data":256,"type":218,"tunes":258},"p-meaning-1",{"text":257},"The phrase is often misunderstood as “the one database that contains everything.” That can be true in a narrow system, but it is usually too simplistic for AI. A real AI application can combine operational databases, documents, APIs, vector indexes, user input, model memory, external web sources and generated summaries.",{},{"id":260,"data":261,"type":218,"tunes":263},"p-meaning-2",{"text":262},"Those sources do not have equal authority. A customer-support manual may define policy but not a customer's current balance. A CRM may define the current account owner but not the legal meaning of a regulation. A source-code repository may define implemented behavior while a product specification defines intended behavior. The architecture must therefore answer a more precise question: which source is authoritative for this specific claim?",{},{"id":265,"data":266,"type":218,"tunes":268},"p-meaning-3",{"text":267},"This makes Source of Truth a relationship between a claim and an authority, not merely a property of a storage technology.",{},{"id":270,"data":271,"type":226,"tunes":275},"principle",{"body":272,"title":273,"variant":274},"\u003Cstrong>One system can have many Sources of Truth because authority is fact-specific.\u003C\u002Fstrong> The important architectural property is not that one database wins globally, but that each important fact or state has an explicit authoritative owner.","Core principle","success",{},{"id":277,"data":278,"type":42,"tunes":280},"h-simple",{"text":279,"level":246},"The simplest example",{},{"id":282,"data":283,"type":218,"tunes":285},"p-simple-1",{"text":284},"A user asks an AI assistant: “What is my current subscription plan?” The assistant has three possible inputs: last month's support transcript, an indexed help-center document describing plan types, and the live billing database.",{},{"id":287,"data":288,"type":218,"tunes":290},"p-simple-2",{"text":289},"The support transcript may mention that the user had a Pro plan. The help-center document explains what Pro means. But the live billing record is the authoritative source for the user's current subscription state.",{},{"id":292,"data":293,"type":218,"tunes":295},"p-simple-3",{"text":294},"A semantic search engine could rank the support transcript above the billing record because it contains language closer to the question. That ranking would still not make the transcript authoritative. Relevance and authority are different dimensions.",{},{"id":297,"data":298,"type":329,"tunes":330},"simple-comparison",{"rows":299,"title":317,"layout":318,"columns":319},[300,305,309,313],{"id":301,"label":302,"values":303},"billing","Billing database",[304,304,304],"",{"id":306,"label":307,"values":308},"help","Help-center documentation",[304,304,304],{"id":310,"label":311,"values":312},"transcript","Old support transcript",[304,304,304],{"id":314,"label":315,"values":316},"model","Model memory",[304,304,304],"The same question can involve different source roles","table",[320,323,326],{"id":321,"label":322},"source","Source",{"id":324,"label":325},"role","Role",{"id":327,"label":328},"authority","Authority for current plan?","comparison",{},{"id":332,"data":333,"type":42,"tunes":335},"h-stops",{"text":334,"level":246},"Where the simple example stops",{},{"id":337,"data":338,"type":218,"tunes":340},"p-stops-1",{"text":339},"Not every domain has one unquestioned authority. Historical research can contain conflicting primary sources. Scientific claims can evolve as new studies appear. Legal interpretation can depend on jurisdiction, date and court authority. Product behavior can differ between documentation and deployed code.",{},{"id":342,"data":343,"type":218,"tunes":345},"p-stops-2",{"text":344},"In these cases the correct architecture is not to invent a single winner. It is to preserve the competing sources, their provenance, their authority class, their applicable scope and the unresolved contradiction. A reliable Source-of-Truth system must be able to represent uncertainty and disagreement.",{},{"id":347,"data":348,"type":42,"tunes":350},"h-authority",{"text":349,"level":246},"Authority is scoped by claim, version and time",{},{"id":352,"data":353,"type":318,"tunes":387},"authority-table",{"content":354,"stretched":43,"withHeadings":14},[355,359,363,367,371,375,379,383],[356,357,358],"Question","Possible authoritative source","Why scope matters",[360,361,362],"What is the user's current account balance?","Ledger \u002F accounting system of record","Historical exports may be accurate for an earlier time but not current state.",[364,365,366],"What does company policy currently allow?","Approved current policy version","An older policy may remain valid evidence of past rules but not present rules.",[368,369,370],"What code is actually deployed?","Deployment artifact \u002F commit \u002F release record","Main branch may differ from production.",[372,373,374],"What did a contract state when signed?","Executed contract version","A draft or later template is not authoritative for the signed agreement.",[376,377,378],"What does a technical protocol specify?","Current official specification for the relevant version","A blog explanation may be useful but is secondary evidence.",[380,381,382],"What happened in a historical event?","Relevant primary evidence plus explicit source criticism","There may be no single authority; conflicting evidence must remain visible.",[384,385,386],"What does a user prefer?","Current explicit user setting or confirmed preference","Old conversation memory may be stale or superseded.",{},{"id":389,"data":390,"type":218,"tunes":392},"p-authority-1",{"text":391},"The word “truth” can therefore be misleading unless its boundary is stated. In architecture, the Source of Truth is usually better understood as the source authorized to determine a specific proposition under defined conditions.",{},{"id":394,"data":395,"type":42,"tunes":397},"h-what-is-not",{"text":396,"level":246},"What a Source of Truth is not",{},{"id":399,"data":400,"type":42,"tunes":402},"h-vs-sor",{"text":401,"level":245},"Source of Truth vs system of record",{},{"id":404,"data":405,"type":218,"tunes":407},"p-vs-sor-1",{"text":406},"A system of record is typically the authoritative operational system for a class of records: for example, a billing ledger, HR master record or order database. It is one common implementation of Source-of-Truth authority.",{},{"id":409,"data":410,"type":218,"tunes":412},"p-vs-sor-2",{"text":411},"But Source of Truth is broader. A signed PDF contract, an official standard, a deployment artifact or a primary archival document may be authoritative without being a transactional system of record.",{},{"id":414,"data":415,"type":42,"tunes":417},"h-vs-prov",{"text":416,"level":245},"Source of Truth vs provenance",{},{"id":419,"data":420,"type":218,"tunes":422},"p-vs-prov-1",{"text":421},"Provenance answers questions such as: Where did this data come from? Who or what produced it? Which transformation created this derivative? Which prior entity was used? W3C PROV models entities, activities, agents and derivations so origin and responsibility can be represented.",{},{"id":424,"data":425,"type":218,"tunes":427},"p-vs-prov-2",{"text":426},"Provenance does not by itself establish authority. Knowing that a value came from a spreadsheet written by a specific employee helps evaluate it, but the application still needs a rule saying whether that spreadsheet is authoritative for the claim.",{},{"id":429,"data":430,"type":42,"tunes":432},"h-vs-evidence",{"text":431,"level":245},"Source of Truth vs evidence",{},{"id":434,"data":435,"type":218,"tunes":437},"p-vs-evidence-1",{"text":436},"Evidence supports or contradicts a claim. A Source of Truth defines which source has the authority to settle or strongly constrain that claim in the current application context.",{},{"id":439,"data":440,"type":218,"tunes":442},"p-vs-evidence-2",{"text":441},"A source can be valuable evidence without being authoritative. Five customer emails may be evidence that users dislike a workflow, but they are not the system of record for current product configuration.",{},{"id":444,"data":445,"type":42,"tunes":447},"h-vs-rag",{"text":446,"level":245},"Source of Truth vs RAG",{},{"id":449,"data":450,"type":218,"tunes":452},"p-vs-rag-1",{"text":451},"RAG is a retrieval pattern. It finds information and supplies selected content to the model. RAG does not automatically know which source deserves authority.",{},{"id":454,"data":455,"type":218,"tunes":457},"p-vs-rag-2",{"text":456},"A RAG pipeline can retrieve a stale document, a secondary summary or a highly similar but non-authoritative source. Source authority must be encoded through corpus design, metadata, filters, ranking policy, validation or post-retrieval checks.",{},{"id":459,"data":460,"type":42,"tunes":462},"h-vs-vector",{"text":461,"level":245},"Source of Truth vs vector database",{},{"id":464,"data":465,"type":218,"tunes":467},"p-vs-vector-1",{"text":466},"A vector database stores or indexes representations used for semantic retrieval. It is an access layer, not automatically a truth layer.",{},{"id":469,"data":470,"type":218,"tunes":472},"p-vs-vector-2",{"text":471},"The same authoritative document may be chunked, embedded, copied and re-indexed many times. The vector record should retain a reference back to the authoritative source and version rather than becoming an untraceable new authority.",{},{"id":474,"data":475,"type":42,"tunes":477},"h-vs-memory",{"text":476,"level":245},"Source of Truth vs memory",{},{"id":479,"data":480,"type":218,"tunes":482},"p-vs-memory-1",{"text":481},"Agent or application memory stores information that may be useful later. Memory can preserve a prior decision, preference or observation, but it can become stale.",{},{"id":484,"data":485,"type":218,"tunes":487},"p-vs-memory-2",{"text":486},"For volatile or consequential state, a reliable agent should normally re-read the authoritative current source rather than assume that remembered state is still true.",{},{"id":489,"data":490,"type":42,"tunes":492},"h-vs-context",{"text":491,"level":245},"Source of Truth vs context",{},{"id":494,"data":495,"type":218,"tunes":497},"p-vs-context-1",{"text":496},"Context is what the model receives during the current inference. Authoritative information can be absent from context, while non-authoritative information can be present.",{},{"id":499,"data":500,"type":218,"tunes":502},"p-vs-context-2",{"text":501},"Context construction therefore needs an authority-aware policy: retrieve or read the source that is allowed to define the claim, then preserve enough metadata for the model or validator to understand its scope.",{},{"id":504,"data":505,"type":42,"tunes":507},"h-vs-ground-truth",{"text":506,"level":245},"Source of Truth vs evaluation ground truth",{},{"id":509,"data":510,"type":218,"tunes":512},"p-vs-ground-1",{"text":511},"Evaluation ground truth is the reference answer, label or outcome against which a system is scored. It can be derived from authoritative sources, expert adjudication or curated test data.",{},{"id":514,"data":515,"type":218,"tunes":517},"p-vs-ground-2",{"text":516},"Ground truth is therefore an evaluation construct. A Source of Truth is an application\u002Fdomain authority construct. They can overlap, but they are not interchangeable.",{},{"id":519,"data":520,"type":42,"tunes":522},"h-vs-quality",{"text":521,"level":245},"Source of Truth vs data quality",{},{"id":524,"data":525,"type":218,"tunes":527},"p-vs-quality-1",{"text":526},"An authoritative source can still contain errors. Authority says which source officially governs the fact; data quality asks whether that source is accurate, complete, timely, consistent and fit for purpose.",{},{"id":529,"data":530,"type":218,"tunes":532},"p-vs-quality-2",{"text":531},"When an authoritative system is known to be wrong, architecture should record the defect, correction process or exception instead of silently substituting an unofficial source and hiding the discrepancy.",{},{"id":534,"data":535,"type":42,"tunes":537},"h-model",{"text":536,"level":246},"A practical Source-of-Truth architecture model",{},{"id":539,"data":540,"type":226,"tunes":543},"model-note",{"body":541,"title":542,"variant":233},"The model below is a practical synthesis for AI systems. It is not a W3C, NIST or ISO standard. It separates authority, provenance, retrieval and model-facing context because those responsibilities are often incorrectly collapsed.","Proposed architecture model",{},{"id":545,"data":546,"type":574,"tunes":575},"sot-flow",{"steps":547,"title":572,"orientation":573},[548,551,554,557,560,563,566,569],{"label":549,"description":550},"1. Define the claim type","Identify what the user is actually asking: current state, policy, historical fact, technical specification, user preference, calculation or interpretation.",{"label":552,"description":553},"2. Resolve authority","Determine which source or authority class is permitted to define that type of claim for the required scope, version and time.",{"label":555,"description":556},"3. Acquire evidence","Read or retrieve the authoritative source and any necessary supporting or conflicting evidence.",{"label":558,"description":559},"4. Preserve provenance","Carry source identity, version, timestamp, locator, transformation history and responsibility metadata.",{"label":561,"description":562},"5. Build model context","Supply the relevant evidence to the model without discarding authority and applicability metadata.",{"label":564,"description":565},"6. Generate or compute","The model may summarize, compare, reason or transform the evidence, but it does not inherit source authority merely by processing it.",{"label":567,"description":568},"7. Validate the claim","Check that the answer is supported by the right source and remains inside its scope and validity boundary.",{"label":570,"description":571},"8. Preserve contradictions","If authoritative or relevant sources disagree, expose the conflict rather than fabricating false certainty.","Authority-aware AI answer path","auto","processFlow",{},{"id":577,"data":578,"type":42,"tunes":580},"h-registry",{"text":579,"level":246},"Authority should be explicit, not inferred from similarity",{},{"id":582,"data":583,"type":218,"tunes":585},"p-registry-1",{"text":584},"One robust implementation pattern is an authority registry or equivalent policy layer that maps claim classes to authoritative source classes. The implementation can be code, metadata, configuration or domain rules; the important property is that authority is deliberate.",{},{"id":587,"data":588,"type":318,"tunes":618},"registry-table",{"content":589,"stretched":43,"withHeadings":14},[590,594,598,602,606,610,614],[591,592,593],"Claim class","Authority rule","Fallback behavior",[595,596,597],"Current account state","Read live account service \u002F system of record","If unavailable, report that current state cannot be verified.",[599,600,601],"Product documentation","Current approved documentation version","Older version may be shown only with version warning.",[603,604,605],"Implemented software behavior","Relevant deployed release \u002F source artifact","Documentation alone cannot prove deployed behavior.",[607,608,609],"Internal policy","Approved policy repository and active version","Drafts are supporting material, not current authority.",[611,612,613],"External technical standard","Official standards body publication for relevant version","Secondary explanations can clarify but not override the specification.",[615,616,617],"Research claim","Evidence policy appropriate to the domain","Preserve conflicting evidence and confidence rather than force one source.",{},{"id":620,"data":621,"type":42,"tunes":623},"h-retrieval",{"text":622,"level":246},"Retrieval should use authority as a ranking constraint",{},{"id":625,"data":626,"type":218,"tunes":628},"p-retrieval-1",{"text":627},"Semantic relevance answers “Which candidate looks related to this query?” Authority answers “Which candidate is allowed to establish this fact?” A production retrieval system often needs both.",{},{"id":630,"data":631,"type":218,"tunes":633},"p-retrieval-2",{"text":632},"A useful sequence is to first constrain the candidate space by identity, tenant, source class, status, version or date, then rank relevant evidence inside the permitted space. If relevance is calculated before critical authorization or authority filters, the pipeline can return a convincing but invalid result.",{},{"id":635,"data":636,"type":226,"tunes":640},"relevance-authority",{"body":637,"title":638,"variant":639},"A search engine can rank a stale summary above the current primary source. A language model can prefer the better-written explanation over the official record. Neither behavior changes which source owns the fact.","Highest similarity is not highest authority","warning",{},{"id":642,"data":643,"type":42,"tunes":645},"h-freshness",{"text":644,"level":246},"Freshness is part of authority",{},{"id":647,"data":648,"type":218,"tunes":650},"p-freshness-1",{"text":649},"Many Source-of-Truth failures are actually time failures. The correct source was known, but the system used an old snapshot, stale embedding, cached API response or superseded document.",{},{"id":652,"data":653,"type":218,"tunes":655},"p-freshness-2",{"text":654},"An authority rule should therefore include invalidation or refresh semantics where the fact can change. “CRM is authoritative” is incomplete when the application reads a week-old replicated export.",{},{"id":657,"data":658,"type":42,"tunes":660},"h-derivation",{"text":659,"level":246},"Derived values need a trace back to authoritative inputs",{},{"id":662,"data":663,"type":218,"tunes":665},"p-derivation-1",{"text":664},"Some important facts are not stored directly. They are computed from authoritative inputs: a risk score, account total, eligibility status or aggregate metric.",{},{"id":667,"data":668,"type":218,"tunes":670},"p-derivation-2",{"text":669},"For derived values, Source-of-Truth architecture should preserve the input authorities, transformation or calculation version and execution time. W3C PROV's distinction between entities, activities and derivations is useful here because it models how one entity was produced from others.",{},{"id":672,"data":673,"type":226,"tunes":676},"derived-rule",{"body":674,"title":675,"variant":274},"A calculated value is only as current and authoritative as its inputs, transformation and validity conditions. Store the lineage needed to recompute or audit it.","Derived truth is conditional",{},{"id":678,"data":679,"type":42,"tunes":681},"h-conflict",{"text":680,"level":246},"What happens when authoritative sources disagree?",{},{"id":683,"data":684,"type":218,"tunes":686},"p-conflict-1",{"text":685},"Conflicts are not edge cases in serious knowledge systems. A signed contract may disagree with a CRM field. Production behavior may disagree with documentation. Two primary historical sources may contradict each other. A current policy can conflict with an outdated local copy.",{},{"id":688,"data":689,"type":218,"tunes":691},"p-conflict-2",{"text":690},"The system needs a resolution policy appropriate to the domain. Sometimes one authority clearly outranks the other. Sometimes the newer version supersedes the old one. Sometimes an expert or business owner must adjudicate. And sometimes the correct result is simply: the evidence is unresolved.",{},{"id":693,"data":694,"type":318,"tunes":717},"conflict-table",{"content":695,"stretched":43,"withHeadings":14},[696,699,702,705,708,711,714],[697,698],"Conflict type","Typical handling",[700,701],"Current vs superseded version","Use current version for present state; retain older version as historical evidence.",[703,704],"System of record vs stale replica","Use system of record; flag replication freshness issue.",[706,707],"Contract vs CRM transcription","Executed contract governs contractual wording; CRM discrepancy becomes a correction task.",[709,710],"Documentation vs deployed behavior","Distinguish intended behavior from observed\u002Fdeployed behavior; do not silently merge them.",[712,713],"Two credible primary sources","Preserve both, assess provenance and scope, and represent unresolved disagreement if no governing authority exists.",[715,716],"User memory vs current user setting","Use current explicit setting; mark memory as superseded where appropriate.",{},{"id":719,"data":720,"type":42,"tunes":722},"h-web",{"text":721,"level":246},"Web search is discovery, not automatically evidence",{},{"id":724,"data":725,"type":218,"tunes":727},"p-web-1",{"text":726},"Search engines are excellent discovery systems. Search snippets, result ranking and generated summaries are not automatically primary evidence.",{},{"id":729,"data":730,"type":218,"tunes":732},"p-web-2",{"text":731},"For claims that require authority, the search result should lead to the original publication, official record, source document, dataset or other appropriate artifact. The result page helps locate the source; it does not inherit the source's authority.",{},{"id":734,"data":735,"type":42,"tunes":737},"h-ai",{"text":736,"level":246},"The language model should not decide authority by itself",{},{"id":739,"data":740,"type":218,"tunes":742},"p-ai-1",{"text":741},"A model can help classify a question, extract claims or compare evidence, but authority should not depend only on the model's preference. Models optimize generation from context; they do not possess a guaranteed domain-specific registry of which database, document or organization owns each fact.",{},{"id":744,"data":745,"type":218,"tunes":747},"p-ai-2",{"text":746},"This is why application architecture should encode critical authority rules deterministically where practical. The model may reason within the boundary, but the boundary itself should not be recreated from scratch for every prompt.",{},{"id":749,"data":750,"type":42,"tunes":752},"h-observability",{"text":751,"level":246},"Authority must survive the execution trace",{},{"id":754,"data":755,"type":218,"tunes":757},"p-observability-1",{"text":756},"If a production answer is important enough to audit, the trace should make it possible to reconstruct which sources were consulted, which version was used, which passage or record supported the claim, which transformations occurred and whether conflicting evidence was available.",{},{"id":759,"data":760,"type":218,"tunes":762},"p-observability-2",{"text":761},"This aligns with the broader provenance principle in W3C PROV and with NIST AI RMF Playbook guidance to document sources, origins, transformations, dependencies, constraints and metadata.",{},{"id":764,"data":765,"type":42,"tunes":767},"h-implementation",{"text":766,"level":246},"Original implementation evidence: Source of Truth Research Engine",{},{"id":769,"data":770,"type":226,"tunes":773},"implementation-note",{"body":771,"title":772,"variant":233},"The Source of Truth Research Engine is my own implementation evidence for an evidence-first architecture. It demonstrates one concrete way to separate discovery, source acquisition, provenance, claims, evidence classes, contradictions and conclusions. It is an implementation pattern, not a universal industry standard.","Original implementation evidence",{},{"id":775,"data":776,"type":218,"tunes":778},"p-impl-1",{"text":777},"The engine is designed around a traceable pipeline rather than direct AI summarization: research task → search → original source or digital artifact → local snapshot → SHA-256 → source ID → claim → evidence class → relation or contradiction → interpretation → conclusion.",{},{"id":780,"data":781,"type":218,"tunes":783},"p-impl-2",{"text":782},"Its shared evidence core stores Sources, Artifacts, provenance, Claims, Relations, Contradictions, a Reference Model and an audit trail. Different research modes can share that core while applying different domain methodologies.",{},{"id":785,"data":786,"type":218,"tunes":788},"p-impl-3",{"text":787},"The architecture deliberately separates discovery from evidence. Search snippets are not treated as evidence, filenames are not treated as content, AI summaries are not treated as primary sources, and semantic similarity is only a discovery signal until a result is traced back to a concrete source and locator.",{},{"id":790,"data":791,"type":218,"tunes":793},"p-impl-4",{"text":792},"Original files are preserved and local bytes receive SHA-256 identifiers. Contradictions and rejected hypotheses are not silently deleted. New evidence is allowed to change the current reference model while the prior evidence path remains auditable.",{},{"id":795,"data":796,"type":318,"tunes":825},"implementation-table",{"content":797,"stretched":43,"withHeadings":14},[798,801,804,807,810,813,816,819,822],[799,800],"Implemented rule","Why it matters for Source-of-Truth architecture",[802,803],"Search ≠ evidence","Discovery ranking cannot silently become authority.",[805,806],"Filename ≠ content","Metadata clues cannot substitute for reading the actual artifact.",[808,809],"Local snapshot + SHA-256","Evidence can be tied to exact bytes rather than a mutable remote label.",[811,812],"Source ID + exact locator","Claims can be traced back to the concrete evidence location.",[814,815],"Claim\u002Fevidence separation","The assertion is not confused with the material supporting it.",[817,818],"Contradictions preserved","The system can represent unresolved disagreement rather than overwrite history.",[820,821],"Semantic similarity is discovery only","Retrieval relevance is explicitly separated from evidentiary authority.",[823,824],"New evidence may update the model","Source-of-Truth state is versioned and revisable rather than treated as immutable dogma.",{},{"id":827,"data":828,"type":42,"tunes":830},"h-document-engine",{"text":829,"level":246},"Aaasaasa Document & Knowledge Engine: applying the same boundary to enterprise documents",{},{"id":832,"data":833,"type":218,"tunes":835},"p-doc-1",{"text":834},"The Aaasaasa Document & Knowledge Engine concept extends the same design principle to enterprise documentation: users should be able to search documents, ask source-grounded questions and review collections against explicit criteria while preserving the distinction between what a document states and what the system infers.",{},{"id":837,"data":838,"type":218,"tunes":840},"p-doc-2",{"text":839},"The important architecture rule is that a universal retrieval core does not make every collection equally authoritative. Contract documents, maintenance records, financial documents and research material need different authority, validation and coverage rules even when they share ingestion and search infrastructure.",{},{"id":842,"data":843,"type":42,"tunes":845},"h-failures",{"text":844,"level":246},"Common Source-of-Truth failure modes",{},{"id":847,"data":848,"type":318,"tunes":889},"failures-table",{"content":849,"stretched":43,"withHeadings":14},[850,853,856,859,862,865,868,871,874,877,880,883,886],[851,852],"Failure mode","What goes wrong",[854,855],"The model is treated as the source of truth","Parametric knowledge can be stale, incomplete, unverifiable or outside the application's authoritative scope.",[857,858],"Top retrieval result wins automatically","Similarity is mistaken for authority.",[860,861],"Vector database becomes authoritative","Derived index records lose the identity and version of the original source.",[863,864],"Everything is copied into one knowledge base","Copies obscure ownership, freshness and correction paths.",[866,867],"Memory is reused as current state","Old observations silently override the current system of record.",[869,870],"No version metadata","The right document is used for the wrong time period.",[872,873],"No source locator","A citation exists but the supporting passage or record cannot be verified.",[875,876],"Conflicts are overwritten","The system appears consistent by destroying evidence of disagreement.",[878,879],"Generated summaries replace originals","A lossy transformation becomes the apparent authority.",[881,882],"Authority is global instead of claim-specific","One source is trusted beyond the domain or fact class it actually owns.",[884,885],"Web snippet is treated as evidence","Discovery metadata replaces the original publication.",[887,888],"Authoritative data is wrong but exceptions are hidden","Operational defects become invisible and cannot be corrected transparently.",{},{"id":891,"data":892,"type":42,"tunes":894},"h-decision",{"text":893,"level":246},"A practical Source-of-Truth decision framework",{},{"id":896,"data":897,"type":574,"tunes":927},"decision-flow",{"steps":898,"title":926,"orientation":573},[899,902,905,908,911,914,917,920,923],{"label":900,"description":901},"1. State the claim precisely","Separate current state, historical state, policy, interpretation, prediction and derived calculation.",{"label":903,"description":904},"2. Identify the authority owner","Determine the system, document, institution, person or evidence class responsible for that claim type.",{"label":906,"description":907},"3. Define scope","Specify tenant, jurisdiction, product, environment, user, document set or other applicability boundary.",{"label":909,"description":910},"4. Define time and version","Determine whether the claim requires current state, a historical snapshot or a specific standard\u002Frelease version.",{"label":912,"description":913},"5. Preserve provenance","Record source identity, origin, locator, transformations and responsible agents or processes.",{"label":915,"description":916},"6. Define retrieval\u002Faccess path","Make sure the application can actually obtain the authoritative information under the correct identity and permissions.",{"label":918,"description":919},"7. Define conflict policy","Decide precedence, supersession, adjudication or explicit unresolved-state behavior.",{"label":921,"description":922},"8. Define invalidation","Specify when cached, indexed, remembered or derived representations must be refreshed.",{"label":924,"description":925},"9. Validate the answer path","Verify that important generated claims can be traced to the intended authority, not merely to a plausible source.","How to decide what should define a claim",{},{"id":929,"data":930,"type":42,"tunes":932},"h-checklist",{"text":931,"level":246},"Source-of-Truth architecture checklist",{},{"id":934,"data":935,"type":318,"tunes":975},"checklist-table",{"content":936,"stretched":43,"withHeadings":14},[937,939,942,945,948,951,954,957,960,963,966,969,972],[356,938],"Expected answer",[940,941],"What exact fact or state is being established?","A claim precise enough to assign authority.",[943,944],"Who or what owns that fact?","Named authoritative system, source class or adjudication rule.",[946,947],"Is the authority current for this scope?","Tenant, jurisdiction, environment, user or domain boundary is explicit.",[949,950],"Is the version\u002Ftime correct?","Current, historical or version-specific applicability is known.",[952,953],"Can the source be verified?","Stable identifier, locator or record reference exists.",[955,956],"Is provenance preserved?","Origin, transformation and responsibility metadata survive ingestion and retrieval.",[958,959],"Can retrieval return non-authoritative material?","If yes, filters or validation distinguish relevance from authority.",[961,962],"Can the source change?","Refresh, invalidation or supersession rules exist.",[964,965],"Can sources disagree?","Conflict and adjudication behavior is explicit.",[967,968],"Can memory become stale?","Volatile state is re-read from the current authority before consequential use.",[970,971],"Can a derived answer be reproduced?","Inputs, transformation version and execution conditions are traceable.",[973,974],"Can an auditor reconstruct the answer?","Execution evidence preserves the source path for important claims.",{},{"id":977,"data":978,"type":42,"tunes":980},"h-misconceptions",{"text":979,"level":246},"Common misconceptions",{},{"id":982,"data":983,"type":318,"tunes":1012},"misconceptions-table",{"content":984,"stretched":43,"withHeadings":14},[985,988,991,994,997,1000,1003,1006,1009],[986,987],"Misconception","Correction",[989,990],"“Source of Truth means one database.”","One database can be authoritative for one domain; complex systems usually have multiple fact-specific authorities.",[992,993],"“The newest document is automatically authoritative.”","Recency helps only when the newer artifact is approved and actually supersedes the older one.",[995,996],"“RAG solves truth.”","RAG solves retrieval. Authority, provenance, evidence quality and validity remain separate problems.",[998,999],"“A citation proves the answer.”","The cited source must actually support the claim, have the right authority and apply to the current scope.",[1001,1002],"“Provenance tells us what is true.”","Provenance tells us origin and derivation; authority and correctness still require domain rules and evaluation.",[1004,1005],"“The system of record is always correct.”","It is authoritative for the operational record, but data-quality defects can still exist and require visible correction.",[1007,1008],"“If several sources agree, the claim is authoritative.”","Agreement increases evidence but does not necessarily establish ownership or applicability.",[1010,1011],"“AI memory can replace repeated reads.”","Only for information whose staleness risk is acceptable; volatile or consequential state should be refreshed from authority.",{},{"id":1014,"data":1015,"type":42,"tunes":1017},"h-edge",{"text":1016,"level":246},"Edge cases",{},{"id":1019,"data":1020,"type":218,"tunes":1022},"p-edge-1",{"text":1021},"Some questions are interpretive rather than factual. “Which architecture is best?” has no single Source of Truth. The system can retrieve authoritative constraints and evidence, but the final judgment is an inference that should expose assumptions and trade-offs.",{},{"id":1024,"data":1025,"type":218,"tunes":1027},"p-edge-2",{"text":1026},"Some domains use distributed authority. A scientific conclusion can depend on multiple studies, datasets and replications. A historical conclusion can depend on conflicting primary and secondary evidence. The architecture should represent evidence structure rather than invent a central database that supposedly owns truth.",{},{"id":1029,"data":1030,"type":218,"tunes":1032},"p-edge-3",{"text":1031},"A user can also be the authority for subjective personal information: preferences, goals, chosen settings or explicit instructions. Even then, newer explicit input can supersede older memory.",{},{"id":1034,"data":1035,"type":218,"tunes":1037},"p-edge-4",{"text":1036},"External events can invalidate previously authoritative data. A price feed, inventory system or security policy may have been correct when captured but no longer valid. Snapshot provenance preserves what was true then; it does not make the snapshot current forever.",{},{"id":1039,"data":1040,"type":42,"tunes":1042},"h-limit",{"text":1041,"level":246},"Limitations",{},{"id":1044,"data":1045,"type":218,"tunes":1047},"p-limit-1",{"text":1046},"Source-of-Truth architecture cannot guarantee that an authoritative source is factually correct. It provides accountability, provenance and deterministic ownership boundaries; data-quality and domain-verification processes remain necessary.",{},{"id":1049,"data":1050,"type":218,"tunes":1052},"p-limit-2",{"text":1051},"Authority can also be contested. Different institutions can legitimately claim authority in different jurisdictions or methodologies. In those situations the system should expose the authority model and disagreement rather than hide it behind a universal “truth score.”",{},{"id":1054,"data":1055,"type":218,"tunes":1057},"p-limit-3",{"text":1056},"Finally, authority rules require maintenance. Systems, owners, policies, versions and regulations change. A stale authority registry can be as dangerous as no registry at all.",{},{"id":1059,"data":1060,"type":42,"tunes":1062},"h-change",{"text":1061,"level":246},"What would change this answer?",{},{"id":1064,"data":1065,"type":218,"tunes":1067},"p-change-1",{"text":1066},"The specific authority mapping changes with the domain. Banking, healthcare, software delivery, scientific research and historical analysis have different systems of record, evidentiary rules and regulatory obligations.",{},{"id":1069,"data":1070,"type":218,"tunes":1072},"p-change-2",{"text":1071},"The implementation also changes with architecture. A small application can encode authority directly in service calls. A larger platform may need registries, source metadata, policy engines, lineage systems or data contracts. The core principle remains the same: do not let retrieval order or model preference silently decide what counts as authoritative.",{},{"id":1074,"data":1075,"type":42,"tunes":1077},"h-related",{"text":1076,"level":246},"Related canonical knowledge",{},{"id":1079,"data":1080,"type":218,"tunes":1082},"p-related-1",{"text":1081},"Source-of-Truth architecture is a prerequisite for later retrieval and governance concepts because retrieval quality alone cannot determine whether evidence is allowed to define the answer.",{},{"id":1084,"data":1085,"type":1090,"tunes":1091},"ref-rag",{"url":1086,"title":1087,"excerpt":1088,"ctaLabel":1089},"https:\u002F\u002Fstajic.de\u002Fblog\u002Fwhat-is-rag-the-simplest-explanation-of-how-it-works","What Is RAG? The Simplest Explanation of How It Works","RAG retrieves external knowledge for a model. This foundation explains why retrieval and authoritative truth are separate responsibilities.","Read the RAG foundation","referralArticle",{},{"id":1093,"data":1094,"type":218,"tunes":1096},"p-related-2",{"text":1095},"Memory is another adjacent concept. A reliable agent separates remembered information from current authoritative application state.",{},{"id":1098,"data":1099,"type":1090,"tunes":1104},"ref-memory",{"url":1100,"title":1101,"excerpt":1102,"ctaLabel":1103},"https:\u002F\u002Fstajic.de\u002Fblog\u002Fai-agent-memory-is-not-rag-how-to-separate-memory-retrieval-state-and-context","AI Agent Memory Is Not RAG: How to Separate Memory, Retrieval, State and Context","A four-layer architecture separating persistent memory, authoritative state, retrieval and the context actually supplied to the model.","Read the memory architecture article",{},{"id":1106,"data":1107,"type":218,"tunes":1109},"p-related-3",{"text":1108},"Authority also connects directly to answer validity. Even an authoritative source supports only claims inside its version, date, scope and evidence boundary.",{},{"id":1111,"data":1112,"type":1090,"tunes":1117},"ref-avb",{"url":1113,"title":1114,"excerpt":1115,"ctaLabel":1116},"https:\u002F\u002Fstajic.de\u002Fblog\u002Fthe-answer-validity-boundary-the-missing-layer-between-relevance-and-reliable-ai-answers","The Answer Validity Boundary: The Missing Layer Between Relevance and Reliable AI Answers","A framework for making explicit where an AI answer remains supported by evidence and which changed conditions invalidate that support.","Read the Answer Validity Boundary",{},{"id":1119,"data":1120,"type":42,"tunes":1122},"h-faq",{"text":1121,"level":246},"Frequently asked questions",{},{"id":1124,"data":1125,"type":1124,"tunes":1160},"faq",{"items":1126,"title":1159},[1127,1131,1135,1139,1143,1147,1151,1155],{"id":1128,"answer":1129,"question":1130},"faq1","It is the authoritative source or authority rule that determines which source is allowed to establish a specific fact, state or rule for a defined scope, version and time.","What is a Source of Truth in an AI system?",{"id":1132,"answer":1133,"question":1134},"faq2","Normally no. A language model can generate, summarize and reason, but its parametric knowledge is not automatically authoritative for current application state, company policy, a specific document version or a regulated domain fact.","Is the language model a Source of Truth?",{"id":1136,"answer":1137,"question":1138},"faq3","Not automatically. A vector database is usually an index or retrieval store. It should preserve references to the authoritative original source and version rather than silently replacing them.","Is a vector database the Source of Truth for RAG?",{"id":1140,"answer":1141,"question":1142},"faq4","Provenance describes where data came from, how it was produced or transformed and who or what was involved. Source-of-Truth rules determine whether that source has authority for the specific claim.","What is the difference between provenance and Source of Truth?",{"id":1144,"answer":1145,"question":1146},"faq5","Yes. In complex systems this is normal because different facts belong to different authoritative systems or source classes.","Can an AI system have multiple Sources of Truth?",{"id":1148,"answer":1149,"question":1150},"faq6","The system needs a domain-specific conflict rule: precedence, version supersession, expert adjudication or an explicit unresolved state. It should not silently choose the source the model prefers.","What happens when two authoritative sources disagree?",{"id":1152,"answer":1153,"question":1154},"faq7","No. RAG retrieves candidates. Authority-aware metadata, filters, source policy and validation are needed to ensure that important claims use the correct source.","Does RAG guarantee that an AI answer uses the Source of Truth?",{"id":1156,"answer":1157,"question":1158},"faq8","Yes. Authority and correctness are different properties. An authoritative system can contain a data-quality defect, which should be corrected transparently rather than hidden by substituting an unofficial source.","Can the Source of Truth be wrong?","Source of Truth in AI systems",{},{"id":1162,"data":1163,"type":42,"tunes":1165},"h-glossary",{"text":1164,"level":246},"Glossary",{},{"id":1167,"data":1168,"type":1167,"tunes":1210},"glossary",{"title":1169,"entries":1170},"Key Source-of-Truth terms",[1171,1175,1179,1183,1187,1190,1194,1198,1202,1206],{"term":1172,"anchor":1173,"definition":1174},"Source of Truth","source-of-truth","The authoritative source or rule permitted to establish a particular fact, state or rule for a defined scope, version and time.",{"term":1176,"anchor":1177,"definition":1178},"System of record","system-of-record","The authoritative operational system responsible for a defined class of records or current business state.",{"term":1180,"anchor":1181,"definition":1182},"Provenance","provenance","Information describing the origin, derivation, transformations, responsible agents and history of data or another entity.",{"term":1184,"anchor":1185,"definition":1186},"Evidence","evidence","Information or an artifact that supports, contradicts or constrains a claim.",{"term":1188,"anchor":327,"definition":1189},"Authority","The application or domain rule determining which source is entitled to define a specific claim.",{"term":1191,"anchor":1192,"definition":1193},"Freshness","freshness","Whether a representation remains current enough for the claim or operation in which it is used.",{"term":1195,"anchor":1196,"definition":1197},"Supersession","supersession","The explicit replacement of an older authoritative version by a newer one while preserving historical traceability.",{"term":1199,"anchor":1200,"definition":1201},"Ground truth","ground-truth","A reference answer, label or outcome used to evaluate a system; it is an evaluation construct rather than automatically the application's Source of Truth.",{"term":1203,"anchor":1204,"definition":1205},"Lineage","lineage","The trace of how data or derived values flow and transform across sources and processing steps.",{"term":1207,"anchor":1208,"definition":1209},"Validity boundary","validity-boundary","The conditions of scope, time, version, evidence and assumptions inside which a claim remains supported.",{},{"id":1212,"data":1213,"type":42,"tunes":1215},"h-conclusion",{"text":1214,"level":246},"Conclusion",{},{"id":1217,"data":1218,"type":218,"tunes":1220},"p-conclusion-1",{"text":1219},"Reliable AI does not come from giving the model more information. It comes from knowing which information is allowed to define the claim, preserving where that information came from, retrieving the correct version and keeping the final answer inside the source's scope.",{},{"id":1222,"data":1223,"type":218,"tunes":1225},"p-conclusion-2",{"text":1224},"That is why Source of Truth, provenance, retrieval, memory and context must remain separate concepts. The Source of Truth defines authority. Provenance explains origin. Retrieval finds candidates. Memory preserves selected past information. Context is what the model sees. Generation turns those inputs into an output.",{},{"id":1227,"data":1228,"type":218,"tunes":1230},"p-conclusion-3",{"text":1229},"When those layers remain explicit, an AI system can do more than sound plausible: important claims can be traced back to the source that actually had the right to establish them.",{},{"id":1232,"data":1233,"type":42,"tunes":1235},"h-sources",{"text":1234,"level":246},"Primary sources and implementation evidence",{},{"id":1237,"data":1238,"type":218,"tunes":1240},"p-sources-note",{"text":1239},"The external sources below support provenance and AI risk-management claims. The Source of Truth Research Engine section is original implementation evidence and is explicitly presented as one implementation pattern rather than a universal standard.",{},{"id":1242,"data":1243,"type":1249,"tunes":1250},"src-w3c-prov",{"link":1244,"meta":1245},"https:\u002F\u002Fwww.w3.org\u002FTR\u002Fprov-dm\u002F",{"image":1246,"title":1247,"description":1248},{"url":304},"W3C PROV-DM — The PROV Data Model","W3C Recommendation defining a domain-agnostic provenance model around entities, activities, agents, derivations and responsibility.","linkTool",{},{"id":1252,"data":1253,"type":1249,"tunes":1259},"src-w3c-publications",{"link":1254,"meta":1255},"https:\u002F\u002Fwww.w3.org\u002Fgroups\u002Fwg\u002Fprov\u002Fpublications\u002F",{"image":1256,"title":1257,"description":1258},{"url":304},"W3C Provenance Working Group — Publications","Official index of W3C PROV Recommendations and related specifications for provenance interchange and constraints.",{},{"id":1261,"data":1262,"type":1249,"tunes":1268},"src-nist-rmf",{"link":1263,"meta":1264},"https:\u002F\u002Fwww.nist.gov\u002Fitl\u002Fai-risk-management-framework",{"image":1265,"title":1266,"description":1267},{"url":304},"NIST AI Risk Management Framework","NIST's voluntary framework for incorporating trustworthiness and risk-management considerations across the AI lifecycle; AI RMF 1.0 is currently being revised.",{},{"id":1270,"data":1271,"type":1249,"tunes":1277},"src-nist-playbook",{"link":1272,"meta":1273},"https:\u002F\u002Fairc.nist.gov\u002Fairmf-resources\u002Fplaybook\u002F",{"image":1274,"title":1275,"description":1276},{"url":304},"NIST AI RMF Playbook","Operational guidance aligned to the AI RMF, including documentation practices for data provenance, sources, origins, transformations, dependencies, constraints and metadata.",{},{"id":1279,"data":1280,"type":1249,"tunes":1286},"src-nist-measure",{"link":1281,"meta":1282},"https:\u002F\u002Fairc.nist.gov\u002Fairmf-resources\u002Fplaybook\u002Fmeasure\u002F",{"image":1283,"title":1284,"description":1285},{"url":304},"NIST AI RMF Playbook — Measure","Guidance on documenting measurement, data provenance and contextual interpretation of AI system outputs.",{},{"id":1288,"data":1289,"type":1249,"tunes":1295},"src-nist-genai",{"link":1290,"meta":1291},"https:\u002F\u002Fwww.nist.gov\u002Fpublications\u002Fartificial-intelligence-risk-management-framework-generative-artificial-intelligence",{"image":1292,"title":1293,"description":1294},{"url":304},"NIST AI 600-1 — Generative AI Profile","NIST generative-AI profile, including provenance and information-integrity considerations for generative AI systems.",{},"2.31.6","A Source of Truth defines which source is authoritative for a specific fact or state. Learn how it differs from RAG, provenance, memory, context, vector databases and systems of record.","\u002Fuploads\u002F2026\u002F10\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from-1791479103235-6bq9em.webp","source-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from-1791479103235-6bq9em","PUBLISHED","2026-10-08T13:02:00.000Z","2026-10-08T17:02:49.770Z","2026-10-08T17:11:41.743Z",{"en":1305,"de":1306,"sr":1307,"es":1308,"fr":1309,"it":1310,"ru":1311,"zh":1312},"\u002Fblog\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from","\u002Fde\u002Fblog\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from","\u002Fsr\u002Fblog\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from","\u002Fes\u002Fblog\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from","\u002Ffr\u002Fblog\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from","\u002Fit\u002Fblog\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from","\u002Fru\u002Fblog\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from","\u002Fzh\u002Fblog\u002Fsource-of-truth-in-ai-systems-where-reliable-knowledge-actually-comes-from",[1314,1318,1322],{"id":1315,"name":1316,"slug":1317},65,"Topical Authority System","topical-authority",{"id":1319,"name":1320,"slug":1321},57,"Data Boundaries","data-boundaries",{"id":1323,"name":1324,"slug":1325},84,"Policy & Data Boundaries","policy-and-data",{"id":1327,"login":1328,"email":1329,"displayName":1330},"20","rooth8233","aleksandar@stajic.de","Aleksandar Stajić",[1332],{"lang":7,"title":208,"content":210,"contentJson":1333,"excerpt":1297},{"time":212,"blocks":1334,"version":1296},[1335,1338,1341,1344,1347,1350,1353,1356,1359,1362,1365,1368,1371,1374,1377,1393,1396,1399,1402,1405,1417,1420,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450,1453,1456,1459,1462,1465,1468,1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501,1504,1507,1510,1522,1525,1528,1539,1542,1545,1548,1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581,1592,1595,1598,1601,1604,1607,1610,1613,1616,1619,1622,1625,1628,1631,1634,1637,1650,1653,1656,1659,1662,1679,1682,1695,1698,1715,1718,1731,1734,1737,1740,1743,1746,1749,1752,1755,1758,1761,1764,1767,1770,1773,1776,1779,1782,1785,1788,1791,1803,1806,1820,1823,1826,1829,1832,1835,1838,1843,1848,1853,1858,1863],{"id":215,"data":1336,"type":218,"tunes":1337},{"text":217},{},{"id":221,"data":1339,"type":226,"tunes":1340},{"body":223,"title":224,"variant":225},{},{"id":229,"data":1342,"type":226,"tunes":1343},{"body":231,"title":232,"variant":233},{},{"id":236,"data":1345,"type":226,"tunes":1346},{"body":238,"title":239,"variant":233},{},{"id":242,"data":1348,"type":247,"tunes":1349},{"title":244,"maxLevel":245,"minLevel":246},{},{"id":250,"data":1351,"type":42,"tunes":1352},{"text":252,"level":246},{},{"id":255,"data":1354,"type":218,"tunes":1355},{"text":257},{},{"id":260,"data":1357,"type":218,"tunes":1358},{"text":262},{},{"id":265,"data":1360,"type":218,"tunes":1361},{"text":267},{},{"id":270,"data":1363,"type":226,"tunes":1364},{"body":272,"title":273,"variant":274},{},{"id":277,"data":1366,"type":42,"tunes":1367},{"text":279,"level":246},{},{"id":282,"data":1369,"type":218,"tunes":1370},{"text":284},{},{"id":287,"data":1372,"type":218,"tunes":1373},{"text":289},{},{"id":292,"data":1375,"type":218,"tunes":1376},{"text":294},{},{"id":297,"data":1378,"type":329,"tunes":1392},{"rows":1379,"title":317,"layout":318,"columns":1388},[1380,1382,1384,1386],{"id":301,"label":302,"values":1381},[304,304,304],{"id":306,"label":307,"values":1383},[304,304,304],{"id":310,"label":311,"values":1385},[304,304,304],{"id":314,"label":315,"values":1387},[304,304,304],[1389,1390,1391],{"id":321,"label":322},{"id":324,"label":325},{"id":327,"label":328},{},{"id":332,"data":1394,"type":42,"tunes":1395},{"text":334,"level":246},{},{"id":337,"data":1397,"type":218,"tunes":1398},{"text":339},{},{"id":342,"data":1400,"type":218,"tunes":1401},{"text":344},{},{"id":347,"data":1403,"type":42,"tunes":1404},{"text":349,"level":246},{},{"id":352,"data":1406,"type":318,"tunes":1416},{"content":1407,"stretched":43,"withHeadings":14},[1408,1409,1410,1411,1412,1413,1414,1415],[356,357,358],[360,361,362],[364,365,366],[368,369,370],[372,373,374],[376,377,378],[380,381,382],[384,385,386],{},{"id":389,"data":1418,"type":218,"tunes":1419},{"text":391},{},{"id":394,"data":1421,"type":42,"tunes":1422},{"text":396,"level":246},{},{"id":399,"data":1424,"type":42,"tunes":1425},{"text":401,"level":245},{},{"id":404,"data":1427,"type":218,"tunes":1428},{"text":406},{},{"id":409,"data":1430,"type":218,"tunes":1431},{"text":411},{},{"id":414,"data":1433,"type":42,"tunes":1434},{"text":416,"level":245},{},{"id":419,"data":1436,"type":218,"tunes":1437},{"text":421},{},{"id":424,"data":1439,"type":218,"tunes":1440},{"text":426},{},{"id":429,"data":1442,"type":42,"tunes":1443},{"text":431,"level":245},{},{"id":434,"data":1445,"type":218,"tunes":1446},{"text":436},{},{"id":439,"data":1448,"type":218,"tunes":1449},{"text":441},{},{"id":444,"data":1451,"type":42,"tunes":1452},{"text":446,"level":245},{},{"id":449,"data":1454,"type":218,"tunes":1455},{"text":451},{},{"id":454,"data":1457,"type":218,"tunes":1458},{"text":456},{},{"id":459,"data":1460,"type":42,"tunes":1461},{"text":461,"level":245},{},{"id":464,"data":1463,"type":218,"tunes":1464},{"text":466},{},{"id":469,"data":1466,"type":218,"tunes":1467},{"text":471},{},{"id":474,"data":1469,"type":42,"tunes":1470},{"text":476,"level":245},{},{"id":479,"data":1472,"type":218,"tunes":1473},{"text":481},{},{"id":484,"data":1475,"type":218,"tunes":1476},{"text":486},{},{"id":489,"data":1478,"type":42,"tunes":1479},{"text":491,"level":245},{},{"id":494,"data":1481,"type":218,"tunes":1482},{"text":496},{},{"id":499,"data":1484,"type":218,"tunes":1485},{"text":501},{},{"id":504,"data":1487,"type":42,"tunes":1488},{"text":506,"level":245},{},{"id":509,"data":1490,"type":218,"tunes":1491},{"text":511},{},{"id":514,"data":1493,"type":218,"tunes":1494},{"text":516},{},{"id":519,"data":1496,"type":42,"tunes":1497},{"text":521,"level":245},{},{"id":524,"data":1499,"type":218,"tunes":1500},{"text":526},{},{"id":529,"data":1502,"type":218,"tunes":1503},{"text":531},{},{"id":534,"data":1505,"type":42,"tunes":1506},{"text":536,"level":246},{},{"id":539,"data":1508,"type":226,"tunes":1509},{"body":541,"title":542,"variant":233},{},{"id":545,"data":1511,"type":574,"tunes":1521},{"steps":1512,"title":572,"orientation":573},[1513,1514,1515,1516,1517,1518,1519,1520],{"label":549,"description":550},{"label":552,"description":553},{"label":555,"description":556},{"label":558,"description":559},{"label":561,"description":562},{"label":564,"description":565},{"label":567,"description":568},{"label":570,"description":571},{},{"id":577,"data":1523,"type":42,"tunes":1524},{"text":579,"level":246},{},{"id":582,"data":1526,"type":218,"tunes":1527},{"text":584},{},{"id":587,"data":1529,"type":318,"tunes":1538},{"content":1530,"stretched":43,"withHeadings":14},[1531,1532,1533,1534,1535,1536,1537],[591,592,593],[595,596,597],[599,600,601],[603,604,605],[607,608,609],[611,612,613],[615,616,617],{},{"id":620,"data":1540,"type":42,"tunes":1541},{"text":622,"level":246},{},{"id":625,"data":1543,"type":218,"tunes":1544},{"text":627},{},{"id":630,"data":1546,"type":218,"tunes":1547},{"text":632},{},{"id":635,"data":1549,"type":226,"tunes":1550},{"body":637,"title":638,"variant":639},{},{"id":642,"data":1552,"type":42,"tunes":1553},{"text":644,"level":246},{},{"id":647,"data":1555,"type":218,"tunes":1556},{"text":649},{},{"id":652,"data":1558,"type":218,"tunes":1559},{"text":654},{},{"id":657,"data":1561,"type":42,"tunes":1562},{"text":659,"level":246},{},{"id":662,"data":1564,"type":218,"tunes":1565},{"text":664},{},{"id":667,"data":1567,"type":218,"tunes":1568},{"text":669},{},{"id":672,"data":1570,"type":226,"tunes":1571},{"body":674,"title":675,"variant":274},{},{"id":678,"data":1573,"type":42,"tunes":1574},{"text":680,"level":246},{},{"id":683,"data":1576,"type":218,"tunes":1577},{"text":685},{},{"id":688,"data":1579,"type":218,"tunes":1580},{"text":690},{},{"id":693,"data":1582,"type":318,"tunes":1591},{"content":1583,"stretched":43,"withHeadings":14},[1584,1585,1586,1587,1588,1589,1590],[697,698],[700,701],[703,704],[706,707],[709,710],[712,713],[715,716],{},{"id":719,"data":1593,"type":42,"tunes":1594},{"text":721,"level":246},{},{"id":724,"data":1596,"type":218,"tunes":1597},{"text":726},{},{"id":729,"data":1599,"type":218,"tunes":1600},{"text":731},{},{"id":734,"data":1602,"type":42,"tunes":1603},{"text":736,"level":246},{},{"id":739,"data":1605,"type":218,"tunes":1606},{"text":741},{},{"id":744,"data":1608,"type":218,"tunes":1609},{"text":746},{},{"id":749,"data":1611,"type":42,"tunes":1612},{"text":751,"level":246},{},{"id":754,"data":1614,"type":218,"tunes":1615},{"text":756},{},{"id":759,"data":1617,"type":218,"tunes":1618},{"text":761},{},{"id":764,"data":1620,"type":42,"tunes":1621},{"text":766,"level":246},{},{"id":769,"data":1623,"type":226,"tunes":1624},{"body":771,"title":772,"variant":233},{},{"id":775,"data":1626,"type":218,"tunes":1627},{"text":777},{},{"id":780,"data":1629,"type":218,"tunes":1630},{"text":782},{},{"id":785,"data":1632,"type":218,"tunes":1633},{"text":787},{},{"id":790,"data":1635,"type":218,"tunes":1636},{"text":792},{},{"id":795,"data":1638,"type":318,"tunes":1649},{"content":1639,"stretched":43,"withHeadings":14},[1640,1641,1642,1643,1644,1645,1646,1647,1648],[799,800],[802,803],[805,806],[808,809],[811,812],[814,815],[817,818],[820,821],[823,824],{},{"id":827,"data":1651,"type":42,"tunes":1652},{"text":829,"level":246},{},{"id":832,"data":1654,"type":218,"tunes":1655},{"text":834},{},{"id":837,"data":1657,"type":218,"tunes":1658},{"text":839},{},{"id":842,"data":1660,"type":42,"tunes":1661},{"text":844,"level":246},{},{"id":847,"data":1663,"type":318,"tunes":1678},{"content":1664,"stretched":43,"withHeadings":14},[1665,1666,1667,1668,1669,1670,1671,1672,1673,1674,1675,1676,1677],[851,852],[854,855],[857,858],[860,861],[863,864],[866,867],[869,870],[872,873],[875,876],[878,879],[881,882],[884,885],[887,888],{},{"id":891,"data":1680,"type":42,"tunes":1681},{"text":893,"level":246},{},{"id":896,"data":1683,"type":574,"tunes":1694},{"steps":1684,"title":926,"orientation":573},[1685,1686,1687,1688,1689,1690,1691,1692,1693],{"label":900,"description":901},{"label":903,"description":904},{"label":906,"description":907},{"label":909,"description":910},{"label":912,"description":913},{"label":915,"description":916},{"label":918,"description":919},{"label":921,"description":922},{"label":924,"description":925},{},{"id":929,"data":1696,"type":42,"tunes":1697},{"text":931,"level":246},{},{"id":934,"data":1699,"type":318,"tunes":1714},{"content":1700,"stretched":43,"withHeadings":14},[1701,1702,1703,1704,1705,1706,1707,1708,1709,1710,1711,1712,1713],[356,938],[940,941],[943,944],[946,947],[949,950],[952,953],[955,956],[958,959],[961,962],[964,965],[967,968],[970,971],[973,974],{},{"id":977,"data":1716,"type":42,"tunes":1717},{"text":979,"level":246},{},{"id":982,"data":1719,"type":318,"tunes":1730},{"content":1720,"stretched":43,"withHeadings":14},[1721,1722,1723,1724,1725,1726,1727,1728,1729],[986,987],[989,990],[992,993],[995,996],[998,999],[1001,1002],[1004,1005],[1007,1008],[1010,1011],{},{"id":1014,"data":1732,"type":42,"tunes":1733},{"text":1016,"level":246},{},{"id":1019,"data":1735,"type":218,"tunes":1736},{"text":1021},{},{"id":1024,"data":1738,"type":218,"tunes":1739},{"text":1026},{},{"id":1029,"data":1741,"type":218,"tunes":1742},{"text":1031},{},{"id":1034,"data":1744,"type":218,"tunes":1745},{"text":1036},{},{"id":1039,"data":1747,"type":42,"tunes":1748},{"text":1041,"level":246},{},{"id":1044,"data":1750,"type":218,"tunes":1751},{"text":1046},{},{"id":1049,"data":1753,"type":218,"tunes":1754},{"text":1051},{},{"id":1054,"data":1756,"type":218,"tunes":1757},{"text":1056},{},{"id":1059,"data":1759,"type":42,"tunes":1760},{"text":1061,"level":246},{},{"id":1064,"data":1762,"type":218,"tunes":1763},{"text":1066},{},{"id":1069,"data":1765,"type":218,"tunes":1766},{"text":1071},{},{"id":1074,"data":1768,"type":42,"tunes":1769},{"text":1076,"level":246},{},{"id":1079,"data":1771,"type":218,"tunes":1772},{"text":1081},{},{"id":1084,"data":1774,"type":1090,"tunes":1775},{"url":1086,"title":1087,"excerpt":1088,"ctaLabel":1089},{},{"id":1093,"data":1777,"type":218,"tunes":1778},{"text":1095},{},{"id":1098,"data":1780,"type":1090,"tunes":1781},{"url":1100,"title":1101,"excerpt":1102,"ctaLabel":1103},{},{"id":1106,"data":1783,"type":218,"tunes":1784},{"text":1108},{},{"id":1111,"data":1786,"type":1090,"tunes":1787},{"url":1113,"title":1114,"excerpt":1115,"ctaLabel":1116},{},{"id":1119,"data":1789,"type":42,"tunes":1790},{"text":1121,"level":246},{},{"id":1124,"data":1792,"type":1124,"tunes":1802},{"items":1793,"title":1159},[1794,1795,1796,1797,1798,1799,1800,1801],{"id":1128,"answer":1129,"question":1130},{"id":1132,"answer":1133,"question":1134},{"id":1136,"answer":1137,"question":1138},{"id":1140,"answer":1141,"question":1142},{"id":1144,"answer":1145,"question":1146},{"id":1148,"answer":1149,"question":1150},{"id":1152,"answer":1153,"question":1154},{"id":1156,"answer":1157,"question":1158},{},{"id":1162,"data":1804,"type":42,"tunes":1805},{"text":1164,"level":246},{},{"id":1167,"data":1807,"type":1167,"tunes":1819},{"title":1169,"entries":1808},[1809,1810,1811,1812,1813,1814,1815,1816,1817,1818],{"term":1172,"anchor":1173,"definition":1174},{"term":1176,"anchor":1177,"definition":1178},{"term":1180,"anchor":1181,"definition":1182},{"term":1184,"anchor":1185,"definition":1186},{"term":1188,"anchor":327,"definition":1189},{"term":1191,"anchor":1192,"definition":1193},{"term":1195,"anchor":1196,"definition":1197},{"term":1199,"anchor":1200,"definition":1201},{"term":1203,"anchor":1204,"definition":1205},{"term":1207,"anchor":1208,"definition":1209},{},{"id":1212,"data":1821,"type":42,"tunes":1822},{"text":1214,"level":246},{},{"id":1217,"data":1824,"type":218,"tunes":1825},{"text":1219},{},{"id":1222,"data":1827,"type":218,"tunes":1828},{"text":1224},{},{"id":1227,"data":1830,"type":218,"tunes":1831},{"text":1229},{},{"id":1232,"data":1833,"type":42,"tunes":1834},{"text":1234,"level":246},{},{"id":1237,"data":1836,"type":218,"tunes":1837},{"text":1239},{},{"id":1242,"data":1839,"type":1249,"tunes":1842},{"link":1244,"meta":1840},{"image":1841,"title":1247,"description":1248},{"url":304},{},{"id":1252,"data":1844,"type":1249,"tunes":1847},{"link":1254,"meta":1845},{"image":1846,"title":1257,"description":1258},{"url":304},{},{"id":1261,"data":1849,"type":1249,"tunes":1852},{"link":1263,"meta":1850},{"image":1851,"title":1266,"description":1267},{"url":304},{},{"id":1270,"data":1854,"type":1249,"tunes":1857},{"link":1272,"meta":1855},{"image":1856,"title":1275,"description":1276},{"url":304},{},{"id":1279,"data":1859,"type":1249,"tunes":1862},{"link":1281,"meta":1860},{"image":1861,"title":1284,"description":1285},{"url":304},{},{"id":1288,"data":1864,"type":1249,"tunes":1867},{"link":1290,"meta":1865},{"image":1866,"title":1293,"description":1294},{"url":304},{},"Post erfolgreich abgerufen",{"items":1870,"source":1953,"manualIds":1954,"manualMatchedIds":1955},[1871,1878,1885,1892,1899,1905,1912,1918,1925,1932,1939,1946],{"id":1872,"slug":1873,"title":1874,"excerpt":1875,"featuredImage":1876,"publishedAt":1877},"495","sovereign-ai-control-of-models-data-infrastructure-and-dependencies","Sovereign AI: Control of Models, Data, Infrastructure and Dependencies","Sovereign AI is about effective control over models, data, infrastructure, software, operations and strategic dependencies — not simply where an AI model is hosted.","\u002Fuploads\u002F2026\u002F10\u002Fsovereign-ai-control-of-models-data-infrastructure-and-dependencies-1791488833132-niy85x.webp","2026-10-08T15:45:00.000Z",{"id":1879,"slug":1880,"title":1881,"excerpt":1882,"featuredImage":1883,"publishedAt":1884},"487","vector-databases-embeddings-and-reranking-three-different-parts-of-retrieval","Vector Databases, Embeddings and Reranking: Three Different Parts of Retrieval","Embeddings represent meaning, vector databases retrieve candidates, and rerankers refine results. Learn how these three retrieval layers differ and work together in RAG.","\u002Fuploads\u002F2026\u002F10\u002Fvector-databases-embeddings-and-reranking-three-different-parts-of-retrieval-1791480129884-9dtasz.webp","2026-10-08T11:21:00.000Z",{"id":1886,"slug":1887,"title":1888,"excerpt":1889,"featuredImage":1890,"publishedAt":1891},"492","mcp-explained-what-it-connects-what-it-does-not-do-and-where-it-fits","MCP Explained: What It Connects, What It Does Not Do and Where It Fits","Model Context Protocol connects AI applications to external tools, resources and prompts through a standard client-server boundary. Learn what MCP does, what it does not do, and where it fits in agent architecture.","\u002Fuploads\u002F2026\u002F10\u002Fmcp-explained-what-it-connects-what-it-does-not-do-and-where-it-fits-1791486640275-7ub1cq.webp","2026-10-08T15:09:00.000Z",{"id":1893,"slug":1894,"title":1895,"excerpt":1896,"featuredImage":1897,"publishedAt":1898},"494","air-gapped-ai-how-ai-systems-work-without-internet-or-cloud-access","Air-Gapped AI: How AI Systems Work Without Internet or Cloud Access","Air-gapped AI runs models, RAG and AI applications inside an isolated security domain without internet or cloud dependencies. Learn how models, data, updates and tools operate offline.","\u002Fuploads\u002F2026\u002F10\u002Fair-gapped-ai-how-ai-systems-work-without-internet-or-cloud-access-1791487983978-e6xqf0.webp","2026-10-08T11:32:00.000Z",{"id":1900,"slug":1901,"title":1101,"excerpt":1902,"featuredImage":1903,"publishedAt":1904},"468","ai-agent-memory-is-not-rag-how-to-separate-memory-retrieval-state-and-context","Agent memory, RAG, state, and context are often used as if they were interchangeable. They are not. This practical architecture model separates the four layers, shows where each belongs, and explains what breaks when systems collapse them into one.","\u002Fuploads\u002F2026\u002F09\u002Fai-agent-memory-is-not-rag-how-to-separate-memory-retrieval-state-and-context-1790350560308-np0xy6.webp","2026-09-25T11:34:00.000Z",{"id":1906,"slug":1907,"title":1908,"excerpt":1909,"featuredImage":1910,"publishedAt":1911},"476","mcp-vs-a2a-vs-ucp-vs-ap2-vs-a2ui-the-agent-protocol-stack-explained","MCP vs A2A vs UCP vs AP2 vs A2UI: The Agent Protocol Stack Explained","MCP, A2A, UCP, AP2 and A2UI are often presented as competing agent standards. They mostly solve different interoperability problems. This guide maps each protocol to the boundary it actually standardizes—and shows how they can work together in one production system.","\u002Fuploads\u002F2026\u002F09\u002Fmcp-vs-a2a-vs-ucp-vs-ap2-vs-a2ui-the-agent-protocol-stack-explained-1790352625869-2ezle0.webp","2026-09-25T12:09:00.000Z",{"id":1913,"slug":1914,"title":1087,"excerpt":1915,"featuredImage":1916,"publishedAt":1917},"478","what-is-rag-the-simplest-explanation-of-how-it-works","RAG sounds complicated, but the idea is simple: before an AI answers, it first looks up useful information from a knowledge source and gives that information to the language model. This guide explains RAG, LLMs, state, memory and tools using one simple mental model.","\u002Fuploads\u002F2026\u002F09\u002Fwhat-is-rag-the-simplest-explanation-of-how-it-works-1790377492124-khjagt.webp","2026-09-25T19:03:00.000Z",{"id":1919,"slug":1920,"title":1921,"excerpt":1922,"featuredImage":1923,"publishedAt":1924},"489","agentic-ai-explained-when-an-ai-system-can-plan-use-tools-and-act","Agentic AI Explained: When an AI System Can Plan, Use Tools and Act","Agentic AI uses models inside multi-step execution loops where they can choose tools, observe results, update state and adapt their next action within explicit runtime and permission boundaries.","\u002Fuploads\u002F2026\u002F10\u002Fagentic-ai-explained-when-an-ai-system-can-plan-use-tools-and-act-1791481499084-wnji2a.webp","2026-10-08T11:43:00.000Z",{"id":1926,"slug":1927,"title":1928,"excerpt":1929,"featuredImage":1930,"publishedAt":1931},"484","what-is-an-ai-platform-architect-models-data-runtime-security-and-operations","What Is an AI Platform Architect? Models, Data, Runtime, Security and Operations","An AI Platform Architect designs reusable AI foundations across models, providers, retrieval, agents, identity, security, evaluation, observability and operations.","\u002Fuploads\u002F2026\u002F10\u002Fwhat-is-an-ai-platform-architect-models-data-runtime-security-and-operations-1791477229171-ou3zcc.webp","2026-10-08T12:32:00.000Z",{"id":1933,"slug":1934,"title":1935,"excerpt":1936,"featuredImage":1937,"publishedAt":1938},"470","what-should-an-ai-agent-remember-forget-recompute-or-retrieve-again","What Should an AI Agent Remember, Forget, Recompute or Retrieve Again?","Long-running agents should not remember everything. This article provides a practical lifecycle model for deciding what belongs in durable memory, what should be retrieved again, what is safer to recompute, and what should expire or be superseded.","\u002Fuploads\u002F2026\u002F09\u002Fwhat-should-an-ai-agent-remember-forget-recompute-or-retrieve-again-1790351131087-iehz28.webp","2026-09-25T09:43:00.000Z",{"id":1940,"slug":1941,"title":1942,"excerpt":1943,"featuredImage":1944,"publishedAt":1945},"480","when-should-an-ai-stop-trusting-its-own-knowledge-the-retrieval-trigger","When Should an AI Stop Trusting Its Own Knowledge? — The Retrieval Trigger","An AI model does not need retrieval for every question. The important problem is knowing when its internal knowledge is no longer enough. The Retrieval Trigger is a practical decision boundary that determines when an AI system should stop relying solely on model knowledge and obtain external evidence before answering.","\u002Fuploads\u002F2026\u002F09\u002Fwhen-should-an-ai-stop-trusting-its-own-knowledge-the-retrieval-trigger-1790574991244-f4rpyg.webp","2026-09-28T01:49:00.000Z",{"id":1947,"slug":1948,"title":1949,"excerpt":1950,"featuredImage":1951,"publishedAt":1952},"483","what-is-an-ai-solution-architect-system-boundaries-responsibilities-and-trade-offs","What Is an AI Solution Architect? System Boundaries, Responsibilities and Trade-offs","An AI Solution Architect turns business requirements into a production-ready AI system across data, models, tools, security, runtime, evaluation and operations.","\u002Fuploads\u002F2026\u002F10\u002Fwhat-is-an-ai-solution-architect-system-boundaries-responsibilities-and-trade-offs-1791476643267-1st5xz.webp","2026-10-08T12:23:00.000Z","fallback",[],[]]