Tuesday, July 21, 2026 Trend Press · Cloudflare Pages

The Trend Tribune

"All the trends that are fit to read" Morning Edition Free of Charge
TODAY'S LEAD STORY

The day the privileges of "OK Google" crumble: The true meaning behind the EU opening up Android to rival AI.

On July 16, the European Commission issued two binding decisions to Google under the Digital Markets Act (DMA). These decisions include Google's obligation to open up 11 Android features to rival AI assistants and its obligation to anonymize and share search data. This article outlines Google's security concerns, the risk of the app sandbox system collapsing as pointed out by experts, the phased rollout until 2027, and the sanctions for violations.

The day the privileges of "OK Google" crumble: The true meaning behind the EU opening up Android to rival AI.
(Photo: illustrative)

The Day the Privileges of "OK Google" Fall: The True Meaning Behind the EU Opening Up Android to Rival AIs

On July 16th, the European Commission issued two binding decisions ordering Google to open up the deepest parts of Android to rival AI assistants. This measure is based on the Digital Markets Act (DMA), a law designed to regulate the EU's "gatekeeper" role for giant tech companies. This article will delve into the details of these decisions and why they are important for engineers.

What Was "Unfair" in the First Place?

First, let's clarify the structure of the problem. When you say "OK Google" on your Android smartphone, Gemini activates, you can start a conversation by long-pressing the home button, read screen content, and perform actions within other apps. This is an OS-level function, an access permission that Google had previously granted exclusively to its own Gemini.

On the other hand, third-party AI assistants lack this deep integration. According to the European Commission's investigation, AI agents created by companies other than Google were unable to perform the same level of functionality on Android as Gemini. This decision recognizes this asymmetry as "illegal" and demands its correction.

Details of the Order: 11 Android Features and Search Data

The decision is broadly divided into two parts.

The first concerns Android interoperability, mandating that third-party AI assistants be granted the same level of access as Gemini to 11 Android feature groups, subject to authentication and user consent. Specifically, this is expected to include features such as voice activation (wake word detection), home button activation, screen content reading, and execution of actions within other apps.

The second concerns search data, mandating that Google Search provide some of its anonymized query, ranking, click, and browsing data to competing search and AI companies, including OpenAI, under a defined fee structure.

The implementation schedule is phased. Search data sharing is scheduled to begin in January 2027, the main Android-related measures are expected to be implemented by the "Android 18" generation, and the simultaneous wake word detection feature will be carried over to the "Android 19" generation.

Google's Counterarguments and Technically Appearing Concerns

Google has strongly opposed this decision. Kent Walker, the company's President of Global Public Relations, stated, "This decision risks undermining crucial privacy and security guardrails for millions of European users," and countered, "We have repeatedly proposed solutions to protect users while meeting DMA goals, but this ruling disregards the abundant evidence of user harm."

This shouldn't be dismissed as mere corporate excuses; it includes technically valid concerns. Roman Stanek, CEO of Good Data AI and an enterprise security expert, accurately points out the risks this change poses. He commented, "Until now, enterprise security has been based on the simple premise that apps are 'boxes,' and the OS controls communication across those boxes. However, when multiple AI agents have the same level of system access, screen context access, cross-app actions, and background execution permissions, this premise itself collapses."

This is a point that resonates from a software engineer's perspective as well. When multiple AI agents can access screen information in parallel at the OS level and perform actions across apps, the design of permission management, audit logs, and anomaly detection becomes fundamentally more complex than when a single AI assistant was assumed. The Commission states that it has included a safeguard that "technical safeguards are permissible, but they must not be used as a pretext for eliminating rivals." However, the specific technical requirements for a service to be recognized as a third-party service, and the liability in the event of a breach of a recognized service, remain unclear from the current announcement.

The culmination of a six-month process

This decision did not come out of nowhere. On January 27th of this year, the European Commission began detailed specification procedures for each of these two structural advantages (Android integration and search data). This decision marks the culmination of that approximately six-month process.

Google is expected to appeal the decision, but under the DMA framework, appealing does not automatically suspend compliance obligations. The rules regarding the order of proceedings at the European General Court, just established on July 8th in the Apple-related gatekeeper lawsuit, also support this point. The penalties for violations are not light, potentially resulting in fines of up to 10% of global revenue (20% for repeated violations).

What Engineers Should Consider

