ReadingResearchRadarInvestment framework
Sign in / Sign up
AllTechnologyProductsInvestingPublic marketsOther

Reading

2026-11-2011 posts

Refresh

Google Launches Tool Retrieval in Gemini API to Optimize Large-Scale Agent Performance

Material
2026-11-20 02:00 GMT+8

On November 19, 2026, Google announced the preview launch of "Tool Retrieval" within the Interactions API of the Gemini API. This update aims to address the context bloat problem faced by AI agents when connecting to dozens or even hundreds of tools. In traditional setups, developers must send the full parameter schema for every tool in each request, which inflates input token counts, adds latency, and lowers tool-selection accuracy as the candidate list grows.

By enabling Tool Retrieval, an agent can keep its full tool library on standby and load parameter schemas only when the current task requires them. Developers simply add a tool_search tool to their request and set defer_loading: true for the tools they wish to hold back. The model still sees the name and description of every deferred tool, so it knows what is available, but the detailed parameter definitions stay out of the initial context window. When the model decides to use a tool, the API loads its full schema within the same request cycle, allowing the model to emit the function call normally.

This mechanism requires no index building or hosting from the developer; the search runs server-side on Gemini's infrastructure. For teams maintaining their own tool registries or permission filters, Google also offers a client-side retrieval mode where the application executes the search logic, though this adds one round trip per search. Additionally, Tool Retrieval is compatible with remote MCP (Model Context Protocol) servers, allowing entire servers' toolsets to be deferred at once.

Regarding pricing, Tool Retrieval incurs no separate charge; input and output tokens are billed at standard rates. While enabling tool_search adds a small fixed block of input tokens, and loaded schemas continue to be billed for the rest of the conversation, the savings from never loading unused schemas typically outweigh these costs for large libraries. The feature currently supports Gemini 3.6 and later models, including all Gemini 4 series models.

Sources:Google

Research

Candid Health's US Medical Billing Platform: What a 59% Resolution Rate Means When AI Voice Agents Must Diagnose and Prescribe in a Single Call

Material
2026-11-19 20:00 GMT+8

Candid Health, a medical billing platform in the United States, has deployed AI voice agents within its revenue cycle management workflow to call insurance companies and investigate the reasons for claim denials. In its initial deployment, these agents handled 12,860 calls, resolving 59% of them. At first glance, the fact that more than 40% of calls failed to resolve the issue might not seem impressive. However, Doug Proctor, Candid Health’s Chief Operating Officer, explains why they consider 59% a meaningful result: the key lies in the definition of 'resolution.'

Candid Health stipulates that a call is only considered 'resolved' if it accomplishes two things simultaneously: uncovering the reason for the denial and identifying the next step to fix it. Proctor stated that they deliberately set a high bar because 'getting part of the answer doesn’t really help our billers.' Billers need complete action information—knowing why a claim was denied and knowing what to do next—to free up their time for more complex work. If an agent only identifies the cause but fails to determine the solution, the biller still needs to make another call themselves, resulting in limited time savings.

This definition directly alters the meaning of the numbers. Under a loose definition—for example, counting a call as 'processed' merely if the agent connected and obtained partial information—the same system might report figures of 80% or higher. Under Candid Health’s strict definition, 59% means that in over half of the calls, the AI agent independently completed the full chain of information gathering from diagnosis to solution, without requiring biller intervention. Proctor noted that 'getting both of these from a single insurance company call is difficult even for an experienced biller.'

The transferable value of this case lies in the fact that whenever any AI voice agent vendor or client reports resolution rates, completion rates, or automation rates, the first question to ask is not about the number itself, but the task definition behind it. Does 'resolution' mean connecting the call, obtaining partial information, or completing an end-to-end workflow? Percentages under different definitions cannot be directly compared. Candid Health’s example demonstrates a conscious choice: preferring to report a lower number to ensure that the figure corresponds to a complete, operationally valuable result.

It is important to note that the 59% figure comes from Candid Health’s self-reporting, published by ElevenLabs as a customer case study. The article does not provide independent audit or scoring rule verification, so readers cannot confirm whether every call was strictly judged according to the described dual criteria. Furthermore, Candid Health’s agents are designed to investigate denials rather than appeal them, which means the scope of 'resolution' has boundaries—it does not include the initiation or execution of subsequent appeals processes.

