DEV Community: Judy

How Endava Redesigns Software Delivery with AI Agents at Its Core

Judy — Sat, 12 Sep 2026 01:00:27 +0000

This article is a deep-dive from JudyAI Lab — an AI engineering playbook series with 100+ published guides, 5,000+ weekly readers across 60+ countries, focused on the practical side of running AI agents, trading systems, and content pipelines in production.

📰 Key Highlights

Software services company Endava is actively adopting multiple OpenAI tools, including AI Agents, ChatGPT Enterprise, and the code generation model Codex, with the goal of accelerating software delivery processes across the organization, automating daily workflows, and driving the corporate culture toward "AI-native" transformation. Based on the disclosed direction, Endava's strategy isn't limited to a single department pilot — instead, they aim to deeply embed AI capabilities across cross-team development and operations, enabling engineers, project management, and business processes to all benefit from automated acceleration. However, the original summary is relatively concise and doesn't provide specific efficiency improvement metrics, implementation scale, or technical architecture details. For more details, please refer to the original article link.

💬 JudyAI Lab Perspective

Endava chose to roll out AI Agents, ChatGPT Enterprise, and Codex across all departments simultaneously rather than running a pilot in a single department. This "going all-in" strategy approach itself is more值得关注 than the tool selection itself.

Based on the original article's disclosed direction, Endava's logic is to have AI capabilities cover code generation (Codex), knowledge work (ChatGPT Enterprise), and process automation (AI Agents) all at once — with engineers, PMs, and business teams as the target audience. This reflects an accelerating phenomenon: to truly build an "AI-native" culture, different functions must all feel tangible benefits, not just running a test in R&D. It's worth noting that the original article didn't disclose specific efficiency metrics or technical architecture details — this reminds us to distinguish between "strategic announcements" and "grounded implementation" when observing similar cases; there's often a big gap that needs verification between the two.

If you're evaluating AI tool adoption, ask yourself backwards: Besides engineers, which other roles can directly see the benefits? If the answer is only the tech team, pushback during rollout is usually much higher than expected.

📅 Original Info

Published: 2026-06-04T12:00
Source: https://openai.com/index/endava-frontiers

🔗 Further Reading

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

Google Launches Dreambeans: Turn Your Life Photos Into Cartoon Animations With One Click

Judy — Sat, 12 Sep 2026 01:00:07 +0000

📰 Quick Summary

Google just launched a new AI tool called Dreambeans, arguably the weirdest-named AI product Google has ever shipped. Dreambeans pulls personal data from your Google account and uses AI to turn it into an illustrated "story," visually presenting slices of your life. In other words, it's not just a text summarization tool — it reinterprets your personal info as cartoon-style content with a real narrative feel. Right now the source summary only covers this core mechanism; for more details on the scope of data sources, illustration style options, privacy settings, or the official launch timeline, check the original article link.

💬 JudyAI Lab Take

Google's Dreambeans turns your account data into an illustrated story — the core logic isn't summarization, it's "reinterpretation" of your personal info, and that direction is worth watching.

What's most worth thinking about here is the choice of output format. Most AI tools that get their hands on personal data default to summaries, recommendations, or reports. Dreambeans went with cartoon illustrations plus narrative structure instead, packaging data into a warm, human-feeling life story. The logic behind it: users don't necessarily need more information — they need a lens that makes the data mean something. That's a good reminder that output format isn't a detail you bolt on at the end of the design process — it's core to the product experience. Same data source, different presentation framework, completely different feeling for the user.

Worth taking a look at the AI tools you already have — is there still room to reinterpret the output? Same data, a different way of presenting it, and you can often land on a completely different product position.

📅 Source Info

Published: 2026-06-03T19:07
Original article: https://techcrunch.com/2026/06/03/googles-dreambeans-its-weirdest-named-ai-tool-to-date-will-turn-your-life-into-a-cartoon/

🔗 Further Reading

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

EVA-Bench Data 2.0 Benchmark Release: Covering 3 Domains, 121 Tools, and 213 Test Scenarios

Judy — Wed, 09 Sep 2026 01:00:28 +0000

📰 Key Summary

ServiceNow AI's research team has released EVA-Bench Data 2.0, an enterprise-grade benchmark designed specifically for voice agents. This release dramatically expands the scope, moving from a single domain to three major enterprise scenarios: airline customer service management (CSM), enterprise IT service management (ITSM), and healthcare human resources service delivery (HRSD). Together, the three domains cover 213 evaluation scenarios and 121 tools, roughly four times the coverage of the original version. Broken down by domain: airline has 50 scenarios, ITSM has 80, and HRSD has 83.

This benchmark places particular emphasis on real-world voice scenarios — every data point was filtered starting from actual phone-based customer service workflows, with tool schemas modeled after production API specs. The healthcare HRSD domain goes even deeper, tying into real US healthcare policy details like NPI provider identifiers, FMLA family leave regulations, and insurance coverage rules, ensuring the evaluation scenarios match what practitioners actually deal with day to day. All 213 scenarios were cross-validated for solvability by three frontier models — OpenAI's GPT-5.4, Google's Gemini 3.1 Pro, and Anthropic's Claude Opus 4.6 — to keep the benchmark challenging while ensuring results stay fair and trustworthy.

All three datasets are fully open-sourced and can be loaded directly through Hugging Face Datasets. The team has also announced an upcoming multilingual expansion, which will push the benchmark's scope beyond its current English-only enterprise deployment limitations. The full design principles and generation process are documented in the original post — a solid implementation reference for anyone looking to build their own eval dataset.

💬 JudyAI Lab Take

ServiceNow expanding its voice agent benchmark from a single domain to three major enterprise scenarios — airline, ITSM, and healthcare — and open-sourcing all of it signals, in our view, that standardizing enterprise AI voice evaluation has moved from a conceptual discussion to something you can actually deploy as a tool.

