<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
 <title>Triadive</title>
 <link>https://triadive.com</link>
 <atom:link href="https://triadive.com/rss.xml" rel="self" type="application/rss+xml" />
 <description>A working field manual for the human / agent / robot triad. Concepts, prompts, plugins, and lessons, written at the level of principles.</description>
 <language>en-us</language>
 <lastBuildDate>Mon, 31 Aug 2026 08:04:45 +0000</lastBuildDate>
  <item>
   <title>Dispatch #5 — The CEO-agent bottleneck: why centralized review is the operator&#x27;s most expensive habit</title>
   <link>https://triadive.com/dispatches/2026-08-29-issue-5-the-ceo-agent-bottleneck/</link>
   <guid isPermaLink="true">https://triadive.com/dispatches/2026-08-29-issue-5-the-ceo-agent-bottleneck/</guid>
   <description>Adding more desks does not make a multi-agent system faster if every desk still reports to the same overloaded coordinator. The CEO-agent bottleneck is the patt</description>
   <pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Work Desks and Specialty Agents: The Architecture Between Sessions and Teams</title>
   <link>https://triadive.com/articles/field-notes/work-desks-and-specialty-agents/</link>
   <guid isPermaLink="true">https://triadive.com/articles/field-notes/work-desks-and-specialty-agents/</guid>
   <description>Sessions, jobs, work desks, and specialty agents are four names for the same primitive — and knowing which one you mean changes how you design, debug, and gover</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>From Prompts to Agents: The Gap You&#x27;re Probably Skipping</title>
   <link>https://triadive.com/articles/concepts/from-prompts-to-agents-the-gap-youre-probably-skipping/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/from-prompts-to-agents-the-gap-youre-probably-skipping/</guid>
   <description>Most people who use LLMs daily are running one-shot or multi-turn prompts — not agents. The difference matters more than it sounds. Here is what actually change</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>From Prompts to Desks: Why One Agent Is Not Enough</title>
   <link>https://triadive.com/articles/concepts/from-prompts-to-desks/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/from-prompts-to-desks/</guid>
   <description>The first time an agent system is set up, it is a single agent in a single session doing everything. That works until it does not. This is the beginner bridge f</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>What Is an LLM?</title>
   <link>https://triadive.com/articles/concepts/what-is-an-llm/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/what-is-an-llm/</guid>
   <description>Large language models are next-token predictors trained on a wide corpus of human-written text. This piece explains what the model actually does, how it is trai</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Setting Up Your First Three Desks</title>
   <link>https://triadive.com/articles/workflows/setting-up-your-first-three-desks/</link>
   <guid isPermaLink="true">https://triadive.com/articles/workflows/setting-up-your-first-three-desks/</guid>
   <description>Three desks cover most small operations: a research desk, an editorial or production desk, and an operations desk. This workflow walks through the setup step by</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Setting Up Your First Three Work Desks: A Practical Starting Point</title>
   <link>https://triadive.com/articles/workflows/setting-up-your-first-three-work-desks/</link>
   <guid isPermaLink="true">https://triadive.com/articles/workflows/setting-up-your-first-three-work-desks/</guid>
   <description>The most common mistake in early agent architecture is building one agent that does everything, then watching it slowly lose coherence under the weight of compe</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Desk Architecture Failure Modes: What Breaks First and How to Fix It</title>
   <link>https://triadive.com/articles/lessons/desk-architecture-failure-modes-what-breaks-first-and-how-to-fix-it/</link>
   <guid isPermaLink="true">https://triadive.com/articles/lessons/desk-architecture-failure-modes-what-breaks-first-and-how-to-fix-it/</guid>
   <description>After running desk-based architectures across dozens of agent systems, the same failure patterns show up in the same order: context bleeds, memory饱和, handoff dr</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Desk Architecture Failure Modes: The Six Ways Operators Get It Wrong</title>
   <link>https://triadive.com/articles/lessons/desk-architecture-failure-modes/</link>
   <guid isPermaLink="true">https://triadive.com/articles/lessons/desk-architecture-failure-modes/</guid>
   <description>Adding desks does not automatically make a system better. It can make it worse — slower, more confused, and harder to debug. This lesson catalogs the six failur</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Job</title>
   <link>https://triadive.com/glossary/job/</link>
   <guid isPermaLink="true">https://triadive.com/glossary/job/</guid>
   <description>A specific assignment given to a work desk: a unit of work with a name, inputs, a deadline, and an expected output. The job is to the desk what a task is to a s</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Specialty Agent</title>
   <link>https://triadive.com/glossary/specialty-agent/</link>
   <guid isPermaLink="true">https://triadive.com/glossary/specialty-agent/</guid>
   <description>A work desk tuned for a narrow function: a specific role, a specific toolset, and a specific scope of work. A specialty agent is a work desk with a defined spec</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Work Desk</title>
   <link>https://triadive.com/glossary/work-desk/</link>
   <guid isPermaLink="true">https://triadive.com/glossary/work-desk/</guid>
   <description>A durable operating context where a named line of work lives: a goal, a role, a memory surface, selected tools, a job queue, and rules for escalation. In a heal</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Workboard</title>
   <link>https://triadive.com/glossary/workboard/</link>
   <guid isPermaLink="true">https://triadive.com/glossary/workboard/</guid>
   <description>A card-based state-tracking system for agent operations. A workboard card holds status, assignee, priority, and an audit trail — the system of record for what i</description>
   <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Dispatch #4 — The vocabulary tax: why naming the primitive is the operator&#x27;s cheapest move</title>
   <link>https://triadive.com/dispatches/2026-08-22-issue-4-the-vocabulary-tax-when-primitives-go-unnamed/</link>
   <guid isPermaLink="true">https://triadive.com/dispatches/2026-08-22-issue-4-the-vocabulary-tax-when-primitives-go-unnamed/</guid>
   <description>When the components of an agent system each use a different word for the same thing, the operator pays the cost in slow debugging, missed audits, and prompts th</description>
   <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Dispatch #3 — Why bounded context wins</title>
   <link>https://triadive.com/dispatches/2026-08-15-issue-3-why-bounded-context-wins/</link>
   <guid isPermaLink="true">https://triadive.com/dispatches/2026-08-15-issue-3-why-bounded-context-wins/</guid>
   <description>The most expensive failure mode in long-running agents is not bad planning, bad tools, or bad models. It is unbounded context — the slow accumulation that makes</description>
   <pubDate>Sat, 15 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Field Note: When the Prompt Cache Saved the Morning</title>
   <link>https://triadive.com/articles/field-notes/field-note-2026-08-09-when-prompt-cache-saved-the-morning/</link>
   <guid isPermaLink="true">https://triadive.com/articles/field-notes/field-note-2026-08-09-when-prompt-cache-saved-the-morning/</guid>
   <description>A small prompt restructure cut our morning cron latency from 4s to 1.1s and dropped the daily cost by 14%. Nothing else changed. A field note on what we learned</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Agents and Robotics: Physical Workflows</title>
   <link>https://triadive.com/articles/concepts/agents-and-robotics/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/agents-and-robotics/</guid>
   <description>A software agent that sends a wrong email is reversible. A robot that drives into a wall is not. This piece covers what changes when the agent&#x27;s actions touch t</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Context Management and System Prompts: How the Operating Manual Gets Assembled</title>
   <link>https://triadive.com/articles/concepts/context-management-and-system-prompts/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/context-management-and-system-prompts/</guid>
   <description>A system prompt is not a single file. It is assembled at runtime from a project file, an agent default, a tool-result injection, and the conversation history. T</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Evaluation, Safety, and Governance for AI Agents</title>
   <link>https://triadive.com/articles/concepts/evaluation-safety-and-governance/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/evaluation-safety-and-governance/</guid>
   <description>Agents fail in ways classical software does not. Eval has to catch open-ended, multi-step, tool-mediated behavior. Safety has to bound runaway loops, prompt inj</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>First Steps: Sessions and Memory</title>
   <link>https://triadive.com/articles/concepts/first-steps-sessions-and-memory/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/first-steps-sessions-and-memory/</guid>
   <description>A session is a single conversation. Memory is what survives between sessions. Together they form the agent&#x27;s lifecycle: each session starts cold, runs hot, and </description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>From Prompts to Agents</title>
   <link>https://triadive.com/articles/concepts/from-prompts-to-agents/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/from-prompts-to-agents/</guid>
   <description>A prompt is a one-shot instruction. An agent is a system that runs prompts over time. The move from one to the other is not a single jump — it is a series of ad</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Future of Agent Architectures</title>
   <link>https://triadive.com/articles/concepts/future-of-agent-architectures/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/future-of-agent-architectures/</guid>
   <description>Today&#x27;s agent architecture is mostly language model plus memory plus tools plus loop. It works and will not be the final form. This piece is a forward-looking m</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Getting Started with Workspaces</title>
   <link>https://triadive.com/articles/concepts/getting-started-with-workspaces/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/getting-started-with-workspaces/</guid>
   <description>A workspace is the file system plus memory plus agent identity that an agent reads when it wakes up. The shape of that workspace determines what the agent can d</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>How Does an Agent Understand?</title>
   <link>https://triadive.com/articles/concepts/how-does-an-agent-understand/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/how-does-an-agent-understand/</guid>
   <description>An agent &#x27;understands&#x27; by routing a query across three places: the current context window, the memory layer, and the model&#x27;s pattern-matching weights. None of t</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Practical Applications: Personal, Team, and Business Agents</title>
   <link>https://triadive.com/articles/concepts/practical-applications/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/practical-applications/</guid>
   <description>Three generations of agent deployments — personal, team, business — differ not in capability but in blast radius, governance, and cost model. This piece is a pr</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Prompting Patterns and Anti-Patterns</title>
   <link>https://triadive.com/articles/concepts/prompting-patterns-and-anti-patterns/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/prompting-patterns-and-anti-patterns/</guid>
   <description>Most agent failures are prompting failures in disguise. The agent did not follow instructions, did not stay on task, did not produce the right output — not beca</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Sandbox and Terminal Safety</title>
   <link>https://triadive.com/articles/concepts/sandbox-and-terminal-safety/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/sandbox-and-terminal-safety/</guid>
   <description>An agent that can run shell commands is an agent that can destroy the file system, leak secrets, or call external APIs in ways the operator did not authorize. T</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>What Is AI?</title>
   <link>https://triadive.com/articles/concepts/what-is-ai/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/what-is-ai/</guid>
   <description>AI is a marketing label that covers several distinct technical generations — rules, classical ML, deep learning, LLMs, agents. The words mean different things a</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>Workspace Organization and Project Hygiene: Files as a Dogfooding Discipline</title>
   <link>https://triadive.com/articles/concepts/workspace-organization-and-project-hygiene/</link>
   <guid isPermaLink="true">https://triadive.com/articles/concepts/workspace-organization-and-project-hygiene/</guid>
   <description>A well-run agent workspace is a small set of explicit files: AGENTS.md, SOUL.md, TOOLS.md, MEMORY.md, and the daily notes. Each file has a job; each file has a </description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
  <item>
   <title>An Agent Eval Workflow</title>
   <link>https://triadive.com/articles/workflows/an-agent-eval-workflow/</link>
   <guid isPermaLink="true">https://triadive.com/articles/workflows/an-agent-eval-workflow/</guid>
   <description>A practical recipe for evaluating an agent system before it ships. Four layers to test, a 30-line harness in prose, what to do when an eval fails, and a minimum</description>
   <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
   <author>Triadive Editorial</author>
  </item>
</channel>
</rss>