Candid Health also revealed a notable side effect: some investigation calls uncovered upstream issues. During one investigation, an agent discovered that a healthcare provider was not credentialed with the payer on the date of service. Fixing such upstream problems can prevent tens, if not hundreds, of future denials for that customer. This indicates that voice agents operating under strict completion standards offer value beyond saving call time; they also feed structural problems discovered during investigations back into the upstream process.

Sources:ElevenLabs

Research

US Senate Majority Leader John Thune Forecasts Debt Ceiling Delay to Late 2027, Forcing Trump-Democrat Negotiations

Material
2026-11-20 07:30 GMT+8

US Senate Majority Leader John Thune (R-S.D.) predicted in an interview with Semafor that the US debt ceiling issue will likely be "punted" into next year. Citing potential extra steps by the Treasury Department, Thune forecasted a final deadline in the second half of 2027.

This timeline implies that President Donald Trump will have to negotiate with a Democratic-controlled House and Senate on the debt ceiling for the first time since taking office. Thune noted that Republicans currently lack the votes to raise the debt ceiling along party lines in either chamber. While budget reconciliation could theoretically address the debt limit, Thune deemed it unlikely this year, stating that any such bill would focus on defense funding rather than avoiding default.

For investors, this forecast shifts the window for debt ceiling political maneuvering to late 2027 and defines its resolution path as dependent on bipartisan negotiation. This increases uncertainty around future fiscal policy, as divergent spending priorities between the parties may intensify during talks.

Sources:semafor.com

Research

AWS upgrades Amazon Bedrock AgentCore harness with Strands defaults and lifecycle hooks

Material
2026-11-20 04:01 GMT+8

Amazon Web Services (AWS) announced on November 19, 2026, that it has upgraded the Amazon Bedrock AgentCore harness to run on the open-source Strands harness. This change brings a set of recommended defaults, including automatic prompt caching, proactive context management, and new built-in tools for planning, web retrieval, and task delegation. The upgrade also introduces lifecycle hooks, allowing developers to insert deterministic code checks at specific points in the agent loop to govern actions.

The integration of Strands provides a production-grade default agent experience without requiring developers to assemble or operate the underlying infrastructure. Key capabilities include a current recommended model, task-oriented system prompts, and context offloading to reduce token usage. AWS states that these optimizations help the harness run at about 34% lower token cost compared to other leading harnesses, based on their internal tests.

Lifecycle hooks enable developers to apply custom logic before or after tool calls and invocations. For example, a Lambda function can allow or deny a request, such as checking a refund against an approval limit before the action executes. This mechanism transforms non-deterministic AI behavior into predictable workflows by enforcing business rules at defined checkpoints.

Sources:Amazon Web Services

Research

Bipartisan US Senators Introduce Bill Requiring Public Companies to Disclose AI Information

Material
2026-11-20 05:04 GMT+8

According to Semafor, a bipartisan group of four US senators introduced legislation on Thursday requiring publicly traded companies to disclose more information about artificial intelligence. This move comes as Anthropic's initial public offering (IPO) heightens Washington's scrutiny of the tech sector.

Rep. Pramila Jayapal criticized the situation, stating that Wall Street should not profit from companies that could turn out to be "ticking time bombs," arguing that going public cements a broken business model. Sen. Elizabeth Warren also called for quick congressional action on safeguards for advanced AI development.

Sources:semafor.com

Research

Ben Carlson: Stocks Outperform Bonds in 85% of Historical Decade Windows, but High Probability Does Not Equal Certainty

Material
2026-11-19 23:48 GMT+8

A reader asked Ben Carlson a question on stage at the Bogleheads conference: Which will have better returns over the next decade, stocks or bonds? The subtext of the question was that the U.S. stock market has risen for almost 18 years; surely mean reversion is due, right?

Carlson, a portfolio manager at Ritholtz Wealth Management, did not answer directly with a yes or no. Instead, he pulled up rolling ten-year return data for the S&P 500 and five-year U.S. Treasuries dating back to 1926. The results showed that stocks outperformed bonds in most decade windows, but not 100% of the time.