The reason we're treating this news as a technical blog post is that it has more significance than just a regulatory battle between large corporations. The theme of interoperability of AI agents at the OS level has the potential to fundamentally change the assumptions behind mobile app development and security design.

Until now, mobile security architectures have been built on the model that "apps are sandboxed boxes, and the OS manages their boundaries." If multiple AI agents begin to request the same level of system access, this assumption will need to be redefined. How this EU decision will be translated into actual technical specifications and certification processes—a series of changes that the developer community cannot ignore during the rollout process towards 2027—is likely to be significant.

GoogleAndroidEUDMA規制AIアシスタント

AI companies are avoiding post-launch safety research—a surprising bias revealed in 9,439 papers.

This article explains the research "Real-World Gaps in AI Governance Research" by Ilan Strauss and colleagues of the AI ​​Disclosures Project. Analyzing 1,178 safety studies extracted from 9,439 generative AI papers, it reveals that corporate research is heavily skewed towards pre-deployment alignment and evaluation, while research in high-risk real-world application areas such as healthcare, finance, and misinformation is remarkably lacking. The article also includes criticisms of Anthropic's own research approach and policy recommendations for information disclosure, drawing parallels to financial regulations.

AI Companies Avoid Post-Launch Safety Research: A Surprising Research Bias Revealed by 9,439 Papers

AI companies announce their "safety initiatives" daily. However, a scrutiny of over 9,000 papers reveals a clear bias: They are enthusiastic about research before a model is released to the public, but surprisingly reluctant to conduct research after it's actually being used. This article introduces the research study "Real-World Gaps in AI Governance Research," which makes this subtle but important point.

A Meticulous Analysis from 9,439 Papers

This paper is by Ilan Strauss and others from the AI ​​Disclosures Project (under the Social Science Research Council). Ilan is also a researcher at UCL, and the co-author is Tim O'Reilly, founder of O'Reilly Media.

The analysis is based on a massive corpus of 9,439 generative AI-related papers published between January 2020 and March 2025. From this corpus, papers from five companies (Corporate AI), including Anthropic, OpenAI, and Google DeepMind, and six universities (Academic AI), including CMU, MIT, and Stanford, were extracted. From these, 1,178 papers related to "safety and reliability" were further selected for analysis. The careful handling of co-authored papers spanning multiple institutions, employing a "proportional author allocation method" that allocates the contribution of each institution according to the number of authors, is commendable research design.

The Premise that Corporate Research Has "Overwhelming Influence"

First, as a foundational fact, while the number of papers published by companies is fewer than those published by universities (1,527 vs. 3,578), the number of citations surpasses that of universities (119,845 vs. 78,858). In particular, the number of citations for general generative AI research by Google DeepMind (69,453) exceeds the combined total of the top four universities analyzed. This establishes the premise that the "voice" in AI research is extremely concentrated in a few giant corporations.

Categorical Analysis of Corporate Research Focused on "Pre-Deployment" Stages

The paper then classifies safety research into eight categories (alignment, testing & evaluation, interpretability, ethics & bias, post-deployment risk, multi-agent safety, policy & governance, privacy & security) and compares the emphasis placed by companies and universities.

The results are clear. The influence (number of citations) of corporate research is primarily driven by research conducted before a model is actually released to the market, specifically "alignment" and "test & evaluation". Conversely, there's an interesting reversal: academics have a far greater presence than corporations in "ethics and bias" research, which deals with the behavior of models after they've been commercially deployed.

The authors' observations on this trend are frank: "Much of the research called 'test & evaluation' actually deals with the pre-deployment context. So-called 'in-the-wild' evaluation attempts to predict how a model will behave after it's actually deployed, but it's essentially retrospective." This suggests a structural limitation: reliance on benchmark datasets based on known failures prevents the capture of newly emerging risks.

The Lack of Research in "High-Risk Areas" as Told by Numbers

Particularly striking in the paper is the table showing the lack of research investment in high-risk areas that have led to actual lawsuits, such as healthcare, finance, misinformation, and addiction. In the medical field, there are 53 papers from universities compared to only 9 from companies. Similarly, in papers on misinformation, there are 53 from universities compared to only 8 from companies. This is a significantly larger disparity than the general ratio of academic papers (approximately 2.5 to 1 between universities and companies).

