[{"data":1,"prerenderedAt":1667},["ShallowReactive",2],{"site-nav-content":3,"hiring-banner-content":177,"blog:\u002Fblog\u002Fwhat-is-ai-token-economics":189,"blog-index-copy":706,"blog:\u002Fblog\u002Fwhat-is-ai-token-economics:surround":727,"site-cta-content":1648},{"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":196,"body":198,"date":682,"definedTerm":164,"department":164,"description":683,"extension":172,"eyebrow":164,"faqHeader":684,"faqs":687,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":697,"relatedHeading":164,"seo":698,"series":699,"sitemap":131,"status":164,"stem":700,"subhead":164,"tags":701,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":705},"content\u002Fblog\u002Fwhat-is-ai-token-economics.md","What is AI Token Economics",[193],{"name":194,"to":195},"Nimbus Research","https:\u002F\u002Fgonimbus.ai",{"label":197},"Explainer",{"type":166,"value":199,"toc":657},[200,220,226,229,237,242,336,347,351,354,374,377,400,403,408,418,424,430,436,445,449,455,465,471,479,490,502,506,509,515,527,531,535,538,542,545,549,552,556,561,565,568,572,575,579,584,588,591,595,598,602,609,613,618,622,625,629,636,640],[201,202,203,204,208,209,214,215,219],"p",{},"A ",[205,206,207],"strong",{},"token"," is a chunk of text the model reads or writes. You pay per chunk. Different models cost different amounts. Input, output, and sometimes tools all meter differently. ",[210,211,213],"a",{"href":212},"https:\u002F\u002Fopenai.com\u002Fapi\u002Fpricing\u002F","OpenAI"," and ",[210,216,218],{"href":217},"https:\u002F\u002Fwww.anthropic.com\u002Fpricing","Anthropic"," publish those ladders. Finance still cannot run the business on “12 million tokens of vendor A’s flagship.”",[201,221,222,225],{},[205,223,224],{},"AI token economics"," is treating that usage like a real budget: measuring, allocating, controlling, and attributing spend so operators can quote before a run, cap during it, and attribute after it — instead of a slide that says “unlimited AI.”",[201,227,228],{},"Without it, organisations either freeze (no production AI) or send every small task to the most expensive model until the bill becomes a board slide.",[201,230,231,232,236],{},"The unit problem is the same one cloud had in its first decade: a metered resource sold with a headcount story. Seat licences predict people. Inference predicts work. When those two are collapsed into “unlimited,” the next chunk ",[233,234,235],"em",{},"feels"," free, so people pick the flagship every time. The ladder did not disappear. It hid.",[238,239,241],"h2",{"id":240},"words-youll-hear","Words you’ll hear",[243,244,245,252,258,269,279,285,291,302,308,319,325],"ul",{},[246,247,248,251],"li",{},[205,249,250],{},"Token."," A piece of text the model processes. Not a business unit. At work, a long wiki dump and a short field extract are wildly different token counts for the same “question.”",[246,253,254,257],{},[205,255,256],{},"Seat licence."," Predictable cost per person. Often marketed as “unlimited.” The underlying work is still metered.",[246,259,260,263,264,268],{},[205,261,262],{},"Pass-through API bill."," Each team has keys. Simple. Invites key sprawl and ",[210,265,267],{"href":266},"\u002Fblog\u002Fwhat-is-shadow-ai\u002F","shadow AI"," on personal keys. At work, the invoice lands in engineering while go-to-market did the looping.",[246,270,271,274,275,278],{},[205,272,273],{},"Quote."," A number ",[233,276,277],{},"before"," they run. At work, this is what makes a brief a decision rather than a surprise.",[246,280,281,284],{},[205,282,283],{},"Cap \u002F ceiling."," A hard stop. The loop cannot spend past it. At work, weekend agent loops die here instead of in next month’s cloud bill.",[246,286,287,290],{},[205,288,289],{},"Pool."," Organisation-level allowance. At work, one department should not be able to burn the company pool on a vanity run.",[246,292,293,296,297,301],{},[205,294,295],{},"Attribution."," Chargeback by job, not “the AI bill.” At work, finance can ask which ",[210,298,300],{"href":299},"\u002Fblog\u002Fwhat-is-an-ai-workstream\u002F","workstream"," consumed the units.",[246,303,304,307],{},[205,305,306],{},"NTU (Nimbus Token Unit)."," Nimbus’s normalised work credit for completed AI activity — analysis, tools, runs, writes — sitting above raw provider tokens. Everyday questions can be included; heavier work consumes pool credits. Finance gets one tape measure across vendors and steps.",[246,309,310,313,314,318],{},[205,311,312],{},"Model routing."," Cheaper model for simple steps, stronger only when needed. See ",[210,315,317],{"href":316},"\u002Fblog\u002Fwhat-is-model-routing\u002F","What is model routing",". At work, classify-this-ticket should not pay flagship rates.",[246,320,321,324],{},[205,322,323],{},"Context window."," How much text the model can see at once. Dumping the whole Drive into context is an economic choice, not a quality strategy.",[246,326,327,330,331,335],{},[205,328,329],{},"Stop condition."," Budget hit, empty result, human cancel. Agent loops can dominate the bill without improving the artefact. See ",[210,332,334],{"href":333},"\u002Fblog\u002Fwhat-is-an-agentic-workflow\u002F","What is an agentic workflow",".",[201,337,338,339,342,343,346],{},"The point is ",[205,340,341],{},"value per unit",", not minimum units regardless of outcome. Caching, wiki citations, and memory should make the ",[233,344,345],{},"same"," outcome cheaper over time. If unit cost of an approved update never falls, you are re-deriving folklore every run.",[238,348,350],{"id":349},"why-you-should-care","Why you should care",[201,352,353],{},"It affects you if you:",[243,355,356,362,368],{},[246,357,358,361],{},[205,359,360],{},"Own the budget."," Surprise invoices arrive after agents looped all weekend.",[246,363,364,367],{},[205,365,366],{},"Run the work."," You should see a number before you commit, not a lecture after.",[246,369,370,373],{},[205,371,372],{},"Are tempted to shame people for using AI."," Shame drives personal keys. Cap the official path so it is safe to use.",[201,375,376],{},"Practical rhythm:",[243,378,379,388,394],{},[246,380,381,384,385,387],{},[205,382,383],{},"Name the run."," Unnamed chats cannot be attributed. That is what a ",[210,386,300],{"href":299}," is for.",[246,389,390,393],{},[205,391,392],{},"Separate exploration from production."," Sandboxes can have tighter caps and cheaper default routes.",[246,395,396,399],{},[205,397,398],{},"Review unit cost of outcomes"," — approved updates per unit — not tokens in the abstract.",[201,401,402],{},"Anti-pattern: a single corporate API key in a wiki, no per-job cap, monthly surprise. That is an unmetered utility.",[404,405,407],"h3",{"id":406},"what-changes-by-role","What changes by role",[201,409,410,413,414,417],{},[205,411,412],{},"Finance."," You need a quote, a ceiling, and a chargeback dimension that matches how the business already thinks — by job, department, or cost centre — not by vendor token type. Multi-vendor ladders are incomparable until you normalise. NTU is that normalisation in Nimbus. Finance should also see ",[233,415,416],{},"stops",": a cap that fired is a successful control, not a failed project.",[201,419,420,423],{},[205,421,422],{},"Legal."," Spend logs are not only money. They are a map of which data classes went to which provider. Uncapped personal keys are a processing-agreement gap. Legal will also ask whether you can stop a run, not only whether you can pay for it.",[201,425,426,429],{},[205,427,428],{},"Operations."," Caps are operational stops, like a queue limit. Ops needs to know whether a paused run is waiting on a person or waiting on budget. Mixing those two in one “it failed” status is how you get the wrong pager.",[201,431,432,435],{},[205,433,434],{},"Go-to-market."," GTM feels the quality-versus-cost trade first. A compact model that extracts fields is usually enough. A flagship model that argues a clause may be worth it. Without routing and quotes, GTM either hoards “the best model” or gets blamed for the bill. Neither produces better pipeline hygiene.",[201,437,438,441,442,444],{},[205,439,440],{},"Security."," API keys are credentials. Personal keys in browser plugins are ",[210,443,267],{"href":266},". A pooled official path with per-workstream ceilings reduces key sprawl. Spend spikes can also be an anomaly signal — a loop that never stops is sometimes a bug, sometimes a prompt-injection success.",[404,446,448],{"id":447},"what-people-get-wrong","What people get wrong",[201,450,451,454],{},[205,452,453],{},"“Unlimited” as a strategy."," Seats hide the ladder. They do not delete it. Heavy agentic work will still surface as a true-up, a throttle, or a degraded model.",[201,456,457,460,461,464],{},[205,458,459],{},"Punishing usage."," Chargeback without a sanctioned path recreates personal keys. Celebrate lower units ",[233,462,463],{},"per artefact"," as playbooks and memory compound.",[201,466,467,470],{},[205,468,469],{},"Tokens as the KPI."," Tokens measure consumption. Outcomes measure value. A cheap run that produces a rejected write is still waste. A dearer run that produces one approved journal may be fine.",[201,472,473,476,477,335],{},[205,474,475],{},"One model for everything."," That is a routing failure dressed as quality culture. See ",[210,478,317],{"href":316},[201,480,481,484,485,489],{},[205,482,483],{},"No stop on loops."," ",[210,486,488],{"href":487},"https:\u002F\u002Fwww.anthropic.com\u002Fengineering\u002Fbuilding-effective-agents","Anthropic’s note on building effective agents"," treats workflows with stop conditions as the grown-up shape. Economics is one of those stops.",[201,491,492,493,214,497,501],{},"Good looks like: named jobs, quotes before commit, hard ceilings, routing policy, attribution, and falling unit cost as the ",[210,494,496],{"href":495},"\u002Fblog\u002Fwhat-is-a-company-wiki-for-ai-agents\u002F","wiki",[210,498,500],{"href":499},"\u002Fblog\u002Fwhat-is-a-lifecycle-graph\u002F","lifecycle graph"," reduce re-derivation. Failure looks like a shared key, a flagship default, and a board slide titled “AI spend.”",[238,503,505],{"id":504},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[201,507,508],{},"Workstreams show quotes and ceilings before runs. Orgs draw from a pooled NTU allowance. Routing is a policy, not a dropdown labelled “best.” Memory and wiki reduce re-derivation, which is how unit cost of an outcome should fall over time.",[201,510,511,512,514],{},"Everyday questions can sit inside the allowance; heavier analysis, tools, and writes consume pool credits. The ",[210,513,23],{"href":499}," can record spend as part of the chain, so “the run stopped because the ceiling was hit” is a causal fact.",[201,516,517,518,214,521,523,524,335],{},"See ",[210,519,44],{"href":520},"\u002Fmodels\u002F",[210,522,317],{"href":316},". Product context: ",[210,525,31],{"href":526},"\u002Fproduct\u002Fworkstreams\u002F",[238,528,530],{"id":529},"questions-people-actually-ask","Questions people actually ask",[404,532,534],{"id":533},"why-cant-we-just-pay-seats-and-call-it-unlimited","Why can’t we just pay seats and call it unlimited?",[201,536,537],{},"Seats predict headcount. Production AI spend is inference, tools, and writes. “Unlimited” hides the ladder; it does not delete it.",[404,539,541],{"id":540},"what-should-finance-actually-see","What should finance actually see?",[201,543,544],{},"A quote before commit, a cap during the run, and attribution by job afterwards — in one unit they can compare across vendors and steps.",[404,546,548],{"id":547},"wont-cheaper-models-get-worse-answers","Won’t cheaper models get worse answers?",[201,550,551],{},"For extract and classify, often no. For hard judgment, often yes. That is a routing policy, not a religion. Measure reject rates on the job, not vibes.",[404,553,555],{"id":554},"do-we-punish-teams-for-using-ai","Do we punish teams for using AI?",[201,557,558,559,464],{},"No. Punishing usage revives shadow AI. Celebrate lower units ",[233,560,463],{},[404,562,564],{"id":563},"what-is-an-ntu-in-plain-language","What is an NTU in plain language?",[201,566,567],{},"A normalised work credit above raw provider tokens, so a finance partner is not asked to compare “vendor A input tokens” with “vendor B output tokens” plus tool calls. In Nimbus, completed activity — analysis, tools, runs, writes — is what consumes the unit.",[404,569,571],{"id":570},"should-every-chat-be-billed-to-a-cost-centre","Should every chat be billed to a cost centre?",[201,573,574],{},"Named production jobs, yes. Tiny sanctioned copilots for personal drafting can live on a lighter path. The failure is mixing them so neither can be capped.",[404,576,578],{"id":577},"how-do-agent-loops-blow-the-budget","How do agent loops blow the budget?",[201,580,581,582,335],{},"They call tools, re-read context, and retry without a finish line. Without a ceiling and a stop condition, “being thorough” is an unbounded loop. See ",[210,583,334],{"href":333},[404,585,587],{"id":586},"is-caching-the-same-as-token-economics","Is caching the same as token economics?",[201,589,590],{},"Caching is a tactic. Economics is the management system: quote, cap, attribute, route. Caching without attribution still leaves you unable to explain the bill.",[404,592,594],{"id":593},"do-we-need-a-data-warehouse-to-do-this","Do we need a data warehouse to do this?",[201,596,597],{},"You need events at run time. A warehouse can hold copies for reporting. It cannot quote a run that has not emitted a number yet.",[404,599,601],{"id":600},"how-does-this-relate-to-write-back","How does this relate to write-back?",[201,603,604,605,335],{},"Writes are usually a small number of tokens and a large operational risk. Do not use spend as a substitute for a named signer. Do use spend as a stop so a looping agent cannot keep proposing writes all weekend. See ",[210,606,608],{"href":607},"\u002Fblog\u002Fwhat-is-write-back-governance\u002F","What is write-back governance",[404,610,612],{"id":611},"can-we-lock-one-vendor-to-simplify-pricing","Can we lock one vendor to simplify pricing?",[201,614,615,616,335],{},"You can. You will pay for it in price, outages, and lock-in. A normalised unit plus routing is how finance keeps a second tape measure. See ",[210,617,317],{"href":316},[404,619,621],{"id":620},"why-not-just-set-a-monthly-company-cap","Why not just set a monthly company cap?",[201,623,624],{},"A company cap without per-job attribution is a shared kitchen. The loudest workflow starves the others, and nobody can say which job did it.",[238,626,628],{"id":627},"related-reading","Related reading",[201,630,631,214,633,335],{},[210,632,317],{"href":316},[210,634,635],{"href":299},"What is an AI workstream",[238,637,639],{"id":638},"sources","Sources",[243,641,642,647,652],{},[246,643,644],{},[210,645,646],{"href":212},"OpenAI API pricing",[246,648,649],{},[210,650,651],{"href":217},"Anthropic pricing",[246,653,654],{},[210,655,656],{"href":487},"Anthropic, Building effective agents",{"title":169,"searchDepth":170,"depth":170,"links":658},[659,660,665,666,680,681],{"id":240,"depth":170,"text":241},{"id":349,"depth":170,"text":350,"children":661},[662,664],{"id":406,"depth":663,"text":407},3,{"id":447,"depth":663,"text":448},{"id":504,"depth":170,"text":505},{"id":529,"depth":170,"text":530,"children":667},[668,669,670,671,672,673,674,675,676,677,678,679],{"id":533,"depth":663,"text":534},{"id":540,"depth":663,"text":541},{"id":547,"depth":663,"text":548},{"id":554,"depth":663,"text":555},{"id":563,"depth":663,"text":564},{"id":570,"depth":663,"text":571},{"id":577,"depth":663,"text":578},{"id":586,"depth":663,"text":587},{"id":593,"depth":663,"text":594},{"id":600,"depth":663,"text":601},{"id":611,"depth":663,"text":612},{"id":620,"depth":663,"text":621},{"id":627,"depth":170,"text":628},{"id":638,"depth":170,"text":639},"2026-08-17","AI token economics treats model usage as a budget: you pay per chunk of text read and written, so finance can quote, cap, and attribute it.",{"eyebrow":685,"title":686},"Short answers","A budget for what the model reads and writes",[688,691,694],{"question":689,"answer":690},"What is AI token economics?","Treating AI usage as a real budget. You pay per chunk of text the model reads and writes.",{"question":692,"answer":693},"Why not buy unlimited AI?","Unlimited hides which job cost what. Finance cannot quote, cap, or attribute the spend.",{"question":695,"answer":696},"What should a team see before a run?","A quote and a ceiling. The run stops when the ceiling is hit.","\u002Fblog\u002Fwhat-is-ai-token-economics",{"title":191,"description":683},"explainer","blog\u002Fwhat-is-ai-token-economics",[699,702,703,704],"token-economics","ntu","model-routing","RvB7TAIXInHDZunYt1V0yUevXBn0a5hFMuTvtxxuXAA",{"hero":707,"id":709,"title":710,"archived":163,"authors":164,"badge":164,"body":711,"date":164,"definedTerm":164,"department":164,"description":715,"extension":172,"eyebrow":716,"faqHeader":164,"faqs":164,"footerBand":717,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":60,"relatedHeading":723,"seo":724,"series":164,"sitemap":131,"status":164,"stem":725,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":726},{"filename":708},"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":712,"toc":713},[],{"title":169,"searchDepth":170,"depth":170,"links":714},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":718,"description":719,"primaryLabel":720,"primaryTo":721,"secondaryLabel":722,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","\u002Fnewsletter","Explore the platform","More research",{"title":710,"description":715},"blog\u002Findex","BFSWGYO9bcTlaulivKYWyg08_DJHsdGg3OC6g_CG1Hw",[728,1174],{"id":729,"title":730,"archived":163,"authors":731,"badge":733,"body":734,"date":682,"definedTerm":164,"department":164,"description":1153,"extension":172,"eyebrow":164,"faqHeader":1154,"faqs":1156,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1166,"relatedHeading":164,"seo":1167,"series":699,"sitemap":131,"status":164,"stem":1168,"subhead":164,"tags":1169,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1173},"content\u002Fblog\u002Fwhat-is-an-agentic-workflow.md","What is an Agentic Workflow",[732],{"name":194,"to":195},{"label":197},{"type":166,"value":735,"toc":1129},[736,739,749,754,757,759,762,786,789,836,845,847,850,857,860,896,899,901,906,916,921,926,940,942,948,954,960,966,976,979,981,988,995,1008,1010,1014,1017,1021,1024,1028,1031,1035,1038,1042,1047,1051,1054,1058,1061,1065,1071,1075,1078,1082,1087,1091,1096,1100,1103,1105,1112,1114],[201,737,738],{},"“We have an agent” often means a chat that never knows when to stop. Someone types a goal. The model keeps calling tools until the budget dies, or until a human closes the tab. There is no finish line. There is a conversation that looked busy.",[201,740,203,741,744,745,748],{},[205,742,743],{},"workflow"," has steps and a stop. An ",[205,746,747],{},"agentic workflow"," is a sequence of steps an AI can run toward a goal, with rules for when to stop — including a person who must approve before a live system changes.",[201,750,751,753],{},[210,752,488],{"href":487}," makes the same cut: workflows with tools and stop conditions, not endless chat. The note is worth reading because it is honest about the boring parts — encoding the job, bounding the tools, and deciding what “done” means — rather than treating fluency as a process.",[201,755,756],{},"Older automation without models is brittle but auditable. Models without a workflow are flexible but unaccountable. An agentic workflow is the attempt to get both: language where the input is messy, and a finish line where the company needs one.",[238,758,241],{"id":240},[201,760,761],{},"Vendors collapse three different layers into the word “agentic”:",[243,763,764,770,776],{},[246,765,766,769],{},[205,767,768],{},"Agentic capability."," The model can use tools, plan, and reflect. At work, this is “it can search Drive and draft a note.” It is not yet a job.",[246,771,772,775],{},[205,773,774],{},"Agentic workflow."," A designed sequence of those capabilities, with business stop conditions. This article is about this layer. At work, this is “extract, compare to the playbook, quote the CRM fields, wait for the named signer, write or refuse.”",[246,777,778,781,782,335],{},[205,779,780],{},"Agent platform."," Identity, connectors, tests, and governance around many workflows. At work, this is closer to an ",[210,783,785],{"href":784},"\u002Fblog\u002Fwhat-is-an-enterprise-ai-operating-system\u002F","enterprise AI operating system",[201,787,788],{},"Other terms:",[243,790,791,797,802,810,820,826],{},[246,792,793,796],{},[205,794,795],{},"Tool."," An action the AI can take: search files, query CRM, post a message. At work, a tool is a hand. Hands are not roles, and they are not stop conditions.",[246,798,799,801],{},[205,800,329],{}," Budget hit, waiting on approval, error, empty result, human cancel. “The model says it is done” is a weak stop by itself.",[246,803,804,807,808,335],{},[205,805,806],{},"Write-back."," The AI is allowed to change a live system, not just draft. See ",[210,809,608],{"href":607},[246,811,812,815,816,335],{},[205,813,814],{},"Human wait."," A step in the sequence, not an interruption. See ",[210,817,819],{"href":818},"\u002Fblog\u002Fwhat-is-human-in-the-loop-ai\u002F","What is human-in-the-loop AI",[246,821,822,825],{},[205,823,824],{},"Version."," Which workflow definition ran. When policy changes, retrieval changes. Operators need to know which version ran last Tuesday.",[246,827,828,831,832,335],{},[205,829,830],{},"MCP."," A common plug so AI apps can use the same tools. Plumbing. It does not define your stops. See ",[210,833,835],{"href":834},"\u002Fblog\u002Fwhat-is-model-context-protocol\u002F","What is Model Context Protocol",[201,837,203,838,840,841,844],{},[210,839,300],{"href":299}," is the company object that ",[233,842,843],{},"hosts"," the workflow: brief, connectors, people, budget, finish line. The workflow is the sequence. The workstream is the job folder. Mixing those two words is how demos skip isolation.",[238,846,350],{"id":349},[201,848,849],{},"Capability demos look like workflows. They are not. A fluent plan is not a paused run waiting on approval, a failed run that did not retry a write, or a replay of which step ran.",[201,851,852,853,856],{},"It affects you if the job is ",[205,854,855],{},"multi-step, tool-using, and repeated"," — the opposite of one-off chat. Close checklists, renewal playbooks, and incident runbooks already have steps. Encode those. If the job is not written down, you will encode folklore and then fight the folklore.",[201,858,859],{},"Practical rules:",[243,861,862,868,874,880,886],{},[246,863,864,867],{},[205,865,866],{},"Read-heavy workflows"," can be long. They should still finish in an artefact with sources.",[246,869,870,873],{},[205,871,872],{},"Write-heavy workflows"," should be short after the quote: one payload, one gate, one execution, one record. Do not hide ten writes in a “cleanup agent.”",[246,875,876,879],{},[205,877,878],{},"Human wait is a step",", not an interruption.",[246,881,882,885],{},[205,883,884],{},"Version the workflow."," Policy and retrieval drift. Last Tuesday’s run needs a definition you can still open.",[246,887,888,891,892,335],{},[205,889,890],{},"Budget is a stop."," See ",[210,893,895],{"href":894},"\u002Fblog\u002Fwhat-is-ai-token-economics\u002F","What is AI token economics",[201,897,898],{},"A mega-agent with “figure it out” as the spec is not a workflow. It is a hope.",[404,900,407],{"id":406},[201,902,903,905],{},[205,904,412],{}," Close and forecast jobs already have checklists. An agentic workflow that posts a journal without a stop at the named signer is not “agentic.” It is unattended posting. Finance also needs spend stops so a retry loop cannot become the month’s inference bill.",[201,907,908,910,911,915],{},[205,909,422],{}," Customer-facing steps and anything that asserts a term need a gate before send. Air Canada’s chatbot invented a bereavement fare and the company was held to it — ",[210,912,914],{"href":913},"https:\u002F\u002Fwww.cbc.ca\u002Fnews\u002Fcanada\u002Fbritish-columbia\u002Fair-canada-chatbot-lawsuit-1.7116416","CBC’s report"," is the cautionary case for “the workflow ended at the message.” Legal also cares that the workflow version is reconstructable.",[201,917,918,920],{},[205,919,428],{}," This is the native language: runbooks, queues, retries, and “do not proceed.” Ops should refuse workflows that cannot pause cleanly, cannot show which step failed, and cannot distinguish “waiting on a person” from “waiting on a tool error.”",[201,922,923,925],{},[205,924,434],{}," Renewal and hygiene jobs are repeated and tool-using. GTM should demand a short write path after the quote, not a weekend “cleanup” that touches hundreds of records behind one click. Time-to-approved-write is the metric, not time-to-first-plan.",[201,927,928,930,931,934,935,939],{},[205,929,440],{}," Tool belts are attack surface. Prompt injection that tricks a model into ",[233,932,933],{},"requesting"," a write should still die at a fail-closed gate. Importing every MCP helper into one workflow is how a demo becomes one actor with every production login. The ",[210,936,938],{"href":937},"https:\u002F\u002Fgenai.owasp.org\u002Fllm-top-10\u002F","OWASP Top 10 for LLM applications"," treats tool use as a security topic for this reason.",[404,941,448],{"id":447},[201,943,944,947],{},[205,945,946],{},"Chat as workflow."," A conversation that looks busy has no durable instance, no version, and no gate.",[201,949,950,953],{},[205,951,952],{},"A checklist in a prompt."," A start. Without tools, a durable job, and a stop, it is still a prompt.",[201,955,956,959],{},[205,957,958],{},"Replacing a stable bot."," If the job is a scheduled export, older automation is the right tool. Agentic workflows help on messy documents. They are not a prestige upgrade for a cron job.",[201,961,962,965],{},[205,963,964],{},"Fully autonomous production."," Only for actions you would already automate without a model, plus logging. If you would not let a scheduled job do it, do not let an agent do it unattended.",[201,967,968,971,972,335],{},[205,969,970],{},"Multi-agent as a requirement."," A single tool-using agent can execute a workflow. Multiple agents help when duties already split. See ",[210,973,975],{"href":974},"\u002Fblog\u002Fwhat-is-multi-agent-ai\u002F","What is multi-agent AI",[201,977,978],{},"Good looks like: named steps, bounded tools, explicit stops (including human wait and budget), versioned definitions, read-only by default, fail-closed writes. Failure looks like a flagship model with every connector and a spec that says “be helpful.”",[238,980,505],{"id":504},[201,982,983,984,335],{},"Nimbus’s delivery unit for operators is the ",[205,985,986],{},[210,987,300],{"href":299},[201,989,990,991,994],{},"The mapping in everyday terms: the brief is the goal; ",[210,992,993],{"href":974},"agent teams"," run the steps; connectors are the tools (default read-only); wiki is the playbook the steps must respect; governance is the wait\u002Fwrite stop; the Lifecycle Graph is the executed run. Model routing chooses the brain per step; it does not choose the stop.",[201,996,517,997,999,1000,1004,1005,335],{},[210,998,31],{"href":526},", ",[210,1001,1003],{"href":1002},"\u002Fproduct\u002Fagent-teams\u002F","Agent teams",", and ",[210,1006,39],{"href":1007},"\u002Fproduct\u002Fgovernance\u002F",[238,1009,530],{"id":529},[404,1011,1013],{"id":1012},"is-a-checklist-in-a-prompt-an-agentic-workflow","Is a checklist in a prompt an agentic workflow?",[201,1015,1016],{},"It is a start. If there are no tools, no durable instance, and no gate, it is a prompt.",[404,1018,1020],{"id":1019},"how-is-this-different-from-older-robotic-automation","How is this different from older robotic automation?",[201,1022,1023],{},"Older automation executes deterministic steps. Agentic workflows add language and planning. That helps on messy documents. It also means you need tests and human gates. Do not replace a stable bot with an agent if the job is still a scheduled export.",[404,1025,1027],{"id":1026},"do-agentic-workflows-require-multiple-agents","Do agentic workflows require multiple agents?",[201,1029,1030],{},"No. A single tool-using agent can execute a workflow. Multiple agents help when duties already split in the organisation.",[404,1032,1034],{"id":1033},"can-a-workflow-be-fully-autonomous-in-production","Can a workflow be fully autonomous in production?",[201,1036,1037],{},"Only for actions you would already automate without a model, plus logging.",[404,1039,1041],{"id":1040},"where-do-tool-connection-standards-fit","Where do tool-connection standards fit?",[201,1043,1044,1045,335],{},"A common plug so AI apps can use the same tools is plumbing. It does not define your stops or approvals. See ",[210,1046,835],{"href":834},[404,1048,1050],{"id":1049},"what-is-a-good-stop-condition-besides-the-model-is-done","What is a good stop condition besides “the model is done”?",[201,1052,1053],{},"Budget ceiling, empty retrieval, tool error, human cancel, and wait-for-named-signer. “Done” from the model is a suggestion. Encode the others.",[404,1055,1057],{"id":1056},"how-long-should-a-write-heavy-workflow-be","How long should a write-heavy workflow be?",[201,1059,1060],{},"Short after the quote. One payload, one gate, one execution, one record. Length belongs in the read and compare steps, not in a bundle of hidden mutations.",[404,1062,1064],{"id":1063},"how-do-we-version-a-workflow-when-the-wiki-changes","How do we version a workflow when the wiki changes?",[201,1066,1067,1068,1070],{},"Treat the playbook version as an input to the run. The ",[210,1069,500],{"href":499}," should cite which wiki version the steps respected. Changing policy without recording which definition ran is how Tuesday becomes unexplained.",[404,1072,1074],{"id":1073},"is-agentic-the-same-as-autonomous","Is “agentic” the same as “autonomous”?",[201,1076,1077],{},"No. Agentic means the model can plan and use tools. Autonomy is a policy about whether a person must still sign. Most production writes should not be autonomous.",[404,1079,1081],{"id":1080},"can-we-import-every-available-tool-and-let-the-model-choose","Can we import every available tool and let the model choose?",[201,1083,1084,1085,335],{},"That is a confused workflow. Least privilege applies to tools as much as to data. See ",[210,1086,635],{"href":299},[404,1088,1090],{"id":1089},"how-does-this-relate-to-human-in-the-loop","How does this relate to human-in-the-loop?",[201,1092,1093,1094,335],{},"Human wait is a first-class step. If the person is only “on the loop” with a kill switch, you have a different design. See ",[210,1095,819],{"href":818},[404,1097,1099],{"id":1098},"will-a-better-model-remove-the-need-for-a-workflow","Will a better model remove the need for a workflow?",[201,1101,1102],{},"Stronger models plan more fluently. They still do not know your finish line, your signer, or your budget. Fluency without stops is a more expensive loop.",[238,1104,628],{"id":627},[201,1106,1107,214,1110,335],{},[210,1108,1109],{"href":784},"What is an enterprise AI operating system",[210,1111,975],{"href":974},[238,1113,639],{"id":638},[243,1115,1116,1120,1125],{},[246,1117,1118],{},[210,1119,656],{"href":487},[246,1121,1122],{},[210,1123,1124],{"href":913},"CBC, Air Canada chatbot lawsuit",[246,1126,1127],{},[210,1128,938],{"href":937},{"title":169,"searchDepth":170,"depth":170,"links":1130},[1131,1132,1136,1137,1151,1152],{"id":240,"depth":170,"text":241},{"id":349,"depth":170,"text":350,"children":1133},[1134,1135],{"id":406,"depth":663,"text":407},{"id":447,"depth":663,"text":448},{"id":504,"depth":170,"text":505},{"id":529,"depth":170,"text":530,"children":1138},[1139,1140,1141,1142,1143,1144,1145,1146,1147,1148,1149,1150],{"id":1012,"depth":663,"text":1013},{"id":1019,"depth":663,"text":1020},{"id":1026,"depth":663,"text":1027},{"id":1033,"depth":663,"text":1034},{"id":1040,"depth":663,"text":1041},{"id":1049,"depth":663,"text":1050},{"id":1056,"depth":663,"text":1057},{"id":1063,"depth":663,"text":1064},{"id":1073,"depth":663,"text":1074},{"id":1080,"depth":663,"text":1081},{"id":1089,"depth":663,"text":1090},{"id":1098,"depth":663,"text":1099},{"id":627,"depth":170,"text":628},{"id":638,"depth":170,"text":639},"An agentic workflow is a sequence of steps an AI can run toward a goal, with a person who must approve before a live system changes.",{"eyebrow":685,"title":1155},"Steps, with a stop",[1157,1160,1163],{"question":1158,"answer":1159},"What is an agentic workflow?","A sequence of steps an AI can run toward a goal, with rules for when to stop.",{"question":1161,"answer":1162},"When must a person be in it?","Before a live system changes. The workflow can prepare the change. It cannot finish it alone.",{"question":1164,"answer":1165},"Is a chatbot flow the same thing?","A chatbot answers. An agentic workflow is allowed to take steps, which is why the stop has to be explicit.","\u002Fblog\u002Fwhat-is-an-agentic-workflow",{"title":730,"description":1153},"blog\u002Fwhat-is-an-agentic-workflow",[699,1170,1171,1172],"agentic-workflow","agents","workstreams","jqFWGede9d2XN3pJ1cSmdtlf_WWT8s5XhX9vIrpWXKY",{"id":1175,"title":1176,"archived":163,"authors":1177,"badge":1179,"body":1180,"date":682,"definedTerm":164,"department":164,"description":1627,"extension":172,"eyebrow":164,"faqHeader":1628,"faqs":1630,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":163,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1640,"relatedHeading":164,"seo":1641,"series":699,"sitemap":131,"status":164,"stem":1642,"subhead":164,"tags":1643,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1647},"content\u002Fblog\u002Fwhat-is-a-lifecycle-graph.md","What is a Lifecycle Graph",[1178],{"name":194,"to":195},{"label":197},{"type":166,"value":1181,"toc":1602},[1182,1189,1192,1195,1198,1200,1255,1276,1278,1281,1284,1286,1312,1327,1329,1336,1341,1346,1351,1356,1360,1363,1380,1383,1386,1394,1396,1403,1414,1421,1430,1433,1435,1441,1447,1454,1466,1468,1472,1479,1483,1489,1493,1496,1500,1503,1507,1512,1516,1519,1523,1526,1530,1536,1540,1543,1547,1550,1554,1559,1563,1570,1572,1582,1584],[201,1183,1184,1185,1188],{},"When people ask what a lifecycle graph is, they are usually asking about ",[205,1186,1187],{},"causality",": why did this number, field, or decision change?",[201,1190,1191],{},"Causality is the difference between “two things happened around the same time” and “this caused that.” If pipeline coverage went up in the same month AI usage went up, that is a coincidence until you can show the actual steps: what was asked, what was used, who approved it, and what the live system did.",[201,1193,1194],{},"A lifecycle graph is the company’s record of those steps. It is not a chat history. Chat history shows that someone talked to a model. A graph shows the chain from the question to the outcome, so the next person — or an auditor — can follow it.",[201,1196,1197],{},"This is an operations problem that existed before generative AI. ERP journals already needed authorisation trails. CRM already had field history. What changed is that a new kind of actor can now propose, and sometimes execute, those changes in fluent language. If the “why” lives only in a personal chat, the company has a causality gap the moment that person leaves, the vendor rotates logs, or the model version rolls.",[238,1199,241],{"id":240},[243,1201,1202,1208,1214,1225,1231,1237,1243,1249],{},[246,1203,1204,1207],{},[205,1205,1206],{},"Causality."," Being able to say what caused what, with evidence. At work, this is “this next-step field changed because this brief ran, cited this playbook version, and this person signed this payload.”",[246,1209,1210,1213],{},[205,1211,1212],{},"Correlation."," Two things moving together. Not the same as cause. At work, AI usage and pipeline moving in the same quarter is a slide, not an explanation.",[246,1215,1216,1219,1220,1224],{},[205,1217,1218],{},"Provenance."," The trail of who, what, and when behind a piece of data. ",[210,1221,1223],{"href":1222},"https:\u002F\u002Fwww.w3.org\u002FTR\u002Fprov-overview\u002F","W3C PROV"," is the open standard for that idea: entities, activities, and agents, linked so you can reconstruct derivation. A lifecycle graph is that instinct applied to AI-mediated work, not a claim that you have implemented the full W3C stack.",[246,1226,1227,1230],{},[205,1228,1229],{},"System of record."," The official live system that holds the fact — Salesforce for an opportunity, NetSuite for a journal. The graph should point at that record, not become a second copy of it. At work, pointing is how you avoid a second CRM that nobody can delete.",[246,1232,1233,1236],{},[205,1234,1235],{},"Audit trail."," A log that something happened. Useful, but thin if it cannot join the question, the policy, the signer, and the change. Provider API logs are an audit trail of calls. They are not a story of the job.",[246,1238,1239,1242],{},[205,1240,1241],{},"Lineage."," Which sources fed which proposal. At work, “which wiki version and which CRM records were in scope when this quote was generated?”",[246,1244,1245,1248],{},[205,1246,1247],{},"Retention."," How long a class of node is kept. A journal that feeds the books may need years. A draft may need weeks.",[246,1250,1251,1254],{},[205,1252,1253],{},"Scope."," Which job’s chain you are allowed to see. At work, a go-to-market question should not surface People Ops briefs.",[201,1256,1257,1258,1261,1262,1266,1267,1270,1271,1275],{},"Keep this graph apart from two neighbours. A ",[205,1259,1260],{},"business knowledge graph"," models customers, products, and sites. ",[210,1263,1265],{"href":1264},"\u002Fblog\u002Fwhat-is-enterprise-rag\u002F","Enterprise RAG"," retrieves documents that ",[233,1268,1269],{},"exist",". ",[210,1272,1274],{"href":1273},"\u002Fblog\u002Fwhat-is-institutional-memory-in-enterprise-ai\u002F","Institutional memory"," is the broader goal — what the company still knows after people leave. The lifecycle graph is the decision-memory layer of that goal: the chain of AI-mediated work.",[238,1277,350],{"id":349},[201,1279,1280],{},"AI makes it easy to change company systems without leaving a story. Someone asks a model to tidy CRM notes. A field moves. Next quarter, finance or legal asks why. The person who asked has left. The “why” lived in a personal chat. The CRM only shows the new value.",[201,1282,1283],{},"That is a causality problem. You cannot manage what you cannot reconstruct.",[201,1285,353],{},[243,1287,1288,1294,1300,1306],{},[246,1289,1290,1293],{},[205,1291,1292],{},"Sign off on numbers."," Forecasts, journals, and board packs inherit whatever AI changed last month.",[246,1295,1296,1299],{},[205,1297,1298],{},"Inherit someone else’s work."," You need the exception, not a rumour that “we always do 18% for strategic accounts.”",[246,1301,1302,1305],{},[205,1303,1304],{},"Answer auditors or regulators."," They will not accept “the chatbot did it.”",[246,1307,1308,1311],{},[205,1309,1310],{},"Switch vendors or models."," Provider logs are the vendor’s artefact. They are not your company memory.",[201,1313,1314,1315,1318,1319,1323,1324],{},"This is not the same as proving that a discount ",[233,1316,1317],{},"caused"," a won deal. That is a statistics question. See ",[210,1320,1322],{"href":1321},"\u002Fblog\u002Fwhat-is-causal-ai-for-operations\u002F","What is causal AI for operations",". A lifecycle graph answers a more basic one: ",[205,1325,1326],{},"what did we actually do, and who caused it?",[404,1328,407],{"id":406},[201,1330,1331,1333,1334,335],{},[205,1332,412],{}," Close packs and forecasts inherit field history. If an AI-proposed journal posted, finance needs the brief, the playbook version, the named signer, and the ERP response — not a Slack screenshot. Spend also belongs on the chain: a run that stopped because a cap was hit is a causal fact, not a missing invoice. See ",[210,1335,895],{"href":894},[201,1337,1338,1340],{},[205,1339,422],{}," Exception language, customer commitments, and “who saw what” are discovery questions. A graph that points at the payload the signer saw is evidence. A chat export from a personal account is not. Legal also cares about retention and deletion: infinite chat fails a privacy review; typed retention with export and legal hold is how records programmes already work.",[201,1342,1343,1345],{},[205,1344,428],{}," Handoffs fail when the next shift cannot see why a run paused. Human wait is a node, not an interruption. Incident reviews need the same chain: which connector was read-only, which write was refused, which wiki page caused the flag.",[201,1347,1348,1350],{},[205,1349,434],{}," Pipeline hygiene and renewal exceptions are where “the bot updated it” becomes a forecast problem. GTM needs to see the quoted fields, not a summary that says “updated pricing.” They also need scope: one team’s competitive notes should not leak into another region’s chain.",[201,1352,1353,1355],{},[205,1354,440],{}," The graph is a sensitive store. It should not hold full transcripts with secrets by default, other teams’ out-of-scope work, or the model’s private scratch reasoning. Access control on the graph is as important as access control on the CRM. A query surface that ignores vaults recreates the god workspace.",[404,1357,1359],{"id":1358},"what-belongs-on-the-chain","What belongs on the chain",[201,1361,1362],{},"Keep the links that let a non-engineer reconstruct a change:",[243,1364,1365,1368,1371,1374,1377],{},[246,1366,1367],{},"the job and the question",[246,1369,1370],{},"the sources (which playbook version, which records, which files)",[246,1372,1373],{},"the people (the model is not an answer for “who”)",[246,1375,1376],{},"the proposed change, in the language of the live system — fields and values, not “updated pricing”",[246,1378,1379],{},"the decision, the timestamp, and whether the live system accepted it",[201,1381,1382],{},"Point at the CRM record and the policy page. Do not copy the whole company into the graph. Copies become a second official system, and a deletion problem.",[201,1384,1385],{},"Do not keep, by default: the model’s private scratch reasoning, full transcripts with secrets, or other teams’ work that was never in scope.",[201,1387,1388,1389,1393],{},"Retention should follow the type of record. A journal that feeds the books may need years. A draft may need weeks. “Keep everything forever because AI” fails a privacy review. ",[210,1390,1392],{"href":1391},"https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fuk-gdpr-guidance-and-resources\u002Fartificial-intelligence\u002F","UK ICO guidance on AI and data protection"," still wants purpose and minimisation when the “user” is an AI.",[404,1395,448],{"id":447},[201,1397,1398,1399,1402],{},"The first mistake is ",[205,1400,1401],{},"treating chat history as the record",". Chat is a user interface. It is not a join of brief, policy, signer, and system response.",[201,1404,1405,1406,1409,1410,1413],{},"The second is ",[205,1407,1408],{},"retrofitting",". Copying six months of ChatGPT and Slack into a warehouse is archaeology. You still need something that ",[233,1411,1412],{},"emits"," events at the moment of the brief, the quote, and the approval.",[201,1415,1416,1417,1420],{},"The third is ",[205,1418,1419],{},"a second CRM",". Duplicating every opportunity into the graph “for completeness” creates conflicting official numbers and an erasure nightmare.",[201,1422,1423,1424,1427,1428,335],{},"The fourth is ",[205,1425,1426],{},"confusing this with causal science",". A fluent model paragraph that says “because” is not identification. Neither is a dashboard of two rising lines. See ",[210,1429,1322],{"href":1321},[201,1431,1432],{},"Good looks like reconstructable interventions with pointers, named people, and typed retention. Failure looks like a vendor log, a personal thread, or an infinite lake of tokens.",[238,1434,505],{"id":504},[201,1436,1437,1438,1440],{},"Nimbus’s ",[205,1439,23],{}," is that chain as a product: briefs, playbook citations, connector reads, spend, approvals, and write results are linked as work proceeds.",[201,1442,1443,1446],{},[205,1444,1445],{},"Perception"," is how you ask it in ordinary language — “why did this opportunity change last month?” — instead of reconstructing Slack.",[201,1448,1449,1450,1453],{},"The graph records ",[205,1451,1452],{},"work",", not every token the company ever sent to a model. Scope follows the job, so a go-to-market question should not surface People Ops briefs. Connectors default to read-only; a read that did not write is itself a node worth knowing. Fail-closed writes mean a missing named signer is a recorded refusal, not a silent mutation.",[201,1455,1456,1457,214,1460,1463,1464,335],{},"Product: ",[210,1458,23],{"href":1459},"\u002Fproduct\u002Flifecycle-graph\u002F",[210,1461,1445],{"href":1462},"\u002Fproduct\u002Fperception\u002F",". The job that produces the chain is a ",[210,1465,300],{"href":299},[238,1467,530],{"id":529},[404,1469,1471],{"id":1470},"is-this-just-a-knowledge-graph-of-the-business","Is this just a knowledge graph of the business?",[201,1473,1474,1475,1478],{},"No. A business knowledge graph models customers, products, and sites. A lifecycle graph models ",[205,1476,1477],{},"AI-mediated work"," — what was asked, who signed, what changed. They can link (the write points at an opportunity). They are not the same thing.",[404,1480,1482],{"id":1481},"cant-the-warehouse-be-the-record","Can’t the warehouse be the record?",[201,1484,1485,1486,1488],{},"You can copy events into a warehouse for reporting. You still need something that ",[233,1487,1412],{}," those events at the moment of the brief, the quote, and the approval. Retrofitting six months of ChatGPT and Slack is archaeology, not operations.",[404,1490,1492],{"id":1491},"how-is-this-different-from-the-model-providers-logs","How is this different from the model provider’s logs?",[201,1494,1495],{},"Provider logs show API calls. They do not know your job, your playbook version, your approver, or whether the write was rejected.",[404,1497,1499],{"id":1498},"how-long-should-we-keep-it","How long should we keep it?",[201,1501,1502],{},"Treat it like other control evidence. Align retention with the type of record, legal hold, and storage limits. The product must support export, deletion, and access control — not infinite chat.",[404,1504,1506],{"id":1505},"how-does-this-relate-to-a-person-having-to-approve","How does this relate to a person having to approve?",[201,1508,1509,1510,335],{},"A human gate only counts if you can later show who signed and what they saw. Without a graph, that gate is a popup that forgets. See ",[210,1511,819],{"href":818},[404,1513,1515],{"id":1514},"does-the-graph-replace-crm-field-history","Does the graph replace CRM field history?",[201,1517,1518],{},"No. Field history says the value changed. The graph says which job, which policy version, and which named signer caused the proposal. Keep both. Point; do not duplicate.",[404,1520,1522],{"id":1521},"what-if-the-models-explanation-disagrees-with-the-graph","What if the model’s explanation disagrees with the graph?",[201,1524,1525],{},"Trust the structure. Fluent “because” text is often written after the fact. The chain of brief, sources, quote, and signature is the operational cause.",[404,1527,1529],{"id":1528},"can-we-store-every-prompt-and-completion","Can we store every prompt and completion?",[201,1531,1532,1533,335],{},"You can. You usually should not. Completeness is reconstructability, not hoarding. Secrets in transcripts become a new breach class. See ",[210,1534,1535],{"href":1273},"What is institutional memory in enterprise AI",[404,1537,1539],{"id":1538},"how-do-permissions-work-on-the-graph","How do permissions work on the graph?",[201,1541,1542],{},"The same least-privilege instincthe job. If you could not see the People Ops workstream, you should not query its chain in ordinary language either.",[404,1544,1546],{"id":1545},"is-a-screenshot-of-the-approval-enough","Is a screenshot of the approval enough?",[201,1548,1549],{},"For a one-off incident, maybe. For a control, no. Screenshots do not join, do not retain by type, and do not survive the laptop.",[404,1551,1553],{"id":1552},"where-does-spend-sit-on-the-chain","Where does spend sit on the chain?",[201,1555,1556,1557,335],{},"Quotes, caps, and stop-on-budget are causal events. “The run did not write because the ceiling was hit” is an answer finance can use. See ",[210,1558,895],{"href":894},[404,1560,1562],{"id":1561},"how-is-this-different-from-mlops-experiment-tracking","How is this different from MLOps experiment tracking?",[201,1564,1565,1566,1569],{},"MLOps tracks model training and deployment. A lifecycle graph tracks operational work that ",[233,1567,1568],{},"uses"," models. They stack. They do not substitute.",[238,1571,628],{"id":627},[201,1573,1574,1575,1463,1577,1579,1580,335],{},"If the goal is what the company still knows after people leave, read ",[210,1576,1535],{"href":1273},[210,1578,300],{"href":299},". For the science versus operations cut, ",[210,1581,1322],{"href":1321},[238,1583,639],{"id":638},[243,1585,1586,1591,1597],{},[246,1587,1588],{},[210,1589,1590],{"href":1222},"W3C PROV overview",[246,1592,1593],{},[210,1594,1596],{"href":1595},"https:\u002F\u002Fwww.w3.org\u002FTR\u002Fprov-dm\u002F","W3C PROV data model",[246,1598,1599],{},[210,1600,1601],{"href":1391},"ICO, AI and data protection",{"title":169,"searchDepth":170,"depth":170,"links":1603},[1604,1605,1610,1611,1625,1626],{"id":240,"depth":170,"text":241},{"id":349,"depth":170,"text":350,"children":1606},[1607,1608,1609],{"id":406,"depth":663,"text":407},{"id":1358,"depth":663,"text":1359},{"id":447,"depth":663,"text":448},{"id":504,"depth":170,"text":505},{"id":529,"depth":170,"text":530,"children":1612},[1613,1614,1615,1616,1617,1618,1619,1620,1621,1622,1623,1624],{"id":1470,"depth":663,"text":1471},{"id":1481,"depth":663,"text":1482},{"id":1491,"depth":663,"text":1492},{"id":1498,"depth":663,"text":1499},{"id":1505,"depth":663,"text":1506},{"id":1514,"depth":663,"text":1515},{"id":1521,"depth":663,"text":1522},{"id":1528,"depth":663,"text":1529},{"id":1538,"depth":663,"text":1539},{"id":1545,"depth":663,"text":1546},{"id":1552,"depth":663,"text":1553},{"id":1561,"depth":663,"text":1562},{"id":627,"depth":170,"text":628},{"id":638,"depth":170,"text":639},"A lifecycle graph is how a company answers “why did this happen?” after AI is involved — the chain of cause and effect, not a chat log.",{"eyebrow":685,"title":1629},"Why this happened",[1631,1634,1637],{"question":1632,"answer":1633},"What is a lifecycle graph?","The chain of cause and effect a company uses to answer why something happened after AI was involved.",{"question":1635,"answer":1636},"How is that different from a chat log?","A chat log is what was said. A lifecycle graph is what caused the outcome, including the approval and the system change.",{"question":1638,"answer":1639},"Who needs it?","Anyone who has to explain a decision after the person who ran the assistant has left.","\u002Fblog\u002Fwhat-is-a-lifecycle-graph",{"title":1176,"description":1627},"blog\u002Fwhat-is-a-lifecycle-graph",[699,1644,1645,1646],"lifecycle-graph","institutional-memory","audit","Ii-lV67KHK9LjLE_sx8wOb9nVjJEttXS0Y8roIiSjNo",{"fold":1649,"id":1653,"title":1654,"archived":163,"authors":164,"badge":164,"body":1655,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":1659,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1663,"relatedHeading":164,"seo":1664,"series":164,"sitemap":163,"status":164,"stem":1665,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1666},{"headline":1650,"description":1651,"primaryLabel":8,"primaryTo":1652,"secondaryLabel":722,"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":1656,"toc":1657},[],{"title":169,"searchDepth":170,"depth":170,"links":1658},[],{"headline":1660,"description":1661,"primaryLabel":8,"primaryTo":1652,"secondaryLabel":1662,"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":1654,"description":169},"shared\u002Fcta","eYqahyaPnbp8GKrWpoORbZdtmkWmgHr5F61ZHOnb8sY",1792999480781]