$ recall --all
12 terms in memory
Recall
These are my agentic engineering terms: the vocabulary I use when writing about building and running AI agents. Each word here has a specific meaning on this blog, and each links back to the post where it first showed up.
When a post uses one of these terms for the first time, it links here. Read the short definition, and follow it back to the post if you want the full story.
recall("dispatch")
One launch, whole crowd: a brief per agent, everything sent out in a single motion.
↳ coined in: The Brief Is an API
recall("ecosystem law")
A rule that, once ratified, every project in the fleet inherits automatically. Fix it once, everywhere, forever.
↳ coined in: Standards Need a Home: Building the Engineering Bay
recall("fleet")
The named agents that head my domains: identities, long memories, standing responsibilities. Not the temporary workers.
↳ coined in: Closing the Loop, One Step at a Time
recall("identity")
Who a call is from, carried all the way to the system that acts on it. Not who the agent is: who is asking.
↳ coined in: The Gateway That Forgot Who Was Calling
recall("knowledge debt")
The human version of technical debt: skip the understanding now, pay with interest when you come back.
↳ coined in: Closing the Loop, One Step at a Time
recall("manifest")
A small file written before launch: which agents went out, where each one writes, what came back.
↳ coined in: When Failure Stops Looking Like Failure
recall("MCP")
The protocol that lets an agent call outside tools: one standard socket instead of a custom plug for every pair.
↳ coined in: The Gateway That Forgot Who Was Calling
recall("operator")
The human seat above the whole system. Owns the two boundaries: the contract going in, the doubt coming out.
↳ coined in: The Brief Is an API
recall("orchestrator")
The model that runs the fleet: writes the briefs, fans the work out, reconciles what returns.
↳ coined in: The Brief Is an API
recall("Spec")
The document that briefs the builder: what to build, the evaluations, the verifications, and what done has to clear.
↳ coined in: Tool Showcase: The Research CLI
recall("swarm")
Several agents on slices of one question, blind to each other, each writing its own file. Gone when the work is done.
↳ coined in: One Agent, Many Questions
recall("write budget")
The turns an agent must hold back from research to actually write its findings down.
↳ coined in: The Brief Is an API