Agents and workflows
Use this page when the main problem is routing, controller loops, tool execution, memory boundaries, or orchestration.
When to use agents and workflows
- Use this page when the work spans more than one prompt or one assistant reply.
- Use it when the system includes an orchestrator, controller loop, retrieval step, memory layer, external tools, or multi-step review path.
- Use it when you need to review trust boundaries, authority transfer, policy enforcement, or workflow routing.
Before you start
- Know which component owns routing, tool calls, memory, retrieval, and final output.
- Know which data sources and tools the workflow can access.
- Know whether the issue is architecture, policy enforcement, request assembly, or runtime behavior.
Core workflows
- Manage LLM memory boundaries Use this when memory or persistent context can affect workflow behavior.
- Run the architecture boundary review Use this when boundaries, ownership, dependencies, or architecture direction need review.
- Run the standards-backed implementation review Use this when the workflow must be checked against official documentation.
- Audit trust-boundary checkpoints Use this to start from ingress, retrieval, tools, write paths, and egress checkpoints.
Platform setup
Configure this topic in your AI tool
Use the platform mapping when this topic becomes a reusable workflow, project setup, assistant configuration, prompt file, knowledge source, or API/system instruction.
ChatGPT
Projects, GPTs, Skills, files/sources, Custom Instructions, Memory, and runtime prompts.
Open mapping →
Claude
Projects, Project Instructions, Project Knowledge, Skills, Claude Code surfaces, and runtime chat input.
Open mapping →
Gemini
Gems, Gem instructions, Knowledge files, Memory, Connected Apps, AI Studio, Gemini API, Files API, File Search, and Vertex AI.
Open mapping →
API / internal systems
System/developer instructions, retrieval, tools, orchestration, approvals, validation, evals, logging, and application state.
Open mapping →