The specific examples cited in the paper are quite stark. It discusses the case of Character.ai, which is being sued over "bots designed to create addiction," and then cites the example of Meta, which subsequently expanded the scope of explicit language permitted in romantic role-playing in its AI chatbots. The paper points out that while corporate system cards mention the risk of persuasion, they often lack concrete safeguards to address it.

Reference to Anthropic's Own Research

What makes this paper particularly interesting is that it specifically examines the research stance of Anthropic itself. The paper points out a disparity in research investment between Anthropic's efforts to conduct interpretability research for risk detection based on the "internal workings of the model" and to validate Claude's values, and the company's own published abuse case reports—specific examples of actual abuses of Claude, such as recruitment fraud, malware development, credential theft, and management of social media bot networks for political influence.

According to the paper, Anthropic's report itself acknowledges the continued risk of future problems, stating that "as agent-based AI systems evolve, these semi-autonomous, organized, and complex abuse systems are expected to continue." Nevertheless, the paper argues that research investment in safeguards for such real-world applications is not commensurate with this risk.

Why does this bias exist?

The authors cite two factors behind this trend. One is simple commercial incentives—the structure makes it unlikely that companies will proactively publish research findings that could negatively impact product market penetration or regulatory treatment. Another factor, the paper points to as an ideological one, is the influence of a philosophy that emphasizes existential risk (x-risk). Under this philosophy, the autonomy inherent in the model itself is considered the primary source of risk, and concern for catastrophic future scenarios tends to take precedence over immediate operational concerns.

Policy Recommendation: Learning from Financial Regulation's "Suspicious Transaction Reporting" System

The latter half of the paper offers concrete recommendations for correcting this information asymmetry. Of particular interest is the framework modeled after the financial industry's "Suspicious Transaction Reporting (SAR)" system. Similar to the "safe harbor" provision that exempts financial institutions from civil liability for good-faith reporting while obligating them to report suspicious transactions to authorities, the paper proposes that AI companies should also have a system in place to disclose operational data (logs, system operation records, etc.) to certified researchers and auditors, exempting them from the risk of liability.

A Note from a Researcher's Perspective

This paper itself has limitations, as acknowledged by the authors. It uses AI models (such as GPT o3-mini) for part of the classification process, and its classification accuracy may not be perfect. Furthermore, it doesn't fully capture the realities of collaborative research between companies and universities (such as the movement of personnel). Also, the paper is based on data from May 2025 and does not reflect subsequent changes in the situation.

Nevertheless, I believe the significance of quantitatively visualizing, with data of this scale, what is actually being researched and what is not being researched behind the scenes of companies' flashy announcements about "safety initiatives" is considerable. This paper reminds us of the importance of developing the habit of being aware of what is not being said when reading company press releases, not just what is stated.

References: arxiv.org / arxiv.org
AI/ML論文AI安全性AI governanceAnthropic研究動向

A $325 million "bargain" acquisition: The real reason Hyundai made Boston Dynamics a wholly owned subsidiary.

On July 16, Hyundai Motor Group acquired the remaining approximately 9.65% of SoftBank's shares for approximately $325 million, making Boston Dynamics a wholly owned subsidiary. This article explains the contractual structure, including the activation of a put option clause set up in 2021; the discrepancy between the valuation of $3.3 billion, which had been fixed for five years, and the actual market value; the plan to deploy the Atlas factory in 2028; development partnerships with NVIDIA and Google DeepMind; and even the social tensions arising from the labor union strike.

A "Bargain" Acquisition of $325 Million: The Real Aim Behind Hyundai's Wholly-Owned Acquisition of Boston Dynamics

On July 16th, Hyundai Motor Group announced its acquisition of SoftBank's remaining shares in Boston Dynamics (approximately 9.65%) for approximately $325 million. This makes Boston Dynamics a wholly-owned subsidiary of Hyundai. While the numbers alone might suggest a small transaction, the underlying contractual structure and the resulting discrepancy in valuation are quite interesting from a software perspective.

The "Put Option" Was a Pre-arranged Measure Five Years Ago

First, let's clarify the legal structure of this transaction. In 2021, when Hyundai and SoftBank entered into an agreement to acquire shares in Boston Dynamics, they pre-arranged a contract that granted SoftBank a "put option" (the right to sell its shares under certain conditions) and Hyundai a corresponding "call option" (the right to buy back the shares under the same conditions). The condition was that "Boston Dynamics remained privately held by this year (2026)."