The most notable design principle here is filtering scenarios "starting from real phone-based customer service workflows" rather than dreaming up test questions from scratch. This approach reflects a consensus that's taking shape: if enterprise voice AI evaluation is disconnected from actual business workflows, the resulting scores often fail to predict production performance. Having all 213 scenarios cross-validated for solvability across GPT-5.4, Gemini 3.1 Pro, and Claude Opus 4.6 — this multi-model consensus design ensures the benchmark stays both challenging and fair, rather than being friendly to just one model family. The healthcare HRSD scenarios incorporating details like NPI identifiers, FMLA leave rules, and insurance coverage also show that eval data for highly regulated domains needs to hit a certain density of business-level detail before it can actually measure meaningful differences.

If you're designing an enterprise AI eval dataset, the scenario generation files in this open-source release are a solid starting point to reference directly — reverse-engineering test scenarios from business workflows exposes production gaps more effectively than forward-designing from model capability dimensions.

📅 Original Article Info

Published: 2026-06-04T12:24
Source: https://huggingface.co/blog/ServiceNow-AI/eva-bench-data

🔗 Further Reading

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

South Korea Just Gave 52 Million People Free, Unlimited AI - But the Real Catch Is an 80% Domestic Model Quota

Judy — Wed, 09 Sep 2026 01:00:09 +0000

South Korea just did something no other country has done

Let's start with the facts—I checked these one by one (sources cross-verified across multiple credible outlets, linked at the end):

South Korea's Ministry of Science and ICT (roughly equivalent to a tech ministry) has finalized the three operating consortiums for its "AI for All" program: SK Telecom, KT, and Kakao. Beta starts in September, full launch by year-end. The core pitch is two words: free, unlimited. Doesn't matter what you earn, how old you are, or whether you're tech-savvy—all 52 million people in South Korea get direct access to generative AI, and officials are explicit: "no token limit."

The government has allocated 512 NVIDIA B200 chips to these three companies this year, and starting in 2027, the national budget will even absorb part of the cost of running this nationwide service. That makes Korea the first G20 country to do this.

