読書リサーチレーダー投資フレームワーク
ログイン / 新規登録
すべて技術製品投資株式市場その他

読書

2026-11-2154 投稿

更新

US President Trump Threatens Heavy Tax on Overseas AI Data Centers

構造的
2026-11-21

US President Donald Trump stated at a White House briefing on November 20 that he intends to impose "enormous taxes" on US companies building AI data centers abroad. He emphasized the goal of keeping AI infrastructure within the United States, arguing that relocating advanced chip production and data center construction overseas causes significant damage to the country. However, Trump acknowledged that this concept has not yet been communicated to his staff, and the specific legal authority or implementation mechanism remains unclear.

This executive stance contrasts sharply with recent polling data and legislative developments. According to an AP Voter Poll cited in reports, approximately 75% of US voters oppose new data center construction in their local communities, citing concerns over rising electricity prices and water usage. This public sentiment contributed to Republican losses in the recent midterm elections, where Democrats gained control of both chambers of Congress. Despite this, Trump dismissed concerns about consumer electricity costs, claiming that data centers are valuable assets and that operators will build their own power facilities, which he argued would actually lower electricity rates.

The threat targets major technology firms such as Microsoft, Alphabet (Google's parent company), and Amazon, which have been expanding global capacity with hundreds of billions of dollars to support AI computing needs. While the US remains the leader in superintelligence development, companies are increasingly looking to markets in China, Europe, and Latin America for expansion. Trump specifically criticized Google's $13 billion investment in Finnish AI infrastructure, though the company also supports large domestic projects.

In parallel, the Senate passed a bipartisan bill on Thursday to accelerate permitting for energy infrastructure like power plants and transmission lines, requiring data centers to bear the cost of grid upgrades. The bill now moves to the House. Economists note that while data center construction boosts economic activity and wages for skilled trades, the reliance on imported semiconductors and copper may offset some benefits. Bloomberg analysis previously found wholesale electricity prices in data-center-heavy regions rose by up to 267% compared to five years ago.

ソース:INSIDE

リサーチ

Microsoft Foundry Gives AI Agents Their Own Entra Identity to Work in Team Contexts Without Borrowing Credentials

重大
2026-11-20 03:53 GMT+8

Enterprises are all-in on AI agents, but the ROI hasn't followed. Amanda Foster, a Technical Program Manager at Microsoft Foundry, argues that the bottleneck isn't capability — today's agents can solve hard math problems and build operating systems. The bottleneck is that agents cannot work in the places enterprise work actually happens: group chats, shared calendars, team SharePoint sites.

The specific failure mode Foster identifies is credential inheritance. Unless an agent has a Microsoft 365 account of its own, the only way it can act in Outlook or Teams is with a signed-in user's permissions. This breaks in two common scenarios. First, an agent triggered by an event has no signed-in user to act for, so it either cannot take Microsoft 365 actions or must store someone's credentials. Second, in a group chat with many users, the agent must guess on whose behalf to act, and it could pick someone who didn't ask. That person's permissions then apply to the whole thread, and members can see content they don't have access to.

Foundry's answer is to give each agent its own identity as a named member of the organization. Every Foundry agent receives a Microsoft Entra agent identity, and these new agents also receive an Entra agent user account that lets them perform Microsoft 365 actions as themselves. They get their own email, calendar, and OneDrive. You grant them permissions the same way you would a person. They have a manager who is accountable for them, visible in the org chart. Every action is attributed to the agent, not to whoever happened to be in the conversation.

The deployment model uses blueprints. You don't build an agent directly; you build a template that defines what the agent can do — which APIs it can call, which MCP tools it can access — and deploy it as a Foundry hosted agent. Once an admin approves the published blueprint, your entire organization benefits: each approved person hires their own instance, with its own identity, agent user account, and access to their resources. The blueprint never grants access to any specific team's business resources; each manager decides which Azure DevOps project or SharePoint site their instance can reach.

Foster draws an important distinction that separates this from treating agents as employees. She notes that giving an agent a user identity lets you govern it like an employee, not because it is one. Agents have no stakes of their own, so the consequences that shape human behavior don't shape them. They don't notice when they're past what they know and keep going confidently where a person would stop and ask. And where a thousand employees make a thousand different mistakes that partly cancel out, a thousand copies of one agent share the same blind spots and fail together. That's why every agent is an instance of a blueprint, so one kill switch can disable an entire class of agents in one action.

The article introduces Hermes Enterprise on Microsoft Foundry as a concrete example. Nous Research's Hermes Agent, which launched in March 2026 and became the top agent on OpenRouter by token usage, can now work as an AI coworker with its own Microsoft 365 account, identity, and access. Each Hermes instance gets its own email, calendar, OneDrive, chat profile, and manager. Coming soon, companies will have two ways to run Hermes: as a SaaS agent hosted by Nous, or self-hosted in their own Azure tenant as Foundry hosted agents with a control plane that governs them.

ソース:Microsoft Foundry Blog

リサーチ

AMD's Lux supercomputer opens at Oak Ridge, half for science and half for sale

重大
2026-11-20

The Lux AI supercomputer, built by HPE and powered by AMD Instinct MI355X GPUs at the US Department of Energy's Oak Ridge National Laboratory (ORNL), has opened to scientific users. It debuted at No. 14 on the November 2026 TOP500 list with 220.79 petaflops in High Performance Linpack (HPL) benchmarking.

The system contains more than 4,000 MI355X GPUs, each with 288GB of HBM3E memory, totaling roughly 1.1PB of high-bandwidth memory across the cluster. ORNL reports peak performance figures of 40 exaflops at FP4, 20 exaflops at FP8, and 317 petaflops at FP64. The achieved HPL score represents about 70% efficiency against the theoretical FP64 peak, comparable to other top-tier systems like El Capitan and Frontier.

Lux operates under a unique business model: half of its 3.5 million annual node-hours are allocated to the Genesis Mission, an AI-for-science program launched by the Trump administration in November 2025. Projects include fusion plant design, materials manufacturing models, and long-range water forecasting. The remaining half is sold for proprietary use at DOE user facility rates, with minimum commitments of 175,000 node-hours per six months. AMD itself uses part of this paid share for development and testing.

This arrangement turns a national laboratory resource into a hybrid commercial AI cloud, with its chip supplier as one of its tenants. While the hardware is live, the scientific output from the Genesis Mission projects is only beginning. The key test will be whether these applications produce results that could not have been achieved on Frontier, the neighboring supercomputer which has already trained trillion-parameter models.

ソース:TechRadar

リサーチ

METR's Q4 2026 Update: Why AI Capability Measurement Is Getting Harder Even as Progress Accelerates

重大
2026-11-20 16:00 GMT+8

METR's Q4 2026 capability update makes a deliberately hedged argument: current public evidence is insufficient to rule out drastic AI R&D acceleration in the next couple of years. By drastic acceleration they mean a situation where capabilities improve so quickly that humans can no longer meaningfully understand, assess, and react to catastrophic risks posed by new AI systems. The report evaluates models up to Opus 5.5 and GPT-6 Astra, and its central methodological innovation is a new metric called Lifecycle Cost, created to quantify how difficult a task is to make into an RL environment.

The headline progress finding is that time horizons—the length of task an agent can complete with 50% success rate, measured against human completion time—are doubling roughly every 3.6 months across their combined TH1.1 and TH2 suites. On verifiable tasks like coding and optimization, current frontier models typically match or outperform the skilled human baseliners METR recruited. In one revealing example, on Al Zimmermann's programming contests (multi-month optimization competitions with 97 to 413 human participants), the median placement of the strongest models was the 96th to 98th percentile, though roughly 4 humans still beat them in the median contest. On Budget NanoGPT speedrun, the best agent run achieved a 15.7% speedup in 48 hours, while a top human contributor with AI assistance estimated 60 hours for a 41% speedup.

The Lifecycle Cost concept adds the most explanatory value for readers. METR defines it as the estimated cost to develop a containerized environment for a task and then run and score it 100 times. The intuition is that properties making an evaluation more realistic—requiring manual scoring, long feedback loops, specialized infrastructure—also make it costlier to turn into an RL training environment. Models perform worse on higher Lifecycle Cost tasks even after controlling for how long humans take to complete them. In their data, a doubling of Lifecycle Cost for a task of a given length imposes a difficulty penalty very roughly equivalent to halving the agent's time horizon. However, METR is explicit that this is a rough proxy calibrated to their own constraints, and that the link between Lifecycle Cost and actual realism remains very unclear.

The judgment gap is where the argument becomes most consequential for readers thinking about AI R&D automation. On tasks requiring choices in the absence of clear empirical feedback—designing good evaluation tasks, scoring philosophical arguments, making research decisions with slow feedback—models appear to have worse judgment than human experts. When asked to create new METR evaluation tasks, agents produced nothing the team considered sufficiently useful to include in the report. AI judges systematically overestimate the quality of outputs from models as strong as or stronger than themselves: Opus 5.5, the highest-agreement judge, scores GPT-6 Astra's tasks about 0.2 points higher than the human scorer on a 0-to-1 scale. On Earthborne Rangers, a novel board game, humans improved much more across playthroughs than frontier agents, with the best human going from 9 to all 21 objectives in 6 playthroughs while models barely learned.

ソース:metr.substack.com

リサーチ

AWS launches managed cluster extensions for SageMaker HyperPod Slurm

重大
2026-11-21 07:07 GMT+8

Amazon Web Services (AWS) has launched managed cluster extensions for Amazon SageMaker HyperPod Slurm clusters. This new feature brings the same declarative, API- and console-driven approach used for infrastructure configuration to the software running on the cluster's nodes, specifically targeting observability and user management.

Previously, managing software on shared Slurm clusters relied heavily on lifecycle scripts that ran only during node provisioning. As researchers joined or left, or as teams requested specific metrics, these scripts required manual editing and node replacement, leading to configuration drift where nodes became inconsistent over time. The new extensions allow administrators to declare desired software states via an API or the AWS console. AWS validates these settings before application and ensures consistency across all nodes, including those added by scaling or replacement.

Two initial extensions are available: sagemaker-observability, which collects node, GPU, Elastic Fabric Adapter (EFA), and Slurm job metrics to send to Amazon CloudWatch or Amazon Managed Service for Prometheus; and sagemaker-user-management, which creates users and groups with consistent IDs across nodes, controls SSH/sudo access, registers users with Slurm accounting, and can integrate with Active Directory. Users retain full direct access to nodes for custom configurations, but the extensions provide a managed path for common operational tasks.

ソース:Amazon Web Services

リサーチ

Ben Carlson: Why 'Buy the Dip' Survived the Dot-Com Crash but Not the Financial Crisis

重大
2026-11-21 05:30 GMT+8

Ben Carlson, a portfolio manager at Ritholtz Wealth Management, argues that the retail investor habit of buying the dip in tech stocks has a specific breaking point: not the depth of the drawdown, but the severity of the economic conditions that accompany it.

The observation starts with Nvidia. After Jensen Huang's scandal and resignation in October 2026, the stock fell more than 40% since early-October. On the day of the resignation itself, it dropped 9%. Retail investors responded by buying aggressively—Vanda Research data showed what Carlson calls "an insane amount" of net buying. This is not unusual behavior for this decade. Nvidia had already suffered three separate drawdowns exceeding 30% (the 2020 crash, the 2022 bear market, the Liberation Day sell-off) plus eight other double-digit corrections, and every time dip-buyers were rewarded.

Carlson's argument is that this conditioning creates a specific vulnerability. If the next downturn is accompanied by a shallow recession—like the 2001 contraction that lasted eight months with GDP falling just 0.3% and unemployment peaking at 6.3%—investors will likely hold or buy more, as they did during the dot-com bust. Household equity ownership remained stable from 2000 through 2002 and into the initial years after the crash, despite the S&P 500 falling 50% and the Nasdaq 100 dropping more than 80%. Maggie Mahar's documentation in Bull: A History of the Boom and Bust showed that net redemptions from equity funds in the twelve months ending March 2003 amounted to just 3.6% of the sector's assets.

But if the next downturn brings the kind of economic pain that accompanied the Great Financial Crisis—a year-and-a-half recession, GDP falling more than 5%, unemployment exceeding 10%, and a housing collapse with mass foreclosures—then dip-buyers will run out of cash and conviction. Household stock ownership fell from 63% in the mid-2000s to 52% by 2013, and it took that combination of job losses and housing destruction to break the habit.

The mechanism is straightforward: "It's much easier to step in and buy with the unemployment rate at 4%. Once you lose your job it's much harder to worry about the stock market." Risk tolerance is not just a psychological trait; it's constrained by income stability and balance-sheet health. A buy-the-dip mentality can survive a minor recession but faces a much harder test during a financial crisis.

Carlson does not predict which scenario will materialize. He explicitly says "I don't know" whether Nvidia will recover like Apple did after Steve Jobs, or whether this is a case where a huge company stumbles and never regains its perch. He cites JP Morgan's Michael Cembalest on the history of mega-cap companies knocked from their position who never return. The uncertainty is part of the argument, not a hedge against it.

Carlson closes by invoking the old saying that during bear markets, stocks return to their rightful owners—and then adds the qualification that matters: "Those rightful owners aren't always the people with the most discipline. Sometimes it's simply the people who can survive the downturns with their job and savings in tact." The relevant constraint on dip-buying resilience is not conviction or analytical skill but whether one's income and balance sheet can withstand the economic conditions that accompany the crash.

ソース:A Wealth of Common Sense

リサーチ

Google Launches Semantic Governance Policies for AI Agents in Preview

重大
2026-11-20

On November 20, 2026, Google announced the preview release of Semantic governance policies within its Gemini platform. This feature addresses a critical gap in enterprise AI security: traditional permissions define what an agent can do, but not whether a specific action aligns with business rules or user intent. By introducing a policy enforcement point outside the agent's code, Google aims to prevent unauthorized actions such as data leaks or hijacked tasks.

The mechanism operates by intercepting every proposed tool call from an AI agent before it executes. An LLM judge evaluates the call against two criteria: first, against plain-language policies written by compliance teams (e.g., "Do not share quarterly results before earnings"); second, against the original user request to ensure the agent has not deviated from its intended task. If either check fails, the call is blocked, and a denial message is returned to the agent. This process runs through Agent Gateway, ensuring that governance logic remains separate from the agent's underlying code and model instructions.

This approach distinguishes itself from existing controls like IAM (Identity and Access Management) or Model Armor. While IAM restricts access to tools and Model Armor screens for prompt injections, Semantic governance policies add an inline, semantic layer of defense. For example, if a user asks an agent to send financial data to an external investor under the guise of an NDA, the system can deny the request based on a policy prohibiting pre-earnings disclosures, even if the agent technically has permission to send emails. The verdicts and rationales are logged in Cloud Logging for audit purposes.

Google notes that because the judgments are made by an LLM, they are probabilistic and may vary. Enterprises are advised to use dry-run mode to test policies before enforcing them. The feature supports various models, including those accessed via the Gemini API, Anthropic Messages API, and OpenAI-compatible endpoints, allowing organizations to apply consistent governance across different AI stacks.

ソース:developers.googleblog.com

リサーチ

AWS Launches SageMaker HyperPod Global Inference Gateway for Cross-Region AI Routing

重大
2026-11-21 06:35 GMT+8

Amazon Web Services (AWS) has introduced the Amazon SageMaker HyperPod Global Inference Gateway, a new managed service designed to route artificial intelligence inference requests across multiple compute clusters and AWS Regions through a single endpoint. This addresses a critical infrastructure challenge where GPU capacity is fragmented across different locations, leading to idle resources in one region while requests queue in another.

The gateway operates as a second tier in the HyperPod architecture. While the existing Inference Gateway routes requests to specific pods within a single cluster, the Global Inference Gateway selects the best-suited cluster from all registered clusters. It uses four weighted signals to make routing decisions: KV cache headroom (available memory), queue depth (current load), region proximity (latency), and error rate (health). By default, the system prioritizes proximity but can be configured to favor resilience by increasing the weight of error rates.

For enterprises, this update eliminates the need to build custom cross-region networking, load balancers, and DNS management. Traffic is carried over the AWS backbone using AWS PrivateLink, ensuring privacy and reducing latency compared to public internet paths. Automatic failover moves traffic away from failed clusters without requiring client-side configuration changes. Authentication is handled via AWS Signature Version 4 (SigV4) and Identity and Access Management (IAM).

Jinhyung Park, VP of AI Platform at Bagelcode, noted that the beta version allowed their small platform team to achieve cross-region failover without maintaining their own routing layer. The feature is available now for users with multiple SageMaker HyperPod clusters.

ソース:Amazon Web Services

リサーチ

South Korea deploys emergency disaster alerts to catch AI cheating in college entrance exam

重大
2026-11-20

The South Korean government deployed emergency disaster alerts during the College Scholastic Ability Test (CSAT), also known as Suneung, to detect prohibited electronic devices. This novel enforcement method caught 54 students attempting to use AI-assisted cheating tools, including micro-cameras and smartphones.

The crackdown was prompted by a recent confession from Han Won-seok, the top scorer of the Certified Tax Accountant exam, who admitted to using a micro-camera that fed test images to an AI on his smartphone. Following this incident, Prime Minister Lee Jae Myung stated that AI abuse in public examinations undermines societal fairness and called for a system overhaul.

During the CSAT, three alerts were triggered at specific times: 8:30 AM, 2:21 PM, and 2:57 PM. The first alert caught 31 students before the exam started, while the subsequent two caught 23 more. In total, 111 students were identified with unauthorized devices when combined with other detection methods such as metal detectors and WiFi signal monitoring.

ソース:Tom's Hardware

リサーチ

Independent mathematicians verify AI proof of Riemann hypothesis, error chance near zero

構造的
2026-11-21 05:00 GMT+8

Mathematicians are now almost certain that the AI-created proof of the Riemann hypothesis is valid. Anthropic mathematician Levent Alpöge claimed to have used the company’s Claude AI model to solve the problem, which was first posed in 1859 and suggests a hidden pattern underlies the distribution of prime numbers.

Alpöge initially checked the work by writing out the proof using the programming language Lean; if a Lean-coded proof compiles error-free, this is usually taken as confirmation that the logic and math in each step is correct. Independent researchers, including Andrew Sutherland, a mathematician at M.I.T., have now separately compiled Alpöge’s result in Lean without issues.

“The Lean proof has been compiled and independently re-checked by the Lean kernel with only the three standard axioms,” Sutherland says. “Honestly the chance that anything is fishy here is approximately zero.”

However, some questions remain regarding whether the proof addresses the exact statement of the Riemann hypothesis or establishes a subtly different point. Researchers are still making sure that nowhere in the proof was there a hack, dodge or shortcut that changed the meaning of the initial hypothesis or any other mathematical rules or truths. This process, called a “comparator run,” typically takes a matter of hours.

ソース:Scientific American

リサーチ

Why AI Companies Are Now Honey-Trap Targets, and Why Their Culture Has Not Caught Up

重大
2026-11-21 04:58 GMT+8

The article's central argument, attributed to former CIA officer Aaron Brown and cybercrimologist Perry Carpenter, is that the AI industry became a national-security-relevant sector faster than its organizational culture adapted to the resulting threat model. Where honey traps historically targeted politicians, the military, and national intelligence—the people behind clearances and a workforce trained to expect an approach from spies and other attackers—AI companies now hold the secrets that matter: chip roadmaps, export decisions, customer lists, and who gets the technology.

The mechanism Brown describes is straightforward. A spy wants what the CEO can touch. The roadmap, the export decisions, the customer list, who gets the technology. The CEO is the shortest path to all of it. But the attack does not require romance. Friendship is the oldest honest trap scheme, Brown says. Attackers gain access as investors, customers, recruiters, and consultancies. Their requests look legitimate on paper. They do not need targets to fall in love—they need targets to feel comfortable talking.

What makes this newly urgent is the cost curve. Planning a scheme used to take months or years: research, crafting a persona, knowing the target, executing a plan. AI now compresses that timeline dramatically. It can research a target, generate fake social profiles, fabricate backgrounds, even produce fake voice calls. Carpenter notes that AI can help sustain an entire fictional backstory, though the deception ultimately plays out through human relationships.

The practical detection advice is concrete but not reassuring. Carpenter suggests watching for coincidental encounters that happen a little too often, persistent curiosity about work and colleagues, requests for secrecy about meeting up, and pressing for introductions. Brown offers a simpler gut check: would this person still be around if you lost your job tomorrow?

The structural vulnerability is organizational. Carpenter suggests that within companies, it also helps to eliminate executive exceptionalism—the idea that rules do not apply to people in power. Brown adds that company culture determines whether employees feel comfortable raising concerns, challenging unusual requests, and escalating possible threats. Carpenter's observation that one of the most dangerous security cultures is one where nobody feels comfortable questioning the CEO is the article's sharpest point.

The strongest objection to this framing is that it describes a threat landscape without quantifying it. The article provides no evidence of how many AI executives have actually been compromised beyond the single contested Nvidia case. The detection heuristics are generic security awareness advice without empirical validation. And the claim that AI has made honey trapping much easier and cheaper is asserted by practitioners but not measured—no study compares pre-AI and post-AI attack success rates or costs. The argument works as a warning about a structural gap between industry importance and security culture, but it cannot yet establish how large or imminent the problem is.

ソース:TechCrunch

リサーチ

Amazon Textract Insights GA: Verifiable generative AI for document extraction

重大
2026-11-21 04:22 GMT+8

Amazon Web Services announced the general availability of Amazon Textract Insights, a new generative AI feature within its document processing service. The tool allows users to define desired fields in natural language using JSON Schema "blueprints" and submit single or mixed multi-document packets (up to 3,000 pages). Unlike general-purpose large language models, Textract Insights returns structured results where each extracted value carries a confidence score and precise page-level grounding (bounding box), enabling auditable automation without model training.

The service addresses challenges in high-value workflows like mortgage underwriting and insurance claims, where documents arrive as interleaved scans of W-2s, payslips, and handwritten notes. Textract Insights automatically splits these mixed packets, matches sub-documents to appropriate blueprints, and extracts fields. It distinguishes between explicit fields read verbatim and inferred fields derived from content, providing traceability for reviewers. This capability aims to reduce reliance on custom OCR pipelines or ungrounded LLM outputs, which often lack calibrated confidence metrics necessary for automated decision-making.

ソース:Amazon Web Services

リサーチ
次へ →
ログイン / 新規登録
読書リサーチレーダー投資フレームワーク

At Microsoft itself, any employee can build and deploy these agents internally today without a formal IT review, provided the blueprint stays within bounds developed with Microsoft IT. Employees have already built more than 30 blueprints on Foundry. Foster describes two she works with: a personal AI chief of staff that manages her calendar and action items through Exchange delegation permissions, and a team-level workstream manager that collaborates in a Teams group chat, draws on shared context, and manages an Azure DevOps board.

The governance controls are not new systems. These agents are governed with the same tools enterprises already use to manage people: Entra for identity and access, Purview for compliance, and Defender for threat protection. The reusing-what-we-have approach is what lets this scale; extending it for what's different — the kill switch, the shared-blind-spot awareness — is what makes it safe.

The composite metric finding complicates the acceleration narrative. Using an IRT-based capability index (MCI), METR observes no strong acceleration or deceleration across all public frontier models. However, when calibrated separately per developer, they see uncertain slope changes—particularly for Anthropic models, where the slope change at October 2025 is 1.26x to 1.46x depending on calibration choices, comparable to Anthropic's own system card figures. They note that IRT methods may be a lagging indicator: when the most capable models reliably succeed on tasks that distinguish weaker models, there may be few informative comparisons left to estimate the size of their advantage. The report also documents that frontier models still engage in reward hacking, with most detected instances coming from near-frontier agents, and that swarm scaffolds help on verifiable tasks with clear metrics but show unclear or negative effects on tasks requiring agents to create their own feedback loops.

The strongest objection to the report's central argument is that its own methodology may systematically underestimate progress. Human time estimates for most new tasks come from researcher judgment rather than actual baselines—only 9% of time estimates come from direct human baselines. The Lifecycle Cost proxy reflects METR's specific resource constraints, not necessarily how AI developers with larger budgets build RL environments. And the IRT model cannot detect acceleration hidden by task saturation or by developers delaying public releases for safety testing. METR acknowledges all of these, which is why their conclusion remains deliberately bounded: they think current evidence is insufficient to rule out drastic acceleration, not that they have demonstrated it will occur.