<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>The Voyager · Deep Dives</title><description>Deep Dives: one topic a day, explained properly.</description><link>https://thevoyager.dev/</link><item><title>🚀 A trillion-parameter open model lands. Your eval set decides whether it&apos;s yours to use</title><link>https://thevoyager.dev/deep-dives/models-agentic/2026-11-02/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/models-agentic/2026-11-02/</guid><description>Mistral Large 4&apos;s open weights (1T total, about 52B active, 1M context) arrive with mostly self-reported benchmarks; the week&apos;s building block is the eval set, calibrated judge and trace that turn those claims into a go/no-go.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>models-agentic</category><category>evals</category><category>llm-judge</category><category>observability</category><category>opentelemetry</category><category>mistral</category><category>open-weights</category></item><item><title>🧪 Lab, Step 1 (part 4): pull one piece out of a small GPT and see what you lose</title><link>https://thevoyager.dev/deep-dives/lab/2026-11-01/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/lab/2026-11-01/</guid><description>Part 4 of Step 1: ablate a tiny GPT one component at a time, measure the damage against a seed-noise baseline, and learn which pieces are load-bearing and which are decoration at this size.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate><category>lab</category><category>lab</category><category>transformers</category><category>nanogpt</category><category>ablation</category><category>research-ladder</category></item><item><title>🛠️ Build: a retrieval harness that tells you what each choice is worth, or a contract-aware chunker</title><link>https://thevoyager.dev/deep-dives/build/2026-10-31/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/build/2026-10-31/</guid><description>Two three-hour builds from this week&apos;s retrieval theme: a harness that scores chunking, context lines and fusion on a labelled set (runnable, numpy only), or a clause-aware chunker for contracts.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><category>build</category><category>build</category><category>rag</category><category>retrieval</category><category>chunking</category><category>hybrid-search</category><category>evals</category><category>python</category></item><item><title>💻 claude-mem: retrieval for an agent&apos;s own memory, in three calls that each cost less than the last</title><link>https://thevoyager.dev/deep-dives/github/2026-10-30/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/github/2026-10-30/</guid><description>thedotmack/claude-mem stores what a coding agent did, then serves it back through search, timeline and get_observations; the interesting part is the retrieval contract and its size caps, which you can copy for any RAG system.</description><pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate><category>github</category><category>rag</category><category>agents</category><category>memory</category><category>retrieval</category><category>progressive-disclosure</category><category>tooling</category></item><item><title>🎯 Principal/Staff Architect, project deep-dive: your retrieval stopped improving. Walk the panel through why</title><link>https://thevoyager.dev/deep-dives/interview/2026-10-29/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/interview/2026-10-29/</guid><description>A practice project deep-dive in the style of a Meta Principal/Staff Architect loop: a RAG system you owned has plateaued, so how do you separate retrieval misses from insufficient context, and why can better recall make answers worse?</description><pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate><category>interview</category><category>interview</category><category>rag</category><category>retrieval</category><category>evals</category><category>abstention</category><category>meta</category><category>project-deep-dive</category></item><item><title>🏗️ A knowledge assistant over policies and contracts: the retrieval design a professional-services firm can defend</title><link>https://thevoyager.dev/deep-dives/system/2026-10-28/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/system/2026-10-28/</guid><description>An end-to-end design for a policy and contract assistant at a professional-services firm: metadata-first retrieval, hybrid search with a reranker, per-document access control, and the numbers and threats that decide whether it ships.</description><pubDate>Wed, 28 Oct 2026 00:00:00 GMT</pubDate><category>system</category><category>rag</category><category>retrieval</category><category>hybrid-search</category><category>metadata-filtering</category><category>access-control</category><category>contracts</category><category>system-design</category></item><item><title>🔬 Three RAG upgrades that should add 47% added 17%: a 450-configuration study of what composes</title><link>https://thevoyager.dev/deep-dives/research/2026-10-27/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/research/2026-10-27/</guid><description>A 21 October paper stacks RAG techniques that each help alone: the top three retrieval gains predicted +46.6% NDCG@10 and delivered +17.2%, and the best pipeline changed as the corpus grew from 5K to 200K documents.</description><pubDate>Tue, 27 Oct 2026 00:00:00 GMT</pubDate><category>research</category><category>rag</category><category>retrieval</category><category>reranking</category><category>evals</category><category>ablations</category><category>scaling</category></item><item><title>🚀 Your citations code may 400 this week. Plus: how to design retrieval you can defend</title><link>https://thevoyager.dev/deep-dives/models-agentic/2026-10-26/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/models-agentic/2026-10-26/</guid><description>Anthropic&apos;s 2026-10-21 API version rejects citations on user-message text blocks, which hits RAG code that replays retrieved chunks; and the retrieval stack worth defending is hybrid search, contextual chunks and a reranker, measured on your own labelled set.</description><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><category>models-agentic</category><category>rag</category><category>retrieval</category><category>hybrid-search</category><category>reranking</category><category>chunking</category><category>claude-api</category></item><item><title>🧪 Lab, Step 1 (part 3): scale your tiny GPT without fooling yourself</title><link>https://thevoyager.dev/deep-dives/lab/2026-10-25/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/lab/2026-10-25/</guid><description>Part 3 of Step 1: swap characters for a BPE tokeniser, grow the model in steps, and read loss against compute using the Chinchilla and Kaplan scaling papers as the yardstick.</description><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><category>lab</category><category>lab</category><category>transformers</category><category>nanogpt</category><category>scaling-laws</category><category>bpe</category><category>research-ladder</category></item><item><title>🛠️ Build: a tool gateway that says no, or a skill router you can measure</title><link>https://thevoyager.dev/deep-dives/build/2026-10-24/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/build/2026-10-24/</guid><description>Two three-hour builds from this week&apos;s ideas: a small MCP-style gateway with per-identity tool listing, deny-by-default calls and an audit log, or a skill-preselection harness that measures how routing recall falls as the catalogue grows.</description><pubDate>Sat, 24 Oct 2026 00:00:00 GMT</pubDate><category>build</category><category>build</category><category>mcp</category><category>tool-gateway</category><category>skill-routing</category><category>authorization</category><category>python</category></item><item><title>💻 context-mode: keep tool output out of the context window, and make the model&apos;s memory survive compaction</title><link>https://thevoyager.dev/deep-dives/github/2026-10-23/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/github/2026-10-23/</guid><description>mksglu/context-mode sits between an agent and its noisy tools: hooks reroute big outputs into a sandbox and a SQLite FTS5 index, so only an answer reaches the context window; the design is worth studying even if you never install it.</description><pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate><category>github</category><category>agents</category><category>mcp</category><category>context-engineering</category><category>tooling</category><category>retrieval</category><category>sqlite</category></item><item><title>🎯 Senior AI/ML Engineer, customer scenario: 140 tools, one agent, and a customer asking for more autonomy</title><link>https://thevoyager.dev/deep-dives/interview/2026-10-22/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/interview/2026-10-22/</guid><description>A practice question in the style of an Anthropic Senior AI/ML Engineer loop: a customer&apos;s agent has 140 tools across five MCP servers and is getting worse as it grows. Do you add autonomy, or take some away?</description><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><category>interview</category><category>interview</category><category>agents</category><category>mcp</category><category>tool-search</category><category>workflows-vs-agents</category><category>anthropic</category><category>customer-scenario</category></item><item><title>🏗️ One MCP URL for a hundred engineers: what a tool gateway actually buys you</title><link>https://thevoyager.dev/deep-dives/system/2026-10-21/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/system/2026-10-21/</guid><description>How Eon replaced ten local MCP servers per developer with one authenticated gateway, and the three design choices that decide whether that pattern holds up: identity, policy and tool listing.</description><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><category>system</category><category>mcp</category><category>gateway</category><category>agent-identity</category><category>cedar</category><category>bedrock-agentcore</category><category>system-design</category></item><item><title>🔬 Skill routing collapse: your agent has 1,000 skills installed and loads half of nothing</title><link>https://thevoyager.dev/deep-dives/research/2026-10-20/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/research/2026-10-20/</guid><description>A 13 October paper shows that with 1,000 irrelevant skills installed, agents&apos; recall of the skills they should load falls from 73.6% to 27.4%, and explicit preselection fixes much of it.</description><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><category>research</category><category>agents</category><category>skills</category><category>context-engineering</category><category>routing</category><category>evals</category><category>tool-selection</category></item><item><title>🚀 The agent that writes its own workflow: when the plan becomes a program</title><link>https://thevoyager.dev/deep-dives/models-agentic/2026-10-19/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/models-agentic/2026-10-19/</guid><description>Managed Agents can now let the model write a program that fans out up to 1,000 agents, which blurs the workflow-vs-agent line and moves the interesting design question to who approves the plan.</description><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><category>models-agentic</category><category>agents</category><category>workflows</category><category>orchestration</category><category>managed-agents</category><category>multi-agent</category><category>claude-api</category></item><item><title>🧪 Lab, Step 1 (part 2): the training loop is where small GPTs quietly go wrong</title><link>https://thevoyager.dev/deep-dives/lab/2026-10-18/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/lab/2026-10-18/</guid><description>Part 2 of Step 1: read nanoGPT&apos;s train.py line by line, then rebuild its warmup, cosine decay, weight-decay groups, gradient clipping and eval loop around your own tiny GPT, and break each one on purpose.</description><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><category>lab</category><category>lab</category><category>transformers</category><category>nanogpt</category><category>training-loop</category><category>adamw</category><category>research-ladder</category></item><item><title>🛠️ Build: a fork lab that counts your agent&apos;s rescues and harms, or a session log that survives zombie workers</title><link>https://thevoyager.dev/deep-dives/build/2026-10-17/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/build/2026-10-17/</guid><description>Two three-hour builds from this week&apos;s ideas: a paired-counterfactual harness that sorts every recovery step into rescue, harm or unchanged, or an offset-addressed session log with idempotent producers and epoch fencing.</description><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><category>build</category><category>build</category><category>agent-evals</category><category>counterfactuals</category><category>durable-execution</category><category>event-log</category><category>python</category></item><item><title>💻 Durable Streams: the agent session as an HTTP log you can resume from any offset</title><link>https://thevoyager.dev/deep-dives/github/2026-10-16/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/github/2026-10-16/</guid><description>durable-streams/durable-streams is a small HTTP protocol for append-only, offset-addressed streams; the interesting design choice is treating the agent&apos;s token and tool-event stream as a resumable log instead of a socket.</description><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><category>github</category><category>agents</category><category>streaming</category><category>protocols</category><category>durability</category><category>http</category><category>infrastructure</category></item><item><title>🎯 Forward Deployed Engineer, LLM system design: one customer, three latency budgets, one bill</title><link>https://thevoyager.dev/deep-dives/interview/2026-10-15/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/interview/2026-10-15/</guid><description>A practice question in the style of an OpenAI Forward Deployed Engineer loop: design the inference tiers, cache layout and eval gate for a customer with live, near-live and bulk workloads.</description><pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate><category>interview</category><category>interview</category><category>system-design</category><category>forward-deployed-engineer</category><category>openai</category><category>cost-latency</category><category>prompt-caching</category><category>evals</category></item><item><title>🏗️ An agent that survives a deploy: durable execution, and the history limit nobody mentions</title><link>https://thevoyager.dev/deep-dives/system/2026-10-14/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/system/2026-10-14/</guid><description>Why long-running agents fit workflow engines like Temporal, where the model call belongs, and the event-history ceiling that shapes how you design the loop.</description><pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate><category>system</category><category>agents</category><category>durable-execution</category><category>temporal</category><category>reliability</category><category>system-design</category><category>openai-agents-sdk</category></item><item><title>🔬 Your agent&apos;s recovery step helps some runs and wrecks others. A paper shows how to measure that</title><link>https://thevoyager.dev/deep-dives/research/2026-10-13/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/research/2026-10-13/</guid><description>A 30 September paper treats agent error recovery as a per-run causal decision: fork from the same state with and without a refresh, count rescues and harms, and route recovery only where it pays.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate><category>research</category><category>agents</category><category>evals</category><category>harness</category><category>error-recovery</category><category>causal-inference</category><category>reliability</category></item><item><title>🚀 The newest models won&apos;t let you force a tool call. Here&apos;s what your agent loop does instead</title><link>https://thevoyager.dev/deep-dives/models-agentic/2026-10-12/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/models-agentic/2026-10-12/</guid><description>Opus 5.5 and Sonnet 5.5 return a 400 on tool_choice any/tool; the replacement is auto plus strict tool use, which changes how you design the agent loop&apos;s guarantees.</description><pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate><category>models-agentic</category><category>agents</category><category>tool-use</category><category>agent-loop</category><category>structured-outputs</category><category>claude-api</category><category>reliability</category></item><item><title>🧪 Lab, Step 1 (part 1): build a GPT you can read in one sitting</title><link>https://thevoyager.dev/deep-dives/lab/2026-10-11/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/lab/2026-10-11/</guid><description>Step 1 of a public research ladder: grow a character-level GPT from a bigram table to a small transformer, watching the loss at each rung, with nanoGPT as the reference.</description><pubDate>Sun, 11 Oct 2026 00:00:00 GMT</pubDate><category>lab</category><category>lab</category><category>transformers</category><category>nanogpt</category><category>attention</category><category>from-scratch</category><category>research-ladder</category></item><item><title>🛠️ Build: a prefix-aware context broker, or a task runner that can pause mid-thought</title><link>https://thevoyager.dev/deep-dives/build/2026-10-10/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/build/2026-10-10/</guid><description>Two three-hour builds that turn this week&apos;s ideas (cache-aware routing, query-time context selection, suspendable agent tasks) into small Python systems you can run without a GPU.</description><pubDate>Sat, 10 Oct 2026 00:00:00 GMT</pubDate><category>build</category><category>build</category><category>kv-cache</category><category>routing</category><category>context-engineering</category><category>durable-execution</category><category>python</category></item><item><title>💻 Google&apos;s AX: Kubernetes-style YAML for agents, with Redis where etcd would choke</title><link>https://thevoyager.dev/deep-dives/github/2026-10-09/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/github/2026-10-09/</guid><description>google/ax declares agent tasks, workspaces and models as manifests and runs them in sandboxes with suspend/resume; the interesting part is the decision to keep short-lived tasks out of etcd.</description><pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate><category>github</category><category>agents</category><category>runtime</category><category>kubernetes</category><category>durable-execution</category><category>sandboxing</category><category>google</category></item><item><title>🎯 Interview, AI/Solution Architect (Google-style): design an enterprise assistant for 50,000 employees</title><link>https://thevoyager.dev/deep-dives/interview/2026-10-08/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/interview/2026-10-08/</guid><description>A system design round for an AI/Solution Architect role: an internal knowledge assistant on Google Cloud, with a framework, a model answer, and the trade-offs interviewers actually probe.</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate><category>interview</category><category>interview</category><category>system-design</category><category>rag</category><category>enterprise</category><category>solution-architect</category><category>google-cloud</category></item><item><title>🏗️ Your load balancer is quietly deleting your prefix cache</title><link>https://thevoyager.dev/deep-dives/system/2026-10-07/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/system/2026-10-07/</guid><description>Round-robin across vLLM replicas turns one warm prefix cache into eight cold ones; llm-d&apos;s precise prefix-cache routing is a good case study in fixing that, and in what its benchmark does and doesn&apos;t prove.</description><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><category>system</category><category>inference</category><category>kv-cache</category><category>routing</category><category>llm-d</category><category>kubernetes</category><category>cost-latency</category></item><item><title>🔬 ReCAP: compacting agent memory from attention you already paid for</title><link>https://thevoyager.dev/deep-dives/research/2026-10-06/</link><guid isPermaLink="true">https://thevoyager.dev/deep-dives/research/2026-10-06/</guid><description>A 30 September paper keeps the attention an agent computes anyway as a tiny graph, then picks context for the next request with no model call, cutting compaction latency by about 95% against Codex-style summarization.</description><pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate><category>research</category><category>agents</category><category>context-engineering</category><category>memory</category><category>kv-cache</category><category>attention</category><category>coding-agents</category></item></channel></rss>