The Era When Execution, Not Intelligence, Became the Edge

The era where execution, not intelligence, is the edge

The theme of the night was blunt. Intelligence doesn't matter the way it did. High IQ, deep knowledge, long careers, AI has started replacing all of it, and one well-made viral open-source project now outweighs a good resume. What's left is the insight and sense to read a market, ideas, and above all the power to execute them fast.

The problem is organizations. Solo builders and small startups can execute while large organizations grind against internal process and approval lines, which is why the phrase of the moment is that people are the bottleneck. Attendees from large organizations nodded hard at that. The bigger the org, the bigger the security risk, and agents that work fine for one person leak at organizational scale. So this event skipped past personal proficiency and went at workflows that actually run in real work, with four companies on one stage and over 150 attendees, enough that we had to open the adjacent space.

Agents at Amazon: platform and process innovation

AWS tech evangelist Yongho Choi opened with Amazon agent cases, starting with delivery. The same address can mean the front door, the security office, or a business closed after hours, and those variables used to live in human notes and manual workarounds. Rebuilt as an agent, a person asks a question and the agent orchestrates: internal databases first, then public address, terrain and business-hour data, then a combined judgment. Early delivery failure rates fell 74 percent.

His emphasis: never stop at one agent, because reuse needs a platform. Amazon stacked each team's agents into an internal platform called Agent Z, 23 thousand agents as of May, so a search usually turns up one already built and workload drops sharply. For the coding tool Kiro, the strength he named was spec-based work. A prompt like build me a shopping mall makes the AI silently decide too many things. Write an intermediate document first, let the human correct it and sync, and you get better results and better token economics. Amazon has accumulated 15 thousand specs in a Spec Studio. The thread running through all of it: don't keep it in your team, spread it, platform it.

The other lesson was process innovation. A Bedrock framework estimated at 30 developers for 18 months shipped to production with six developers in 76 days using stack-based tooling. Here's the interesting part. For the first weeks productivity barely moved. It jumped only after they realized that using AI isn't enough and the work process itself has to change. Three lessons came out of it. Results improve when you hand agents goals and let them run rather than commanding task by task. When multiple agents collaborate rather than ping-ponging with one. And when runs stretch to hours and days rather than seconds. The newest features of Claude Code and Codex are evolving in exactly that direction.

Japan and APAC today: work slop and context

The second session came from Akimasa Omori, executive officer at Classmethod headquarters in Japan, an AWS premier partner that also oversees the Korean and Malaysian entities. He delivered it in Japanese with live interpretation. Malaysia and Thailand are still a step before adoption, slowed by cost and security concerns. Japan is adopting gradually, along four current trends: AI-driven development, security measures, reverse engineering, and company-wide adoption. Demand runs especially high for reverse engineering, feeding spaghetti legacy systems to AI to document structures nobody understands anymore. Company-wide adoption is the hardest, because making internal knowledge shareable takes the longest.

His warning was work slop. AI produces plenty of good-looking material that turns out to be unreadable, costing an average of two hours a day to interpret and fix, which is a net productivity loss. Hence his emphasis on context. In high-context societies, answers drift further and further off unless you understand the context and ask. The biggest problem he sees in companies is ideas pouring out with nobody executing, so his constant line is to execute something, however small, and produce a result. He also re-reads AI as Actual Intelligence, meaning human intelligence. Things move when artificial and actual intelligence execute together, which is why communities that share context and best practices matter.

A lawyer and an AI safety expert on what comes next

The centerpiece fireside brought together Hyunseo Lim, an attorney specializing in insolvency, and Haeon Park, co-founder and CTO of the AI security and safety startup AIM Intelligence. Lim now handles roughly 2.5 times the workload of a year and a half ago and sleeps through nights he used to lose. The AI strength he named first was replacing emotional labor. Pleading, asking, the unpleasant tasks. AI does them well. He uses it everywhere it can be used and rates it above 90 percent of lawyers in general reasoning, with one Korean limitation: court decisions aren't public, so domain grounding is weak. And in law, the gap between users and non-users has suddenly torn open.

Park's company attacks AI security from both sides. A red-team solution automatically probes the risks in a customer's AI service, and a guardrail solution closes the gaps. They work with global big tech to test models before release, checking for example that a model won't produce bioweapon instructions. The NASA story stayed with the room. Testing an official chatbot connected to the Parker Solar Probe, they found dangerous outputs with no filter or guard, reported it, and NASA shut the service down and sent a letter of recognition.

His warning: as model capability rises, so does hacking capability, to the point where ordinary people hack at expert level and institutions nobody imagined are getting breached. Government regulation, on that view, isn't a strange instinct.

I asked what they never hand to AI. Park said the balance of control and use is the crux, and the one thing he always checks himself is any email that goes out in his own voice. Lim doesn't auto-send either, though he added that the speed itself already feels beyond human control.

The collapse of advisory, and copyright chaos

On the future of law, Lim thinks the collapse of the advisory market has already started. Time-based advice is getting hard to justify, and if an AI strong in rules and reasoning finds the answer, the search-proxy species of advisory lawyer stops being necessary. What's left is consulting, strategy, and the experiential expertise only a firm that's been around the loop holds, like overseas fund registration, which you can't search for and only know if you've done it. His view of AI judges has shifted too. Standards of reasonable doubt vary by individual, and if that intelligence could be kept more uniform, why insist on judges with personal variance? Though the system isn't ready for full digitization yet.

Copyright, in his blunt phrasing, is pandemonium. Pure AI output gets no recognition of creativity, human involvement does, and verifying the difference is close to impossible. In one case an obviously AI-generated image was claimed as hand-drawn until someone asked for evidence, and the answer came back: the hand has six fingers. Copyright protects only the form of expression, so copying an idea isn't infringement, and a copier who claims AI did it can't be checked, which leaves everything suspended.

The conclusion was that the whole framework has to change completely and nobody takes responsibility. Asked who survives the AI era, Lim chose the diligent one-clicker and Park chose the person with the skill to verify and take responsibility, because AI won't carry responsibility for a while yet, and the verifying eye only grows from doing the domain many times.

From the roundtables

The four-person roundtables branched widely, and the thread that came up most was generalists versus specialists. Today AI fills the empty areas and favors generalists, and once the areas fill, the specialists take over. With knowledge now the baseline for everyone, the domain expert who can point where to go on top of that domain becomes decisive.

What companies can take away

Four things remain, in working language. One, platform your agents. One-off agents die, and reuse needs an internal registry the whole company can search. Two, change the process, not just the tool. Productivity jumps only when workflows get redesigned around long-running, multi-agent, goal-driven work. Three, fight work slop with context. Unreadable AI output is a net loss, and shared context is the antidote. Four, keep verification human. The responsible, domain-trained eye that checks what goes out in your name can't be delegated.

FAQ

What did Amazon achieve with delivery agents? Early delivery failure rates fell 74 percent by letting an orchestrating agent combine internal data with public address, terrain and business-hour information.

What is work slop? AI-produced material that looks polished and reads as nothing, costing hours a day to interpret and fix. The antidote is context: understand it, and ask.

What do the experts never hand to AI? Anything going out in their own voice. Emails are always personally checked, and neither of them auto-sends.

Join Bloom

Bloom builds offline rooms where people and technology meet. We run them in Seoul, and now beyond it.

• 💬 Discord community, where events are announced first
• ▶️ YouTube, full talks from past events
• 📸 Instagram, photos from our events
• 🎟️ Bloom app, upcoming events and Mixers