Patterns
RAD patterns show how individual components work together across the full arc of an agent run — from pre-execution disclosure through active monitoring, approval gates, error recovery, and post-run accountability.
What is a pattern?
A RAD component is a building block — a Disclosure Alert, an Approval Gate, an Audit Trail. A RAD pattern is the choreography: which components appear at which moment, in what order, with what conditions, and in response to which system events.
Span the full user journey
Patterns cover complete flows — not single moments. Each one maps a user journey from trigger to resolution.
Encode governance requirements
Each pattern specifies when consent is required, what must be logged, and what cannot be auto-approved.
Reference specific components
Every pattern names which RAD components it requires, with links to the component documentation.
How RAD components combine to cover the full arc of an autonomous agent run — from pre-execution disclosure through active execution, approval gates, and post-run audit.
How RAD error and recovery components combine to handle the distinct failure modes of AI systems — from model errors and agent pauses to confidence failures and scope violations.
The execution arc for a network of agents. Governing principle: trust doesn't transfer automatically. Consent to run the orchestrator is not consent to run every subagent it may spawn.
The failure and accountability layer for multi-agent runs — handling network-level failures, conflicting outputs, and aggregate audit rollup across the full agent network.
How to use patterns
Patterns define the choreography. Components are the instruments. Pick the pattern that matches your scenario, then use the required components to execute it. The pattern tells you when each component should appear and why.
Identify your scenario — what is the agent doing? What could go wrong? Who needs to authorize what?
Choose the pattern family that matches your failure mode or execution arc. Read the governing principle first.
Implement the required components in the order the pattern specifies. Follow the governance requirements — they are not optional.