Arc 08 · Staff AI Engineer
Agentic Systems, Tools, and Protocols
Treat agents as bounded distributed workflows with typed tools, explicit state, permissions, recovery, and human authority.
Exit capability: Ship a tool-using workflow whose actions are bounded, observable, and recoverable.
- Mapped lessons
- 7
- Published now
- 1
- Full-arc estimate
- ≈18 hours
- Last edited
- 2026-08-11
Lesson sequence
Live units open into complete labs. Planned units stay visible to show the dependency path, but intentionally have no detail route.
- 01
Tools Are Typed Authority Boundaries
PlannedDesign tool names, schemas, errors, idempotency, and authorization for safe model use.
Build labAdvanced105 min estimate
- 02
A Tool-Using Agent Is a Bounded State Machine
LiveImplement budgets, typed transitions, approval gates, idempotency, and terminal states around a probabilistic planner.
Build labAdvanced135 min estimateArtifact: Tested bounded agent runtime
- 03
State, Memory, and Context Are Different Things
PlannedSeparate durable workflow state, retrievable memory, and model-visible context.
Concept labAdvanced95 min estimate
- 04
MCP Host, Client, and Server Boundaries
PlannedImplement protocol capabilities without delegating consent, authorization, or validation to the model.
Systems labAdvanced115 min estimate
- 05
Durable Agent Workflows
PlannedSurvive retries, restarts, partial tool success, human pauses, and changing external state.
Systems labAdvanced120 min estimate
- 06
When Multiple Agents Are Actually Justified
PlannedUse ownership, isolation, parallelism, and context constraints—not personas—to decide decomposition.
Design reviewAdvanced100 min estimate
- 07
Agent Red-Team: Untrusted Instructions Meet Real Tools
PlannedTest prompt injection, confused deputy behavior, data exfiltration, and excessive agency.
Failure labAdvanced120 min estimateArtifact: Agent threat model