[{"data":1,"prerenderedAt":1902},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/loop-vs-workflow-vs-agent":179,"blog-index-copy":931,"blog:/blog/loop-vs-workflow-vs-agent:surround":952,"hiring-banner-content":1871,"site-cta-content":1883},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":132,"id":163,"title":164,"archived":165,"authors":166,"badge":166,"body":167,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":175,"relatedHeading":166,"seo":176,"series":166,"sitemap":165,"status":166,"stem":177,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":178},{"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","/overview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","/product/conflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","/product/agent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","/product/lifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","/product/wiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","/product/workstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","/product/perception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","/product/governance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","/models",{"label":47,"to":48},"Pricing","/pricing",{"label":50,"to":51},"Integrations","/integrations",{"label":53,"to":54},"Security","/security",{"label":56,"to":57},"Partners","/partners",{"label":59,"to":60},"Insights","/blog",{"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://docs.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","/careers",{"label":82,"to":83},"System status","/status",{"label":7,"to":85},"/contact",[87,90,93,96,99],{"label":88,"to":89},"Glossary","/glossary",{"label":91,"to":92},"Compare","/compare",{"label":94,"to":95},"Evaluate","/evaluate",{"label":97,"to":98},"Problems","/problems",{"label":100,"to":101},"Use cases","/use-cases",[103,106],{"label":104,"to":105},"Terms of Service","/terms",{"label":107,"to":108},"Privacy Policy","/privacy",[110,113,116],{"label":111,"href":112},"LinkedIn","https://www.linkedin.com/company/gonimbusai/",{"label":114,"href":115},"X","https://x.com/gonimbusai",{"label":117,"href":118},"Instagram","https://www.instagram.com/gonimbus_ai/",[120,122,124,127,128],{"label":121,"to":105},"Terms",{"label":123,"to":108},"Privacy",{"label":125,"to":126},"Compliance","/compliance",{"label":82,"to":83},{"label":129,"to":130,"external":131},"LLMs.txt","/llms.txt",true,{"text":133,"prompt":134},"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":135,"platforms":137},{" Summarize the highlights from Nimbus's website":136},"https://gonimbus.ai",[138,143,148,153,158],{"name":139,"label":140,"icon":141,"hrefPrefix":142},"chatgpt","ChatGPT","simple-icons:openai","https://chatgpt.com/?prompt=",{"name":144,"label":145,"icon":146,"hrefPrefix":147},"perplexity","Perplexity","mdi:magnify","https://www.perplexity.ai/search/new?q=",{"name":149,"label":150,"icon":151,"hrefPrefix":152},"grok","Grok","simple-icons:x","https://x.com/i/grok?text=",{"name":154,"label":155,"icon":156,"hrefPrefix":157},"claude","Claude","simple-icons:anthropic","https://claude.ai/new?q=",{"name":159,"label":160,"icon":161,"hrefPrefix":162},"google-ai","Google AI","simple-icons:google","https://www.google.com/search?udm=50&aep=11&q=","content/shared/nav.md","Site navigation",false,null,{"type":168,"value":169,"toc":170},"minimark",[],{"title":171,"searchDepth":172,"depth":172,"links":173},"",2,[],"md","/shared/nav",{"title":164,"description":171},"shared/nav","1dD7ahDRl0SQ4hz53-kKo0tEFrGaLuaztZ3PPfp6a9k",{"id":180,"title":181,"archived":165,"authors":182,"badge":185,"body":187,"date":904,"definedTerm":166,"department":166,"description":905,"extension":174,"eyebrow":166,"faqHeader":906,"faqs":909,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":922,"relatedHeading":166,"seo":923,"series":924,"sitemap":131,"status":166,"stem":925,"subhead":166,"tags":926,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":930},"content/blog/loop-vs-workflow-vs-agent.md","Loop vs Workflow vs Agent",[183],{"name":184,"to":136},"Nimbus Research",{"label":186},"Explainer",{"type":168,"value":188,"toc":894},[189,201,204,274,283,288,295,298,327,330,333,339,351,355,364,367,396,410,416,421,428,432,445,448,477,486,491,499,503,613,625,633,637,640,658,661,664,704,711,715,721,727,737,747,753,764,768,771,785,831,837,840,847,864,868,881,890],[190,191,192,193,200],"p",{},"A workflow enumerates steps a person invented. A loop is a compiled standing order that fires when a signal repeats. An agent reasons when the path is not yet known. ",[194,195,199],"a",{"href":196,"rel":197},"https://www.anthropic.com/engineering/building-effective-agents",[198],"nofollow","Anthropic’s guidance on building effective agents"," is blunt about the distinction: encode the job when you can; reserve autonomy for inputs that will not sit still. Operators need the noun that matches how stable the job is — not the noun that wins the demo.",[190,202,203],{},"Three words, disambiguated up front, plus the sibling people keep folding in:",[205,206,207,229,240,260],"ul",{},[208,209,210,214,215,218,219,223,224,228],"li",{},[211,212,213],"strong",{},"Loop."," A compiled ",[211,216,217],{},"standing order",": triggers, a trusted recipe, outcomes on a run page, skip when nothing changed. See ",[194,220,222],{"href":221},"what-is-loop-engineering","what is loop engineering"," and ",[194,225,227],{"href":226},"six-things-that-start-a-loop","six things that start a loop",". Loops are for work that repeats on recognizable signals.",[208,230,231,234,235,239],{},[211,232,233],{},"Eval loop."," An independent verification that a job finished — tests, schema, read-back, signer — not the model’s claim. See ",[194,236,238],{"href":237},"eval-loops-for-enterprise-agent-harnesses","eval loops for enterprise agent harnesses",". A loop may include eval steps; “eval loop” is not “loop.”",[208,241,242,245,246,249,250,254,255,259],{},[211,243,244],{},"Agentic workflow."," A ",[211,247,248],{},"designed sequence"," of steps toward a goal, with business stop conditions — including a person before a live system changes. See ",[194,251,253],{"href":252},"what-is-an-agentic-workflow","what is an agentic workflow",". Workflows are what someone invented; they are versioned and hosted on a ",[194,256,258],{"href":257},"what-is-an-ai-workstream","workstream",".",[208,261,262,265,266,223,270,259],{},[211,263,264],{},"Agent."," A reasoner that picks tools when the path is not fully enumerated. See ",[194,267,269],{"href":268},"what-is-an-agent-harness","what is an agent harness",[194,271,273],{"href":272},"a-loop-is-not-an-agent","a loop is not an agent",[190,275,276,277,282],{},"If your buying conversation starts with “we need an agent,” pause. That sentence often means three different jobs. Buying the wrong one wastes the quarter — not because the model is weak, but because the operating object is wrong. ",[194,278,281],{"href":279,"rel":280},"https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai",[198],"McKinsey’s 2025 State of AI"," keeps showing high usage and uneven scale. Scale, in this vocabulary, usually means compiling what worked — into a workflow or a loop — not hiring a larger model to improvise the same close every month.",[284,285,287],"h2",{"id":286},"workflow-steps-a-person-invented","Workflow — steps a person invented",[190,289,290,291,294],{},"A ",[211,292,293],{},"workflow"," is a sequence someone designed: extract, compare to a playbook, quote the CRM fields, wait for the named signer, write or refuse. The author is a person. The instance is durable. The finish line is named before the run starts.",[190,296,297],{},"Workflows excel when:",[205,299,300,307,313,320],{},[208,301,302,303,306],{},"the ",[211,304,305],{},"stop conditions"," matter as much as the steps — budget, approval, empty result, a clause that is non-standard",[208,308,309,312],{},[211,310,311],{},"roles"," differ by step — analyst drafts, controller signs, counsel refuses",[208,314,315,316,319],{},"the job is ",[211,317,318],{},"interactive"," — humans join mid-flight with context attached",[208,321,322,323,326],{},"you must ",[211,324,325],{},"version"," the definition — “which workflow ran last Tuesday?” is a fair audit question",[190,328,329],{},"A workflow is the right object when the path is known enough to draw and still needs a person at a gate. Month-end sign-off is a workflow even if a loop assembled the pack. Discount exceptions are a workflow even if a loop watched the stage change. The designed sequence is how you keep roles from collapsing into “the model posted it.”",[190,331,332],{},"Workflows fail when teams treat them as magic. A checklist in a prompt is not a workflow. A chat with tools is not a workflow. A Lucidchart on a wiki is not a workflow runtime. A workflow has a durable instance, a finish line, and a record that survives the session. If you hide the chat and cannot reconstruct which step was waiting on a person, you bought conversation.",[190,334,335,338],{},[211,336,337],{},"Operator test:"," Can an independent reader reconstruct which steps ran, what was waiting on a person, and what was refused — without Slack search?",[190,340,341,345,346,350],{},[194,342,344],{"href":343},"what-is-human-in-the-loop-ai","What is human-in-the-loop AI"," belongs here more than it belongs on the loop. Loops can pause; workflows are often ",[347,348,349],"em",{},"about"," the pause. The pause is the product. If your vendor cannot show a named stop, you do not have a workflow. You have a script with optimism.",[284,352,354],{"id":353},"loop-a-compiled-standing-order","Loop — a compiled standing order",[190,356,290,357,360,361,363],{},[211,358,359],{},"loop"," is what you run when the world sends the same signal again: Monday close, file in folder, stage flipped, billing event, someone presses run now. See ",[194,362,227],{"href":226},". The author compiled the recipe once. The trigger admits a run. The run page is the contract.",[190,365,366],{},"Loops excel when:",[205,368,369,376,382,389],{},[208,370,371,372,375],{},"the recipe is ",[211,373,374],{},"stable"," enough to reuse without re-prompting",[208,377,378,381],{},[211,379,380],{},"skip semantics"," matter — “nothing changed” should be a first-class outcome",[208,383,384,385,388],{},"operators need a ",[211,386,387],{},"run page",", not a transcript",[208,390,391,392,395],{},"the same kernel should answer to ",[211,393,394],{},"several triggers"," without several copies",[190,397,398,399,403,404,409],{},"Loops are not “set and forget” if forget means no record. A good loop logs quiet outcomes, notifies the roster, and attaches outputs where the next role expects them. ",[194,400,402],{"href":401},"how-to-evaluate-loop-engineering","How to evaluate loop engineering"," is the RFP sheet for this object. ",[194,405,408],{"href":406,"rel":407},"https://www.nist.gov/itl/ai-risk-management-framework",[198],"NIST’s AI Risk Management Framework"," Measure function assumes you can observe those outcomes. A loop without a run page is not observable. It is email archaeology.",[190,411,412,413,415],{},"Loops fail when they are copied from someone’s channel, when skip is implemented as “don’t email,” or when every step secretly calls a model. On the happy path, ",[194,414,273],{"href":272},": it should not re-derive the job. If Monday’s close still begins with “please do the usual,” you have not compiled anything.",[190,417,418,420],{},[211,419,337],{}," Run it ten times with empty inputs. Do you get ten run pages that say skipped — or ten emails saying error?",[190,422,423,427],{},[194,424,426],{"href":425},"loop-engineering-vs-harness-engineering","Loop engineering vs harness engineering"," draws the line: loop engineering compiles repeat work; harness engineering tightens the environment when interactive agents fail. You need both crafts. They fail differently. A loop that guesses at 3am is a harness problem you imported into unattended hours.",[284,429,431],{"id":430},"agent-reasons-when-the-path-is-unknown","Agent — reasons when the path is unknown",[190,433,434,435,438,439,444],{},"An ",[211,436,437],{},"agent"," (in the product sense) chooses actions when you cannot enumerate every branch upfront: read these ten documents and tell me which clause conflicts; investigate why margin diverged across three regions; draft three options for a novel pricing exception. ",[194,440,443],{"href":441,"rel":442},"https://docs.langchain.com/oss/python/langchain/agents",[198],"LangChain’s definition"," is a useful shorthand: Agent = Model + Harness. The harness is not optional. Without tools, stops, and a budget, you have a chatbot with aspirations.",[190,446,447],{},"Agents excel when:",[205,449,450,457,463,470],{},[208,451,452,453,456],{},"inputs are ",[211,454,455],{},"messy or novel"," — PDFs, threads, ambiguous tickets, a vendor paper the team has not seen",[208,458,302,459,462],{},[211,460,461],{},"path emerges"," during the job — you would not trust a fixed script yet",[208,464,465,466,469],{},"the cost of a wrong step is ",[211,467,468],{},"bounded"," — read-only tools, draft-only outputs",[208,471,472,473,476],{},"a human will ",[211,474,475],{},"compress"," the result into a decision artefact",[190,478,479,480,485],{},"Agents fail when teams use them as cron with charisma. If the job is the same every Monday, an agent rediscovering the steps is expensive theatre. It is also a control failure: the path that ran last week is not a path you can open next week. ",[194,481,484],{"href":482,"rel":483},"https://aiindex.stanford.edu/",[198],"Stanford HAI’s AI Index"," is a reminder that capability is not the scarce resource. Operational maturity is.",[190,487,488,490],{},[211,489,337],{}," If you hid the chat and kept only the artefact, would the company still know what changed? If not, you bought conversation, not control.",[190,492,493,494,498],{},"Score agents with ",[194,495,497],{"href":496},"how-to-evaluate-an-agent-harness","how to evaluate an agent harness",", not with this page’s skip-semantics tests. The hero metric for an agent is whether you can stop a write and replay what was refused. The hero metric for a loop is whether you can skip quietly and prove it.",[284,500,502],{"id":501},"three-way-comparison","Three-way comparison",[504,505,506,525],"table",{},[507,508,509],"thead",{},[510,511,512,516,519,522],"tr",{},[513,514,515],"th",{},"Question",[513,517,518],{},"Workflow",[513,520,521],{},"Loop",[513,523,524],{},"Agent",[526,527,528,543,557,571,585,599],"tbody",{},[510,529,530,534,537,540],{},[531,532,533],"td",{},"Who designed the path?",[531,535,536],{},"A person encoded steps",[531,538,539],{},"A compiled recipe",[531,541,542],{},"The model plans within bounds",[510,544,545,548,551,554],{},[531,546,547],{},"Typical host",[531,549,550],{},"Workstream with gates",[531,552,553],{},"Recipe library + run page",[531,555,556],{},"Workstream or task room",[510,558,559,562,565,568],{},[531,560,561],{},"Best when",[531,563,564],{},"Stops and roles matter",[531,566,567],{},"Signal repeats",[531,569,570],{},"Path unknown",[510,572,573,576,579,582],{},[531,574,575],{},"Quiet success",[531,577,578],{},"Waiting on signer",[531,580,581],{},"Skipped — no change",[531,583,584],{},"“Nothing found” with sources",[510,586,587,590,593,596],{},[531,588,589],{},"Versioning",[531,591,592],{},"Workflow definition",[531,594,595],{},"Recipe version",[531,597,598],{},"Prompt + tool grants",[510,600,601,604,607,610],{},[531,602,603],{},"Audit reader asks",[531,605,606],{},"Which step, which gate",[531,608,609],{},"Which trigger, which run",[531,611,612],{},"Which sources, which draft",[190,614,615,616,619,620,624],{},"None of these rows replaces your CRM. They describe how work runs ",[211,617,618],{},"on top of"," systems of record. The ",[194,621,623],{"href":622},"what-is-an-enterprise-ai-operating-system","enterprise AI operating system"," metaphor is the kernel version of the same problem — isolation, permissions, durable state — applied to jobs rather than applications. This article stays at the operator nouns. Use the OS page when you need the kernel language; use this page when someone says “agent” and means a Monday report.",[190,626,627,632],{},[194,628,631],{"href":629,"rel":630},"https://www.iso.org/standard/81230.html",[198],"ISO/IEC 42001"," will not tell you which noun to buy. It will ask whether you can name the system, the owner, and the record. Workflows, loops, and agents all fail that test when they live only in a transcript.",[284,634,636],{"id":635},"how-they-compose-in-one-quarter","How they compose in one quarter",[190,638,639],{},"Real companies stack all three. The stack is not three products competing. It is three stability levels: novel → designed → repeated.",[641,642,643,648,653],"ol",{},[208,644,645,647],{},[211,646,524],{}," investigates a new vendor contract — extracts obligations, flags non-standard terms, drafts a summary for counsel. The path is unknown. The output is a draft. Nothing customer-facing sends.",[208,649,650,652],{},[211,651,518],{}," routes the summary through Legal review on a workstream, with a hard stop before anything leaves the company. Roles stay distinct. The instance is durable. Counsel can refuse.",[208,654,655,657],{},[211,656,521],{}," watches the signed folder and, every time a countersigned PDF lands, updates the renewal tracker and notifies RevOps — skipping if the hash matches last week’s file. The signal repeats. The recipe does not.",[190,659,660],{},"That composition is how you avoid the two failure modes that dominate programmes: agent-for-everything, and checklist-in-a-wiki. The first burns tokens and produces untraceable month six. The second produces a drawing that nobody runs.",[190,662,663],{},"Department guides use the same stack with different default nouns:",[205,665,666,680,694],{},[208,667,668,671,672,223,676,259],{},[211,669,670],{},"Finance and planning"," — loops for scheduled packs; workflows for close sign-offs; agents for one-off variance forensics. See ",[194,673,675],{"href":674},"loops-for-finance-and-planning","loops for finance and planning",[194,677,679],{"href":678},"collaborative-ai-for-finance-and-planning","collaborative AI for finance and planning",[208,681,682,685,686,223,690,259],{},[211,683,684],{},"Revenue operations"," — loops on stage changes; workflows for discount exceptions; agents for messy account research. See ",[194,687,689],{"href":688},"loops-for-revenue-operations","loops for revenue operations",[194,691,693],{"href":692},"collaborative-ai-for-revenue-operations","collaborative AI for revenue operations",[208,695,696,699,700,259],{},[211,697,698],{},"Legal and compliance"," — workflows for approvals; loops on inbound redlines; agents for first-pass clause comparison. See ",[194,701,703],{"href":702},"loops-for-legal-and-compliance","loops for legal and compliance",[190,705,706,710],{},[194,707,709],{"href":708},"what-is-collaborative-ai","Collaborative AI"," is the roster pattern underneath all three: multiple roles, one job object, a finish line. The noun you pick does not replace the roster. An agent without a roster is a personal copilot. A loop without a roster notifies a dead channel. A workflow without a roster has nobody to stand at the gate.",[284,712,714],{"id":713},"what-people-get-wrong","What people get wrong",[190,716,717,720],{},[211,718,719],{},"Agent for everything."," Impressive week one; untraceable month six. The model will happily re-solve a solved problem. You will pay for it twice: inference, and the incident when it improvises a write.",[190,722,723,726],{},[211,724,725],{},"Workflow without an instance."," A diagram is not a runtime. If you cannot open last Tuesday’s run and see the step that was waiting, you have documentation, not a workflow.",[190,728,729,732,733,736],{},[211,730,731],{},"Loop copied from someone’s Slack channel."," If reuse means “find the old thread,” you have folklore, not ",[194,734,735],{"href":221},"loop engineering",". Folklore does not survive vacation.",[190,738,739,742,743,746],{},[211,740,741],{},"Confusing eval loops with loops."," Benchmarks and read-backs verify completion; standing-order loops start and record repeat work. Both can coexist on one job. Collapsing them hides whether you can start work ",[347,744,745],{},"and"," whether you can prove it finished.",[190,748,749,752],{},[211,750,751],{},"Buying a platform that only sells one noun."," If the vendor cannot host a workflow gate, a loop run page, and an agent task on the same roster, you will rebuild org boundaries in email. That is not a tooling preference. It is how departments already work.",[190,754,755,758,759,763],{},[211,756,757],{},"Treating RPA as the fourth synonym."," Screen replay is a different category. See ",[194,760,762],{"href":761},"loop-vs-rpa","loop vs RPA",". A bot that clicks an ERP has a place. It is not a standing-order loop, a designed workflow, or a reasoner.",[284,765,767],{"id":766},"choosing-this-week","Choosing this week",[190,769,770],{},"Ask two questions, in this order:",[641,772,773,779],{},[208,774,775,778],{},[211,776,777],{},"Do we know the steps?"," No → agent, bounded. Yes → workflow or loop.",[208,780,781,784],{},[211,782,783],{},"Will the same signal fire again?"," Yes → loop. No → workflow.",[786,787,791],"pre",{"className":788,"code":789,"language":790,"meta":171,"style":171},"language-mermaid shiki shiki-themes github-light github-dark","flowchart TD\n  steps{\"Do we know the steps?\"}\n  steps -->|no| agentPick[\"Agent: explore, keep a draft\"]\n  steps -->|yes| signal{\"Will the same signal fire again?\"}\n  signal -->|yes| loopPick[\"Loop: standing order\"]\n  signal -->|no| workflowPick[\"Workflow: designed sequence with stops\"]\n","mermaid",[792,793,794,802,807,813,819,825],"code",{"__ignoreMap":171},[795,796,799],"span",{"class":797,"line":798},"line",1,[795,800,801],{},"flowchart TD\n",[795,803,804],{"class":797,"line":172},[795,805,806],{},"  steps{\"Do we know the steps?\"}\n",[795,808,810],{"class":797,"line":809},3,[795,811,812],{},"  steps -->|no| agentPick[\"Agent: explore, keep a draft\"]\n",[795,814,816],{"class":797,"line":815},4,[795,817,818],{},"  steps -->|yes| signal{\"Will the same signal fire again?\"}\n",[795,820,822],{"class":797,"line":821},5,[795,823,824],{},"  signal -->|yes| loopPick[\"Loop: standing order\"]\n",[795,826,828],{"class":797,"line":827},6,[795,829,830],{},"  signal -->|no| workflowPick[\"Workflow: designed sequence with stops\"]\n",[190,832,833,834,836],{},"If both yes — stable steps ",[347,835,745],{}," a repeating signal — start with a loop. Add workflow gates inside it when a named signer must appear. Add an agent step when one stage still needs reading messy inputs. That is the composition above, reduced to a decision tree you can use in a working session.",[190,838,839],{},"If both no — unknown steps and a one-off — you are in research. Do not compile yet. Do not buy a bot. Bound the tools, keep the output as a draft, and decide next week whether the path is now known.",[190,841,842,846],{},[194,843,845],{"href":844},"four-pillars-of-an-enterprise-ai-platform","The four pillars of an enterprise AI platform"," is the wider map: communication brings context, collaboration hosts the job, automate repeats the recipe, governance refuses what should not land. Loops, workflows, and agents all sit on that map. They are not a substitute for it.",[190,848,849,850,853,854,858,859,863],{},"Related reading: ",[194,851,852],{"href":708},"what is collaborative AI",", ",[194,855,857],{"href":856},"how-to-evaluate-collaborative-ai","how to evaluate collaborative AI",", and ",[194,860,862],{"href":861},"what-is-harness-engineering","what is harness engineering"," when agents and loops share the same stops.",[284,865,867],{"id":866},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[190,869,870,871,873,874,877,878,880],{},"Nimbus hosts all three nouns on the same ",[194,872,258],{"href":32},". Loops are standing orders with run pages. Agentic workflows are designed sequences with ",[194,875,876],{"href":40},"governance"," gates. Agents run as bounded teammates with scoped grants, not as a second platform. ",[194,879,15],{"href":16}," is often the communication door that starts a loop when a file lands.",[190,882,883,884,223,887,889],{},"Treat that as one vendor’s mapping of the pattern, not as the definition. If you are writing an RFP, paste the questions from ",[194,885,886],{"href":401},"how to evaluate loop engineering",[194,888,497],{"href":496}," and run them on whoever claims the nouns. The useful outcome is not a logo. It is whether Tuesday’s close, Tuesday’s exception, and Tuesday’s novel contract can share a roster without collapsing into one chat.",[891,892,893],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":171,"searchDepth":172,"depth":172,"links":895},[896,897,898,899,900,901,902,903],{"id":286,"depth":172,"text":287},{"id":353,"depth":172,"text":354},{"id":430,"depth":172,"text":431},{"id":501,"depth":172,"text":502},{"id":635,"depth":172,"text":636},{"id":713,"depth":172,"text":714},{"id":766,"depth":172,"text":767},{"id":866,"depth":172,"text":867},"2026-09-12","A workflow enumerates steps a person invented. A loop is a compiled standing order with a run page. An agent reasons when the path is unknown. Three nouns vendors collapse — and operators pay for the confusion.",{"eyebrow":907,"title":908},"Common questions","Standing orders, sequences, and reasoners",[910,913,916,919],{"question":911,"answer":912},"Can a loop contain an agent?","Yes, and that composition is often the adult design. A loop is the standing order — triggers, recipe, run page, skip semantics. A step inside may call an agent when the input is messy, the same way a close pack may include a first-pass read of a PDF. The loop still owns notifications, quiet outcomes, and where artefacts land. Use this pattern when one stage is genuinely unstructured and the rest is known. Refuse a design that lets the agent rewrite the recipe, skip the signer, or hide its tool calls off the run page. The reasoner is a guest on the standing order, not the owner of the job.",{"question":914,"answer":915},"Is an agentic workflow just a loop with extra steps?","Not quite, and the difference shows up under audit. Workflows are authored sequences with explicit stops — often interactive, versioned per department, and meant for jobs that need a person mid-flight. Loops are reused recipes optimized for repeat signals and quiet skips. Many teams use both on the same workstream: the loop watches the folder, the workflow carries the exception that needs counsel. Choose a workflow when stop conditions and roles matter as much as the steps. Choose a loop when the same signal will fire again and nobody should re-describe the job. Refuse a vendor that uses the two words interchangeably on slide one and cannot show both objects in a demo.",{"question":917,"answer":918},"When should I choose an agent instead of a loop?","When nobody can write the steps yet — novel research, one-off negotiation, exploratory analysis, a contract shape the team has not seen. Agents earn their keep on the unknown path. Once the path stabilizes, compile it into a loop or a workflow so the company is not paying for rediscovery every Monday. Use an agent when the cost of a wrong step is bounded — read-only tools, draft-only outputs, a human who will compress the result. Refuse an agent as a Monday cron job. That is expensive theatre, and it fails the first time the model improvises a write. See [a loop is not an agent](a-loop-is-not-an-agent).",{"question":920,"answer":921},"How do I keep the three nouns from collapsing in an RFP?","Score them on different sheets. Ask for a designed sequence with a durable instance and a named stop — that is the workflow. Ask for a repeating signal, a skipped run, and a recipe you can clone — that is the loop. Ask for a bounded reasoner that cites sources and cannot write without a signer — that is the agent. [How to evaluate loop engineering](how-to-evaluate-loop-engineering) and [how to evaluate an agent harness](how-to-evaluate-an-agent-harness) exist because one checklist cannot cover both. Refuse a single “agentic platform” scorecard that starts with context-window size. That sheet buys a model for a job that needed a standing order.","/blog/loop-vs-workflow-vs-agent",{"title":181,"description":905},"explainer","blog/loop-vs-workflow-vs-agent",[927,924,928,929],"loops","agentic-workflow","agents","WsdKtSsbWOvqG1UsJ3XMgcLoc3qJt6B_RUAqj_i_Si4",{"hero":932,"id":934,"title":935,"archived":165,"authors":166,"badge":166,"body":936,"date":166,"definedTerm":166,"department":166,"description":940,"extension":174,"eyebrow":941,"faqHeader":166,"faqs":166,"footerBand":942,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":60,"relatedHeading":948,"seo":949,"series":166,"sitemap":131,"status":166,"stem":950,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":951},{"filename":933},"u2221455217_Flat_design_of_a_futuristic_minimalist_landscape__5d589295-cdea-4ea9-a262-be766881accf_1.png","content/blog/index.md","Exploring the future of intelligence.",{"type":168,"value":937,"toc":938},[],{"title":171,"searchDepth":172,"depth":172,"links":939},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":943,"description":944,"primaryLabel":945,"primaryTo":946,"secondaryLabel":947,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":935,"description":940},"blog/index","BFSWGYO9bcTlaulivKYWyg08_DJHsdGg3OC6g_CG1Hw",[953,1163],{"id":954,"title":955,"archived":165,"authors":956,"badge":958,"body":959,"date":1141,"definedTerm":1142,"department":166,"description":1143,"extension":174,"eyebrow":166,"faqHeader":1144,"faqs":1147,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1157,"relatedHeading":166,"seo":1158,"series":924,"sitemap":131,"status":166,"stem":1159,"subhead":166,"tags":1160,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1162},"content/blog/rbac-for-enterprise-ai.md","What is RBAC for enterprise AI, and why should you care?",[957],{"name":184,"to":136},{"label":186},{"type":168,"value":960,"toc":1135},[961,964,967,975,979,988,999,1002,1016,1019,1023,1032,1035,1049,1052,1056,1059,1062,1086,1092,1096,1103,1116,1125],[190,962,963],{},"RBAC means role-based access control: who is allowed to do what. For enterprise AI, the “who” is not only people. It is also the model acting with someone’s credentials — reading files, and sometimes changing a live system.",[190,965,966],{},"You should care because a fluent answer can still be the wrong change in the wrong place. Access rules are how you keep AI useful without pretending every user should see every record.",[190,968,969,970,974],{},"This guide explains the idea, why it shows up in vendor conversations, and a practical way to start. It is not a claim that one product has solved it. ",[194,971,973],{"href":972},"what-is-ai-governance","What is AI governance"," is the parent definition.",[284,976,978],{"id":977},"what-is-rbac-for-enterprise-ai","What is RBAC for enterprise AI?",[190,980,981,982,987],{},"Classic RBAC, described by Ferraiolo and Kuhn in a ",[194,983,986],{"href":984,"rel":985},"https://csrc.nist.gov/files/pubs/conference/1992/10/13/rolebased-access-controls/final/docs/ferraiolo-kuhn-92.pdf",[198],"NIST paper"," (1992), assigns permissions to roles, then roles to people. Enterprise AI adds three extra questions:",[205,989,990,993,996],{},[208,991,992],{},"Which jobs and files can this person (and this model) see?",[208,994,995],{},"Which tools can it call?",[208,997,998],{},"If it can change a live system, who must approve, and is that approval stored?",[190,1000,1001],{},"A chatbot login answers “may this person talk to the bot?” That is necessary. It is not the same as answering the three questions above.",[190,1003,1004,1005,1009,1010,1015],{},"NIST’s ",[194,1006,1008],{"href":406,"rel":1007},[198],"AI Risk Management Framework"," (2023) and ",[194,1011,1014],{"href":1012,"rel":1013},"https://csrc.nist.gov/pubs/sp/800-207/final",[198],"SP 800-207"," (2020) on zero trust are the public-sector language for the same idea: do not assume a session is trusted just because it authenticated.",[190,1017,1018],{},"Guests, members, and admins are the people side of the same idea: who is on the job. The model side is which tools that session may call. Both belong in RBAC. Do not treat a chatbot login as the whole answer.",[284,1020,1022],{"id":1021},"why-should-you-care-about-rbac-for-ai","Why should you care about RBAC for AI?",[190,1024,1025,1026,1031],{},"IBM’s ",[194,1027,1030],{"href":1028,"rel":1029},"https://newsroom.ibm.com/2024-07-30-ibm-report-escalating-data-breach-disruption-pushes-costs-to-new-highs",[198],"Cost of a Data Breach"," report (2024) put the global average breach cost at $4.88 million. You do not need a breach for RBAC to matter. You need a customer record changed without a name next to the change, or a contractor who still sees a workstream after the project ended.",[190,1033,1034],{},"A simple example: a guest from an agency is invited to a campaign workstream. The model in that room can read the CRM export because a member pasted it. When the campaign ends, the guest login is forgotten. The export is still in the history. Roles that follow the job — not only the person — are how you close that gap.",[190,1036,1037,1038,1043,1044,1048],{},"Microsoft and LinkedIn’s ",[194,1039,1042],{"href":1040,"rel":1041},"https://www.microsoft.com/en-us/worklab/work-trend-index/ai-at-work-is-here-now-comes-the-hard-part",[198],"Work Trend Index"," (2024) found that 78% of AI users bring their own tools (BYOAI). That is ",[194,1045,1047],{"href":1046},"what-is-shadow-ai","shadow AI",": useful, and outside the roles you think you assigned.",[190,1050,1051],{},"You should care if you have guests on a job, if AI can write to CRM or finance systems, or if an auditor might ask who approved a machine-initiated change. If AI only summarises public wiki pages, the stakes are lower — you can still use roles so the wiki is not everyone’s dump of customer data.",[284,1053,1055],{"id":1054},"how-do-you-apply-it-when-ai-can-change-records","How do you apply it when AI can change records?",[190,1057,1058],{},"Write-back means the AI changes a live system. Fail-closed means if nobody approves, nothing happens. Payload means the exact change, shown before it goes out.",[190,1060,1061],{},"A practical sequence:",[641,1063,1064,1072,1075,1083],{},[208,1065,1066,1067,1071],{},"Keep the model from writing until you can name the object class and the signer. ",[194,1068,1070],{"href":1069},"what-is-write-back-governance","Write-back governance"," is the checklist.",[208,1073,1074],{},"For each write, name the approver role — not “the channel”.",[208,1076,1077,1078,1082],{},"Store the payload and the decision so you can reopen them. ",[194,1079,1081],{"href":1080},"what-auditors-are-asking-for","What auditors are asking for"," is the evidence pack.",[208,1084,1085],{},"When someone leaves the job, remove them from the roster the same week.",[190,1087,1088,1091],{},[194,1089,1090],{"href":1046},"Shadow AI"," is what happens when the unofficial path never got those roles.",[284,1093,1095],{"id":1094},"what-should-you-ask-a-vendor","What should you ask a vendor?",[190,1097,1098,1099,1102],{},"A short list of demo questions lives in ",[194,1100,1101],{"href":1080},"what auditors are asking for",". In one sentence: can they show who could see a job, which tool ran, and who approved a write — without a screenshot hunt?",[190,1104,1105,1106,1111,1112,1115],{},"The ",[194,1107,1110],{"href":1108,"rel":1109},"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R1689",[198],"EU AI Act"," (2024/1689) and ",[194,1113,631],{"href":629,"rel":1114},[198]," are reasons those questions are showing up in procurement. You do not have to implement every clause on day one. You do need an answer you could give an auditor.",[190,1117,1118,1119,223,1121,1124],{},"Nimbus’s ",[194,1120,876],{"href":40},[194,1122,1123],{"href":54},"security"," pages describe how we approach this. Other vendors will have their own. The useful test is the same: roles on the job, not only on the chat login.",[190,1126,1127,1128,1130,1131,259],{},"For how teams share the job once access is clear, see ",[194,1129,852],{"href":708},". For where the decision should live after the thread ends, see ",[194,1132,1134],{"href":1133},"search-is-not-memory","search is not memory",{"title":171,"searchDepth":172,"depth":172,"links":1136},[1137,1138,1139,1140],{"id":977,"depth":172,"text":978},{"id":1021,"depth":172,"text":1022},{"id":1054,"depth":172,"text":1055},{"id":1094,"depth":172,"text":1095},"2026-08-27","RBAC","RBAC is who is allowed to do what. For enterprise AI it has to cover the model as well as the people — what it can read, what it can change, and who can stop it. A plain-language guide.",{"eyebrow":1145,"title":1146},"Short answers","Roles when the user is a model",[1148,1151,1154],{"question":1149,"answer":1150},"Is a shared chatbot login the same as RBAC?","No. A shared login says who can open the chat. RBAC says who can see which jobs, which tools, and which live systems — and whether the model may write at all.",{"question":1152,"answer":1153},"Do we need RBAC if AI is read-only?","You still need it for what the model can see. Read-only reduces the chance of a bad write. It does not decide which customer files belong in whose session.",{"question":1155,"answer":1156},"Where should we start?","Name who can approve a change to a live system, keep AI from writing until that is clear, and list unofficial tools. The auditors guide on this site is a first evidence pack.","/blog/rbac-for-enterprise-ai",{"title":955,"description":1143},"blog/rbac-for-enterprise-ai",[924,1142,1161],"access","g2P_DB_QD94yq1LoWlZBKGVnScVo4TxpXZx40Kjx12Y",{"id":1164,"title":1165,"archived":165,"authors":1166,"badge":1168,"body":1169,"date":904,"definedTerm":166,"department":166,"description":1849,"extension":174,"eyebrow":166,"faqHeader":1850,"faqs":1852,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1865,"relatedHeading":166,"seo":1866,"series":924,"sitemap":131,"status":166,"stem":1867,"subhead":166,"tags":1868,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1870},"content/blog/loop-vs-rpa.md","Loop vs RPA",[1167],{"name":184,"to":136},{"label":186},{"type":168,"value":1170,"toc":1839},[1171,1187,1190,1193,1219,1227,1236,1239,1243,1250,1266,1269,1295,1298,1324,1327,1359,1362,1366,1372,1400,1410,1418,1427,1441,1445,1549,1563,1597,1601,1604,1630,1637,1640,1646,1650,1653,1682,1690,1695,1699,1705,1711,1720,1730,1740,1744,1747,1784,1787,1790,1810,1820,1822,1834,1837],[190,1172,1173,1174,1179,1180,1183,1184,259],{},"Robotic process automation records clicks on screens. A standing-order loop records a recipe that runs when a signal fires, skips when nothing changed, and leaves a run page. ",[194,1175,1178],{"href":1176,"rel":1177},"https://www.gartner.com/reviews/market/robotic-process-automation",[198],"Gartner defines RPA"," as software that automates tasks by using scripts that emulate human interaction with an application user interface. That definition is honest about the superpower — ",[211,1181,1182],{},"any screen"," — and the weakness — ",[211,1185,1186],{},"the screen",[190,1188,1189],{},"The two categories are cousins, not synonyms. Both sit above systems of record. Both can run unattended. Both fail when nobody owns the definition of the job. They fail for different mechanical reasons, and programmes that collapse them into “automation” spend years fixing the wrong fragility.",[190,1191,1192],{},"Three adjacent nouns, so they do not leak into this comparison:",[205,1194,1195,1204,1211],{},[208,1196,1197,1199,1200,223,1202,259],{},[211,1198,213],{}," Compiled repeat work with triggers and a run page. See ",[194,1201,735],{"href":221},[194,1203,227],{"href":226},[208,1205,1206,1208,1209,259],{},[211,1207,233],{}," Independent verification that a job finished — not UI replay, not a trigger. See ",[194,1210,238],{"href":237},[208,1212,1213,1215,1216,1218],{},[211,1214,244],{}," A person-designed sequence with stops — often interactive. See ",[194,1217,253],{"href":252},". Different from both RPA and loops.",[190,1220,1221,1226],{},[194,1222,1225],{"href":1223,"rel":1224},"https://www.ibm.com/think/topics/rpa",[198],"IBM’s explainer on robotic process automation"," describes the same pattern in plainer language: software robots execute repetitive office tasks by interacting with applications the way a person would — extracting data, filling forms, moving files. IBM is also careful to separate process-driven replay from data-driven AI. That split is the educational core of this page. A bot follows a recording. A standing-order loop follows a recipe attached to a signal. A model, if it appears at all, is an optional step for messy reads — not the reason the job exists.",[190,1228,1229,1230,1235],{},"This is not a hit piece on UiPath, Automation Anywhere, Blue Prism, or desktop flows in Power Automate. Those products built real value on a real constraint: when the only path into a 1990s terminal or a thick-client ERP is click-type-click, RPA is still the right hammer. ",[194,1231,1234],{"href":1232,"rel":1233},"https://www.deloitte.com/us/en/insights/topics/talent/intelligent-automation-2022-survey-results.html",[198],"Deloitte’s Global Intelligent Automation survey"," found RPA in the mainstream — seventy-four percent of respondents were already implementing it — and also found that toolkits widen because one technology does not cover the work. Integration debt, not model quality, is what usually caps scale.",[190,1237,1238],{},"The mistake is using the hammer when the job already has an API, a webhook, or a file drop — and then calling the recording “AI transformation.”",[284,1240,1242],{"id":1241},"what-rpa-is-as-a-category","What RPA is, as a category",[190,1244,1245,1246,1249],{},"RPA’s contract is the user interface. A person performs a task; a recorder or a low-code author turns that performance into a script; a runtime called a bot or robot executes the script against the same screens. Gartner’s wording matters: the executable is the robot; the thing being automated is a ",[347,1247,1248],{},"task"," inside a process, not necessarily the process end to end.",[190,1251,1252,1253,1258,1259,1262,1263,1265],{},"That is why IBM’s companion note on ",[194,1254,1257],{"href":1255,"rel":1256},"https://www.ibm.com/think/topics/rpa-types",[198],"types of RPA"," is worth reading even if you never buy IBM. The piece argues that “robotic ",[347,1260,1261],{},"process"," automation” is partly a misnomer — the technology is often robotic ",[347,1264,1248],{}," automation — and that orchestration across humans, decisions, and multiple automations is a different job, closer to business process management. Standing-order loops live on that orchestration side of the line: they care about the signal, the skip, and the run, not about whether the fetch happened by API or by a leftover bot.",[190,1267,1268],{},"RPA shines in constrained, UI-only environments:",[205,1270,1271,1277,1283,1289],{},[208,1272,1273,1276],{},[211,1274,1275],{},"Legacy green-screen or thick-client ERP"," with no stable API",[208,1278,1279,1282],{},[211,1280,1281],{},"High-volume, low-variance data entry"," where the steps never change and the screen rarely does",[208,1284,1285,1288],{},[211,1286,1287],{},"Short-lived bridge automation"," while IT delivers a proper integration",[208,1290,1291,1294],{},[211,1292,1293],{},"Attended automation"," where a person still drives the session and the bot takes the repetitive keystrokes",[190,1296,1297],{},"Operator virtues of a mature RPA programme are real:",[205,1299,1300,1306,1312,1318],{},[208,1301,1302,1305],{},[211,1303,1304],{},"Deterministic steps"," when the UI cooperates",[208,1307,1308,1311],{},[211,1309,1310],{},"A central bot inventory",", if the CoE actually has one",[208,1313,1314,1317],{},[211,1315,1316],{},"Audit logs of bot accounts",", if IT enforces service identities instead of shared logins",[208,1319,1320,1323],{},[211,1321,1322],{},"Speed to a first automation"," when the alternative is a twelve-month interface project",[190,1325,1326],{},"Operator failures everyone has seen are also real:",[205,1328,1329,1335,1341,1347,1353],{},[208,1330,1331,1334],{},[211,1332,1333],{},"Brittle selectors"," — CSS changes, A/B tests, localisation, a vendor’s “minor” redesign",[208,1336,1337,1340],{},[211,1338,1339],{},"Timing flakes"," — load spinners, network blips, a pop-up that was not on the recording",[208,1342,1343,1346],{},[211,1344,1345],{},"No skip semantics"," — the bot runs, clicks through zero rows, and emails success",[208,1348,1349,1352],{},[211,1350,1351],{},"Outcomes in bot logs",", not on a roster-facing run page",[208,1354,1355,1358],{},[211,1356,1357],{},"Shadow bots"," on personal laptops when the IT backlog is measured in quarters",[190,1360,1361],{},"Deloitte’s survey is useful because it normalises the second list. Organisations started with RPA and OCR, got value, then hit the limit of automating the current process with one or two tools. The response was a wider toolkit and, often, process redesign. That is the mature reading. The immature reading is “replace the CoE with agents.”",[284,1363,1365],{"id":1364},"what-a-standing-order-loop-is-as-a-category","What a standing-order loop is, as a category",[190,1367,1368,1369,1371],{},"A loop is a ",[211,1370,217],{}," in the company’s automation library:",[205,1373,1374,1382,1388,1394],{},[208,1375,1376,1379,1380,259],{},[211,1377,1378],{},"Triggers"," — schedule, file, data change, drop, ping, run now. See ",[194,1381,227],{"href":226},[208,1383,1384,1387],{},[211,1385,1386],{},"Recipe"," — the trusted sequence, versioned, replayable",[208,1389,1390,1393],{},[211,1391,1392],{},"Run page"," — what ran, skipped, produced, notified",[208,1395,1396,1399],{},[211,1397,1398],{},"Skip when nothing changed"," — quiet success is success",[190,1401,1402,1403,1405,1406,1409],{},"Loops prefer structured paths: a CRM field changed, a file hash matches last week, a billing webhook is idempotent. When inputs are messy — a PDF allowance list, a scanned statement — a loop may include a ",[211,1404,468],{}," model step, then return to deterministic writes with ",[194,1407,1408],{"href":1069},"write-back governance",". The model is not the loop. The loop is the standing order that decided to call a reader.",[190,1411,1412,1413,1417],{},"Compare ",[194,1414,1416],{"href":1415},"loop-vs-workflow-vs-agent","loop vs workflow vs agent",": loops compile repeat work; agents reason on novel paths; workflows carry explicit human stops. RPA is a fourth cousin — UI replay — not a substitute for any of the three. If you only remember one sentence from this page, remember that.",[190,1419,1420,1423,1424,1426],{},[211,1421,1422],{},"Operator test from"," ",[194,1425,886],{"href":401},": run ten times with empty inputs. Do you get ten skipped run pages — or ten green checkmarks that lied? RPA programmes often fail that test because “the script finished” is treated as success. Finishing a script that had nothing to do is how Finance learns to ignore the 6am email.",[190,1428,1429,1432,1433,1436,1437,1440],{},[194,1430,281],{"href":279,"rel":1431},[198]," is not an argument to rip out RPA. It is an argument to stop treating screen bots as the only automation language while models make ",[211,1434,1435],{},"reading"," cheap and ",[211,1438,1439],{},"governed writes"," remain hard. Usage without redesign is the survey’s recurring theme. Redesign, for repeat work, looks like a recipe library with start conditions — not a larger bot farm.",[284,1442,1444],{"id":1443},"side-by-side","Side by side",[504,1446,1447,1459],{},[507,1448,1449],{},[510,1450,1451,1453,1456],{},[513,1452,515],{},[513,1454,1455],{},"RPA",[513,1457,1458],{},"Standing-order loop",[526,1460,1461,1472,1483,1494,1505,1516,1527,1538],{},[510,1462,1463,1466,1469],{},[531,1464,1465],{},"Primary interface",[531,1467,1468],{},"Screen clicks",[531,1470,1471],{},"Events, files, APIs",[510,1473,1474,1477,1480],{},[531,1475,1476],{},"When UI changes",[531,1478,1479],{},"Breaks often",[531,1481,1482],{},"Often unaffected",[510,1484,1485,1488,1491],{},[531,1486,1487],{},"Repeat signal",[531,1489,1490],{},"Scheduler on a bot",[531,1492,1493],{},"Several trigger types",[510,1495,1496,1499,1502],{},[531,1497,1498],{},"Nothing to do",[531,1500,1501],{},"May still “succeed”",[531,1503,1504],{},"Skipped run recorded",[510,1506,1507,1510,1513],{},[531,1508,1509],{},"Outcome surface",[531,1511,1512],{},"Bot log / email",[531,1514,1515],{},"Run page + roster",[510,1517,1518,1521,1524],{},[531,1519,1520],{},"Best for",[531,1522,1523],{},"No API, stable UI",[531,1525,1526],{},"Repeat ops with signals",[510,1528,1529,1532,1535],{},[531,1530,1531],{},"Model required?",[531,1533,1534],{},"No",[531,1536,1537],{},"Optional, bounded",[510,1539,1540,1543,1546],{},[531,1541,1542],{},"Typical fragility",[531,1544,1545],{},"Selectors and timing",[531,1547,1548],{},"Stale recipes, missing skips",[190,1550,1551,1552,1555,1556,1559,1560,259],{},"Neither row replaces your system of record. Both sit ",[211,1553,1554],{},"above"," CRM and ERP. They are part of the automate pillar in ",[194,1557,1558],{"href":844},"the four pillars of an enterprise AI platform",", not a second ledger. If a bot or a loop writes without a quoted payload and a signer, you have a control problem that no category name will fix. See ",[194,1561,1562],{"href":972},"what is AI governance",[786,1564,1566],{"className":788,"code":1565,"language":790,"meta":171,"style":171},"flowchart TD\n  door{\"How does the work get in?\"}\n  door -->|\"Only a screen\"| rpaPick[\"RPA: record the clicks\"]\n  door -->|\"File, field, or event\"| loopPick[\"Loop: run the recipe\"]\n  rpaPick --> fetch[\"Often: fetch a file\"]\n  fetch --> loopPick\n",[792,1567,1568,1572,1577,1582,1587,1592],{"__ignoreMap":171},[795,1569,1570],{"class":797,"line":798},[795,1571,801],{},[795,1573,1574],{"class":797,"line":172},[795,1575,1576],{},"  door{\"How does the work get in?\"}\n",[795,1578,1579],{"class":797,"line":809},[795,1580,1581],{},"  door -->|\"Only a screen\"| rpaPick[\"RPA: record the clicks\"]\n",[795,1583,1584],{"class":797,"line":815},[795,1585,1586],{},"  door -->|\"File, field, or event\"| loopPick[\"Loop: run the recipe\"]\n",[795,1588,1589],{"class":797,"line":821},[795,1590,1591],{},"  rpaPick --> fetch[\"Often: fetch a file\"]\n",[795,1593,1594],{"class":797,"line":827},[795,1595,1596],{},"  fetch --> loopPick\n",[284,1598,1600],{"id":1599},"when-rpa-is-still-the-right-tool","When RPA is still the right tool",[190,1602,1603],{},"Choose RPA — or keep the bot you have — when most of the following are true:",[641,1605,1606,1612,1618,1624],{},[208,1607,1608,1611],{},[211,1609,1610],{},"No integration exists"," and IT has not prioritized one. The screen is the only door, not the door a citizen developer preferred.",[208,1613,1614,1617],{},[211,1615,1616],{},"The UI path is stable."," That module has not been redesigned in years, and the vendor’s roadmap does not threaten it this quarter.",[208,1619,1620,1623],{},[211,1621,1622],{},"Volume justifies babysitting."," Operations accepts selector maintenance as opex and has a named owner for break-fix, not a hero who “knows the recording.”",[208,1625,1626,1629],{},[211,1627,1628],{},"The action is fetch-shaped."," Scrape, download, paste into a governed folder that a standing-order loop picks up next. The bot’s job ends when the file lands.",[190,1631,1632,1633,1636],{},"That last pattern is common and sensible: ",[211,1634,1635],{},"RPA fetches; the loop processes."," The bot is a temporary or permanent adapter. The loop owns variance checks, notifications, and draft writes waiting on sign. You have not “failed at AI” because a 1990s terminal still needs a click. You have been honest about the interface.",[190,1638,1639],{},"Also keep RPA for attended automation where a person is already in the session. A desktop helper that types the next twenty fields while a clerk reviews exceptions is a different object from an unattended Monday close. Do not force that helper into a standing-order costume.",[190,1641,1642,1645],{},[194,1643,408],{"href":406,"rel":1644},[198]," still applies if the bot’s output later feeds a model or a write. Map the system. Measure the outcomes. Do not pretend a bot log is Measure if only the CoE can read it.",[284,1647,1649],{"id":1648},"when-a-standing-order-loop-is-the-right-tool","When a standing-order loop is the right tool",[190,1651,1652],{},"Choose a loop when:",[641,1654,1655,1661,1667,1676],{},[208,1656,1657,1660],{},[211,1658,1659],{},"The signal is already digital"," — webhook, CRM field, calendar, a file hash, an event from billing",[208,1662,1663,1666],{},[211,1664,1665],{},"Skip semantics matter"," — month-end with no exceptions should not spam Legal",[208,1668,1669,1672,1673],{},[211,1670,1671],{},"The roster needs a run page"," — audit, handoffs, ",[194,1674,1675],{"href":708},"collaborative AI",[208,1677,1678,1681],{},[211,1679,1680],{},"You will reuse the recipe"," across teams without copying Slack threads",[190,1683,1684,1689],{},[194,1685,1688],{"href":1686,"rel":1687},"https://www.ibm.com/think/topics/event-driven-architecture",[198],"IBM on event-driven architecture"," is the right adjacent reading for this side of the comparison. Something happened elsewhere; your process responds with idempotence and a record. If the same event arrives twice, one run should process and one should skip. Bots can be written that way. They often are not, because the recording did not include “check whether we already did this.”",[190,1691,1692,1693,259],{},"Loops are also the right tool when the “RPA job” is actually document intelligence wearing a bot costume. Bots should not pretend to read contracts. A loop step may use a model to extract tables; the write still quotes a payload and waits on sign. See ",[194,1694,703],{"href":702},[284,1696,1698],{"id":1697},"what-goes-wrong-in-hybrid-programmes","What goes wrong in hybrid programmes",[190,1700,1701,1704],{},[211,1702,1703],{},"Lift-and-shift the bot into a loop skin."," Changing the logo does not add skip semantics or a roster. If the runtime is still clicking Production with a god account, you kept the brittleness and added a new name.",[190,1706,1707,1710],{},[211,1708,1709],{},"Loop that secretly RPAs the CRM."," If your “AI automation” is still one service identity clicking through a web UI because “the connector was slower,” you have not moved categories. You have hidden a bot behind a recipe.",[190,1712,1713,1716,1717,1719],{},[211,1714,1715],{},"RPA for PDF intelligence."," Screen replay is a poor reader. If the job is “understand this invoice,” you need a document step with evals — see ",[194,1718,238],{"href":237}," — not a tighter selector on the PDF viewer.",[190,1721,1722,1725,1726,1729],{},[211,1723,1724],{},"No ownership."," RPA bots die when Linda leaves. Loops die when “the recipe” lives in Linda’s channel. ",[194,1727,1728],{"href":221},"Loop engineering"," is org-owned recipes — the same discipline as shared close checklists. Deloitte’s wider-toolkit finding is really an ownership finding: more tools without a named owner is how shadow automation returns.",[190,1731,1732,1735,1736,1739],{},[211,1733,1734],{},"Automation that cannot refuse."," Whether the runtime clicks or reacts to a webhook, an unsigned write should not land. ",[194,1737,1738],{"href":1069},"What is write-back governance"," is category-agnostic. If your CoE cannot show a refused payload and an unchanged system of record, you are scoring the wrong success metric.",[284,1741,1743],{"id":1742},"a-practical-migration-path","A practical migration path",[190,1745,1746],{},"Treat migration as an inventory problem, not a branding problem.",[641,1748,1749,1755,1761,1767,1773],{},[208,1750,1751,1754],{},[211,1752,1753],{},"Inventory bots."," For each one: which screen, how often, how brittle, which service account, who gets the failure email, what the last three incidents were.",[208,1756,1757,1760],{},[211,1758,1759],{},"Mark API-available jobs."," If the system now exposes an event, a file export, or a documented API, migrate those jobs to standing-order loops first. Stop paying selector tax on work that no longer needs a screen.",[208,1762,1763,1766],{},[211,1764,1765],{},"Pair fetch bots with loops."," Where the screen remains the only door, shrink the bot to fetch-and-drop. The loop owns processing, skip, notify, and any draft write.",[208,1768,1769,1772],{},[211,1770,1771],{},"Keep one honest bot"," where the screen is the only door and the UI is stable. Review it quarterly with IT for an integration. Do not hide it. Name it in the architecture review.",[208,1774,1775,1778,1779,1423,1781,1783],{},[211,1776,1777],{},"Score new buys"," with ",[194,1780,886],{"href":401},[347,1782,745],{}," your existing RPA ops metrics — hours lost to break-fix, mean time to repair a selector, percentage of “success” emails that were empty runs.",[190,1785,1786],{},"A sensible first quarter is not “zero bots.” It is “zero bots clicking a system that already had an API,” plus “every remaining bot has a named owner and a fetch-shaped job.” That is a programme a CFO can understand and an auditor can follow.",[190,1788,1789],{},"Department starting points for the loop side of the hybrid:",[205,1791,1792,1798,1804],{},[208,1793,1794,1797],{},[194,1795,1796],{"href":674},"Loops for finance and planning"," — scheduled packs, quiet skips",[208,1799,1800,1803],{},[194,1801,1802],{"href":688},"Loops for revenue operations"," — stage-triggered hygiene",[208,1805,1806,1809],{},[194,1807,1808],{"href":702},"Loops for legal and compliance"," — inbound redlines without click bots",[190,1811,849,1812,1815,1816,1819],{},[194,1813,1814],{"href":622},"what is an enterprise AI operating system"," for the kernel metaphor, and ",[194,1817,1818],{"href":425},"loop engineering vs harness engineering"," when interactive agents need different stops than repeat recipes.",[284,1821,867],{"id":866},[190,1823,1824,1825,1778,1828,1830,1831,1833],{},"Nimbus Loops are standing orders on ",[194,1826,1827],{"href":32},"workstreams",[194,1829,876],{"href":40}," — not a bot farm and not a recorder. They prefer events, files, and APIs; they record skipped runs; they notify a roster. When a legacy screen is still the only door, the honest pattern is the one above: let the incumbent RPA tool click, land the file in ",[194,1832,15],{"href":16}," or a governed folder, and let the Loop compile what happens next.",[190,1835,1836],{},"That is one vendor’s implementation of the category split, not a requirement that every bot be replaced. If you are scoring platforms, keep Gartner’s UI-emulation definition for RPA and keep this page’s run-page tests for standing orders. Run both. The companies that get hurt are the ones that buy a single noun for both jobs.",[891,1838,893],{},{"title":171,"searchDepth":172,"depth":172,"links":1840},[1841,1842,1843,1844,1845,1846,1847,1848],{"id":1241,"depth":172,"text":1242},{"id":1364,"depth":172,"text":1365},{"id":1443,"depth":172,"text":1444},{"id":1599,"depth":172,"text":1600},{"id":1648,"depth":172,"text":1649},{"id":1697,"depth":172,"text":1698},{"id":1742,"depth":172,"text":1743},{"id":866,"depth":172,"text":867},"RPA records clicks on screens. A standing-order loop records a recipe that runs when a signal fires, skips when nothing changed, and leaves a run page. Both have a place — the mistake is sending a bot to read a PDF when an API would do.",{"eyebrow":907,"title":1851},"Clicks, standing orders, and when each fits",[1853,1856,1859,1862],{"question":1854,"answer":1855},"Should we replace our RPA bots with standing-order loops?","Not automatically, and a rip-and-replace programme is how you lose the jobs that still have no API. Keep RPA where the only interface is a legacy screen and the UI path is stable enough that selector maintenance is accepted opex. Add standing-order loops where the job already has a digital signal, needs skip semantics, and should land on a run page the roster can audit. Use a hybrid when a bot’s only honest job is to fetch a file that a loop then processes. Refuse a migration that changes the logo on the bot farm and calls the result “AI transformation.” The screen did not get an API because you renamed the programme.",{"question":1857,"answer":1858},"Is a loop just RPA with a model attached?","No. A loop is a compiled standing order — triggers, recipe, run page — that may include a bounded model step for messy inputs. RPA is UI replay: scripts that emulate a person on a screen. Some loops never call a model; some RPA bots never should have been bots. Use RPA when the application will only talk through its interface, and use a loop when the signal is already an event, a file, or a field. Refuse a pitch that treats “intelligent automation” as a single category: Gartner’s RPA definition is about emulating UI interaction, which is a different object from a standing order.",{"question":1860,"answer":1861},"Why do RPA projects break when a vendor moves a button?","Because the bot’s contract is the screen, not the business event. Selectors, pixel layout, load timing, localisation, and surprise pop-ups are all part of the interface the script assumed would sit still. When the vendor redesigns a module, the recording is now a lie. Standing-order loops prefer structured events and payloads when those exist, so a CSS change does not cancel month-end. Keep the bot if the screen is truly the only door — and budget the break-fix. Refuse to point a bot at a system that already exposes an API just because the recording was faster than an integration ticket. Speed in week one is how you buy fragility for year two.",{"question":1863,"answer":1864},"What should a migration inventory include?","For each bot, name the screen, the frequency, the last three break-fix incidents, the service account, and whether an API or file export now exists. Mark jobs that can move to a standing-order loop first — those are the ones still paying a selector tax for no reason. Keep a short list of screens that remain the only door and review them quarterly with IT. Pair fetch-only bots with loops so the bot’s job ends when the file lands. Refuse an inventory that is only a licence count. Licences do not tell you which automations lie on empty tables.","/blog/loop-vs-rpa",{"title":1165,"description":1849},"blog/loop-vs-rpa",[927,924,1455,1869],"automation","-iI03pSB3WJWjPFfWvfEvVDXqlQitOm0KbTlQ1rmFdw",{"enabled":165,"message":1872,"linkLabel":79,"linkHref":80,"id":1873,"title":1874,"archived":165,"authors":166,"badge":166,"body":1875,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1879,"relatedHeading":166,"seo":1880,"series":166,"sitemap":165,"status":166,"stem":1881,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1882},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":168,"value":1876,"toc":1877},[],{"title":171,"searchDepth":172,"depth":172,"links":1878},[],"/shared/hiring",{"title":1874,"description":171},"shared/hiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",{"fold":1884,"id":1888,"title":1889,"archived":165,"authors":166,"badge":166,"body":1890,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":1894,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1898,"relatedHeading":166,"seo":1899,"series":166,"sitemap":165,"status":166,"stem":1900,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1901},{"headline":1885,"description":1886,"primaryLabel":8,"primaryTo":1887,"secondaryLabel":947,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed agent swarms, 2,000+ integrations, and a knowledge graph that stays inside your walls. Start on Free.","/signup?plan=free","content/shared/cta.md","Site CTAs",{"type":168,"value":1891,"toc":1892},[],{"title":171,"searchDepth":172,"depth":172,"links":1893},[],{"headline":1895,"description":1896,"primaryLabel":8,"primaryTo":1887,"secondaryLabel":1897,"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","/shared/cta",{"title":1889,"description":171},"shared/cta","PS2VPJsszmUpMBZT6nEp8cWXCdeiN6zDRl-p8d0uY2k",1789797893111]