[{"data":1,"prerenderedAt":915},["ShallowReactive",2],{"insight-insights_en-what-agents-should-never-do-alone":3,"insight-related-insights_en-what-agents-should-never-do-alone":270},{"id":4,"title":5,"author":6,"blobHue":10,"body":11,"category":245,"date":246,"description":17,"draft":247,"extension":248,"featured":247,"headline":249,"hue":250,"letter":251,"meta":252,"navigation":253,"path":254,"readMinutes":255,"related":256,"seo":260,"stem":261,"summary":262,"toc":263,"__hash__":269},"insights_en\u002Finsights\u002Fwhat-agents-should-never-do-alone.md","What agents should never do alone",{"name":7,"role":8,"bio":9},"André","Founder & CTO","André is the founder and CTO of WizardingCode. Eight years building the software companies run on, now putting agents into production.",null,{"type":12,"value":13,"toc":236},"minimark",[14,18,21,26,33,39,45,48,52,55,58,61,65,68,90,93,97,100,214,217,223,227,230,233],[15,16,17],"p",{},"The question we hear most from operations leads is not “can the agent do this?”. It is “what stops it doing something stupid?”. The honest answer is not a better prompt. It is a short list of rules, written by the people who own the risk, that the agent cannot talk its way around.",[15,19,20],{},"Writing those rules is less work than it sounds. Almost everything that should stay with a person falls into three kinds of decision.",[22,23,25],"h2",{"id":24},"three-kinds-of-decisions","Three kinds of decisions",[15,27,28,32],{},[29,30,31],"strong",{},"Money."," Refunds, credits, discounts, prices, payments. Anything that moves money in or out of the business, or changes what a customer pays.",[15,34,35,38],{},[29,36,37],{},"Promises."," A delivery date, a replacement, an exception to the policy, anything that commits the company to a customer or a supplier. A wrong answer is fixable. A wrong promise has to be honoured or broken.",[15,40,41,44],{},[29,42,43],{},"Anything you can’t undo."," Deleting records, sending to your whole customer base, cancelling or changing an order that is already moving. If the mistake cannot be reversed by clicking something, a person decides.",[15,46,47],{},"Everything else, like reading, classifying, drafting, looking up, summarising and routing, is usually safe for an agent to do alone, provided it is visible afterwards.",[22,49,51],{"id":50},"draft-then-apply","Draft, then apply",[15,53,54],{},"The most useful distinction in approval rules is between preparing an action and executing it. An agent can do all the work of a refund: find the order, check the policy, calculate the amount, write the reply. Then it stops, and a person applies it with one tap.",[15,56,57],{},"This keeps most of the time saving and almost none of the risk. The person is not doing the work. They are checking a finished proposal, with the order, the policy and the amount on one screen.",[15,59,60],{},"Over time, some drafts earn the right to apply themselves. When a person has approved the same kind of action enough times without changes, you can move it below the threshold. That is a decision for the team that owns it, not for the agent.",[22,62,64],{"id":63},"thresholds-not-feelings","Thresholds, not feelings",[15,66,67],{},"“Ask me when it’s important” is not a rule. An agent cannot know what feels important to you. A rule needs a number, a category or a list:",[69,70,71,78,84],"ul",{},[72,73,74,77],"li",{},[29,75,76],{},"A number."," Refunds up to a limit are applied; above it, they go to the ops lead.",[72,79,80,83],{},[29,81,82],{},"A category."," Any change to a contract goes to legal, whatever the value.",[72,85,86,89],{},[29,87,88],{},"A list."," New suppliers, key accounts and anything to the press always go to a person.",[15,91,92],{},"Every rule names who decides and where they are asked: in Slack, Teams or email, wherever that person already works. A rule that sends approvals to a dashboard nobody opens is a rule that stops the business.",[22,94,96],{"id":95},"a-worked-example","A worked example",[15,98,99],{},"This is the shape of a rule set for an online store’s support and commerce agents. The limits are yours to set; the structure is what matters.",[101,102,103,119],"table",{},[104,105,106],"thead",{},[107,108,109,113,116],"tr",{},[110,111,112],"th",{},"ACTION",[110,114,115],{},"AGENT ALONE",[110,117,118],{},"GOES TO A PERSON",[120,121,122,136,149,162,175,188,201],"tbody",{},[107,123,124,130,133],{},[125,126,127],"td",{},[29,128,129],{},"Order status, tracking, policy questions",[125,131,132],{},"Answers",[125,134,135],{},"Never, unless the customer asks for one",[107,137,138,143,146],{},[125,139,140],{},[29,141,142],{},"Refund",[125,144,145],{},"Drafts every one, applies small ones",[125,147,148],{},"Above €500 in this example, the ops lead",[107,150,151,156,159],{},[125,152,153],{},[29,154,155],{},"Voucher or discount",[125,157,158],{},"Proposes, inside the margin floor",[125,160,161],{},"Anything outside the agreed limits",[107,163,164,169,172],{},[125,165,166],{},[29,167,168],{},"Price change",[125,170,171],{},"Never writes a price",[125,173,174],{},"The pricing owner, after the margin check",[107,176,177,182,185],{},[125,178,179],{},[29,180,181],{},"Delivery date",[125,183,184],{},"Quotes what the courier data says",[125,186,187],{},"Any exception or guarantee",[107,189,190,195,198],{},[125,191,192],{},[29,193,194],{},"Order change or cancellation",[125,196,197],{},"Drafts",[125,199,200],{},"Always applied by a person",[107,202,203,208,211],{},[125,204,205],{},[29,206,207],{},"Campaign to the whole base",[125,209,210],{},"Prepares and simulates",[125,212,213],{},"Always sent by a person",[15,215,216],{},"Start with the right-hand column. The right-hand column is the list of things your team has decided to keep. Everything to its left is work they no longer have to do.",[218,219,220],"blockquote",{},[15,221,222],{},"If you can’t undo it, a person does it.",[22,224,226],{"id":225},"the-veto-that-isnt-a-model","The veto that isn’t a model",[15,228,229],{},"Some rules are too important to leave to a language model, even one that is being checked. Margin is the clearest case.",[15,231,232],{},"In the marketplace system we built, no agent ever writes a price. Agents can propose a discount or a clearance offer, but every proposal passes through a margin guardrail first. The guardrail is plain code, not a model. It calculates the floor for that product after returns, fees and shipping, and anything below it is vetoed. There is nothing to persuade and no prompt to get wrong.",[15,234,235],{},"That is the pattern we use wherever a rule can be expressed as arithmetic or a lookup. The model proposes, deterministic code checks, and a person approves what the rules say a person approves. Each layer does the thing it is good at, and none of them is asked to be the last line of defence alone.",{"title":237,"searchDepth":238,"depth":238,"links":239},"",2,[240,241,242,243,244],{"id":24,"depth":238,"text":25},{"id":50,"depth":238,"text":51},{"id":63,"depth":238,"text":64},{"id":95,"depth":238,"text":96},{"id":225,"depth":238,"text":226},"playbooks","2026-09-08",false,"md","What agents should never do ==alone.==","sun","!",{},true,"\u002Finsights\u002Fwhat-agents-should-never-do-alone",4,[257,258,259],"every-agent-needs-a-judge","the-30-day-playbook-week-by-week","what-an-agentic-os-is-and-what-it-isnt",{"title":5,"description":17},"insights\u002Fwhat-agents-should-never-do-alone","A practical way to write approval rules: money, promises and anything you can’t undo.",[264,265,266,267,268],{"id":24,"label":25},{"id":50,"label":51},{"id":63,"label":64},{"id":95,"label":96},{"id":225,"label":226},"mWnCbu3ZKOI9CJrpjxbakDDnQwkJuenNM8EI7HSjdMA",[271,463,675],{"id":272,"title":273,"author":274,"blobHue":10,"body":275,"category":443,"date":444,"description":279,"draft":247,"extension":248,"featured":247,"headline":445,"hue":446,"letter":447,"meta":448,"navigation":253,"path":449,"readMinutes":255,"related":450,"seo":453,"stem":454,"summary":455,"toc":456,"__hash__":462},"insights_en\u002Finsights\u002Fevery-agent-needs-a-judge.md","Every agent needs a judge",{"name":7,"role":8,"bio":9},{"type":12,"value":276,"toc":436},[277,280,283,287,290,293,296,300,303,371,374,377,381,384,405,408,412,415,418,421,426,430,433],[15,278,279],{},"A language model is very good at sounding right. That is the problem. An answer with a wrong refund amount reads exactly as confidently as one with the right amount, and a person skimming a queue of drafts will not catch it every time.",[15,281,282],{},"So we don’t ask people to catch it. In the marketplace system we built, 90 agents work across eight departments, and every team has a judge: 9 judges in all. A judge is a second model whose only job is to check another agent’s answer before anyone relies on it.",[22,284,286],{"id":285},"why-a-second-model","Why a second model",[15,288,289],{},"Asking the same model to review its own work helps less than you would think. It tends to agree with itself, and it shares the blind spots that produced the mistake in the first place.",[15,291,292],{},"That is why our judges run on a different model family from the agents they check. Different training, different habits, different failure modes. When two unrelated models agree that an answer is grounded and within policy, that means much more than one model agreeing with itself twice.",[15,294,295],{},"A judge also sees the answer differently. The agent was trying to be helpful. The judge is only trying to find what is wrong. Giving it a narrow brief, and nothing else to do, is what makes it useful.",[22,297,299],{"id":298},"block-or-grade-later","Block or grade later",[15,301,302],{},"There are two ways to put a judge in the path, and choosing between them is the main design decision.",[101,304,305,317],{},[104,306,307],{},[107,308,309,311,314],{},[110,310],{},[110,312,313],{},"BLOCK AND REPAIR",[110,315,316],{},"SHIP, THEN GRADE",[120,318,319,332,345,358],{},[107,320,321,326,329],{},[125,322,323],{},[29,324,325],{},"When the judge runs",[125,327,328],{},"Before the answer leaves",[125,330,331],{},"After it has gone out",[107,333,334,339,342],{},[125,335,336],{},[29,337,338],{},"If it fails",[125,340,341],{},"Sent back once with the reasons, then shipped with reservations",[125,343,344],{},"Flagged, counted, fed into the next lessons",[107,346,347,352,355],{},[125,348,349],{},[29,350,351],{},"Cost to the user",[125,353,354],{},"Some extra seconds",[125,356,357],{},"None",[107,359,360,365,368],{},[125,361,362],{},[29,363,364],{},"Use it for",[125,366,367],{},"Anything a customer sees, anything with money",[125,369,370],{},"High volume, low risk, easy to correct",[15,372,373],{},"In the blocking path, a failed answer is not simply rejected. It goes back to the agent once, with the judge’s reasons, and the agent gets a chance to repair it. If the repaired answer still fails, it goes out marked with the judge’s reservations, or, where the rules require it, to a person. Nothing leaves without a verdict.",[15,375,376],{},"In the grading path, the answer goes out and the judge scores it afterwards. The scores show where an agent drifts, and they feed the lessons the system learns overnight. Those lessons are not applied on their own: a person approves each one before agents use it.",[22,378,380],{"id":379},"what-a-judge-checks","What a judge checks",[15,382,383],{},"A judge with a vague brief (“is this a good answer?”) is expensive noise. Ours check specific things, and each check can fail on its own:",[385,386,388],"prose-checklist",{"title":387},"What a judge checks, every time",[69,389,390,393,396,399,402],{},[72,391,392],{},"Can every number in the answer be traced to data the agent actually read in this run?",[72,394,395],{},"Does it contradict a policy in the shared memory?",[72,397,398],{},"Does it answer the question that was asked, completely?",[72,400,401],{},"Does it propose an action the approval rules do not allow?",[72,403,404],{},"Is the tone right for who will read it?",[15,406,407],{},"The first check is the one that matters most. A refund amount, a delivery date or a stock figure that does not appear in any tool result is treated as invented, however plausible it looks.",[22,409,411],{"id":410},"what-it-costs-and-when-to-skip-it","What it costs, and when to skip it",[15,413,414],{},"A judge is another model call on every answer. It adds tokens, and in the blocking path it adds seconds. For a customer reply that is cheap insurance. For some work, it is waste.",[15,416,417],{},"We skip the judge, or move it to grading later, when the output is low stakes, reversible and cheap to check. An internal tag suggestion that a person sees anyway, or a draft that someone always edits before sending, does not need a second model standing in front of it.",[15,419,420],{},"We also never ask a model to check what code can check. Whether a price is above its floor, whether a date is in the future or whether an order exists are deterministic questions. They get deterministic answers, which are faster and do not have opinions.",[218,422,423],{},[15,424,425],{},"A judge is for judgement. If a rule can be written as code, write it as code.",[22,427,429],{"id":428},"fail-loudly-not-silently","Fail loudly, not silently",[15,431,432],{},"Judges fail too. They time out, or their provider is down for a few minutes. The worst thing a system can do then is pretend the check happened.",[15,434,435],{},"When a judge cannot run, the answer is shown with a visible “not validated” mark, and the person reading it decides whether to rely on it. A silent pass is how a system loses the trust of the people who work with it, and that trust is much harder to rebuild than a timeout is to fix.",{"title":237,"searchDepth":238,"depth":238,"links":437},[438,439,440,441,442],{"id":285,"depth":238,"text":286},{"id":298,"depth":238,"text":299},{"id":379,"depth":238,"text":380},{"id":410,"depth":238,"text":411},{"id":428,"depth":238,"text":429},"engineering","2026-09-01","Every agent needs a ==judge.==","blue","J",{},"\u002Finsights\u002Fevery-agent-needs-a-judge",[451,259,452],"what-agents-should-never-do-alone","testing-a-campaign-on-customers-who-dont-exist",{"title":273,"description":279},"insights\u002Fevery-agent-needs-a-judge","Why we put a second model in front of every answer, and when it isn’t worth the cost.",[457,458,459,460,461],{"id":285,"label":286},{"id":298,"label":299},{"id":379,"label":380},{"id":410,"label":411},{"id":428,"label":429},"XzL5diXOtcDslArv3P74XXRkQd_4qZoVSP7GUPDaC8E",{"id":464,"title":465,"author":466,"blobHue":10,"body":467,"category":245,"date":655,"description":471,"draft":247,"extension":248,"featured":247,"headline":656,"hue":657,"letter":658,"meta":659,"navigation":253,"path":660,"readMinutes":255,"related":661,"seo":664,"stem":665,"summary":666,"toc":667,"__hash__":674},"insights_en\u002Finsights\u002Fthe-30-day-playbook-week-by-week.md","The 30-day playbook, week by week",{"name":7,"role":8,"bio":9},{"type":12,"value":468,"toc":647},[469,472,475,479,482,485,489,492,519,522,526,529,532,535,539,542,545,627,631,634,637,641,644],[15,470,471],{},"Thirty days sounds fast for putting AI agents into production. It is fast. It is also the reason most of our projects ship: a fixed date forces every decision that a pilot would postpone to be taken in the first week.",[15,473,474],{},"This is the playbook we follow. Every step ends with something written down and someone’s name next to it.",[22,476,478],{"id":477},"week-0-diagnose","Week 0: diagnose",[15,480,481],{},"It starts with a free call. If there is a fit, we spend the next week inside your operations, most of it with the people who do the work. We sit in on the inbox, the report, the supplier file. We want to see where the hours go and where the money leaks, not how the process is described in a slide.",[15,483,484],{},"The artefact is a map of your operations with the value of every agent we would build, and a fixed price. The sign-off is yours: which process goes first. We push for one with volume, clear rules and a number someone already cares about.",[22,486,488],{"id":487},"week-1-map","Week 1: map",[15,490,491],{},"This is the week most pilots skip, and the week that decides whether yours ships.",[493,494,495,501,507,513],"ol",{},[72,496,497,500],{},[29,498,499],{},"Access."," Real credentials to the real systems: the CRM, the helpdesk, the ERP, the inbox. Not an export.",[72,502,503,506],{},[29,504,505],{},"Real cases."," A set of past emails, tickets or files, with what a good answer looked like. They become the tests.",[72,508,509,512],{},[29,510,511],{},"One metric, signed off."," First response time, time to spot a new listing, partner hours on admin. One number, owned by the team whose work changes, signed by the person who owns it.",[72,514,515,518],{},[29,516,517],{},"First approval rules."," What the agents may do alone, and what always goes to a person, written in plain language.",[15,520,521],{},"If week 1 ends without access and a signed metric, we say so, because it is cheaper for both sides than finding out on day 29.",[22,523,525],{"id":524},"week-2-build","Week 2: build",[15,527,528],{},"Now we build the agents, the rules, the shared memory and the command center, wired into your tools. The agents live where your team already works; nobody gets a new app to learn.",[15,530,531],{},"The real cases from week 1 become evals: automated tests that run every answer against what a good answer looked like. Customer-facing answers get a judge. Tone is agreed with the people who own it, often in a single working session with a pile of past replies.",[15,533,534],{},"The sign-off at the end of the week is a walkthrough with the team lead, on their own cases.",[22,536,538],{"id":537},"week-3-prove","Week 3: prove",[15,540,541],{},"First the evals, on real cases the agents have never seen. Then shadow mode on live work: the agents draft, people send. Every edit a person makes is a signal, and we read them daily.",[15,543,544],{},"This is also where the handoff rules are tuned with the team. Which cases go straight to a person, at what threshold, through which channel. The team should be able to change a rule themselves, and in week 3 they practise doing it.",[101,546,547,560],{},[104,548,549],{},[107,550,551,554,557],{},[110,552,553],{},"STEP",[110,555,556],{},"ARTEFACT",[110,558,559],{},"WHO SIGNS",[120,561,562,575,588,601,614],{},[107,563,564,569,572],{},[125,565,566],{},[29,567,568],{},"Week 0",[125,570,571],{},"Operations map, value per agent, fixed price",[125,573,574],{},"You: which process first",[107,576,577,582,585],{},[125,578,579],{},[29,580,581],{},"Week 1",[125,583,584],{},"Access, real cases, first approval rules",[125,586,587],{},"The owner of the metric",[107,589,590,595,598],{},[125,591,592],{},[29,593,594],{},"Week 2",[125,596,597],{},"Agents, memory, rules, command center, evals",[125,599,600],{},"The team lead, after a walkthrough",[107,602,603,608,611],{},[125,604,605],{},[29,606,607],{},"Week 3",[125,609,610],{},"Eval results, shadow-mode log, tuned handoffs",[125,612,613],{},"The team lead: ready to go live",[107,615,616,621,624],{},[125,617,618],{},[29,619,620],{},"Day 30",[125,622,623],{},"Production, monitoring, trained team",[125,625,626],{},"Both of us, against the metric",[22,628,630],{"id":629},"day-30-live","Day 30: live",[15,632,633],{},"On day 30 the agents are in production, on live work, monitored from the command center. The team is trained on it: how to read a run, how to approve, how to pause an agent, how to change a rule.",[15,635,636],{},"Production means the agents answer, route or update on their own inside the rules, and the number from week 1 is tracked every day from then on. It does not mean “available on request” or “ready for phase two”.",[22,638,640],{"id":639},"why-the-date-holds","Why the date holds",[15,642,643],{},"Three things keep the date honest. The scope is one process, not the company. The metric is agreed before a line of code, so nobody can move the goalposts later. And we put our money on it: live in 30 days, or your money back.",[15,645,646],{},"After day 30 we run the fleet: monitoring, tuning and, when you are ready, the next squad. On our largest project that became one new squad a month, each built on the memory and rules of the ones before it.",{"title":237,"searchDepth":238,"depth":238,"links":648},[649,650,651,652,653,654],{"id":477,"depth":238,"text":478},{"id":487,"depth":238,"text":488},{"id":524,"depth":238,"text":525},{"id":537,"depth":238,"text":538},{"id":629,"depth":238,"text":630},{"id":639,"depth":238,"text":640},"2026-08-18","The 30-day playbook, week by ==week.==","magenta","30",{},"\u002Finsights\u002Fthe-30-day-playbook-week-by-week",[662,451,663],"why-95-percent-of-ai-pilots-never-reach-production","build-buy-or-both",{"title":465,"description":471},"insights\u002Fthe-30-day-playbook-week-by-week","From the first call to production: the exact steps, artefacts and sign-offs we use.",[668,669,670,671,672,673],{"id":477,"label":478},{"id":487,"label":488},{"id":524,"label":525},{"id":537,"label":538},{"id":629,"label":630},{"id":639,"label":640},"rT6HBQ-x40ciVZH-qHpcDH1wLuGv79MQR2E3ffHF_dY",{"id":676,"title":677,"author":678,"blobHue":10,"body":679,"category":897,"date":898,"description":683,"draft":247,"extension":248,"featured":247,"headline":899,"hue":900,"letter":901,"meta":902,"navigation":253,"path":903,"readMinutes":255,"related":904,"seo":905,"stem":906,"summary":907,"toc":908,"__hash__":914},"insights_en\u002Finsights\u002Fwhat-an-agentic-os-is-and-what-it-isnt.md","What an Agentic OS is, and what it isn’t",{"name":7,"role":8,"bio":9},{"type":12,"value":680,"toc":890},[681,684,687,691,694,697,701,707,739,745,751,757,823,828,832,838,844,850,854,857,860,864,887],[15,682,683],{},"Most people meet AI agents as a chat window. You ask, it answers, and then nothing happens. That is useful, but it isn’t how a business runs. A business runs on work that moves between systems, people and decisions, every day, whether anyone is watching or not.",[15,685,686],{},"An Agentic OS is what it takes to hand some of that work to agents and still sleep at night.",[22,688,690],{"id":689},"a-plain-definition","A plain definition",[15,692,693],{},"An Agentic OS is a team of AI agents trained on how your business works, running inside the tools you already use, following rules your people set. Each agent owns one job. They share what they know. They stop and ask when a decision is above their limits. And everything they do is visible on one screen.",[15,695,696],{},"The word “OS” is deliberate. An operating system is not an app you open. It is what sits underneath and keeps everything else running. The agents are the visible part; the layers around them are what make it safe.",[22,698,700],{"id":699},"the-four-layers","The four layers",[15,702,703,706],{},[29,704,705],{},"Agents"," do the work. We use five kinds, and most companies go live with two or three:",[493,708,709,715,721,727,733],{},[72,710,711,714],{},[29,712,713],{},"Responder"," answers customers, suppliers and colleagues, in your tone, from your data.",[72,716,717,720],{},[29,718,719],{},"Classifier"," reads what comes in, from emails to tickets to documents, and sends it to the right place.",[72,722,723,726],{},[29,724,725],{},"Scraper"," watches the sources you care about and brings back what changed.",[72,728,729,732],{},[29,730,731],{},"Orchestrator"," runs work that spans several systems: the refund, the CRM update, the courier booking.",[72,734,735,738],{},[29,736,737],{},"Analyst"," reads the numbers and has the report ready before the meeting.",[15,740,741,744],{},[29,742,743],{},"Shared memory"," is what the agents know about your business: policies, price lists, customer history, past decisions. Every agent reads from the same source, and it stays current as you work. No more “ask Maria, she knows”.",[15,746,747,750],{},[29,748,749],{},"Approval rules"," decide what an agent may do alone. They are written in plain language and set by your team. Above the limit, the agent pauses and a person decides, in the tools they already use.",[15,752,753,756],{},[29,754,755],{},"The command center"," shows every run, cost and result on one screen. You can replay any decision step by step, pause any agent, and follow the number you agreed on, every day.",[101,758,759,772],{},[104,760,761],{},[107,762,763,766,769],{},[110,764,765],{},"LAYER",[110,767,768],{},"WHAT IT ANSWERS",[110,770,771],{},"WITHOUT IT",[120,773,774,786,798,810],{},[107,775,776,780,783],{},[125,777,778],{},[29,779,705],{},[125,781,782],{},"Who does the work?",[125,784,785],{},"Nothing gets done",[107,787,788,792,795],{},[125,789,790],{},[29,791,743],{},[125,793,794],{},"What do they know?",[125,796,797],{},"Every agent guesses",[107,799,800,804,807],{},[125,801,802],{},[29,803,749],{},[125,805,806],{},"What can they do alone?",[125,808,809],{},"Nobody dares switch them on",[107,811,812,817,820],{},[125,813,814],{},[29,815,816],{},"Command center",[125,818,819],{},"What did they do, and did it work?",[125,821,822],{},"Nobody can prove it",[218,824,825],{},[15,826,827],{},"Agents alone are a demo. What makes them safe is everything around them.",[22,829,831],{"id":830},"what-it-isnt","What it isn’t",[15,833,834,837],{},[29,835,836],{},"It isn’t a chatbot."," A chatbot waits for a question. An Agentic OS works through a queue. It reads the inbox overnight, reconciles the stock file, drafts the replies, and leaves the three decisions that need a person at the top of the list in the morning.",[15,839,840,843],{},[29,841,842],{},"It isn’t a platform licence."," You don’t rent seats in someone else’s product and bend your process to fit it. The agents are built around your process, inside your systems, and you own the code, the prompts and the data.",[15,845,846,849],{},[29,847,848],{},"It isn’t a pilot."," A pilot runs on an export, for a demo, with nobody accountable for the result. An Agentic OS runs on live systems from the first week, against a number that the team whose work it takes has signed off. If it isn’t in production, it isn’t an OS yet.",[22,851,853],{"id":852},"where-to-start","Where to start",[15,855,856],{},"Nobody builds all four layers for the whole company at once. You start with one process that hurts, usually one with volume, clear rules and a number: the support inbox, the supplier files, the weekly report. You build the first squad of agents with its memory, its rules and its screen. Then you add a squad at a time.",[15,858,859],{},"The layers are what make the second squad cheaper than the first. The memory is already there. The rules have a format the team knows. The command center already shows the first squad’s numbers, so the next one is judged on the same screen, against the same kind of target.",[22,861,863],{"id":862},"how-to-tell-if-you-have-one","How to tell if you have one",[385,865,867],{"title":866},"You have an Agentic OS if the answer is yes to all of these",[69,868,869,872,875,878,881,884],{},[72,870,871],{},"Do the agents work inside the systems your team already uses?",[72,873,874],{},"Can you say, in one sentence, which decisions they may not take alone?",[72,876,877],{},"Do they all read from the same, current source of policies and history?",[72,879,880],{},"Can you open one screen and see what they did today, what it cost and what is waiting for you?",[72,882,883],{},"Has a number moved, and does the team that owns it agree?",[72,885,886],{},"Do you own the code, the prompts and the data?",[15,888,889],{},"If any answer is no, you have agents. That is a good start. The rest is the part that lets you rely on them.",{"title":237,"searchDepth":238,"depth":238,"links":891},[892,893,894,895,896],{"id":689,"depth":238,"text":690},{"id":699,"depth":238,"text":700},{"id":830,"depth":238,"text":831},{"id":852,"depth":238,"text":853},{"id":862,"depth":238,"text":863},"strategy","2026-09-15","What an Agentic OS is, and what it ==isn’t.==","violet","OS",{},"\u002Finsights\u002Fwhat-an-agentic-os-is-and-what-it-isnt",[662,257,451],{"title":677,"description":683},"insights\u002Fwhat-an-agentic-os-is-and-what-it-isnt","Not a chatbot, not a platform licence. A plain-language definition, with the four layers that make agents safe to run a business.",[909,910,911,912,913],{"id":689,"label":690},{"id":699,"label":700},{"id":830,"label":831},{"id":852,"label":853},{"id":862,"label":863},"O4B58r8Hq-cONZEYpn0ps8PFaK7Sr4eN71hJvwSQj0c",1790618465014]