1"use strict";(globalThis.webpackChunkadri_docs=globalThis.webpackChunkadri_docs||[]).push([[5940],{275:t=>{t.exports=JSON.parse('{"permalink":"/blog/genai/executive-impact-context-instrumentation","editUrl":"https://github.com/GetAdriAI/adri-docs/tree/main/blog/genai/executive-impact-context-instrumentation.md","source":"@site/blog/genai/executive-impact-context-instrumentation.md","title":"Why Executives Should Care About Context Instrumentation","description":"The business impact of context instrumentation in SAP: speed, cost, and scalability.","date":"2026-04-19T00:00:00.000Z","tags":[{"inline":false,"label":"GenAI","permalink":"/blog/tags/genai","description":"All posts about GenAI"}],"readingTime":1.2,"hasTruncateMarker":true,"authors":[{"name":"Shyam Swaroop","title":"Co-Founder & CTO, Adri AI","url":"https://www.linkedin.com/in/shyamswaroop/","page":{"permalink":"/blog/authors/ss"},"socials":{"linkedin":"https://www.linkedin.com/in/shyamswaroop/","github":"https://github.com/cruxcode"},"imageURL":"https://github.com/cruxcode.png","key":"ss"}],"frontMatter":{"title":"Why Executives Should Care About Context Instrumentation","description":"The business impact of context instrumentation in SAP: speed, cost, and scalability.","tags":["genai"],"authors":["ss"],"date":"2026-04-19T00:00:00.000Z"},"unlisted":false,"prevItem":{"title":"SAP\'s Shift in Terminology: From Custom Development to Extensibility","permalink":"/blog/sap/sap-shift-in-terminology"},"nextItem":{"title":"The Return of Simple Prompting in SAP","permalink":"/blog/genai/simple-prompting-context-instrumentation"}}')},7105:(t,e,n)=>{n.r(e),n.d(e,{assets:()=>c,contentTitle:()=>r,default:()=>m,frontMatter:()=>a,metadata:()=>i,toc:()=>u});var i=n(275),o=n(4848),s=n(8453);const a={title:"Why Executives Should Care About Context Instrumentation",description:"The business impact of context instrumentation in SAP: speed, cost, and scalability.",tags:["genai"],authors:["ss"],date:new Date("2026-04-19T00:00:00.000Z")},r=void 0,c={authorsImageUrls:[void 0]},u=[];function l(t){const e={p:"p",...(0,s.R)(),...t.components};return(0,o.jsx)(e.p,{children:"AI in SAP is often discussed in technical terms, but the real story is business impact.\nThis is about speed, cost, and scalability."})}function m(t={}){const{wrapper:e}={...(0,s.R)(),...t.components};return e?(0,o.jsx)(e,{...t,children:(0,o.jsx)(l,{...t})}):l(t)}},8453:(t,e,n)=>{n.d(e,{R:()=>a,x:()=>r});var i=n(6540);const o={},s=i.createContext(o);function a(t){const e=i.useContext(s);return i.useMemo(function(){return"function"==typeof t?t(e):{...e,...t}},[e,t])}function r(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(o):t.components||o:a(t.components),i.createElement(s.Provider,{value:e},t.children)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.