[{"data":1,"prerenderedAt":1841},["ShallowReactive",2],{"site-nav-content":3,"hiring-banner-content":177,"blog:\u002Fblog\u002Fthe-general-counsel-and-the-cross-border-ai-problem":189,"blog-index-copy":662,"blog:\u002Fblog\u002Fthe-general-counsel-and-the-cross-border-ai-problem:surround":683,"site-cta-content":1822},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":132,"id":161,"title":162,"archived":163,"authors":164,"badge":164,"body":165,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":173,"relatedHeading":164,"seo":174,"series":164,"sitemap":163,"status":164,"stem":175,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":176},{"productLabel":5,"loginLabel":6,"contactLabel":7,"contactSalesLabel":8},"Product","Log in","Contact","Get started for free",[10,14,18,22,26,30,34,38],{"label":11,"to":12,"description":13},"Overview","\u002Foverview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","\u002Fproduct\u002Fconflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","\u002Fproduct\u002Fagent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","\u002Fproduct\u002Flifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","\u002Fproduct\u002Fwiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","\u002Fproduct\u002Fworkstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","\u002Fproduct\u002Fperception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","\u002Fproduct\u002Fgovernance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","\u002Fmodels",{"label":47,"to":48},"Pricing","\u002Fpricing",{"label":50,"to":51},"Integrations","\u002Fintegrations",{"label":53,"to":54},"Security","\u002Fsecurity",{"label":56,"to":57},"Partners","\u002Fpartners",{"label":59,"to":60},"Insights","\u002Fblog",{"productHeading":5,"companyHeading":62,"resourcesHeading":63,"legalHeading":64,"docsLabel":65,"docsUrl":66,"statementLines":67,"copyright":70,"companyLinks":71,"resourcesLinks":86,"legalLinks":102,"socialLinks":109,"bottomLinks":119},"Company","Resources","Legal","Docs","https:\u002F\u002Fdocs.gonimbus.ai",[68,69],"Stop training someone else's model.","Control your AI.","© 2026 Nimbus Intelligence, Inc. All rights reserved.",[72,73,74,75,76,78,81,84],{"label":47,"to":48},{"label":50,"to":51},{"label":53,"to":54},{"label":59,"to":60},{"label":77,"to":57},"Partner Program",{"label":79,"to":80},"Careers","\u002Fcareers",{"label":82,"to":83},"System status","\u002Fstatus",{"label":7,"to":85},"\u002Fcontact",[87,90,93,96,99],{"label":88,"to":89},"Glossary","\u002Fglossary",{"label":91,"to":92},"Compare","\u002Fcompare",{"label":94,"to":95},"Evaluate","\u002Fevaluate",{"label":97,"to":98},"Problems","\u002Fproblems",{"label":100,"to":101},"Use cases","\u002Fuse-cases",[103,106],{"label":104,"to":105},"Terms of Service","\u002Fterms",{"label":107,"to":108},"Privacy Policy","\u002Fprivacy",[110,113,116],{"label":111,"href":112},"LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fgonimbusai\u002F",{"label":114,"href":115},"X","https:\u002F\u002Fx.com\u002Fgonimbusai",{"label":117,"href":118},"Instagram","https:\u002F\u002Fwww.instagram.com\u002Fgonimbus_ai\u002F",[120,122,124,127,128],{"label":121,"to":105},"Terms",{"label":123,"to":108},"Privacy",{"label":125,"to":126},"Compliance","\u002Fcompliance",{"label":82,"to":83},{"label":129,"to":130,"external":131},"LLMs.txt","\u002Fllms.txt",true,{"text":133,"prompt":134,"platforms":135},"Ask AI about Nimbus","I'm researching enterprise intelligence platforms and want to know how Nimbus combines perception, collaboration, and autonomous agents to drive strategic decision-making. Summarize the highlights from Nimbus's website: https:\u002F\u002Fgonimbus.ai",[136,141,146,151,156],{"name":137,"label":138,"icon":139,"hrefPrefix":140},"chatgpt","ChatGPT","simple-icons:openai","https:\u002F\u002Fchatgpt.com\u002F?prompt=",{"name":142,"label":143,"icon":144,"hrefPrefix":145},"perplexity","Perplexity","mdi:magnify","https:\u002F\u002Fwww.perplexity.ai\u002Fsearch\u002Fnew?q=",{"name":147,"label":148,"icon":149,"hrefPrefix":150},"grok","Grok","simple-icons:x","https:\u002F\u002Fx.com\u002Fi\u002Fgrok?text=",{"name":152,"label":153,"icon":154,"hrefPrefix":155},"claude","Claude","simple-icons:anthropic","https:\u002F\u002Fclaude.ai\u002Fnew?q=",{"name":157,"label":158,"icon":159,"hrefPrefix":160},"google-ai","Google AI","simple-icons:google","https:\u002F\u002Fwww.google.com\u002Fsearch?udm=50&aep=11&q=","content\u002Fshared\u002Fnav.md","Site navigation",false,null,{"type":166,"value":167,"toc":168},"minimark",[],{"title":169,"searchDepth":170,"depth":170,"links":171},"",2,[],"md","\u002Fshared\u002Fnav",{"title":162,"description":169},"shared\u002Fnav","Q7sDe7TuGEwhwUMamyeOxjvGlsUaF3Iay9VTW0KaE_U",{"enabled":163,"message":178,"linkLabel":79,"linkHref":80,"id":179,"title":180,"archived":163,"authors":164,"badge":164,"body":181,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":185,"relatedHeading":164,"seo":186,"series":164,"sitemap":163,"status":164,"stem":187,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":188},"We're hiring! Join the team building the Sentient Enterprise.","content\u002Fshared\u002Fhiring.md","Hiring banner",{"type":166,"value":182,"toc":183},[],{"title":169,"searchDepth":170,"depth":170,"links":184},[],"\u002Fshared\u002Fhiring",{"title":180,"description":169},"shared\u002Fhiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",{"id":190,"title":191,"archived":163,"authors":192,"badge":197,"body":199,"date":637,"definedTerm":164,"department":164,"description":638,"extension":172,"eyebrow":164,"faqHeader":639,"faqs":642,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":652,"relatedHeading":164,"seo":653,"series":654,"sitemap":131,"status":164,"stem":655,"subhead":164,"tags":656,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":661},"content\u002Fblog\u002Fthe-general-counsel-and-the-cross-border-ai-problem.md","How Employee AI Usage Triggers Cross-Border Compliance Nightmares",[193],{"name":194,"role":195,"to":196},"Zac Radbone","Co-Founder and CCO","https:\u002F\u002Fgonimbus.ai",{"label":198},"Thought Leadership",{"type":166,"value":200,"toc":628},[201,205,219,224,227,230,237,304,308,311,319,378,382,385,393,400,450,454,457,464,470,476,482,485,493,565,569,572,576,579,582,585,589],[202,203,204],"p",{},"General counsel did not ask for a new category of international transfer. They received one anyway, every time an employee pasted a European customer file, a health-adjacent note, or a worker record into a chatbot whose servers, logs, and subprocessors they could not name. The paste takes a second. The lawful-basis analysis, if anyone had done it, would have taken a meeting. Almost nobody scheduled the meeting.",[202,206,207,208,213,214,218],{},"This is not an argument for freezing tools. It is an argument for noticing that AI use is data processing, and that cross-border processing already had a law before the model had a brand. The ",[209,210,212],"a",{"href":211},"https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fuk-gdpr-guidance-and-resources\u002Fartificial-intelligence\u002Fguidance-on-ai-and-data-protection\u002F","UK Information Commissioner’s Office guidance on AI and data protection"," starts from that plain fact: data protection law applies when you use AI, including the duties around fairness, purpose limitation, and security. The ",[209,215,217],{"href":216},"https:\u002F\u002Feur-lex.europa.eu\u002Flegal-content\u002FEN\u002FTXT\u002F?uri=OJ:L_202401689","EU AI Act"," adds product duties for certain systems. It does not repeal the GDPR. A company that treats “AI policy” as a substitute for its existing privacy programme will fail both.",[220,221,223],"h2",{"id":222},"what-actually-crosses-the-border","What actually crosses the border",[202,225,226],{},"Leaders picture a formal integration: an API, a data-processing agreement, a transfer impact assessment. Some of the risk looks like that. Much of it looks like a prompt.",[202,228,229],{},"A support lead in Dublin asks a consumer chatbot to rewrite a complaint that contains a name, an address, and a medical detail the customer volunteered. A finance analyst in Singapore asks a personal account to classify invoices that include tax identifiers. A recruiter in California asks a tool hosted abroad to compare résumés. Each is a disclosure to a new recipient, often in another country, often for a purpose — “help me draft” — that was never written down as a purpose. Purpose limitation is not a slogan. It is the question of why you are allowed to use that data at all. “Because the model is helpful” is not a purpose a regulator will recognise.",[202,231,232,236],{},[209,233,235],{"href":234},"https:\u002F\u002Fnewsroom.ibm.com\u002F2025-07-30-ibm-report-13-of-organizations-reported-breaches-of-ai-models-or-applications,-97-of-which-reported-lacking-proper-ai-access-controls","IBM’s 2025 research"," found that shadow-AI incidents exposed personally identifiable information more often than breaches did on average, and that only 37 percent of organisations had policies to manage AI or detect shadow use. The legal team is often the last to see the prompt and the first to see the letter.",[238,239,240,256],"table",{},[241,242,243],"thead",{},[244,245,246,250,253],"tr",{},[247,248,249],"th",{},"What leadership pictures",[247,251,252],{},"What actually happens",[247,254,255],{},"Why it is already a legal event",[257,258,259,271,282,293],"tbody",{},[244,260,261,265,268],{},[262,263,264],"td",{},"An API, a data-processing agreement, a transfer impact assessment",[262,266,267],{},"A support lead in Dublin pastes a complaint: name, address, a medical detail the customer volunteered",[262,269,270],{},"A new recipient, another country, a purpose nobody wrote down",[244,272,273,276,279],{},[262,274,275],{},"A sanctioned enterprise tenant",[262,277,278],{},"A finance analyst in Singapore classifies invoices with tax identifiers in a personal account",[262,280,281],{},"The tab that was open, not the default counsel would have chosen",[244,283,284,287,290],{},[262,285,286],{},"A hiring workflow inside the HR system",[262,288,289],{},"A recruiter in California compares résumés in a tool hosted abroad",[262,291,292],{},"Disclosure of worker data for “help me compare,” which is not a purpose",[244,294,295,298,301],{},[262,296,297],{},"An AI policy on the intranet",[262,299,300],{},"The paste, then the letter",[262,302,303],{},"The legal team sees the prompt last",[220,305,307],{"id":306},"the-act-the-gdpr-and-the-confusion-between-them","The Act, the GDPR, and the confusion between them",[202,309,310],{},"Boards are being briefed on the EU AI Act as if it were the whole problem. It is a large problem for defined uses: some employment, credit, and safety contexts carry documentation, data-governance, and human-oversight duties, on a timetable the regulation itself sets out. It is the wrong frame for the paste in Dublin. That paste is a confidentiality and data-protection event even if no “high-risk AI system” is involved.",[202,312,313,314,318],{},"Counsel should brief the two regimes separately, in one sitting, so the business stops shopping for the more convenient label. If the use is high-risk under the Act, you need the technical file and the oversight. If the use touches personal data, you need a basis, a purpose, a retention story, and a transfer tool — adequacy, clauses, or another lawful route — regardless of the Act. The ",[209,315,317],{"href":316},"https:\u002F\u002Foecd.ai\u002Fen\u002Fai-principles","OECD AI Principles"," sit above both as political commitment: transparency, accountability, respect for human rights. They do not fill in a standard contractual clause. Someone in the company still has to.",[238,320,321,332],{},[241,322,323],{},[244,324,325,327,329],{},[247,326],{},[247,328,217],{},[247,330,331],{},"Data protection law you already had",[257,333,334,345,356,367],{},[244,335,336,339,342],{},[262,337,338],{},"The question",[262,340,341],{},"Is this use high-risk, and do the product duties apply?",[262,343,344],{},"Was this personal data processed lawfully, for a stated purpose, with a transfer tool?",[244,346,347,350,353],{},[262,348,349],{},"What a complete answer contains",[262,351,352],{},"Documentation, data governance, human oversight, on the regulation’s timetable",[262,354,355],{},"A basis, a purpose, a retention story, and adequacy, clauses, or another lawful route",[244,357,358,361,364],{},[262,359,360],{},"What it does not cover",[262,362,363],{},"The paste in Dublin, if no high-risk system is involved",[262,365,366],{},"It does not repeal, and it is not repealed by, an “AI policy”",[244,368,369,372,375],{},[262,370,371],{},"The convenient mistake",[262,373,374],{},"Treating the Act as the whole problem",[262,376,377],{},"Treating the Act’s label as a way to avoid the transfer analysis",[220,379,381],{"id":380},"records-or-the-absence-of-them","Records, or the absence of them",[202,383,384],{},"The cross-border question becomes acute when something goes wrong and the company cannot say what was sent. Consumer tools vary in whether chats are retained, whether they are used to improve a model, and whether an enterprise agreement changes those defaults. Employees do not select the default. They select the tab that is already open.",[202,386,387,388,392],{},"A defensible programme therefore logs the sanctioned path and starves the unsanctioned one by substitution, not only by policy. ",[209,389,391],{"href":390},"https:\u002F\u002Fwww.cnbc.com\u002F2023\u002F05\u002F02\u002Fsamsung-bans-use-of-ai-like-chatgpt-for-staff-after-misuse-of-chatbot.html","Samsung’s 2023 restriction"," after code was uploaded is the intellectual-property version. Personal data is the same gesture with a different statute. If you cannot reconstruct the prompt, you cannot answer a data-subject request, a customer audit, or a regulator who asks whether a particular file left the region. “We told people not to” is a training record. It is not a processing record.",[202,394,395,399],{},[209,396,398],{"href":397},"https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fworklab\u002Fwork-trend-index\u002Fai-at-work-is-here-now-comes-the-hard-part","Microsoft’s finding"," that 78 percent of AI users bring their own tools is the factual predicate for this advice. Assume the paste is happening. Design as if the log on the official system is the only log you will ever be able to show.",[238,401,402,415],{},[241,403,404],{},[244,405,406,409,412],{},[247,407,408],{},"If you are asked",[247,410,411],{},"A training record answers",[247,413,414],{},"A processing record answers",[257,416,417,428,439],{},[244,418,419,422,425],{},[262,420,421],{},"Did this file leave the region?",[262,423,424],{},"“We told people not to”",[262,426,427],{},"What was sent, to which vendor, in which region",[244,429,430,433,436],{},[262,431,432],{},"Was it used to improve a model?",[262,434,435],{},"The policy on the intranet",[262,437,438],{},"The default in the agreement the employee actually used",[244,440,441,444,447],{},[262,442,443],{},"Can you answer a data-subject request?",[262,445,446],{},"That staff were trained",[262,448,449],{},"The prompt, or an honest statement that the only log is on a consumer tool you do not control",[220,451,453],{"id":452},"the-memo-counsel-should-be-able-to-write-in-a-day","The memo counsel should be able to write in a day",[202,455,456],{},"If a regulator, a customer, or a data subject asked tomorrow what left the building, the memo has four headings.",[202,458,459,463],{},[460,461,462],"strong",{},"Jobs as purposes."," The jobs allowed to use an assistant, stated as specific purposes.",[202,465,466,469],{},[460,467,468],{},"Vendors, region, and retention."," The vendors that see prompts, with region, retention, and whether prompts train a model.",[202,471,472,475],{},[460,473,474],{},"Restricted categories."," The categories that do not go in at all without a recorded exception.",[202,477,478,481],{},[460,479,480],{},"The last drill."," One real prompt, walked from the screen to the region and back.",[202,483,484],{},"If a heading is empty, say so in the advice. Do not soften it into a roadmap paragraph. Roadmap paragraphs are how cross-border risk stays theoretical until it is a paste.",[202,486,487,488,492],{},"Where the assistant speaks to customers, add a fifth heading: the rule version and the person who can approve a promise. ",[209,489,491],{"href":490},"https:\u002F\u002Fwww.canlii.org\u002Fen\u002Fbc\u002Fbccrt\u002Fdoc\u002F2024\u002F2024bccrt149\u002F2024bccrt149.html","The company’s words have been enforced against it",". Privacy counsel and commercial counsel are in the same memo because the customer does not separate the transfer from the promise. The EU instrument and data-protection guidance will ask versions of these headings. Write them before the notice does.",[238,494,495,508],{},[241,496,497],{},[244,498,499,502,505],{},[247,500,501],{},"Heading",[247,503,504],{},"Complete",[247,506,507],{},"Empty means",[257,509,510,521,532,543,554],{},[244,511,512,515,518],{},[262,513,514],{},"Jobs as purposes",[262,516,517],{},"“Draft a reply against the current refund rule,” not “productivity”",[262,519,520],{},"You cannot say why the data was used",[244,522,523,526,529],{},[262,524,525],{},"Vendors, region, retention, training default",[262,527,528],{},"Named, including tools inside larger suites",[262,530,531],{},"The tool is not approved for personal data",[244,533,534,537,540],{},[262,535,536],{},"Categories that do not get pasted without a recorded exception",[262,538,539],{},"Special-category data, children’s data, secrets, material non-public information, source code — on one page",[262,541,542],{},"The prohibition is a forty-page policy nobody remembers at 6 p.m.",[244,544,545,548,551],{},[262,546,547],{},"The last drill",[262,549,550],{},"One real prompt, walked from the screen to the region and back",[262,552,553],{},"You will reconstruct it from the customer’s screenshot",[244,555,556,559,562],{},[262,557,558],{},"If the assistant speaks to a customer: rule version and approver",[262,560,561],{},"The sentence, the policy version, the person",[262,563,564],{},"You will be held to the words and asked where the data went. One memo has to answer both",[220,566,568],{"id":567},"four-headings-no-roadmap","Four headings, no roadmap",[202,570,571],{},"Jobs as purposes. Vendors, with region and retention. Categories that do not get pasted. The last drill, walked end to end. If a heading is empty, say so in the advice. Add the rule version on anything the assistant says to a customer. You will be held to those words, and you will be asked where the data went. One memo answers both, if it is factual.",[220,573,575],{"id":574},"a-call-to-general-counsel","A call to general counsel",[202,577,578],{},"Do not let the AI Act briefing crowd out the transfer you already know how to analyse. The novel object is the prompt. The duties are familiar: basis, purpose, minimisation, security, a record, a vendor you can describe. The companies that get this wrong will not fail a philosophy exam. They will fail a questionnaire from a customer in Germany, or a complaint from a person whose complaint was pasted into a tool the company does not have a contract with.",[202,580,581],{},"Put the sanctioned path in place. Log it. Forbid the categories that cannot be logged. Then tell the board the truth: cross-border AI risk is mostly a discipline problem you were already paid to solve.",[583,584],"hr",{},[220,586,588],{"id":587},"references","References",[590,591,592,598,603,607,612,617,622],"ul",{},[593,594,595],"li",{},[209,596,597],{"href":211},"ICO, guidance on AI and data protection",[593,599,600],{},[209,601,602],{"href":216},"Regulation (EU) 2024\u002F1689, the AI Act",[593,604,605],{},[209,606,317],{"href":316},[593,608,609],{},[209,610,611],{"href":234},"IBM newsroom, 30 July 2025",[593,613,614],{},[209,615,616],{"href":390},"CNBC, Samsung restricts generative AI after misuse",[593,618,619],{},[209,620,621],{"href":397},"Microsoft and LinkedIn, 2024 Work Trend Index",[593,623,624],{},[209,625,627],{"href":626},"https:\u002F\u002Fwww.nist.gov\u002Fitl\u002Fai-risk-management-framework","NIST AI Risk Management Framework",{"title":169,"searchDepth":170,"depth":170,"links":629},[630,631,632,633,634,635,636],{"id":222,"depth":170,"text":223},{"id":306,"depth":170,"text":307},{"id":380,"depth":170,"text":381},{"id":452,"depth":170,"text":453},{"id":567,"depth":170,"text":568},{"id":574,"depth":170,"text":575},{"id":587,"depth":170,"text":588},"2026-09-22","What happens when global employees paste proprietary context into overseas models, and how to construct an auditable data transfer record.",{"eyebrow":640,"title":641},"Short answers","The transfer, not the model",[643,646,649],{"question":644,"answer":645},"What is the cross-border AI problem for a general counsel?","An employee in one country pastes a customer list into a tool hosted in another.",{"question":647,"answer":648},"Is the model the hard question?","No. The transfer, the purpose, and the record are.",{"question":650,"answer":651},"What should be reconstructable?","What left the country, why, which tool received it, and whether that purpose was allowed.","\u002Fblog\u002Fthe-general-counsel-and-the-cross-border-ai-problem",{"title":191,"description":638},"insight","blog\u002Fthe-general-counsel-and-the-cross-border-ai-problem",[657,658,659,660],"thought-leadership","legal","privacy","governance","iYaUpyX2Xa7JEg07MLecCR1VMasNOs90XnTde9nbEMk",{"hero":663,"id":665,"title":666,"archived":163,"authors":164,"badge":164,"body":667,"date":164,"definedTerm":164,"department":164,"description":671,"extension":172,"eyebrow":672,"faqHeader":164,"faqs":164,"footerBand":673,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":60,"relatedHeading":679,"seo":680,"series":164,"sitemap":131,"status":164,"stem":681,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":682},{"filename":664},"u2221455217_Flat_design_of_a_futuristic_minimalist_landscape__5d589295-cdea-4ea9-a262-be766881accf_1.png","content\u002Fblog\u002Findex.md","Exploring the future of intelligence.",{"type":166,"value":668,"toc":669},[],{"title":169,"searchDepth":170,"depth":170,"links":670},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":674,"description":675,"primaryLabel":676,"primaryTo":677,"secondaryLabel":678,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","\u002Fnewsletter","Explore the platform","More research",{"title":666,"description":671},"blog\u002Findex","BFSWGYO9bcTlaulivKYWyg08_DJHsdGg3OC6g_CG1Hw",[684,1202],{"id":685,"title":686,"archived":163,"authors":687,"badge":690,"body":691,"date":637,"definedTerm":164,"department":164,"description":1181,"extension":172,"eyebrow":164,"faqHeader":1182,"faqs":1184,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1194,"relatedHeading":164,"seo":1195,"series":654,"sitemap":131,"status":164,"stem":1196,"subhead":164,"tags":1197,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1201},"content\u002Fblog\u002Fthe-lifecycle-graph-and-the-chat-scroll.md","Lost in the Chat Scroll: The Audit Trail AI Leaves Behind",[688],{"name":689,"to":196},"Nimbus Research",{"label":198},{"type":166,"value":692,"toc":1170},[693,696,703,711,715,718,721,729,736,797,800,804,807,810,818,879,883,886,892,898,904,910,917,928,932,935,938,941,944,1016,1020,1023,1030,1038,1042,1045,1053,1056,1102,1109,1113,1120,1123,1127,1130,1133,1135,1137],[202,694,695],{},"The model answered. The employee copied the answer into the deck, the ticket, or the ledger. Next quarter someone asks why the number moved. The person has changed teams. The chat, if it was retained at all, sits in a personal account the company does not administer. The system of record shows the new value and not the proposal, the policy version, or the name that let it through. Nothing in that sequence required a bad model. It required a place that forgets by design.",[202,697,698,699,702],{},"That place is the chat scroll. Consumer assistants, and the enterprise chat windows modelled on them, are excellent at a single sitting. They are a poor system of memory. Organisational intelligence — which rule was in force, who had already signed a similar exception, which source the figure came from — is trapped in threads that do not join. People become the join. They paste, re-explain, and re-ground a fresh session because the last session cannot see the ledger and the ledger cannot see the last session. ",[209,700,701],{"href":397},"Seventy-eight percent of AI users bring their own tools to work",". Each of those tools is another scroll the company will not be able to subpoena from itself.",[202,704,705,706,710],{},"A lifecycle graph is the record built for the question the scroll cannot answer: what caused this outcome? Not a transcript of tokens. A chain — the brief, the sources in scope, the action proposed, the person who released it, the system that changed, and when. ",[209,707,709],{"href":708},"https:\u002F\u002Fwww.w3.org\u002FTR\u002Fprov-overview\u002F","W3C’s provenance model"," has described this shape for years: entities, activities, and agents, linked so derivation can be reconstructed. A lifecycle graph is that instinct applied to work a model helped do. It is not a claim that a chat product has implemented a standards stack. It is a claim that without some chain of that kind, the company does not know why its own systems moved.",[220,712,714],{"id":713},"how-context-fragments","How context fragments",[202,716,717],{},"Fragmentation is not a metaphor. It is a Monday.",[202,719,720],{},"A finance manager asks a personal assistant to explain a revenue line, pasting an export because the official tool cannot see the close file. A seller, in another product, drafts a concession from a battlecard that was replaced in January. Support, in a third, answers the same customer from a macro the model ranked as relevant. Three sentences now exist about one commercial fact. None of them knows about the others. The human who notices, if anyone does, is doing integration work the stack refused to do.",[202,722,723,724,728],{},"The pattern scales with adoption. ",[209,725,727],{"href":726},"https:\u002F\u002Fwww.mckinsey.com\u002Fcapabilities\u002Fquantumblack\u002Four-insights\u002Fthe-state-of-ai","McKinsey’s 2025 survey"," puts use in at least one function at 88 percent of organisations, with nearly two-thirds not yet scaling. Local chats multiply faster than any shared memory. Each chat is a small truth with a confident tone. The company does not have a contradiction report. It has employees who have learned to check the assistant against a colleague, which is the old process with extra steps.",[202,730,731,732,735],{},"There is a legal version of the same fracture. If a customer relied on one of those sentences, the company will be asked which sentence was the company’s. ",[209,733,734],{"href":490},"A tribunal has already declined to treat the chatbot as a separate legal person",". Context fragmentation is how you arrive at that hearing with three versions and no chain.",[238,737,738,751],{},[241,739,740],{},[244,741,742,745,748],{},[247,743,744],{},"Where the context sits",[247,746,747],{},"What a later reader can recover",[247,749,750],{},"What they cannot",[257,752,753,764,775,786],{},[244,754,755,758,761],{},[262,756,757],{},"A personal chat",[262,759,760],{},"Whatever that vendor still retains, if you can get the login",[262,762,763],{},"Who was allowed to rely on it, and whether it matched the rule in force",[244,765,766,769,772],{},[262,767,768],{},"A copilot thread inside a document",[262,770,771],{},"The document, sometimes the thread",[262,773,774],{},"The other system the number was pasted into",[244,776,777,780,783],{},[262,778,779],{},"The system of record",[262,781,782],{},"The new value",[262,784,785],{},"The proposal, the sources, and the signer",[244,787,788,791,794],{},[262,789,790],{},"A shared lifecycle graph",[262,792,793],{},"The brief, the sources, the action, the approval, the outcome",[262,795,796],{},"A second, private scroll that never entered the job",[202,798,799],{},"The last row is the point of the architecture. It does not automatically ingest the personal scroll. It makes the personal scroll unnecessary for the jobs that matter, because the sanctioned path can see the file and will keep the chain.",[220,801,803],{"id":802},"what-retrieval-does-not-do","What retrieval does not do",[202,805,806],{},"Most “memory” projects in the last two years have been retrieval: chunk documents, embed them, fetch the nearest passages, hope the model behaves. Retrieval is necessary and it is not a record of work. It answers “what text looks similar to this question?” It does not answer “what did we decide last quarter, under which policy, with whose signature?”",[202,808,809],{},"Similarity is indifferent to time. A page from 2022 and a page from this morning can be equally near the query. The model then blends them, which is how a bereavement rule and a current policy page both speak. Similarity is indifferent to authority. A draft in a shared drive and the certified close can both be retrieved. The draft is often better written. Similarity is indifferent to permission. A chunk the searcher should not see is a chunk the index may still return if the index was built for the whole corpus.",[202,811,812,813,817],{},"Temporal context, dependency, and prior sign-off are not passages. They are relations. The revenue line depends on a contract. The contract was amended. An exception was signed in March and must not be re-litigated by a model that has not been shown the signature. A vector store can be made to hold some of this with enough metadata discipline. At that point you are no longer “doing RAG.” You are building a graph and using search as one way to enter it. ",[209,814,816],{"href":815},"\u002Fblog\u002Fwhat-is-enterprise-rag\u002F","Enterprise retrieval"," remains the right tool for “find the clause.” It is the wrong tool for “why did this field change?”",[238,819,820,833],{},[241,821,822],{},[244,823,824,827,830],{},[247,825,826],{},"Question",[247,828,829],{},"Retrieval can help",[247,831,832],{},"A lifecycle graph is for",[257,834,835,846,857,868],{},[244,836,837,840,843],{},[262,838,839],{},"Where is the clause?",[262,841,842],{},"Yes, if the current document is in the index and the stale one is not",[262,844,845],{},"Pointing at the version that was in force for this job",[244,847,848,851,854],{},[262,849,850],{},"What did we decide?",[262,852,853],{},"Only if someone wrote the decision down as a document the index likes",[262,855,856],{},"The action, the approver, and the system that changed",[244,858,859,862,865],{},[262,860,861],{},"May this run see it?",[262,863,864],{},"Only if the index was built inside the person’s scope",[262,866,867],{},"Scope as a property of the chain, not an afterthought",[244,869,870,873,876],{},[262,871,872],{},"What should the next run inherit?",[262,874,875],{},"A similar passage",[262,877,878],{},"The prior sign-off that is still binding",[220,880,882],{"id":881},"four-questions-one-chain","Four questions, one chain",[202,884,885],{},"People reach for “4D” because a flat log feels one-dimensional: a list of messages in time. The record operators actually need has to answer four questions at once.",[202,887,888,891],{},[460,889,890],{},"What."," The entity: a customer, a contract, a journal line, a policy version, a workstream.",[202,893,894,897],{},[460,895,896],{},"What happened."," The action: a draft, a refusal, a proposed write, a released write.",[202,899,900,903],{},[460,901,902],{},"When."," Not only a timestamp on a message. Which version of the rule and which state of the system were in scope. A bi-temporal habit — when the fact was true in the world, and when the company recorded it — is what stops a late correction from rewriting history.",[202,905,906,909],{},[460,907,908],{},"Under whose authority."," The person or role that released the action, and the rule that made it theirs to release. A model is an actor in the chain. It is not the authority.",[202,911,912,916],{},[209,913,915],{"href":914},"\u002Fproduct\u002Flifecycle-graph\u002F","The lifecycle graph"," is this chain kept as the company’s, not as a feature of one chat vendor. It points at systems of record. It does not become a second ledger. The official number stays in the financial system. The graph says how an AI-mediated job touched it. That distinction matters. A shadow ledger that “becomes the truth” is a new fragmentation, only more confident.",[202,918,919,920,923,924,927],{},"Provenance of this kind is also what ",[209,921,922],{"href":626},"NIST’s framework"," is asking for when it says map and measure, and what a data-protection inquiry means by a record of processing. ",[209,925,926],{"href":211},"The ICO’s AI guidance"," does not require a branded graph. It requires you to be able to say why this data was in this system. A scroll that the employee selected because the tab was open is a weak answer. A chain with a purpose, a source, and a time is a serious one.",[220,929,931],{"id":930},"a-close-that-can-be-reopened","A close that can be reopened",[202,933,934],{},"Consider a quarterly close in which revenue recognition depends on a contract, a delivery milestone, and an exception finance signed earlier in the year. The work is familiar. The new risk is that each input now has a fluent twin.",[202,936,937],{},"Without a graph, the sequence is a tour of tabs. Someone exports the contract list. Someone else asks an assistant whether a performance obligation has been satisfied, pasting a paragraph. A third person drafts the commentary. The commentary is lucid and slightly wrong about the exception, because the exception lives in an email the assistant did not see. The pack goes to the audit committee. Six weeks later the auditor asks why a line was treated as recognised. The company can produce the journal. It cannot produce the chain. The hours spent reconstructing it are the cost of the scroll.",[202,939,940],{},"With the chain, the job is a workstream. The contract and the milestone are reads against systems the team is allowed to see. The earlier exception is an entity on the graph, with the person who signed it and the date it still binds. The assistant may draft commentary that cites those objects. It may not introduce a treatment that is not among them. If a proposed journal entry would change the books, a person releases that payload. The graph keeps the draft, the refusal if there was one, the sources, and the release. When the auditor asks, the answer is a path, not a search through inboxes.",[202,942,943],{},"Nothing in that picture requires the model to “understand accounting.” It requires the company to keep the decision in a place a successor can open. Standards such as revenue recognition remain the finance team’s. The graph is how an agent-assisted close stays inspectable. The same shape fits a claim, a price exception, or a hiring decision: prior authority in, proposed action, human release, outcome stored.",[238,945,946,959],{},[241,947,948],{},[244,949,950,953,956],{},[247,951,952],{},"Step in the close",[247,954,955],{},"Chat-scroll habit",[247,957,958],{},"Chain",[257,960,961,972,983,994,1005],{},[244,962,963,966,969],{},[262,964,965],{},"Find the contract and the milestone",[262,967,968],{},"Export, paste, hope the session remembers",[262,970,971],{},"Read, in scope, from the system of record",[244,973,974,977,980],{},[262,975,976],{},"Honour an exception already signed",[262,978,979],{},"Hope someone pastes the email",[262,981,982],{},"The prior approval is an object the run can cite and cannot quietly overrule",[244,984,985,988,991],{},[262,986,987],{},"Draft the commentary",[262,989,990],{},"A fluent paragraph with a number it was not given",[262,992,993],{},"Prose that may quote only the objects in the job",[244,995,996,999,1002],{},[262,997,998],{},"Post",[262,1000,1001],{},"Whoever has the token",[262,1003,1004],{},"A person releases the payload",[244,1006,1007,1010,1013],{},[262,1008,1009],{},"The auditor asks",[262,1011,1012],{},"Reconstruction from memory",[262,1014,1015],{},"The path from brief to journal",[220,1017,1019],{"id":1018},"the-person-who-became-the-join","The person who became the join",[202,1021,1022],{},"Context fragmentation has a job description, and someone on the team already holds it. They are the colleague who “knows where that lives.” They keep a private note of which assistant gave a usable answer, which export is current, and which email contained the exception finance will ask about. When a new hire needs the same fact, the colleague pastes it again. When they are on leave, the fact is on leave with them. The organisation has automated the draft and left the integration to a person.",[202,1024,1025,1026,1029],{},"That labour is easy to miss because it looks like diligence. The manager who re-grounds a fresh chat with three attachments before every meeting is performing retrieval the stack would not do. The analyst who checks a model’s number against a colleague is performing reconciliation. The counsel who asks “which version did it see?” is performing provenance by interview. None of these tasks appear in a pilot’s success slide. They appear as calendar load, and they grow as more teams adopt more windows. ",[209,1027,1028],{"href":726},"McKinsey’s finding that most organisations are still piloting"," is consistent with a world in which local fluency is high and shared memory is still a person.",[202,1031,1032,1033,1037],{},"The cost shows up when the person leaves or when two people glue different versions. Sales has a concession in one scroll. Support has a warmer cousin of it in another. Finance discovers both when the credit posts. The reconstruction is then an email search, which fails if one of the scrolls was a personal account the company cannot open. ",[209,1034,1036],{"href":1035},"\u002Fblog\u002Fwhat-is-institutional-memory-in-enterprise-ai\u002F","Institutional memory"," is the property that survives that departure. A lifecycle graph is the mechanism: the exception is an object with an author, a date, and a scope, and the next job starts from the object.",[220,1039,1041],{"id":1040},"what-the-next-run-is-allowed-to-inherit","What the next run is allowed to inherit",[202,1043,1044],{},"The first close proves the chain can be built. The second close is where it earns its cost. A later run preparing commentary should meet the earlier exception as a relation it can cite: who signed it, which contract it binds, whether the date still holds. If the exception remains in force, the draft quotes it. If it has lapsed, the run says so and stops, rather than extending a treatment because last quarter’s prose sounded settled. Inheritance here is a relation a person can expire, narrow, or refuse to apply. It is not a model’s recollection of a thread.",[202,1046,1047,1048,1052],{},"Departments compound when they share that relation. Legal’s sign-off on a clause helps finance only once finance’s workstream can see it without asking legal to paste the email again. Support can see that a concession was refused and can stop drafting a near-copy for the next customer. The human join shrinks because the next brief starts from the chain, not from whoever remembers the meeting. ",[209,1049,1051],{"href":1050},"\u002Fblog\u002Fwhat-is-collaborative-ai\u002F","Collaborative work"," is this handoff: several functions, one operational story, a model that drafts inside it.",[202,1054,1055],{},"There is a failure mode that looks like compounding and is only a larger pile. If every chat is ingested into an index and treated as authority, last quarter’s wrong draft becomes this quarter’s source. The graph has to be selective. Released outcomes, current policy versions, and explicit refusals are inheritable. Unreleased brainstorming is not. A refusal is as useful as an approval: it tells the next swarm which treatment was already declined, and by whom. Teams that store only the happy path will relitigate the same bad idea every cycle, fluently.",[238,1057,1058,1068],{},[241,1059,1060],{},[244,1061,1062,1065],{},[247,1063,1064],{},"What may pass to the next run",[247,1066,1067],{},"What stays out of the inheritance",[257,1069,1070,1078,1086,1094],{},[244,1071,1072,1075],{},[262,1073,1074],{},"A signed exception, with its date and the contract it binds",[262,1076,1077],{},"A draft nobody released",[244,1079,1080,1083],{},[262,1081,1082],{},"The policy version that was in force",[262,1084,1085],{},"A superseded page left in an index because it embedded well",[244,1087,1088,1091],{},[262,1089,1090],{},"A refusal, with the reason and the role that refused",[262,1092,1093],{},"A personal scroll the company cannot administer",[244,1095,1096,1099],{},[262,1097,1098],{},"The system of record the outcome was written to",[262,1100,1101],{},"A second copy of the number, kept because the chat “had context”",[202,1103,1104,1105,1108],{},"Bi-temporal discipline is what keeps a correction from laundering history. When a milestone is later found to have been met on a different date, the company records both the new fact and the moment it learned the new fact. The commentary that shipped in March remains explicable: it was written against what was known in March. A scroll that is edited, or a vector index that quietly re-chunks, cannot show that distinction. Auditors and successors ask it constantly. ",[209,1106,1107],{"href":211},"The ICO’s expectation that you can explain why data was used"," is the privacy version of the same question. The operational version is “why did we recognise this line?”",[220,1110,1112],{"id":1111},"what-to-stop-storing-only-in-the-thread","What to stop storing only in the thread",[202,1114,1115,1116,1119],{},"Pick the decisions that already cause arguments: revenue, concessions, coverage, access, anything a customer can screenshot. For each, require the chain before the outcome is allowed to stand. If the work happened in a personal chat, it has not happened as far as the record is concerned — which means you either bring it into the workstream or you accept that you cannot explain it. ",[209,1117,1118],{"href":234},"Shadow use is already a breach-cost problem",", not only a knowledge problem. The same paste that fragments context is the paste that leaves.",[202,1121,1122],{},"Do not fund a “memory” programme that is only a larger index. Fund the relations: version, authority, scope, and the link to the system that actually holds the fact. Search remains how people enter. The graph is what they are entering.",[220,1124,1126],{"id":1125},"a-call-to-chief-information-officers","A call to chief information officers",[202,1128,1129],{},"The chat window will not get less convenient. People will keep it for drafting that does not touch a decision. The decisions themselves have to leave a chain your successor can open. That is not a knowledge-management fashion. It is how you keep a single operational story once every team has a model.",[202,1131,1132],{},"If the only answer to “why did this change?” is a transcript nobody can find, the company does not yet have institutional memory. It has a collection of sittings. The graph is the difference.",[583,1134],{},[220,1136,588],{"id":587},[590,1138,1139,1143,1148,1153,1158,1162,1166],{},[593,1140,1141],{},[209,1142,621],{"href":397},[593,1144,1145],{},[209,1146,1147],{"href":708},"W3C, PROV-Overview",[593,1149,1150],{},[209,1151,1152],{"href":726},"McKinsey, The State of AI: Global Survey 2025",[593,1154,1155],{},[209,1156,1157],{"href":490},"Moffatt v. Air Canada, 2024 BCCRT 149",[593,1159,1160],{},[209,1161,627],{"href":626},[593,1163,1164],{},[209,1165,597],{"href":211},[593,1167,1168],{},[209,1169,611],{"href":234},{"title":169,"searchDepth":170,"depth":170,"links":1171},[1172,1173,1174,1175,1176,1177,1178,1179,1180],{"id":713,"depth":170,"text":714},{"id":802,"depth":170,"text":803},{"id":881,"depth":170,"text":882},{"id":930,"depth":170,"text":931},{"id":1018,"depth":170,"text":1019},{"id":1040,"depth":170,"text":1041},{"id":1111,"depth":170,"text":1112},{"id":1125,"depth":170,"text":1126},{"id":587,"depth":170,"text":588},"Why linear chat scroll logs trap critical project context, and how graph-based state models create transparent, signable audit trails.",{"eyebrow":640,"title":1183},"The chain, not the scroll",[1185,1188,1191],{"question":1186,"answer":1187},"What fails when context lives in personal chats?","The next person cannot open the chain from question to outcome. The model is not the only failure.",{"question":1189,"answer":1190},"What does a lifecycle graph keep?","The cause and effect of the work, so the decision can be reopened after the chat is gone.",{"question":1192,"answer":1193},"Is exporting the transcript enough?","No. A scroll is a sequence of messages. A graph is the relationship between the question, the evidence, the approval, and the result.","\u002Fblog\u002Fthe-lifecycle-graph-and-the-chat-scroll",{"title":686,"description":1181},"blog\u002Fthe-lifecycle-graph-and-the-chat-scroll",[657,1198,1199,1200],"lifecycle-graph","knowledge","operations","MIt1VQeBv1pEKZ26ngcL5LatJykT-GHqz6TPa1QviM4",{"id":1203,"title":1204,"archived":163,"authors":1205,"badge":1207,"body":1208,"date":637,"definedTerm":164,"department":164,"description":1801,"extension":172,"eyebrow":164,"faqHeader":1802,"faqs":1804,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1814,"relatedHeading":164,"seo":1815,"series":654,"sitemap":131,"status":164,"stem":1816,"subhead":164,"tags":1817,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1821},"content\u002Fblog\u002Fthe-financial-mechanics-of-ai-workloads.md","The Financial Mechanics of AI: Accounting for Compute over Seats",[1206],{"name":689,"to":196},{"label":198},{"type":166,"value":1209,"toc":1791},[1210,1213,1216,1221,1225,1228,1231,1242,1304,1308,1316,1319,1322,1330,1412,1416,1419,1425,1431,1437,1443,1504,1510,1514,1517,1520,1523,1530,1591,1595,1598,1605,1608,1620,1674,1678,1681,1684,1687,1749,1753,1756,1759,1761,1763],[202,1211,1212],{},"Procurement knows how to buy a login. A person, a month, a price that moves when headcount moves. The comparison set is email, documents, a CRM seat. Finance can forecast it. The board can be told the cost is predictable because the workforce is predictable.",[202,1214,1215],{},"Agent work does not behave like a login. One analyst might ask three questions. A workstream might read a contract set, call a ledger, draft, get refused, draft again, and stop before anyone posts a journal — or it might not stop, and the meter continues. Two customers with the same headcount will consume wildly different inference once one of them lets runs touch real volume. The seat was the easy line. The workload is the bill that arrives as a variance, an overage, or a second product bought because the first could not be capped.",[202,1217,1218,1220],{},[209,1219,727],{"href":726}," is why this matters now rather than later. Eighty-eight percent of organisations use AI in at least one function. Nearly two-thirds have not scaled it. The invoice does not wait for the operating model. Companies are paying seat prices for a pattern of use that is still a pilot, and they cannot say which jobs consumed the money. A unit of work is how the bill becomes something a finance committee can approve, cap, and stop.",[220,1222,1224],{"id":1223},"why-the-seat-breaks","Why the seat breaks",[202,1226,1227],{},"A seat assumes the costly thing is the person being entitled to open the application. For a chat window used a few times a day, that assumption roughly holds, which is why the first wave of enterprise assistants was sold that way. It stops holding when the entitled actor is a run that can loop.",[202,1229,1230],{},"Loops multiply cost without multiplying headcount. A simulation that tries several treatments of a revenue line, a swarm that reviews a queue overnight, a retry that calls a tool again because the first response was malformed: none of these appear as a new employee. They appear as inference, retrieval, and orchestration. If the contract only knows seats, those units are either bundled until they are not, or they spill into a cloud invoice nobody mapped to a job. Finance then meets the programme as a surprise. Surprises are how standing orders survive reviews that should have killed them.",[202,1232,1233,1234,1237,1238,1241],{},"There is a second distortion. Seats are bought for people. A large share of actual use is not on the enterprise seat at all. ",[209,1235,1236],{"href":397},"Seventy-eight percent of AI users bring their own tools",". Those subscriptions are small. The work done inside them is off the ledger the board approved, and off the log. The official seat bill is a lower bound on both spend and risk. ",[209,1239,1240],{"href":234},"IBM’s 2025 figures"," put a cost on the shadow path: one in five studied breaches involved shadow AI, and high shadow use was associated with about $670,000 in higher average breach cost. A seat true-up will not show that number. A workload view at least tells you which sanctioned jobs exist, so the unsanctioned ones are the residual rather than the whole practice.",[238,1243,1244,1254],{},[241,1245,1246],{},[244,1247,1248,1251],{},[247,1249,1250],{},"Seat",[247,1252,1253],{},"Workload",[257,1255,1256,1264,1272,1280,1288,1296],{},[244,1257,1258,1261],{},[262,1259,1260],{},"Forecast from headcount",[262,1262,1263],{},"Forecast from jobs and their ceilings",[244,1265,1266,1269],{},[262,1267,1268],{},"One person, one login, roughly similar use",[262,1270,1271],{},"A quiet user and an overnight review are different orders of cost",[244,1273,1274,1277],{},[262,1275,1276],{},"Overage is a surprise or a true-up",[262,1278,1279],{},"Quoted work pauses. More units are a pack or a commitment you choose",[244,1281,1282,1285],{},[262,1283,1284],{},"“Adoption” is the success metric",[262,1286,1287],{},"A stopped run is a success metric",[244,1289,1290,1293],{},[262,1291,1292],{},"Shadow subscriptions sit outside the true-up",[262,1294,1295],{},"Unsanctioned use is visible as work that never hit a job identifier",[244,1297,1298,1301],{},[262,1299,1300],{},"The business case is a vendor calculator",[262,1302,1303],{},"The business case names a job, a baseline, and a cancelled cost",[220,1305,1307],{"id":1306},"the-unit-is-the-run-not-the-chair","The unit is the run, not the chair",[202,1309,1310,1311,1315],{},"Nimbus meters use in Nimbus Token Units. An NTU is a prepaid unit of completed work: analysis that retrieves or calls tools, governed runs, reports, writes, index jobs. It is a work credit. It is not a raw count of the tokens a model vendor bills wholesale, and it is not a fraction of a seat. Lightweight questions that do not retrieve or call tools can sit outside that meter; the moment the work becomes a run against company data, it draws the pool. Current plan figures, and the line between the two, belong on the ",[209,1312,1314],{"href":1313},"\u002Fpricing\u002F","pricing"," page. They will move. The mechanic is what finance should understand when the price changes.",[202,1317,1318],{},"The pool is organisational. Operators share one allowance for the period. A quiet login does not trap a private bundle the close cannot use, and a busy login does not receive a larger bundle merely because a seat was added. On the published plans, extra seats entitle more people to start work. They do not enlarge the NTU pool. Capacity is a separate decision: a higher allowance, a commitment, or a pack bought with eyes open. That split is the point. Headcount and workload are different budgets. Binding them back together is how the seat model hides the bill.",[202,1320,1321],{},"High-commitment work shows a quote and a ceiling before anyone confirms it. The operator sees the units this brief is expected to consume, and the point at which the run will halt. A failed run does not book units. A successful retry books the quoted work once. Near the top of the pool, quoted work pauses until someone adds capacity or the period resets. The pause is the control. A meter that continues and invoices is a different product, and it should be bought as that product, on purpose.",[202,1323,1324,1325,1329],{},"The unit also gives procurement a question the seat never did. What does this job cost in units, and what happens at the ceiling? A product that continues and bills is a different risk from a product that stops and records the stop. Put the stop in the order. A warning is a suggestion. ",[209,1326,1328],{"href":1327},"\u002Fblog\u002Fwhat-is-ai-token-economics\u002F","The same discipline applies to any meter sold as intelligence",": if you cannot join the unit to a job identifier you already use for cost centres, you have a recollection, not a cost system.",[238,1331,1332,1344],{},[241,1333,1334],{},[244,1335,1336,1338,1341],{},[247,1337,826],{},[247,1339,1340],{},"Seat answer",[247,1342,1343],{},"NTU answer",[257,1345,1346,1357,1368,1379,1390,1401],{},[244,1347,1348,1351,1354],{},[262,1349,1350],{},"What are we buying?",[262,1352,1353],{},"The right to log in",[262,1355,1356],{},"Units consumed when runs execute, pooled across operators",[244,1358,1359,1362,1365],{},[262,1360,1361],{},"Who can starve whom?",[262,1363,1364],{},"A quiet seat hoards its bundle",[262,1366,1367],{},"The pool follows the job, inside a ceiling",[244,1369,1370,1373,1376],{},[262,1371,1372],{},"What happens when use spikes?",[262,1374,1375],{},"A surprise, or a true-up after the fact",[262,1377,1378],{},"Quoted work pauses until you add capacity on purpose",[244,1380,1381,1384,1387],{},[262,1382,1383],{},"Can we stop a runaway job?",[262,1385,1386],{},"Not if the seat is simply “on”",[262,1388,1389],{},"A workspace or run cap halts execution and leaves a record",[244,1391,1392,1395,1398],{},[262,1393,1394],{},"What do we show the board?",[262,1396,1397],{},"Licences versus last year",[262,1399,1400],{},"Units, stops, and the job they belonged to",[244,1402,1403,1406,1409],{},[262,1404,1405],{},"What does another seat buy?",[262,1407,1408],{},"Another login, and often a vague sense of more capacity",[262,1410,1411],{},"Another person who may start work. The pool stays the pool until you change it",[220,1413,1415],{"id":1414},"what-the-unit-is-counting","What the unit is counting",[202,1417,1418],{},"A finance partner should be able to say, without a vendor engineer in the room, which activities draw the meter. Four do, in practice.",[202,1420,1421,1424],{},[460,1422,1423],{},"Model work that is actually a job."," A short question with no company context is cheap and often unmetered. A pass that reads a contract set, drafts against a policy, and revises after a refusal is the workload. The unit collapses that activity into something a cost centre can hold. It does not pretend that every prompt costs the same.",[202,1426,1427,1430],{},[460,1428,1429],{},"Tool calls."," Each reach into a ledger, a file store, or a ticket system is work, and it is also a place the run can loop. A malformed response that is retried is a second call. The ceiling is what stops “retry until it looks right” from becoming an unbounded invoice. If the connector can write, the retry is no longer only a cost. It is a second side effect, which is why the quote and the release belong together.",[202,1432,1433,1436],{},[460,1434,1435],{},"Retrieval and indexing."," Grounding a run in the current playbook and the current records has a cost the first time the corpus is prepared, and a smaller cost when the same job runs again against material the workspace already holds. That is the economic content of “context that compounds.” The first forecast pack pays to assemble the sources. A later pack, on the same workstream, should be able to start from the chain and the playbook version rather than from a blank paste. Treat any specific decline in the quote as a design aim you can watch on your own usage, not as a saving a brochure has already booked.",[202,1438,1439,1442],{},[460,1440,1441],{},"Orchestration."," Splitting a brief across specialist passes costs more than a single window, and it is often the correct spend. You are buying a finance pass that cannot send mail and a policy pass that cannot invent a clause. The unit makes that choice visible. A single generalist prompt can look thrifty on the meter and expensive in concessions. Attribute both the units and the outcome, or the cheap run will win every review and lose on the customer sentence.",[238,1444,1445,1458],{},[241,1446,1447],{},[244,1448,1449,1452,1455],{},[247,1450,1451],{},"Activity",[247,1453,1454],{},"Why it belongs on the meter",[247,1456,1457],{},"What a ceiling is for",[257,1459,1460,1471,1482,1493],{},[244,1461,1462,1465,1468],{},[262,1463,1464],{},"A governed run against company data",[262,1466,1467],{},"This is the workload that replaces a seat’s fiction of “similar use”",[262,1469,1470],{},"Halt a brief that would otherwise loop",[244,1472,1473,1476,1479],{},[262,1474,1475],{},"Tool calls",[262,1477,1478],{},"External systems are where cost and side effects accumulate",[262,1480,1481],{},"Stop a retry from becoming a second write",[244,1483,1484,1487,1490],{},[262,1485,1486],{},"Indexing and retrieval",[262,1488,1489],{},"The first assembly of sources is real work",[262,1491,1492],{},"Keep corpus jobs inside a period allowance",[244,1494,1495,1498,1501],{},[262,1496,1497],{},"Specialist orchestration",[262,1499,1500],{},"Separation of mandates is worth paying for",[262,1502,1503],{},"Prevent a swarm from spending past the job’s value",[202,1505,1506,1509],{},[209,1507,1508],{"href":1327},"The same questions apply to any meter sold as intelligence",". If the unit cannot be joined to a job identifier you already use for cost centres, you have a recollection. If failed work is billed the same as finished work, you will hesitate to stop a bad run. If another seat silently buys more inference, you are back to forecasting cost from headcount.",[220,1511,1513],{"id":1512},"caps-before-the-swarm-starts","Caps before the swarm starts",[202,1515,1516],{},"Financial control that arrives in the monthly invoice is archaeology. The run has finished. The money is spent. The review explains. Caps move the decision to before the long job starts, which is the only moment a finance partner can still say no.",[202,1518,1519],{},"Three levels are enough. A workspace pool is the budget for a team’s runs this period. A workstream estimate is what this brief is expected to consume before specialists start, shown to the operator in units rather than discovered afterwards. A hard stop is the point at which the run halts even if the model would like another pass. Soft warnings exist for people who are watching. They are not the control. The control is the halt, recorded, so “we explored” cannot be confused with “we overran.”",[202,1521,1522],{},"Approval gates belong next to the cap when the run is allowed to cause a side effect or to spend past a threshold a manager cares about. A simulation that only drafts can be cheap to retry. A simulation that is about to post, send, or pay is no longer a metering question. It is a release question. The person who releases it should see the cost and the payload together. Splitting them — finance sees the bill next month, operations sees the sentence now — is how both miss the decision.",[202,1524,1525,1526,1529],{},"This is ordinary commitment control applied to a new meter. You would not let a plant order materials with no purchase-order limit because the vendor’s interface was conversational. Do not let a swarm do it because the interface is a brief. ",[209,1527,1528],{"href":626},"NIST’s govern-and-measure language"," is the public version. The internal version is a ceiling that fires.",[238,1531,1532,1545],{},[241,1533,1534],{},[244,1535,1536,1539,1542],{},[247,1537,1538],{},"Gate",[247,1540,1541],{},"When it fires",[247,1543,1544],{},"What “fired” looks like in the pack",[257,1546,1547,1558,1569,1580],{},[244,1548,1549,1552,1555],{},[262,1550,1551],{},"Estimate before start",[262,1553,1554],{},"The operator sees expected units for this brief",[262,1556,1557],{},"A number, not “it depends”",[244,1559,1560,1563,1566],{},[262,1561,1562],{},"Workspace pool",[262,1564,1565],{},"The team’s period allowance is exhausted",[262,1567,1568],{},"New runs wait, or overage is explicitly on",[244,1570,1571,1574,1577],{},[262,1572,1573],{},"Hard stop on a run",[262,1575,1576],{},"The brief hits its own cap mid-flight",[262,1578,1579],{},"The run halts. The halt is stored",[244,1581,1582,1585,1588],{},[262,1583,1584],{},"Release on a write or a high spend",[262,1586,1587],{},"A person must see payload and cost",[262,1589,1590],{},"A name, or the action did not happen",[220,1592,1594],{"id":1593},"attribute-the-unit-to-a-signed-outcome","Attribute the unit to a signed outcome",[202,1596,1597],{},"Units are not a benefit. They are a cost. The benefit is a job that finished: a commentary a controller will sign, a claim answered against the current rule, a queue cleared without a rise in reopen rate. Roi that stops at “hours saved,” especially hours a vendor modelled, is the personal clock. The operating clock is elapsed time, quality, and a step you actually deleted, set against a baseline you froze before the run was allowed in.",[202,1599,1600,1601,1604],{},"Join them. For each workstream worth money, report units consumed, whether it stopped at a ceiling, whether a person released or refused the output, and what happened to the external measure you already trust — concessions, rework, a contractor line. A month of units and no refusals is a month you bought fluency without a control. A month of units and no movement in the job is a popular meter. ",[209,1602,1603],{"href":726},"Most organisations are still in that pattern",". The ones that leave it will be the ones whose finance team can point at five jobs and say what the units bought.",[202,1606,1607],{},"Do not book a saving from the meter. Book a saving when the job got shorter or cheaper against the baseline, the error rate did not worsen, and something left the calendar or the contractor list. Hold headcount claims until that cycle has happened. Taking the seat-count “efficiency” in the announcement is how the cost returns later as complaints and contractors under another name.",[202,1609,1610,1614,1615,1619],{},[209,1611,1613],{"href":1612},"https:\u002F\u002Fwww.sec.gov\u002Fnewsroom\u002Fpress-releases\u002F2024-36","Public cases about describing a capability you cannot show"," are a useful constraint on the business case itself. “AI-driven savings” is a claim. If the evidence is a unit total and a survey of people who feel faster, say that, and do not say more. ",[209,1616,1618],{"href":1617},"https:\u002F\u002Fwww.ftc.gov\u002Fbusiness-guidance\u002Fblog\u002F2023\u002F02\u002Fkeep-your-ai-claims-check","The FTC’s instruction on AI claims"," is aimed at advertisers. It is also a sound rule for an internal pack.",[238,1621,1622,1632],{},[241,1623,1624],{},[244,1625,1626,1629],{},[247,1627,1628],{},"Show this",[247,1630,1631],{},"Do not show this as the result",[257,1633,1634,1642,1650,1658,1666],{},[244,1635,1636,1639],{},[262,1637,1638],{},"Units by workstream, and stops",[262,1640,1641],{},"A single platform total labelled “adoption”",[244,1643,1644,1647],{},[262,1645,1646],{},"Release or refusal beside the units",[262,1648,1649],{},"A month of spend with no refusal",[244,1651,1652,1655],{},[262,1653,1654],{},"Baseline versus outcome on the job",[262,1656,1657],{},"A vendor calculator of hours saved",[244,1659,1660,1663],{},[262,1661,1662],{},"The contractor or meeting that disappeared",[262,1664,1665],{},"A headcount reduction taken before the quality cycle",[244,1667,1668,1671],{},[262,1669,1670],{},"Overage, if you chose it, as a conscious rate",[262,1672,1673],{},"A cloud variance nobody can name",[220,1675,1677],{"id":1676},"one-recurring-pack-attributed","One recurring pack, attributed",[202,1679,1680],{},"Consider a commentary workstream finance already trusts enough to put in front of a controller. Before the first run, the operator sees a quote in units and a ceiling. The brief names the finish: a pack that cites the ledger and the playbook, and does not post. The run either completes inside the ceiling or halts and records the halt. Units book when the run succeeds. The person who will sign the pack is the person who releases it. Next month the same workstream runs again. The quote is visible again. If the workspace already holds the sources and the prior release, the quote can come down. You will see that on the usage record if it happens. You should not put a brochure’s illustration into the board pack as if it were your result.",[202,1682,1683],{},"The attribution line is short. Workstream name. Units booked. Whether it halted. Whether a person released or refused. The external measure you already track for that job: cycle time to a signed pack, number of restatements, a contractor day you did not buy. A quarter of those lines is a cost system. A quarter of platform-wide totals labelled “AI spend” is a variance with a new name.",[202,1685,1686],{},"Procurement’s schedule can require the mechanic without freezing a price that will move. Define the unit as completed work, not as a wholesale model token and not as a seat. State that the allowance is pooled at the organisation, and that seats do not increase it. State what happens near exhaustion: an alert, then a pause of quoted work, until someone adds capacity on purpose. State that a failed run does not book. State that usage can be exported by workstream, beside the release. A vendor that can only invoice seats, or can only invoice after the overrun, has not met the schedule. Pay them for a chat window if that is what you want. Do not pay them as if they had sold a workload you can stop.",[238,1688,1689,1699],{},[241,1690,1691],{},[244,1692,1693,1696],{},[247,1694,1695],{},"Put this in the order",[247,1697,1698],{},"The answer that counts",[257,1700,1701,1709,1717,1725,1733,1741],{},[244,1702,1703,1706],{},[262,1704,1705],{},"What is the unit?",[262,1707,1708],{},"Completed governed work, pooled, separate from the seat",[244,1710,1711,1714],{},[262,1712,1713],{},"What does a seat add?",[262,1715,1716],{},"A person who may start work. Not a larger inference budget",[244,1718,1719,1722],{},[262,1720,1721],{},"What happens before a long run?",[262,1723,1724],{},"A quote and a ceiling the operator can see",[244,1726,1727,1730],{},[262,1728,1729],{},"What happens if the run fails?",[262,1731,1732],{},"It does not book. A successful retry books once",[244,1734,1735,1738],{},[262,1736,1737],{},"What happens when the pool is exhausted?",[262,1739,1740],{},"Quoted work pauses. More capacity is a decision",[244,1742,1743,1746],{},[262,1744,1745],{},"What do we receive each month?",[262,1747,1748],{},"Units, halts, and releases by workstream",[220,1750,1752],{"id":1751},"a-call-to-chief-financial-officers","A call to chief financial officers",[202,1754,1755],{},"Keep the seat if you need to know how many people may start work. Do not let the seat be the cost system. Ask for the unit, the pool, the ceiling, and the stop. Ask which jobs consumed last month’s units and which of those jobs changed a number you already manage. Freeze the lines you cannot map.",[202,1757,1758],{},"The argument worth having is no longer whether the company will “do AI.” People already are. The argument is which jobs are worth the next increment of units, and which runs should halt. That is a finance conversation. The meter has to be built so the conversation can happen before the invoice, not after it.",[583,1760],{},[220,1762,588],{"id":587},[590,1764,1765,1769,1773,1777,1781,1786],{},[593,1766,1767],{},[209,1768,1152],{"href":726},[593,1770,1771],{},[209,1772,621],{"href":397},[593,1774,1775],{},[209,1776,611],{"href":234},[593,1778,1779],{},[209,1780,627],{"href":626},[593,1782,1783],{},[209,1784,1785],{"href":1612},"U.S. SEC press release 2024-36",[593,1787,1788],{},[209,1789,1790],{"href":1617},"U.S. FTC, Keep your AI claims in check",{"title":169,"searchDepth":170,"depth":170,"links":1792},[1793,1794,1795,1796,1797,1798,1799,1800],{"id":1223,"depth":170,"text":1224},{"id":1306,"depth":170,"text":1307},{"id":1414,"depth":170,"text":1415},{"id":1512,"depth":170,"text":1513},{"id":1593,"depth":170,"text":1594},{"id":1676,"depth":170,"text":1677},{"id":1751,"depth":170,"text":1752},{"id":587,"depth":170,"text":588},"How agentic AI shifts enterprise IT budgeting from per-seat SaaS headcount pricing to variable compute and tool-execution costs.",{"eyebrow":640,"title":1803},"A unit of work, with a ceiling",[1805,1808,1811],{"question":1806,"answer":1807},"Why does a seat price misdescribe an agent?","A seat is a person with a login. An agent run is compute, tool calls, and a job that may never map to a headcount line.",{"question":1809,"answer":1810},"How should the bill be shaped?","As a unit of work, with a ceiling, before it is a subscription.",{"question":1812,"answer":1813},"What should finance see before the run?","A quote for the job and a cap that stops it. Unlimited AI is not a control.","\u002Fblog\u002Fthe-financial-mechanics-of-ai-workloads",{"title":1204,"description":1801},"blog\u002Fthe-financial-mechanics-of-ai-workloads",[657,1818,1819,1820],"finance","procurement","token-economics","SYkeMl_8eKvtn37lxnq2dvkKA-TGilDBuEC_pGQWLlA",{"fold":1823,"id":1827,"title":1828,"archived":163,"authors":164,"badge":164,"body":1829,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":1833,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1837,"relatedHeading":164,"seo":1838,"series":164,"sitemap":163,"status":164,"stem":1839,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1840},{"headline":1824,"description":1825,"primaryLabel":8,"primaryTo":1826,"secondaryLabel":678,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed workstreams, 3,000+ integrations, and a proprietary knowledge graph. Start on Free.","\u002Fsignup?plan=free","content\u002Fshared\u002Fcta.md","Site CTAs",{"type":166,"value":1830,"toc":1831},[],{"title":169,"searchDepth":170,"depth":170,"links":1832},[],{"headline":1834,"description":1835,"primaryLabel":8,"primaryTo":1826,"secondaryLabel":1836,"secondaryTo":85},"See what governed AI looks like on your stack.","Connect your tools, run a workstream, and keep every decision on your ledger. Start on Free.","Talk to our team","\u002Fshared\u002Fcta",{"title":1828,"description":169},"shared\u002Fcta","eYqahyaPnbp8GKrWpoORbZdtmkWmgHr5F61ZHOnb8sY",1791647063103]