Section Front

The Articles

Every Triadive essay, explainer, workflow review, lesson, glossary entry, and dispatch — organized so you can read what you actually need, not whatever happens to be newest. Field Notes are flagship essays. Concept Briefs are explainers. Workflow Reviews are patterns. Lessons are reflections. Glossary entries are the working vocabulary. Dispatches are the weekly newsletter.

Field Notes

Flagship essays — single-topic deep dives into how the human / agent / robot triad actually works in practice. Each piece aims for the longest useful life: principles first, examples second, hand-waving third. Read these when you want the conceptual foundation before the next workflow or lesson, or when you need a single, durable take on a topic that the rest of the manual keeps returning to.

Concept Briefs

Short explainers on loops, graphs, memory, prompting, and the core vocabulary of agentic systems. Each piece stands alone — pick the topic you need right now and read it without preparing. Use these to fill vocabulary gaps, not to learn a full system. Concepts are written to be reread, not learned once.

See all concepts →

Workflow Reviews

Pattern reviews: what a given workflow is good for, where it breaks, and how to improve it. Each piece documents a real workflow as it runs in practice, with the failure modes surfaced and the cost in operator time made explicit. Read these when you have a workflow problem to solve, or when a workflow you already run has started failing and you need to know why.

  • Setting Up Your First Three Desks

    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 step — writing charters, carving the workspace, defining the job queue, and proving the system works before adding a fourth desk.

    WORKFLOWS intermediate 2026-08-26

  • Setting Up Your First Three Work Desks: A Practical Starting Point

    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 competing contexts. The fix is not more prompts. It is a small desk architecture. Here is how to set it up in practice.

    WORKFLOWS intermediate 2026-08-26

  • An Agent Eval Workflow

    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-viable eval you can stand up in an afternoon. Built for operators, not researchers.

    WORKFLOWS intermediate 2026-08-09

  • Simple Workflows for Beginners

    A workflow is a procedure the agent runs on a schedule, on demand, or in response to an event. The simplest workflows are the most reliable. This piece covers what a workflow is, the three trigger shapes, the minimum viable workflow, and the patterns that hold up as you grow.

    WORKFLOWS beginner 2026-08-09

  • Using Agents to Manage Asset Libraries for 3D Work

    Asset libraries fail when organization depends on the artist's discipline. An agent can tag, index, and surface assets without ever importing one — and that is exactly the value.

    WORKFLOWS intermediate 2026-08-07

  • Blender + OpenClaw: Agents in the 3D Pipeline

    Blender is a creative engine with a Python API. Agents should sit beside it, not inside it — automating render queues, writing bpy scripts for human review, and packaging assets the human then refines.

    WORKFLOWS intermediate 2026-08-07

  • Crons + Skills + Loops + Lobsters + Workboard: How the Pieces Compose

    A cron fires a payload. The payload is an agent turn. The agent turn runs skills, walks loops, drives lobsters, advances workboard cards. The composition is the design — and the design is what most operators skip.

    WORKFLOWS intermediate 2026-08-07

  • Effective Cron Design: Idempotency, Pacing, Retries, and Condition Triggers

    An effective cron is one you can run twice without breaking anything. The disciplines are idempotency, pacing, retries, condition triggers, and observability. Each one is cheap to add; each one is expensive to skip.

    WORKFLOWS advanced 2026-08-07

  • Graph-Driven Pipelines: Blender, Game Engines, and Printers

    When Blender hands off to a game engine, a 3D printer, or another tool, the handoff has shape. State graphs are how you make that shape explicit, debuggable, and recoverable.

    WORKFLOWS advanced 2026-08-07

  • Long-Context Agents: Designing Workflows That Survive a Million Tokens

    Long context changes what an agent can hold in mind, but it does not remove the need for good memory, good chunking, or good governance. This is the working set of patterns for designing workflows that use long context well — and the failure modes that arrive when long context is used as a substitute for design.

    WORKFLOWS advanced 2026-08-07

  • Designing Safe Render Loops for Blender

    A render queue should be a loop that respects budgets, fails honestly, and never modifies the source scene. The discipline is in the bound — not in the cleverness of the agent.

    WORKFLOWS advanced 2026-08-07

  • State Graphs in Practice: Beyond Loops and Pipelines

    Loops are how an agent makes progress. State graphs are how an operator builds a workflow that survives being long, branched, and shared with other agents. This article is about the move from loop-shaped systems to graph-shaped systems — what the new shape buys you, what it costs, and how to keep the graph from collapsing into spaghetti.

    WORKFLOWS advanced 2026-08-07

  • Workflow Review: The Daily Check-in Loop

    A small loop that runs once a day to surface what changed overnight, what is overdue, and what is at risk. Less work than you think, more leverage than you expect.

    WORKFLOWS intermediate 2026-07-29

  • Workflow Review: The Daily Triage Routine

    A triage routine is the cheapest reliable habit a long-running agent can have. It doesn't replace careful work; it just makes sure the careful work happens to the right thing. The pattern is small enough to ship in a day.

    WORKFLOWS beginner 2026-07-29

  • Three rules for picking the first plugin you actually keep

    Most operators install too many plugins too early. Three filters separate the ones that earn their place from the ones that get uninstalled by week two.

    PLUGINS intermediate 2026-07-29