He approached the quantification of this issue from another angle: using the current government bond yield of approximately 5% as a benchmark line, stocks have historically exceeded this level in 85% of all ten-year time frames. If you hold a broad-based stock index fund for ten years, there is an 85% probability that your annualized return will exceed the coupon income of Treasury bonds during the same period.

But frequency is only half the story. Carlson further compared the magnitude of difference in performance when each asset class wins: when stocks outperform bonds, the margin of victory is far greater than when bonds outperform stocks. This means that even if you occasionally pick the wrong side, your losses are relatively limited; whereas when you pick the right side, the gains are significantly higher.

Based on this asymmetry, Carlson’s conclusion is that if he had to place a bet in Las Vegas on who would win over the next decade, he would pick stocks every time because the odds are in his favor. However, he simultaneously emphasized that high probability does not equal certainty. That 15% of failure periods were not pleasant for investors. He cited a metaphor from Bill Bernstein at the conference: holding the market for the long term makes you the house because the odds are in your favor; but even the house loses sometimes.

Carlson did not frame this issue as an either/or choice. He pointed out clearly that the good news is you do not need to bet on one or the other. Holding bonds is not suitable for everyone, but fixed income can provide a cushion when you lose a hand or two. Although the current 5% yield level does not guarantee that bonds will definitely earn 5%, the starting yield is a good approximation of future returns—meaning that even if interest rates continue to rise, once the dust settles, expected returns could actually be higher. His advice is essentially: take on stock risk when probabilities are favorable, while using bonds to provide a margin of safety when truly needed.

Sources:A Wealth of Common Sense

Research

Google Selects Blue Origin's New Glenn for First Heavy-Lift Project Suncatcher Launch, Targeting Q1 2029

Material
2026-11-19 21:00 GMT+8

Google Research has announced a partnership with Blue Origin, selecting its New Glenn heavy-lift rocket for the first major launch of the "Project Suncatcher" initiative. The project aims to scale artificial intelligence infrastructure in space by leveraging abundant solar power available in orbit.

According to the official Google blog post, the launch is targeted for the first quarter of 2029. Blue Origin's New Glenn rocket will deploy Google's satellites into sun-synchronous orbit. Each satellite is designed to have roughly the capacity of a ground-based data center rack.

This dedicated launch builds upon Google's ongoing work with other satellite and launch partners and represents a crucial milestone on its long-term roadmap, marking a shift from early prototype testing toward scalable orbital computing capabilities.

Sources:Google

Research

European Court of Human Rights bans lawyer for two years over AI hallucinations

Material
2026-11-20 00:37 GMT+8

According to German tech outlet heise online, the European Court of Human Rights (ECtHR) in Strasbourg, France, has barred a Romanian lawyer from representing clients before the court for two years. The chamber found that she submitted legal briefs containing AI-generated "hallucinations," including fictitious precedents and fabricated paragraphs from real judgments.

The judges noted that while the lawyer admitted to "sloppiness" and "citation errors," this understated the issue. They stated that no verification was performed on the cited cases, which could have been identified as inventions by a superficial check of the court's database. Some cited judgments were unrelated to the legal questions or even contradicted her own arguments. The court emphasized that reviewing these false citations and proceeding against the lawyer diverted significant time from judicial work, impairing the administration of justice.

A court spokesperson confirmed to heise online that under Rule 44D, 25 lawyers had been excluded from proceedings in the past decade, but this is the first time sanctions were imposed specifically for AI hallucinations. The President of the Court confirmed the ban on November 13, 2026.

This ruling comes as the court reassesses its internal AI policies. Its 2025 annual report limits AI use to accelerating administrative and organizational procedures. The spokesperson indicated that new guidelines regarding the use of AI by persons appearing in proceedings are being drafted and will be published soon.

Sources:heise online

Research

Weaviate Agent Experience Engineer Joon-Pil Hwang: Coding Agents Encounter Silent Failures Invisible to Humans When Reading Documentation

Material
2026-11-19 08:00 GMT+8