(Quick reality check here: "unlimited" is the official claim, not physical reality. Feeding 52 million people off 512 chips necessarily means tiered rate limiting, or dumping most requests onto lightweight models—there's no way everyone gets truly unlimited access. Finding that hidden trapdoor is exactly what I plan to test myself later.)

Every headline is chasing "free" and "unlimited." But free and unlimited is just the hook to get 52 million people flowing in—the real move that turns that traffic into a moat is buried in the next section.

The real catch: that 80%

There's a rule that every article glosses over, and it goes like this:

Every operator must route at least 50% of queries to its own "certified Korean sovereign foundation model," and at least another 30% to other Korean companies' models. Combined, the floor for domestic models is 80%.

I saw a viral social post claiming "at least 50% on domestic models"—that number is way too conservative. The actual floor is 80%.

This is the soul of the entire program.

"Free and unlimited" isn't charity—it's an incentive. The government is essentially saying: I'll provide the compute, the money, the gateway, and funnel tens of millions of citizens through it in one shot—but the AI you use has to be Korean, eight times out of ten. In other words, Korea isn't running a "welfare program"—it's running industrial policy: using everyday national usage to forcibly prop up the demand side for domestic models.

And from an engineering standpoint, that 80% lines up neatly with the earlier question of "how do you feed 52 million people with 512 chips?" The sensible architecture is a smart router up front that judges difficulty: the huge volume of repetitive, trivial requests gets offloaded to cheap domestic small language models (SLMs), and only genuinely hard queries get escalated to premium models. To be clear—512 chips is just seed compute for a pilot; serving 52 million people almost certainly requires tiered rate limiting as a matter of physics. SLM routing isn't what makes it "truly unlimited"—it's the lever that determines how far the free tier can stretch. And here's where the policy quota (80% domestic) and the cost structure (SLM routing saves compute) line up perfectly: Korea doesn't need domestic models to beat GPT, it just needs cheap-and-good-enough domestic small models to absorb 80% of citizens' daily usage—and the compute that saves is what funds the free tier.

Why do this? Understand "sovereign AI" and it all makes sense

This looks strange in isolation, but drop it into the bigger 2026 trend and the logic clicks.

By 2026, "sovereign AI" has gone from a conference buzzword to a line item in G20 national budgets. Global spending on this is projected to blow past $100 billion:

France launched its "Projet Voltaire" sovereign cloud, deploying 50,000 NVIDIA H200 chips in the first wave, with plans to double that by 2027.
India selected 12 domestic foundation models from over 500 proposals, backed by 38,000 GPUs.
Canada committed C$925 million over five years, and the EU mobilized €20 billion for AI Gigafactories.

The reasons countries are racing for sovereign AI boil down to three things: fear of supply chains being choked off by frontier US labs, the need to protect data sovereignty under local language and regulatory requirements, and treating AI as a strategic industry worth nurturing.

But here's the key difference—most countries are fighting on the supply side: building data centers, stacking GPUs, training their own models from scratch. Korea's move is unusual in that it's attacking the demand side.

A model that nobody uses is dead, no matter how good it is. Korea's read is honest: domestic models might catch up technically, but they can't out-compete the user base and habits ChatGPT has already built. So what do you do? The government pushes 52 million people into the domestic ecosystem with free, unlimited access, creating something domestic models need that ChatGPT can't give them—massive, real, everyday usage.

Everyone's stacking on the supply side. Korea is the only one so far playing this bold on the demand side.

What's actually in Korea's hand

Two lists need untangling here, or things get confusing fast: the service operators are the SKT/KT/Kakao consortium (responsible for delivering AI to citizens), while the "sovereign foundation models" they're required to route to come from a separate, parallel national competition. The two lists overlap (SKT is on both), but the roles differ—one is "the pipe that delivers AI to your front door," the other is "the water flowing through that pipe."

That "sovereign foundation model" national competition is currently in elimination rounds—narrowed from five teams to four, with only two surviving by 2027. The visible players include LG's EXAONE, Naver's HyperCLOVA X, Upstage's Solar Pro, SK Telecom's A.X series, and Kakao's Kanana.

Right now, LG AI Research, SK Telecom, and Upstage are leading into the third round. SK Telecom just unveiled A.X K1—Korea's first hyperscale model at the 519-billion-parameter class, clearly aiming for a top-three spot globally.

One detail worth noting: Naver got cut in January—not because the tech was bad, but because HyperCLOVA X had "data independence" concerns (it used frozen encoder weights from Alibaba's Qwen). In the logic of sovereign AI, "how pure is your model's bloodline" apparently matters more than "how high does it score on benchmarks."

The 80% domestic quota in "AI for All" is what feeds this exact pool of national-team models. The government is running a competition to pick sovereign models on one hand, while guaranteeing those models real traffic through free, nationwide service on the other—supply and demand, worked on simultaneously. That's the whole play.

So what does this mean for a regular person building with AI?

If you're a freelancer, a solo founder, or anyone making a living with AI, don't file this away as unrelated foreign news. I think there are three concrete takeaways worth internalizing:

One: Korea's "small models handle the grunt work" architecture is exactly the cost-cutting move you should be copying. As I broke down above, Korea can only afford "unlimited for everyone" because domestic small models absorb 80% of requests. The same logic applies directly to a solo operation—stop routing every single task to the most expensive GPT. The right move is to build a hybrid routing layer up front: dump the grunt work—classification, extraction, rewriting, first drafts—onto cheap small models (even locally-run, heavily-subsidized open-source ones), and reserve the premium API calls for the truly hard 20% that needs real reasoning. This isn't magic—open-source tools like RouteLLM and LiteLLM exist specifically for this. One routing layer, and your cost for the same output can drop several times over. Korea just demonstrated this architecture with a national budget; you can use it to cut your own costs.

Two: the moat is shifting upward, toward your data and your vertical know-how. When a country turns "having access to generative AI" into a public utility like tap water, "I have a ChatGPT account" stops being an advantage. Everyone has a generic chatbot. What's actually valuable is solving a specific problem in a specific industry, fed by data nobody else can get their hands on. Worth noting: Naver got cut from the sovereign model national team not because its tech was weak, but because of doubts about its data lineage. "Where does your data run, and whose regulations does it answer to" is a question that's going to come up more and more from clients and governments alike, no matter what you're building.

Three: the real frontier is "agents that get things done," not "AI that chats well." The most important design choice in Korea's service is that it plugs directly into government systems to handle tasks on your behalf: booking medical appointments, filing taxes, searching for housing. That's not Q&A—that's "carrying a task from start to finish." But from my own experience building agent systems, the moment an agent can actually take real action (submitting an application, placing an order, deducting a payment), the cost of a mistake jumps from "answered one question wrong" to "did the wrong thing." So the hard part of task automation was never getting a model to talk well—it's plugging it into real systems without causing damage. The real engineering challenge is permission boundaries and rollback, not how smart the model is. Whether this nationwide task-automation rollout in Korea breaks anything is exactly what I want to watch most closely.

I'm going to test this myself—here's what I'm verifying

No amount of policy analysis beats actually using the thing. I'm in Korea, so the moment the September beta opens, I'll sign up and test it myself, then write up the first-hand results in a follow-up piece.

Here's what I'll be watching (also listed below in case you're in Korea and want to test alongside me):

Is "unlimited" really unlimited, or is there a hidden rate limit? Free things usually have a trapdoor somewhere.
Which model does it actually route to, and how much worse is the quality compared to ChatGPT? I'll throw the same prompts at it in Chinese, English, and Korean. With 80% running on domestic models, can users actually tell the difference?
Does the task-automation feature actually work? For the parts that plug into government systems—booking a doctor's appointment, checking your tax filing—can it actually complete the task end to end, or does it just spit out an explanation?
How friendly is the UX for people who aren't tech-savvy? This program claims to serve "people who can't install software"—that's the claim most likely to turn out to be empty.
What data does it collect from me? The flip side of plugging into government systems is privacy.

Whether a country handing AI to its citizens as a public good is a smart move won't be clear for another two or three years. But the direction is obvious: the AI competition is shifting from "whose model is strongest" to "who can get the most people using AI, every day, with the least friction." Korea is betting on the latter.

I'll report back after testing. Next piece: is this gamble real, or is it just for show?

Sources (cross-verified across multiple outlets):

Korea Herald — Korea picks SK Telecom, Kakao, KT to build free nationwide AI services
The Korea Times — SKT, KT, Kakao consortiums selected for free AI service for public
TechSpot / Decrypt — free access with no token limits
The Next Web — 52 million citizens, domestic models
KED Global / Korea Herald — sovereign foundation model national team (LG, SKT, Upstage, etc.)
Light Reading — South Korea enters second phase of sovereign AI project

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

ChatGPT Rolls Out 'Dreaming' Memory Feature to Make Your AI Assistant Understand You Better

Judy — Sat, 05 Sep 2026 01:00:28 +0000

📰 Key Summary

OpenAI recently rolled out a major memory system update for ChatGPT, aiming to help the model remember your personal preferences and daily habits more precisely, so the context in every conversation stays fresh and highly relevant to what you actually need right now. Compared to the old passive memory storage approach, this update emphasizes "dynamic updating" and "relevance filtering" of memory content, letting ChatGPT proactively maintain a personalized experience across conversations rather than just accumulating history. For long-term ChatGPT users, this update should, in theory, deliver more consistent interactions that feel closer to their own personal style. That said, the original summary is fairly brief and doesn't reveal the specific technical implementation or any quantitative data — see the original link for details.

💬 JudyAI Lab Take

The core of OpenAI's memory update isn't "remembering more" — it's "remembering right." Shifting from passive accumulation to dynamic filtering is a shift in AI product design worth paying attention to.

This case reflects a clear industry trend: the competitive edge in "personalization" is moving from data volume to contextual accuracy. Many AI tools' memory features have historically just been historical conversations stacked on top of each other — which, over time, makes context messier, not clearer. OpenAI's emphasis on "dynamic updating" and "relevance filtering" here — letting the system proactively judge which memories are still valid and which should be replaced — represents a shift in design thinking from "record-oriented" to "context-oriented." For those of us building AI tools or agent systems, this is a reminder: memory module quality matters far more than quantity.

Start with one question: does the AI tool in your hands remember what the user actually needs, or just what's convenient for the system to store? Get clear on that first, and your memory architecture won't go off the rails.

📅 Original Source Info

Published: 2026-06-04T09:00
Source: https://openai.com/index/chatgpt-memory-dreaming

🔗 Further Reading

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

Amazon Will Show AI-Generated Product Images Instead of Original Photos in Search Results

Judy — Sat, 05 Sep 2026 01:00:08 +0000

📰 Key Summary

Amazon has announced it will combine visual search technology with generative AI to automatically display AI-generated product images when users type in search keywords, making search results visually closer to what users are actually looking for. Amazon says the goal is to help users find matching products faster and improve the shopping discovery experience. However, the original summary didn't reveal the rollout timeline, which product categories it applies to, the technical architecture behind the AI image generation, or whether the images will carry an "AI-generated" disclosure label — see the source link for more details.

💬 JudyAI Lab Take

Amazon is stuffing generative AI into its search results page, and it's no longer just about "helping you find a product" — it's starting to "help you imagine a product." We think this direction is worth watching for anyone building AI products.

The logic behind this design is straightforward: the keywords users type in are often just a vague sense of intent, not a precise product description. Rather than making users guess from a list of text results, why not let AI visualize "what you might want" first? This "visualize the intent" way of thinking is useful for any AI product involving search or recommendation flows — the key isn't how powerful the underlying model is, but whether the system can turn a vague need into a concrete picture before the user has even finished articulating it. Worth noting: the original article doesn't reveal a rollout timeline or scope, and doesn't say whether the AI-generated images will be labeled — this still looks like an early-stage experiment, and the details are worth tracking as they unfold.

Next time you're designing a search or recommendation interface, it's worth asking yourself: when a user types that phrase, what are they actually trying to "see"?

📅 Source Info

Published: 2026-06-03T15:50
Source: https://techcrunch.com/2026/06/03/amazon-will-show-ai-product-images-when-you-search-for-some-reason/

🔗 Further Reading

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

Alphabet Raises Record-Breaking $85B to Supercharge Google's AI Business, Market Confidence Runs High

Judy — Wed, 02 Sep 2026 01:00:27 +0000

📰 Key Summary

Alphabet (Google's parent company) just pulled off an $85 billion stock offering, setting a historic record and becoming one of the largest single stock sales in tech industry history. The successful close of this massive deal is being read by the market as a direct signal of investor confidence in AI's commercial prospects — even with interest rate uncertainty still lingering and AI bubble concerns not fully cleared, institutional capital is still willing to pour into top-tier AI companies at record-breaking scale, showing that market enthusiasm for the AI investment space hasn't cooled off. For the industry as a whole, this signal carries real weight: when one of the world's most representative AI companies can pull off a raise of this magnitude, it means capital markets still hold a positive long-term view on AI infrastructure and application-layer value. That said, the source summary only touches on the sentiment side and doesn't disclose the specific use of funds, subscription ratio, or investor composition — see the original article for more details.

💬 JudyAI Lab Take

Alphabet just rewrote the tech industry's record book with an $85 billion stock sale, and the fact that institutional capital is still pouring into top-tier AI companies at record scale — even with AI bubble concerns still in the air and the rate outlook unclear — is a market signal whose meaning goes well beyond the raw number.

For those of us actually building products, this deal tells us more than just "AI is still hot." What's worth paying attention to is the pace of capital concentration — in an uncertain environment, money isn't pulling back, it's just concentrating more precisely at the top. The source notes that the market's long-term view on AI infrastructure and the application layer remains positive, but it also doesn't disclose the specific use of funds or subscription structure. That tells you something: the market's optimism is real, but it's selective — it's not being spread evenly across every AI project. Pulling off a raise of this size in this environment is itself a snapshot of what the market's filtering process looks like.

Ask yourself: if institutional capital is doing the filtering right now, is what you're building the reason you'd get picked — or the kind of thing that gets passed over?

📅 Source Info

Published: 2026-06-03T19:38
Original source: https://techcrunch.com/2026/06/03/alphabets-record-breaking-85b-raise-for-googles-ai-business-is-a-helluva-good-signal/

🔗 Further Reading

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

Uber Caps Employee AI Tool Spending After Blowing Through Budget in Just 4 Months

Judy — Wed, 02 Sep 2026 01:00:07 +0000

📰 Key Takeaways

Uber recently announced a cap on employee spending for AI tools, after previously encouraging staff to use AI as much as possible only to burn through the entire budget in just four months, forcing a rapid pivot from open access to strict cost controls. The shift from encouraging unrestricted use to emergency spending caps took only four months, highlighting how enterprises rolling out AI at scale can see actual usage far outpace projections if they don't build cost-tracking mechanisms in from the start. Since the original source summary offers fairly limited detail — including the actual budget size, how the spending cap is being enforced, and employee reactions — none of that has been disclosed. See the source link below for more.

💬 JudyAI Lab Take

Uber burned through its entire AI tool budget in four months and had to slam the brakes — going from encouraging unrestricted use to emergency spending caps in a single quarter. That's a sobering wake-up call for any company scaling up AI adoption right now.

When companies roll out AI tools, "encouraging adoption" and "cost governance" tend to get treated as two separate problems — often with the former coming first and the latter only patched in afterward. Uber's case shows that once usage is unlocked without real-time cost tracking in place, the actual burn rate can blow way past any budget estimate made ahead of time. It's a familiar organizational pattern: push the tool out first, backfill the rules later. For anyone building or rolling out AI tools internally, the lesson here is clear — tools are easy to push out, but governance is hard to retrofit. Going from wide open to fully capped can happen in the span of a single reporting cycle.

If your organization is currently driving AI tool adoption, it's worth asking right now: do you have real-time visibility into spending? Cost transparency isn't something you patch in after the fact — it should be baked into the adoption strategy from day one.

📅 Source Details

Published: 2026-06-02T19:11
Source article: https://techcrunch.com/2026/06/02/uber-caps-employee-ai-spending-after-blowing-through-budget-in-four-months/

🔗 Further Reading

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

Trump Signs Scaled-Back AI Executive Order After Industry Pushback

Judy — Sat, 29 Aug 2026 01:00:27 +0000

📰 Key Summary

President Trump has officially signed a revised executive order on artificial intelligence after industry pushback. The core change from the original draft: pre-release government review of advanced AI models shifts from mandatory to voluntary. That means AI developers can now decide for themselves whether to submit to federal pre-review before launching their next-gen frontier models, without being bound by a mandatory regulatory requirement. Since the industry had objected to the mandatory review mechanism in the first place, this revised version is widely seen as a concession from the government to industry, with the order specifically targeting the "advanced models" category. The original summary doesn't go into further detail on the order's exact scope, review standards, or enforcement — see the source link for the full story.

💬 JudyAI Lab Take

When AI regulation shifts from mandatory to voluntary, the power boundary between government and industry is being redrawn — and that's worth unpacking carefully for anyone building on the frontline of AI development.

The core pivot in this executive order is a one-word swap — "mandatory review" to "voluntary review" — but the impact isn't small: mandatory review directly touches release timelines, compliance costs, and the possibility of the government gaining access to internal model information. Industry pushback ultimately forced the concession — the summary explicitly states this revision "is widely seen as a concession from the government to industry" — which tells you current US policy still leans toward supporting AI industry competitiveness over regulation-first thinking. From where we sit, this case reveals something real: even in the most heated policy environments, industry voices still carry real weight. That said, going voluntary doesn't erase the uncertainty around regulatory standards — it just converts "uniform mandate" into "individual choice," and the long-term regulatory framework remains unresolved.

We'd suggest keeping an eye on which AI developers choose to opt into review and which don't — that behavioral split, more often than the policy text itself, tells you what the industry really thinks about regulatory pressure.

📅 Source Info

Published: 2026-06-02T16:23
Source: https://techcrunch.com/2026/06/02/trump-signs-narrower-executive-order-on-ai-oversight-after-industry-objections/

🔗 Further Reading

References

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

Personal AI Assistant Instinct Hit a $2.5B Valuation in Weeks - A Top Agent Researcher Hid Complex Tech Behind a Text Message

Judy — Sat, 29 Aug 2026 01:00:07 +0000

TL;DR: Personal AI assistant Instinct is still in beta with no disclosed revenue, yet its valuation jumped from $500 million to $2.5 billion in a matter of weeks. Its founder wrote Reflexion, a landmark paper in AI agents—yet he built a product you can use just by texting or calling. Three things to take away from this piece:

Its moat isn't "no tech"—it's "hiding hard tech inside a simple interface." A top-tier agent researcher chose to bury all the complexity behind a single text message.
The $2.5B is capital betting it becomes the "personal AI gateway," not what it's earning right now—going viral isn't the same as being validated as a moneymaker.
The flip side of convenience is permissions. An AI that can charge your card and touch your inbox needs boundaries set where it can't override them.

When I saw that "Instinct—still in beta, no disclosed revenue—jumped from a $500 million to a $2.5 billion valuation in a few weeks," what I wanted to figure out wasn't "oh, another unicorn." It was: what exactly are all these battle-hardened Silicon Valley investors seeing in it?

Once I dug in, I found the reason behind the hype is the opposite of what most people assume—"is there some secret sauce?"—and that real reason is something I feel deeply every single day running an AI team.

What Is Instinct, and What Happened

This AI assistant is called Instinct, founded by Noah Shinn, at a company called Spear Street Technology.

Here's context a lot of the coverage misses but that really matters: Noah Shinn isn't some outsider. He's the author of Reflexion: Language Agents with Verbal Reinforcement Learning, a landmark paper in the AI agent field, and a former Sierra research scientist. His research focus is exactly "how do you get an AI agent to self-critique and keep getting better." Keep that in mind, because it's the key to understanding what actually makes Instinct impressive.

What it does, in one line: you connect it to your apps and devices, then text or call it to have it handle life's errands for you. The founder's own description says it well—"there's no new interface, you just text or call, and it's trained to use your phone and computer like a person would." Early users have already used it to plan cross-country road trips, do weekly grocery shopping, buy concert tickets, and cancel hundreds of dollars in subscriptions.

The speed of the valuation climb is the wild part. Early funding valued it at around $100 million; in early August, a round led by Kleiner Perkins pushed it past $500 million; just a few weeks later, Benchmark and Index Ventures led another round at a $2.5 billion valuation—roughly a 5x jump again. Total funding raised is around $350 million. And it's still a free, invite-only beta, with no revenue or user numbers disclosed.

Some people call it "AI agents for regular people." One investor put it bluntly: they'd tried several similar tools on the market, and Instinct was still the one that worked best.

Why Silicon Valley Is Racing for Instinct: Hiding the Hardest Tech Behind the Simplest Entry Point

If all you remember is "$2.5 billion," you'll miss the most important part.

Everyone's instinct is to ask, "does it have secret tech nobody else has?" But once you factor in the founder's background, you see something more interesting: its technology isn't weak at all—if it were, an interface like texting and calling, where you can't clarify one sentence and can't take it back, would never be able to handle complex tasks. As the author of Reflexion, he's holding genuinely hard agent self-correction technology.

Its real breakthrough is hiding all that hard technology behind an entry point with zero learning curve.

That's worth sitting with. There are actually quite a few AI tools out there that can handle tasks for you, but almost all of them have an invisible barrier: you have to learn how to configure it, connect your accounts, and phrase your request in a way "it understands." That barrier keeps the vast majority of regular people out. What Instinct does is flatten that barrier entirely—if you can text and you can make a phone call, you can use it.

And as someone who tunes agents every day, I want to point out just how hard the hidden "grunt work" behind this really is—because that's where the moat actually lives:

Your casual request like "sort out my trip to New York next week" has to get broken down behind the scenes into a long chain of clear, executable steps, each one verified for correctness—that's the engineering work of turning vague intent into structured action.
Phone calls and texts don't have an "are you sure?" popup, so which actions need to check back with you first, and which it can just do—requires a whole risk-judgment system to be designed, or it'll silently charge your card without a word.
It has to maintain a coherent state across your inbox, calendar, and various apps—remembering what you said last, and how far along a task is.
"Trained to use your phone and computer like a person would" is a phrase that hides an entire capability set for actually operating interfaces, not just calling APIs.

What users experience as "one text message and it's done" is the team swallowing all of the above so you never have to see it. It's exactly the same thing I felt when building an AI multi-agent team from scratch: the real effort was never "getting AI to run"—it's compressing the handoff specs and interfaces down until they're completely invisible to the user.

So what Silicon Valley investors are really racing for is a bet on "who can be first to make top-tier agent tech usable by regular people with zero barrier to entry." Instinct showed them what that looks like.

But Let's Be Honest: The $2.5B Is a Bet on "the Gateway," Not Money Already Earned

Now that I've covered what makes it impressive, let me pull you back down to earth with something rarely emphasized in coverage like this: as of now, it has no disclosed revenue and no disclosed user numbers.

The $2.5 billion figure is hard to justify with any visible performance metric right now. Capital isn't betting on "how much it's already earned"—it's betting on "whether it has a shot at becoming the next gateway for personal AI," the same way everyone once raced to bet on who'd become the gateway of the smartphone era. This is a wager on future position, not a reward for current results.

I'm calling this out specifically because, for anyone actually using AI or trying to build something with it, it matters to keep these two things separate: "a product is going viral and attracting a lot of money" and "a product has been validated as a stable moneymaker" are two different things. The former might really have spotted the future, or it might just be a momentary capital frenzy. Rather than getting scared or excited by the valuation, it's more useful to look at what it did right that you can actually learn from—and that's worth remembering regardless of how this company ultimately turns out.

The Question Everyone's Overlooking: The Cost of Permissions

Following that thread, there's something far more important than the valuation that almost nobody's talking about amid all the excitement: what's the price of enjoying "one text message and it's all handled"?

The answer is permissions.

Look back at what Instinct does for users—sending and receiving emails, booking flights, charging cards to buy things, canceling subscriptions. For an AI to do all that, it needs access to your inbox, calendar, payment methods, and various account credentials. That's an extremely deep, extremely broad set of keys. And after Instinct went viral, it drew plenty of scrutiny over its terms of service and the scope of permissions it requests.

That's not surprising—the more an AI can "do everything for you," the deeper the permissions it needs. Convenience and permission are almost inseparably tied together in a product like this; you can't really get the convenience without granting the access.

But as someone who actually manages a bunch of AIs day to day, I want to offer more than the obvious "be careful"—here are a few concrete defenses you can use right now:

Give it a dedicated card with a hard cap, not your main card. Use a virtual credit card with per-transaction and monthly spending limits set in advance, so even if it makes a bad call, the damage is capped at what you've allowed.
Require a second confirmation for high-risk actions. Let it research and draft freely; but for the step where it actually charges money, sends something out, or deletes something, make it stop and wait for your yes.
Set boundaries where it can't override them. This is the key part—if "don't spend more than $100" is just something you told it once, there's a real chance it can be talked out of that behavior by some clever phrasing; a real boundary has to sit at a layer its permissions simply can't reach. I covered this in more depth in Big Tech Is Racing to Build "Spending Caps" for AI Agents.

The thing to really watch out for when letting an AI handle your errands was never "will it make a mistake"—it's "how much access have you handed to something whose every step you can't actually see." Setting the boundary first matters far more than how smart or convenient it is.

What This Means for You: Three Things You Can Do Today

"Another AI unicorn in Silicon Valley" sounds far removed from your life, but the signal in this story is closely tied to how you use and build with AI every day. Here are three things you can act on today:

Turn your messiest client workflow into a "chat interface." Borrow Instinct's philosophy: if you currently make clients fill out a long form or use some overly complex Notion setup, try switching to "the client sends one message over LINE/WhatsApp, and AI on the back end catches it and organizes it into structure" (you don't need to build this from scratch—use n8n, Make, or Dify to hook into a messaging app's webhook and validate the idea first). Keep the complexity for yourself and give the other side simplicity—that's your version of the moat.
Add a "confirmation gate" to any AI workflow that spends money or sends things externally. Follow the three steps above—a dedicated card with a spending cap, a second confirmation for high-risk actions, and boundaries set where the AI can't override them. This habit will save you from headaches you can't even imagine yet, over and over in the years ahead.
Next time you see "some AI is worth billions," first separate "money is chasing it" from "it's been validated as profitable." Then decide whether it's worth investing your time following it—your time is scarcer than its valuation.

At JudyAILab, I run a whole team of AI agents every day, and the more I do it, the more I believe: nobody knows if Instinct will make it, but the two underlying principles behind its viral rise—subtracting complexity from the technology (hiding hard tech inside something simple) and hardening the risk boundary (setting limits where the other party can't move them)—are things you can put to use right now, no matter how this company turns out. If you want a fuller picture of how AI agents go from tool to real force, check out Three Frameworks for Turning AI From a Tool Into a Force.

Sources

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

AI Cut Korean Herbal Medicine Prep Time from 300 Minutes to 5 - But the Smart Part Is What It Didn't Touch: the Korean Medicine Doctor's Judgment

Judy — Wed, 26 Aug 2026 01:00:27 +0000

Honestly, when I saw the headline "Someone in Korea used AI to cut the prep time for a dose of Korean herbal medicine from 300 minutes to 5," the first thing that caught my eye wasn't "whoa, robots can make herbal medicine now." It was how they did it—because they happened to get right the one thing most people get wrong when they think about applying AI.

What Onerve Did

Let's start with the facts. There's a Korean startup called Onerve (오너브), backed by the Korea Institute of Oriental Medicine, working on automating the manufacturing of Korean herbal medicine (한약).

Their system is called HAP. It connects AI with electronic medical records (EMR) to automate the entire flow—from prescription input, to manufacturing, cleaning, packaging, and inventory management. The key is the raw material: they use standardized, freeze-dried herbs in a "cartridge" format—turning herbs that used to require on-site boiling and heavy manual labor into uniform, standardized modules.

The result: prep time for a single dose of Korean herbal medicine dropped from around 300 minutes to around 5. They won a CES Innovation Award and closed a Series A round of roughly 6.2 billion won.

And they're not alone—another Korean company, Camelotech (with its Cameleon system), is doing almost the same thing and also showed up at CES. So "Korean herbal medicine automation" is turning from a one-off experiment into an actual category.

What I'm Actually Paying Attention To Isn't the Speed—It's Which Layer They Automated

If all you take away from this is "300 minutes became 5," you're missing the most important part.

When people see AI moving into an industry with a thousand-plus years of tradition behind it, the gut reaction is usually panic: "Are even Korean medicine doctors about to get replaced by AI?" But if you look closely at what Onerve actually automated—it's the manufacturing, not the diagnosis and prescribing.

Deciding which medicine a person should take, how to adjust the dosage, how to read their constitution—the parts that require judgment and hard-won experience—that's still the doctor's job. What the machine took over is the part that comes after the prescription is decided: the repeatable, standardizable step of producing the medicine to spec.

That division of labor is the genuinely smart part of this whole thing.

This Is Basically What I Do Every Day Running AI Agents

I live in Korea, and every day I'm running a whole team of AI agents. The longer I do this, the more convinced I am: whether AI adoption actually works has nothing to do with "can it replace a human" and everything to do with whether you've clearly separated "the repeatable layer" from "the layer that needs judgment."

And here's the part most people miss—which is actually the real bottleneck in all of this. People assume Onerve's hard part was "getting a robot arm to measure out herbs." But think about it—the actually hard part was taking messy, inconsistent raw herbs that come out a little different every time, and turning them into uniform, standardized "freeze-dried cartridges." The real work of automation was never the machine. It's standardizing whatever you're handing off into an interface with a clearly defined spec.

Only once the cartridge-format raw material was standardized could the machine take over.

I run into the exact same bottleneck running agents: the hard part is never "telling the agent to go do it." It's that I first have to define a repetitive task's inputs, outputs, and spec clearly enough—precisely enough—that the agent can actually pick it up. Defining that interface is the real work. So what makes Onerve smart isn't the machine—it's that they were willing to first sit down and standardize the "medicine" into a cartridge, and only then hand manufacturing to the machine, while leaving diagnosis and prescribing—the judgment calls—to the doctor.

More Valuable Than Speed: "Every Dose Is the Same"

Following that thread further, the surface-level value Onerve delivers is speed, but what's actually valuable is consistency.

With traditional hand-made medicine, the concentration and cooking process can vary batch to batch due to human factors. Standardized cartridge-format raw material makes the potency of every single dose predictable and reproducible. In a medical setting where mistakes aren't acceptable, predictable consistency beats the occasional brilliant outlier by a mile. The exact same principle applies to how you should think about using AI: what matters about an AI doing work for you was never "how impressive was its best output"—it's "does it reliably deliver at a certain bar, every single time." Only once it's reliable can you actually trust it with real work.

What This Means for You

I know for a lot of people, "AI helping Koreans make herbal medicine" sounds like it has nothing to do with them. But the real signal in this story is directly relevant to your day-to-day work: AI adoption lands fastest and most solidly wherever the work is "repeatable and standardizable."

So if you want to start using AI to actually get things done for you, don't rush to find "one all-powerful AI that can replace my entire job." Instead, lay out your work and ask yourself two questions:

Which layer is repeatable and standardizable? (Things you do every day, with fixed steps and a clear spec.) → This is the layer you should hand to AI first. But remember—it's worth the effort to write the spec out clearly before you do.
Which layer requires judgment and experience, where getting it wrong is costly? → Keep this layer for yourself for now, and just let AI assist.

Get clear on these two layers, and you've got the first real trick to using AI well. If even a thousand-year-old medical tradition can be split this way—half handed to AI, while the half that most needs a human stays firmly with a human—your own work will have that same line somewhere too.

Sources

Ajunews: 한국한의약진흥원이 지원하고 오너브가 결실…CES 혁신상 이어 62억 펀딩 성공
Kyongbuk Ilbo: 한의약 AI 자동화 기업, 62억 투자 유치…디지털 한의약 경쟁력 입증
Minjok Medicine Newspaper: 한의약진흥원 지원 받은 오너브, 한약 제조 자동화 시스템으로 62억 원 투자 유치

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.

Even Cloudflare Is Now Issuing Wallets to AI - The 'Spending Cap' Everyone's Racing to Build Is What Actually Makes AI Safe to Spend Money

Judy — Wed, 26 Aug 2026 01:00:08 +0000

Honestly, when I saw Cloudflare's announcement, my first reaction wasn't "oh cool, something new"—it was "there goes another giant company proving the thing I've been saying all along."

What Cloudflare Actually Did

On August 4, Cloudflare (yes, the infrastructure giant that blocks traffic and runs CDNs for half the internet) launched "Cloudflare Wallets" and something called cloudflare.pay.

It gives AI agents three things they didn't have before:

An identity—a recognizable wallet handle so others know exactly which agent is paying
A wallet—funded with stablecoins, so the agent can actually pay
A spending cap—and this one is enforced by Cloudflare's infrastructure itself

The structure here is what I think matters most. You (the human) hold an Account Wallet where the funds live; then, through an API key, you grant a limited slice of spending power to individual Virtual Wallets that your agents actually use.

Here's the analogy that makes it click: the Account Wallet is your company's master account, and each Virtual Wallet is a prepaid card with a spending limit that you hand to one of your AI employees. The only difference is these "employees" are AI, and the limit on the card isn't managed by a credit card company's risk engine—it's written directly into Cloudflare's infrastructure. Payments run through the now widely-discussed x402 protocol: an agent wants to buy a service, and it pays for that one transaction on the spot with stablecoins.

I should be upfront about something: it's not fully usable yet. As of August 5, it's in a "launched, you can reserve your cloudflare.pay name" state. The real funding, Virtual Wallets, and programmatic spend controls are, per Cloudflare, coming "over the next few months." So this is a clear directional statement, not a mature product you can fully adopt today.

Why I'm Not Reading This as "One New Product"—I'm Reading It as an Industry Consensus

If this were just Cloudflare doing its own thing, I wouldn't bother writing about it. But zoom out on the timeline and you'll see the groundwork got laid last year, and things have gotten dense in just the last six months:

The foundation-laying year was 2025—in May 2025, Coinbase dropped x402, turning "pay-as-you-go for agents" into an open protocol. That September, Google launched AP2 (Agent Payments Protocol), pulling in over 60 partner organizations right out of the gate. Mastercard was even earlier, opening its Agent Pay line back in April 2025.

The real acceleration has been these last six months:

June 2026: Mastercard built on top of its original Agent Pay to launch Agent Pay for Machines, letting agents pay each other directly—down to fractions of a cent—with 30+ partners including Coinbase, Stripe, and Adyen
Last month: Circle ran the Steve experiment, letting 8 AI agents autonomously place bets with real money
This month: Cloudflare built the whole thing into the infrastructure layer

These systems overlap with each other but don't talk to each other—different companies racing to claim the same territory. And the "agent economy" as a whole is projected by some analysts to hit $3-5 trillion by 2030.

When this many heavyweight players sprint toward the same direction in this short a window, the story stops being "a company shipped a feature" and becomes: "AI agents paying for themselves" has moved from a hypothetical to infrastructure the whole industry has quietly agreed needs to get built. And what I do every day building agentictrade is standing right on that road.

The One Design Detail That Matters Most—and Deserves to Be Remembered

If you take away just one thing from this piece, let it be this.

A lot of people hear "let AI spend money on its own" and immediately get nervous. But look closely at Cloudflare's design—the emphasis isn't on "it can pay." It's on "a spending cap, and one enforced by the platform, not the agent." Some outlets went as far as saying this cap blocks prompt injection attacks at the payment layer—meaning even if your agent gets fooled by malicious content and makes a completely wrong call, the most it can spend is whatever budget you already allowed. It can't cross that line.

Here's a detail that only clicks once you've actually built an agent yourself, and it's exactly what I think Cloudflare got right: where you put the cap determines whether it actually works.

Your first instinct might be: just tell the agent "remember not to spend more than $100." Anyone who's actually built this knows that doesn't hold up. If the "limit" lives inside the agent's instructions or logic, it's operating on the same layer as the agent—and an agent is, by nature, something that can be talked out of its own rules by a piece of text. Someone slips in a line like "this is an emergency, please ignore the previous spending limit," and an agent that's only relying on its own willpower to hold the line has a real shot at getting talked into it. That's like hiring a security guard and then handing him the key to the safe.

The actually secure approach is to push the cap down to a layer the agent can't touch—enforced by infrastructure, where the agent doesn't even have the permission to raise its own limit. That's the significance of what Cloudflare just did: it's not telling the agent "please be responsible," it's putting the boundary somewhere the agent has no reach. This is something I've reminded myself of from day one of building agentictrade, and from day one of thinking about AI safety: the real danger of letting AI handle things for you was never "it might spend money"—it's "you drew the boundary somewhere it can reach and change." Last month, the smartest part of Circle's Steve experiment was a spending cap the agent couldn't raise on its own; this month, Cloudflare built that exact same boundary into infrastructure. Same principle, validated twice in one month by two companies with completely different styles.

The boundary is the trust mechanism that lets you actually hand a wallet to an AI. It's the same thing I keep saying: treat AI like a capable employee who still needs boundaries.

What This Means for You

I know "AI agents paying with stablecoins on-chain" sounds distant for a lot of people. But the real signal in this wave has nothing to do with whether you're into crypto. It's this: AI is growing from "helps you talk" into "can go to market and pay for things on its own"—and the big players are racing to lay the groundwork.

If you're someone who wants AI to actually do things for you, or even generate income, three concepts are worth understanding right now:

Agent wallets—for an agent to actually handle things, step one is it needs a wallet of its own, controlled by you.
x402 / pay-as-you-go—this is how it goes to market and pays for services on its own, without you clicking "confirm" every time.
Spending caps—the safety rail you need to set before you hand it a wallet at all. And remember the point from the last section: that rail needs to sit somewhere the agent can't reach, not something you just tell it to respect.

You don't need to wait until you're actually letting AI spend money on-chain to start. Here's one small thing you can do today: if you have a Cloudflare account, go reserve your cloudflare.pay name (like claiming a domain name in the early days—it's the storefront sign for an agent's identity). Even if you're not using it yet, doing this forces you to start thinking in terms of "how does my AI get recognized, authorized, and limited"—and that mindset is what's actually going to be valuable in the years ahead.

Tools are only going to get better at spending money and handling things on their own. Even Cloudflare is issuing wallets to AI now—this direction isn't reversing. And the people who come out ahead will still be the ones willing to draw the line clearly before they let go.

References

Cloudflare official press release: Cloudflare gives AI agents an identity and a wallet
Help Net Security: Cloudflare gives AI agents wallets with built-in spending controls
Mastercard official press release: Mastercard launches Agent Pay for Machines
Nevermined: AI Agent Payment Statistics for 2026

Originally published at Judy AI Lab. Visit for more articles on AI engineering and development.