Now, Boston Dynamics has reached this deadline without having had an IPO (Initial Public Offering), and SoftBank has notified them of its exercise of the put option. The Hyundai shareholders (Hyundai Motor 28%, Hyundai Motor Group Chairman Euisun Chung personally 22.6%, Kia 17.2%, Hyundai Mobis 11.3%, Hyundai Glovis 11.25%) will purchase the shares at a predetermined price. This clause, set in motion five years ago, has now been activated.

What the predetermined price means: A "fixed" valuation of $3.3 billion

This is the most interesting point from an accounting and investment perspective. The acquisition price of $325 million represents a valuation of Boston Dynamics as a whole at approximately $3.3 billion. This is roughly the same valuation as when Hyundai acquired an 80% controlling stake from SoftBank in 2021 (an overall valuation calculated backward from the $1.1 billion transaction size), meaning that the company's "contractual valuation" has remained completely unchanged for five years.

On the other hand, analysts at the South Korean securities firm Kiwoom Securities point out that the valuation calculated backward from the terms of this transaction is far removed from the actual market value, with some brokerage estimates suggesting Boston Dynamics' potential value exceeds 300 trillion won (approximately $19 billion). The contractual structure of a put option forces a transaction at a price fixed five years ago, regardless of the market's current valuation. The 2.1% drop in Hyundai's stock price on the day of the announcement is seen as a result of investors' skepticism regarding the validity of this "unchanged valuation."

A Realistic Timeline for Atlas Factory Deployment: "2028"

Let's move on to the technical aspects. Hyundai explains that the main goal of this complete acquisition is to build an "integrated AI robotics ecosystem" centered around the humanoid robot "Atlas." Training will be conducted at the Robot Metaplant Application Center in Georgia, with the first actual deployment targeted for 2028 at a factory in the same state, and plans to expand production capacity to a maximum of 30,000 units per year. Initially, tasks will begin with welding and material handling, and by 2030, the scope will expand to include parts assembly processes.

This schedule is not overly ambitious compared to other companies' humanoid mass production plans that I've previously discussed in this column (Tesla's Optimus Gen3 was for internal testing only until 2026, with full-scale mass production starting in 2027 at its Texas factory). In fact, the phrase "actual deployment in 2028" gives a positive impression as a grounded plan. As technical justification, Boston Dynamics CEO Robert Playter mentioned specific hurdles to practical application, stating that Atlas needs to learn new factory tasks within 1-2 days and achieve 99.9% reliability.

Development Partners: NVIDIA and Google DeepMind

It is reported that collaboration with NVIDIA and Google DeepMind is underway in the development of Atlas. This approach of collaborating with external specialist companies for the foundation of the AI ​​model, rather than developing it alone, is similar to the "LLM-independent" strategy of Agility Robotics previously discussed, and the partnership between Mitsubishi Motors and Highlanders, and can be seen as an example of the increasingly widespread division of labor model in the humanoid industry.

The Unmissable "Tension with Labor Unions"

This is a subtle but important point that I, Takahashi, would like to highlight. The acquisition announcement coincides with a period when Hyundai's domestic labor union in South Korea is intensifying industrial action over annual wage negotiations. According to reports, the union held a two-hour strike from Monday to Wednesday and is planning a four-hour strike from July 20th to 22nd. The union is demanding a bonus pool equivalent to 30% of net profits and a written guarantee of employment security as robots are introduced.

At the very heart of the automobile manufacturer's plan to fully deploy humanoid robots in its factories, the workers themselves are raising their voices due to job insecurity—this conflict highlights once again that the practical application of humanoids is not merely a technological issue, but a social issue concerning the very nature of work.

Summary: Wholly Owned Subsidiary as a Streamlined Governance Process

This wholly owned subsidiary is less about a technological breakthrough and more about accelerating decision-making and streamlining governance. By eliminating the process of negotiating interests with SoftBank as a minority shareholder, Hyundai will be able to determine the Atlas development roadmap solely based on the needs of its own group. Some believe this complete acquisition could be a stepping stone to Boston Dynamics' IPO. Now that it has become a wholly owned subsidiary at a "fixed valuation" of $3.3 billion, the next time the company's true market value will be tested will likely be when these IPO speculations actually materialize.

HyundaiBoston DynamicsAtlasM&AヒューマノイドSoftBank
Advertisement300 × 250