When coding agents read technical documentation on behalf of humans, a class of failures emerges that human readers never encounter. Joon-Pil Hwang, Lead Developer and Agent Experience Engineer at Weaviate, describes this problem: pages are truncated, code examples are missing for certain languages, and sections are lost—and the agent will not tell you about it. It quietly searches elsewhere or writes incorrect code based on incomplete context.

Hwang points out that the root cause of these issues lies in the fact that agents read web pages in a completely different way than humans using browsers. Fetch tools in different coding environments return different parts of a page and often do not notify the site that content is missing. More critically, even if an agent notices that information is incomplete, it is unlikely to report the problem to document maintainers—it simply works around it. This means documentation defects can persist unnoticed because the affected class of readers rarely provides feedback.

To discover what agents actually see, the Hwang team did not adopt traditional user interviews but instead directly observed agent behavior. They set up multiple agents to execute the same task in a repeatable manner, then examined their logs and outputs—not just the final answers, but the paths they took to reach those answers: which tools were used, which searches were run, and which pages were read.

This allowed them to identify specific failure modes. Before modifying the documentation, one fetch tool returned the correct language example in only 7 of 15 TypeScript runs and 3 of 15 Go runs. After the modification, every run returned the correct code snippet. They also found that an outdated sentence on a concepts page caused agents to use an older client library, even though the code examples were not on that page—after correcting it, every answer they checked used the current client.

Another finding was that when useful content is missing, agents attempt to bypass the issue by searching for raw source files or downloading the page and writing a parser. In one example, when the required code was hidden, the agent took 23 turns to find a solution; with the Markdown version of the page, it took only 6 turns. The team subsequently released Markdown versions of the documentation pages, reducing token usage for page loads by approximately 20%.

These tests also helped them detect regressions. A change that fixed hidden code tabs caused one fetch tool to return only part of the Quickstart while discarding the rest. Re-running the tests exposed the problem, which was resolved with a small layout adjustment.

From this, Hwang proposes a core judgment: agents should be treated as a distinct class of reader. The goal of developer experience has never been simply to make writing code faster, but to reduce friction between developers and value creation. When agents intervene between developers and products, good experience must serve both: for developers, it means helping them make sound architectural decisions, communicate intent to agents, and verify results; for agents, it means ensuring information is complete and discoverable, providing agent-appropriate tools, reducing ambiguity, and making correctness observable.

Sources:weaviate.io

Research

LoRA: Low-Rank Adaptation of Large Language Models

Verified 2026-11-20 00:01 GMT+8

Long-term reading · 《LoRA: Low-Rank Adaptation of Large Language Models》(2021)

In the field of natural language processing, adapting large pre-trained models to specific tasks typically relies on full fine-tuning. However, as model parameter scales reach hundreds of billions (e.g., GPT-3), storing and deploying independent fine-tuned copies for each downstream task becomes extremely costly and difficult to maintain. Microsoft Research proposed LoRA (Low-Rank Adaptation) to address this efficiency bottleneck.

The core assumption of LoRA is that weight changes during adaptation to new tasks exhibit an "intrinsic low-rank" property. This method freezes the original weights of the pre-trained model and injects trainable low-rank decomposition matrices at every layer of the Transformer architecture. By optimizing only these small incremental matrices rather than all parameters, LoRA significantly reduces the number of trainable parameters. Experiments show that compared to full fine-tuning of GPT-3 175B using Adam optimization, LoRA can reduce trainable parameters by a factor of 10,000, lower GPU memory requirements by threefold, while maintaining model quality on RoBERTa, DeBERTa, GPT-2, and GPT-3 equal to or better than full fine-tuning.

Compared to other parameter-efficient methods, LoRA avoids the inference latency introduced by adapters. Adapters insert modules by increasing network depth, which leads to significant computational overhead in online inference scenarios. In contrast, LoRA employs a simple linear design that allows trainable matrices to be merged with frozen weights during deployment, achieving efficient adaptation without increasing inference latency. Additionally, LoRA is orthogonal to many existing methods and can be combined with techniques such as prefix tuning.

For engineers and researchers seeking to customize large language models but constrained by computational resources, LoRA provides a practical solution balancing efficiency and performance. It is recommended to start with Section 4 of the paper regarding the description of low-rank parameterized update matrices to understand the mathematical principles, followed by referring to the code implementation in the appendix for practice. This work was published by Edward Hu et al. in 2021 under the title "LoRA: Low-Rank Adaptation of Large Language Models".