See all workflows →

Lessons Learned

Anonymized, pattern-based reflections from running long-lived agents and tool chains. These are not how-tos. They are the postmortems: what went wrong, what the operator did about it, and what to keep in your back pocket for the next time it happens. Read these when you want to avoid a mistake someone else already paid for — or when you want to know which mistakes are inevitable and which are avoidable.

  • Desk Architecture Failure Modes: What Breaks First and How to Fix It

    After running desk-based architectures across dozens of agent systems, the same failure patterns show up in the same order: context bleeds, memory饱和, handoff drops, and authority drift. Here is what each one looks like in practice, why it happens, and how to detect it before it causes real damage.

    LESSONS intermediate 2026-08-26

  • Desk Architecture Failure Modes: The Six Ways Operators Get It Wrong

    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 failure modes operators hit when they move from one generalist agent to a desk-based architecture, with the diagnostic signals and the fix for each.

    LESSONS intermediate 2026-08-26

  • Where AI Helps Blender, and Where It Should Stop

    AI helps with the tedious parts of 3D — base meshes, texture cleanup, denoising, rig auto-weighting. It does not help with the parts that need judgment. The line between is worth drawing clearly.

    LESSONS intermediate 2026-08-07

  • Lessons Learned: Memory Design Mistakes in Early Agent Work

    Three memory mistakes show up in nearly every first attempt at long-running agents: writing too much, writing too little, and writing in the wrong place. Each looks like a different kind of failure, but the underlying cause is the same — the agent is writing notes without writing knowledge. The fixes are architectural, not behavioral.

    LESSONS intermediate 2026-07-29

  • Lessons Learned: Why Agents Stall Without Clear Termination

    Termination is the most under-engineered part of the agent loop. Most agents stop on the wrong signal — or no signal at all — because the operator treated stop conditions as something the model would figure out. This piece walks through the four failure modes, the four parts of a testable stop condition, and the concrete patterns that make termination reliable.

    LESSONS intermediate 2026-07-29

  • Lessons Learned: Why Context Explodes Without Bounding

    The most common silent failure in long-running agents is unbounded context growth. The runtime decides to keep accumulating context without bound, and the model — responding to the unbounded transcript — eventually degrades. The fix is at the runtime layer: cap tool result sizes, cap retry counts, summarize resolved turns, and offload old context to long-term memory at intervals.

    LESSONS intermediate 2026-07-29

See all lessons →

Glossary

The vocabulary of agentic systems — concise definitions of the terms that show up in every Triadive article. Each entry stands alone and is referenced from concept, workflow, and lesson pieces. Read these once, then refer back as needed. The glossary is a working reference, not a sequential read. Start with the foundational primitives — loop, graph, memory, session — and branch out from there.

Job Specialty Agent Work Desk Workboard Compaction Embedding HITL (Human-in-the-Loop) MCP (Model Context Protocol) Observability Agent Loop Agentic RAG Algorithm Context vs. Memory Cron vs. Heartbeat Cron Graph-Based Memory Memory Sandbox Session Skill State Graph Tool

See all glossary terms →

Dispatches

Weekly editorial newsletter published every Saturday morning. Each issue is a 1,800–2,500 word pattern essay + short recap + one observation. The dispatches are how the manual itself stays current: the week's new pieces, the operator-decision pattern, and one observation on what changed. Subscribe via RSS or read in the browser; new issues land here every Saturday at 11:00 ET.

See all dispatches →