<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai on Marginalia</title><link>https://icorer.com/icorer_blog/en/categories/ai/</link><description>Recent content in Ai on Marginalia</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 11 Nov 2026 14:12:52 +0800</lastBuildDate><atom:link href="https://icorer.com/icorer_blog/en/categories/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>No Vector Store: a 25.87 MiB SQLite Index Reaches 86.62 Recall@10</title><link>https://icorer.com/icorer_blog/en/posts/ai/sag2-embedding-free-retrieval/</link><pubDate>Wed, 11 Nov 2026 14:12:52 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/sag2-embedding-free-retrieval/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. The semantic call can wait until after the question arrives. Keep words and counts in the index, and MuSiQue R@10 moves from 54.41 to 86.62 on a 2.36-second build with no model calls.
The paper is SAG2: Embedding-Free Multi-Hop Retrieval with BM25 and JEV, by Yuchao Wu at Zleap AI, arXiv 2610.</description></item><item><title>Designing a Coding Agent Without a KV Cache</title><link>https://icorer.com/icorer_blog/en/posts/ai/jev-harness-design/</link><pubDate>Wed, 11 Nov 2026 07:16:58 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/jev-harness-design/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. A design note from September 2026 gathers six coding-agent complaints under one sentence. Suppose a language model had no KV cache. What would these agents look like then. The answer contains no stronger model. It contains one thing, someone deciding what goes in front of the model on every turn.</description></item><item><title>Multi-teacher distillation is a token budget</title><link>https://icorer.com/icorer_blog/en/posts/ai/mopd-token-share/</link><pubDate>Tue, 10 Nov 2026 07:02:51 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/mopd-token-share/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. TRL&amp;rsquo;s multi-teacher on-policy distillation example ran 60 steps. Instruction following held 20 percent of the prompts and got 1 to 3 percent of the trained tokens, and it was the only domain that barely moved. Open-MOPD calls this token budget misallocation, and fixing it raised the recoverable headroom from 35.</description></item><item><title>The Ontology Divide Is Not Model Size</title><link>https://icorer.com/icorer_blog/en/posts/ai/ontology-evolution/</link><pubDate>Mon, 09 Nov 2026 11:08:09 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/ontology-evolution/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. Between December 2025 and November 2026, six papers closed in on one conclusion from three directions. The bottleneck in ontology construction moved from who can write an ontology to who can prove the written thing is right. Every number below goes back to a named section or table.
Two minutes twenty-three, voiced in English, captions burned in and switchable in the player.</description></item><item><title>Evals: Four Numbers That Tell You Whether an AI System Actually Works</title><link>https://icorer.com/icorer_blog/en/posts/ai/evals-honest-numbers/</link><pubDate>Mon, 09 Nov 2026 07:36:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/evals-honest-numbers/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. An eval spends most of its budget on reading outputs and labelling cases. Code is the cheap part. This piece splits the work into four parts and gives each part a number you can recompute.
The film runs one minute forty-four, voiced in English, with the captions burned in and switchable in the player.</description></item><item><title>Retrieval as Navigation: DecisionRAG Asks a Tree Instead of Scoring a Corpus</title><link>https://icorer.com/icorer_blog/en/posts/ai/decisionrag-retriever-free/</link><pubDate>Sun, 08 Nov 2026 12:06:43 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/decisionrag-retriever-free/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. The bottleneck in retrieval is not the size of the candidate pool. It is what you let the model see, and in which order. DecisionRAG replaces scoring with asking, and returns a 65.4 top-1 hit over 2.68M passages in 1.7 seconds. It also loses three cells, plainly.
English voiceover, 3 minutes 12 seconds.</description></item><item><title>One Graph, Fifteen Spellings, a 28-Point Difference</title><link>https://icorer.com/icorer_blog/en/posts/ai/graph-serialization-15-formats/</link><pubDate>Sun, 08 Nov 2026 12:01:41 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/graph-serialization-15-formats/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line. How a graph is spelled into a prompt is a measurable system parameter. It is worth 1.3 to 3.9 points on ontology extraction and 28.4 points on structural reasoning, and the three reasoning tiers of a single model family each prefer a different format, with the most accurate tier burning the fewest tokens.</description></item><item><title>Project EVE: What Happens When Agents Enter an Economy That Already Has One</title><link>https://icorer.com/icorer_blog/en/posts/ai/agent-economy-project-eve/</link><pubDate>Sat, 07 Nov 2026 11:25:06 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/agent-economy-project-eve/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: this is not a review of &amp;ldquo;AI playing a game&amp;rdquo;. It is the first experiment that splits an agent economy into three billable layers — execution, tooling capital, and the cost of trust — and quotes a price for each: four months of model progress buys 3× the return; swapping the author of a scaffold moves a fleet from losing ships daily to zero losses in twelve hours; and a saboteur who is told to sabotage is almost never caught.</description></item><item><title>The four-layer memory stack, and the dreaming loop beside it: reading Anthropic's memory research</title><link>https://icorer.com/icorer_blog/en/posts/ai/agent-memory-stack/</link><pubDate>Fri, 06 Nov 2026 22:12:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/agent-memory-stack/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: memory is not a transcript you keep, it is cargo moved between four layers — the low ones are true and hard to use, the top one is easy and easy to get wrong. Dreaming is the worker that moves it while nobody is watching.
Note on figures: the diagrams here are redrawn from the article&amp;rsquo;s own data and structure; its fifteen-odd figures and screenshots are at the source linked at the end.</description></item><item><title>The Database Got a New User: Record Stores and Context Layers for Agents</title><link>https://icorer.com/icorer_blog/en/posts/ai/agent-native-database/</link><pubDate>Fri, 06 Nov 2026 11:30:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/agent-native-database/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: the database&amp;rsquo;s main user stopped being a person, so it grew a second leg — one that holds state and provisions on demand, one that supplies context and compiles it ahead of the query. What really changed is the definition of retrieval: from a recall algorithm to an orchestration frame plus a compiled supply.</description></item><item><title>Seven layers between the model and the result: reading the guide against its own evidence</title><link>https://icorer.com/icorer_blog/en/posts/ai/seven-layers-agent/</link><pubDate>Fri, 06 Nov 2026 09:22:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/seven-layers-agent/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. Abstract. Most production agent failures do not happen in the model layer. Split the distance from model to result into seven layers — model, instructions and context, tools, memory, loop, evals and guardrails, human signature — and the most common reflex (swap the model, rewrite the prompt) acts on the one layer least likely to be broken.</description></item><item><title>How one prompt grew into a company brain: Recall in four generations</title><link>https://icorer.com/icorer_blog/en/posts/ai/recall-company-brain/</link><pubDate>Thu, 05 Nov 2026 22:42:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/recall-company-brain/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: it turns &amp;ldquo;remembering&amp;rdquo; into a retrieval contract — the source is stored upstream and never edited, the index and sandbox are rebuildable projections, and the server owns recall while precision and citation go back to the frontier model that asked.
Source material: the author&amp;rsquo;s long post, plus the open skill repository (the engine is not open source; the skills are, MIT, 13 of them).</description></item><item><title>Reading DSec section by section: what a 3-million-sandbox-a-day platform says about agent training</title><link>https://icorer.com/icorer_blog/en/posts/ai/deepseek-dsec-sandbox-platform/</link><pubDate>Thu, 05 Nov 2026 15:28:40 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/deepseek-dsec-sandbox-platform/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: the contribution is not another sandbox runtime. It is a measurement of what agent-training sandboxes actually look like — requests arrive in tens of thousands, CPU usage sits at 5% of what was requested, state lives for minutes to hours, and images are barely reused. Once all four hold, the platform cannot be a container runtime; it has to be an elastic execution platform.</description></item><item><title>Open Responses: one contract instead of N×M adapters</title><link>https://icorer.com/icorer_blog/en/posts/ai/open-responses/</link><pubDate>Thu, 05 Nov 2026 08:22:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/open-responses/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: it swaps &amp;ldquo;messages&amp;rdquo; for bidirectional items, swaps token streaming for state-machine events, and gives extensions a namespaced side channel — so the endpoint and model name become configuration, and the cost moves from adapters to the semantics of individual fields.
Read from three places: the specification itself (both the 2026-01-15 and 2026-04-24 versions), its TypeSpec schema and repository, and the docs of two live implementations at Databricks and Vercel.</description></item><item><title>A chat box is not an agent OS: five places a 30-person company breaks it</title><link>https://icorer.com/icorer_blog/en/posts/ai/ankole-agent-os/</link><pubDate>Wed, 04 Nov 2026 21:32:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/ankole-agent-os/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: a chat box on a single-user harness moves the interface and nothing else. The difference is five things — who is speaking, what it remembers, what survives the process, which machine it acts on, and whether the reply arrived.
First, the material boundary. The article&amp;rsquo;s body is behind an X login; what I could read is its own claim plus the opening paragraph.</description></item><item><title>Automatic Ontology Engineering: Reading NVIDIA's Auto-Ontology at the Source</title><link>https://icorer.com/icorer_blog/en/posts/ai/auto-ontology/</link><pubDate>Wed, 04 Nov 2026 20:41:07 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/auto-ontology/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: Auto-Ontology automates the most expensive month of ontology engineering — it reads your metadata and query history, compiles a business ontology, and hands it to agents through nine read-only tools. What it hands over is a draft: in this codebase, certification is a badge rendered for display, not a gate on the query path.</description></item><item><title>One person as a creative team: what transfers from Dan Koe's letter</title><link>https://icorer.com/icorer_blog/en/posts/ai/one-person-creative-team/</link><pubDate>Wed, 04 Nov 2026 07:20:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/one-person-creative-team/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: the part worth carrying away is the job split. It cuts the creative director role into brand strategy, content strategy, and writing plus ops. The price tags, the product plugs and the growth numbers belong to the sales side of the letter.
Dan Koe published a long letter in November arguing that the most lucrative skill has always been capturing attention.</description></item><item><title>Cognitive surrender: hand off the work, not the judgement</title><link>https://icorer.com/icorer_blog/en/posts/ai/cognitive-surrender/</link><pubDate>Wed, 04 Nov 2026 06:54:07 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/cognitive-surrender/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: handing over the work is fine. Handing over the judgement is a different act, and the slope between the two is quiet.
English narration, 2 min 41 s. The Chinese cut runs 2 min 33 s with the same scenes and the same numbers.
Addy Osmani published a long piece on X in November about keeping critical thinking while working with agents.</description></item><item><title>Think Before You Act: How JevAct Gates LLM Agent Actions</title><link>https://icorer.com/icorer_blog/en/posts/ai/jevact-decision-gate/</link><pubDate>Tue, 03 Nov 2026 12:27:14 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/jevact-decision-gate/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 This English page stays available at its own URL. The Chinese version is the one maintained first. English readers land here directly. To pin English after switching languages, use ?lang=en on this URL, e.g. this link. An agent&amp;rsquo;s action should pass through a gate that can check, compute, and send back before anything executes. JevAct splits that gate in two. code settles what tool records decide, a decision model answers only &amp;ldquo;what did the conversation actually say&amp;rdquo;, and a boolean rule combines them.</description></item><item><title>Super-agent: DeepSeek Takes Sessions Away From the User</title><link>https://icorer.com/icorer_blog/en/posts/ai/super-agent-design/</link><pubDate>Mon, 02 Nov 2026 06:30:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/super-agent-design/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: the interesting claim in DeepSeek Harness&amp;rsquo;s architecture note is not its five modules — modules change with deployment. It is one sentence: sessions should be an implementation detail of the system, not a mental burden on its user. Everything below is that sentence, taken seriously.
Published 2026-10-31, the note opens by telling you what it is not: an architecture discussion, not a description of shipping features.</description></item><item><title>A Decentralized, Trusted MCP Runtime: Architecture and Implementation</title><link>https://icorer.com/icorer_blog/en/posts/ai/trusted-mcp-runtime-architecture/</link><pubDate>Sun, 01 Nov 2026 12:00:00 +0800</pubDate><guid>https://icorer.com/icorer_blog/en/posts/ai/trusted-mcp-runtime-architecture/</guid><description>中文版是这篇文章的默认版本。 阅读中文版 → This English page stays available at this URL; the Chinese version is the one we maintain first. In one line: treat a tool as a content-addressed artifact, run it inside a sandbox, and keep an identity behind it — only then does &amp;ldquo;trusted&amp;rdquo; mean anything. That is the architecture; the second half of this article is the implementation.
1. The problem: an agent&amp;rsquo;s tools are black boxes# An agent&amp;rsquo;s capability is not bounded by its model.</description></item></channel></rss>