Sources:《LoRA: Low-Rank Adaptation of Large Language Models》(2021)

Research

Buffett's 2018 Letter to Shareholders: Why Investors Should Ignore Accounting Noise and Focus on Operating Earnings

Verified 2026-11-20 00:01 GMT+8

Long-term reading · 《Berkshire Hathaway Shareholder Letter 2018》(2018)

In the 2018 letter to shareholders, Warren Buffett, Chairman of Berkshire Hathaway Inc., presented his core views on how investors should evaluate corporate value: they should exclude short-term profit fluctuations driven by changes in accounting standards and concentrate on the company's true operational capabilities. This philosophy is critical for understanding long-term value investing.

First, Buffett noted that new Generally Accepted Accounting Principles (GAAP) require unrealized capital gains or losses on stock portfolios to be included in current earnings, resulting in "wild and erratic swings" in the "bottom line." He wrote in the letter: "We have always believed that mark-to-market changes in Berkshire produce what I call 'wild and erratic swings' in the 'bottom line.'" These fluctuations do not stem from deterioration or improvement in the underlying businesses but are immediate reflections of market sentiment on asset valuations. Therefore, he advised readers: "Focus on operating earnings; pay almost no attention to various types of gains and losses." This means that when evaluating a business, one should filter out market noise and assess whether its core operations generate stable and growing cash flow.

Second, based on this logic, Buffett announced the abandonment of "book value per share" as the primary metric for measuring the company's progress. He argued that this metric has lost relevance because Berkshire has transitioned from a company primarily holding tradable stocks to a conglomerate whose main value lies in operating enterprises. He explained in the letter: "In fact, the annual change in Berkshire’s book value—last appearing on page 2—is a measure that has lost the relevance it once had." As the company's structure evolved, book value could no longer accurately reflect the true intrinsic value of numerous non-listed subsidiaries, whereas operating earnings more directly demonstrate management's capital allocation efficiency.

Finally, Buffett attributed part of Berkshire’s success to "The American Tailwind." He emphasized that the prosperity of the U.S. economy was a result of bipartisan efforts; despite inflation, wars, and financial crises, productivity gains driven by savings and investment served as long-term drivers. He stated: "Remember how I described retained earnings as key to Berkshire’s prosperity earlier in this letter? The same applies to America." This reminder urges investors to consider whether the macro-institutional environment supporting their chosen high-quality companies fosters long-term wealth accumulation.

Consider a modern investor facing a tech giant whose stock price has plummeted due to fair value adjustments in quarterly earnings reports. Following the principles outlined in this letter, the investor would not panic-sell but would instead verify whether the company’s core revenue streams and user retention remain healthy. If the operating fundamentals are solid, temporary accounting losses are merely reflections of market volatility rather than destruction of value. This mindset helps investors navigate economic cycles without being distracted by noise.

Sources:《Berkshire Hathaway Shareholder Letter 2018》(2018)

Research

Unstructured

  • We parsed GTA 6 before it came out 🎮↗

    Video · 2026-11-19

Luma AI

  • How to Make AI Videos With Consistent Characters (Step by step)↗

    Video · 2026-11-19

Aswath Damodaran / YouTube

  • The Value of Human Frailty: Nvidia faces a Jensen Test!↗

    Video · 2026-11-19

Anthropic

  • Why we built Anthropic↗

    Video · 2026-11-19

Morgan Stanley

  • From AI to air conditioners: Asia's power boom↗

    Video · 2026-11-19

  • Why the bond market remains calm after the Blue Wave↗

    Video · 2026-11-19

PolyAI

  • Poly AI: Could the Next CEO Come From the Contact Center?↗

    Video · 2026-11-19

NVIDIA

  • AI is more than a better way to search.↗

    Video · 2026-11-19

  • Europe’s AI Future With Judith Dada | Pub Conversations↗

    Video · 2026-11-19

Capital Group

  • The North Star of our investment business↗

    Video · 2026-11-19

a16z

  • Build something big.↗

    Video · 2026-11-19

DeepLearningAI

  • Andrew Ng on adding voice to his daughter’s math quiz #deeplearningai #aiagents↗

    Video · 2026-11-19

  • Full Course: AI Coding Workflows From Cloud to Local↗

    Video · 2026-11-19

Google DeepMind

  • Gemini and the path to AGI with Koray Kavukcuoglu↗

    Video · 2026-11-19

Insilico Medicine

  • George Church at ARDD2026: Multiplex testing of de-aging polypharmacy & targeted delivery↗

    Video · 2026-11-19

Fidelity Investments

  • What Could Quantum Computing Mean For Bitcoin? | Fidelity Investments↗

    Video · 2026-11-19

  • How much do I need to retire?↗

    Video · 2026-11-19

Helion

  • Unlocking late time FRC dynamics↗

    Video · 2026-11-19

Nokia

  • AI-RAN: From Proof of Concept to Profit?↗

    Video · 2026-11-19

Cerebras

  • What Would the Ideal LLM Inference Chip Look Like?↗

    Video · 2026-11-19

Glean

  • Behind the Feature: How Glean Memory Works↗

    Video · 2026-11-19

Intercom

  • In Focus: Evals & Releases↗

    Video · 2026-11-19

Dimensional Fund Advisors

  • Will Your Kids Inherit Your Values?↗

    Video · 2026-11-19

Fortinet

  • Fortinet: 4x Leader in the 2026 Westlands IT/OT Navigator Report↗

    Video · 2026-11-19

LangChain

  • Can a Better Model Fix a Broken Agent? Look at the Traces↗

    Video · 2026-11-19

  • LangSmith Tool Gateway: Secure, Governed Tool Use for Agents↗

    Video · 2026-11-19

Descript

  • Remove a video background (without a green screen)↗

    Video · 2026-11-19

財報狗 Podcast

  • 580. [Financial Current Affairs Magnifier] How ARR and Bans Impact AI CapEx↗

    Podcast · 2026-11-19

声动早咖啡

  • Coffee Beans | Coffee shops and pizza places are selling burgers, why is Tastien making pizza instead?↗

    Podcast · 2026-11-19

Voices in AI

  • The AI Forecasting Agenda - By Scott Alexander↗

    Podcast · 2026-11-19

Excess Returns

  • Who Pays for the AI Buildout? Two Bond Investors Take Us Inside the Debt Market↗

    Podcast · 2026-11-19

Macro Voices

  • MacroVoices #559 Ole Hansen: What's Next After The spec Washout in Commodities↗

    Podcast · 2026-11-19

80,000 Hours Podcast

  • Julian Gewirtz on the AI risks that actually scare Beijing↗

    Podcast · 2026-11-19

You’re all caught up in this view

Sign in / Sign up
ReadingResearchRadarInvestment framework

He cites Don Norman's concepts of the "gulf of execution" and "gulf of evaluation" to illustrate this: people need to understand how to act and whether their actions were effective. Agents change the interfaces and mechanisms involved, but these underlying needs remain unchanged. In practice, the Hwang team is applying these principles to Weaviate's tools and workflows—for example, when asked to update a Go service using the v5 client, some agents attempted to call the server's gRPC API directly rather than seeking the updated Go v6 client; they are also measuring agents' ability to build Weaviate applications from scratch, including using current features such as HFresh indexing, Rotational Quantization, and PathSeer filtering.

The core practices have not changed: find where people get stuck, improve the experience, and verify that the improvement is effective. What has changed is the set of users and tools that need to be measured. Developers now work through coding agents as well as IDEs and browsers, and agents rarely tell you when they cannot find or understand something. This makes measurement more important, not less. By testing how agents use documentation and tools before and after changes, we can simultaneously reduce friction for both developers and agents, helping developers derive more value from their work.

The "Berkshire Hathaway Shareholder Letter 2018," written by Warren Buffett and published in 2019, is suitable for investors seeking to deeply understand how to distinguish accounting profits from economic reality and how to assess a company’s long-term competitiveness from a macro perspective. It is recommended to begin with sections discussing GAAP rule changes and their impacts, then gradually expand to discussions on the evolution of valuation metrics.