019 blueprints
Engineering
Bounded engineering workflows that turn operational and code evidence into reviewable action packets.
View all Engineering patterns →new · implementation patterns, not idea lists
The production agent blueprint library.
108 bounded workflows for teams putting agents next to real systems. Every blueprint names its evidence, topology, scoped authority, human decision, acceptance test, failure containment, and measurable outcome.
108
workflow contracts
12
operating teams
1
human gate in every flow
Published by a2a cloudVersioned against product contracts
01
A bounded job
One trigger, named inputs, inspectable outputs.
02
Scoped authority
Read and propose first; never ambient access.
03
A human decision
Consequential writes stop at an accountable owner.
04
Signed run facts
Receipt fields match the SDK contract, not marketing lore.
choose the operating owner
Start where expensive human judgment meets repetitive evidence work.
Each team collection contains nine distinct, searchable workflows. The team hub gives you the common operating model; each detail page supplies the implementation contract.
029 blueprints
Security
Evidence-first security workflows that stop at a reviewed recommendation before containment or access changes.
View all Security patterns →039 blueprints
IT
Service-management blueprints that prepare bounded resolutions while keeping access and device changes human-approved.
View all IT patterns →049 blueprints
Finance
Evidence-linked finance workflows that prepare reconciliations and proposals without posting or moving money autonomously.
View all Finance patterns →059 blueprints
Sales & Revenue Operations
Research and deal-support workflows that produce evidence-linked drafts while leaving customer commitments to accountable sellers.
View all Sales & Revenue Operations patterns →069 blueprints
Customer Support & Success
Customer workflows that draft and synthesize from approved evidence while keeping refunds, commitments, and outreach human-controlled.
View all Customer Support & Success patterns →079 blueprints
Marketing
Source-backed marketing workflows that generate reviewable drafts without publishing claims or contacting people autonomously.
View all Marketing patterns →089 blueprints
Legal
Legal-operations blueprints that extract and compare evidence while reserving advice, negotiation, and legal decisions for counsel.
View all Legal patterns →099 blueprints
Compliance & Audit
Control workflows that preserve source references and human attestation while organizing evidence and exceptions.
View all Compliance & Audit patterns →109 blueprints
Procurement
Sourcing and purchasing workflows that compare approved evidence and prepare decisions without selecting suppliers or committing spend autonomously.
View all Procurement patterns →119 blueprints
People Operations
Administrative people workflows that organize consented evidence and drafts while prohibiting autonomous employment decisions.
View all People Operations patterns →129 blueprints
Data & Analytics
Data workflows that make definitions, lineage, evidence, and uncertainty explicit before a human approves changes or conclusions.
View all Data & Analytics patterns →methodology
Useful at the URL even if search did not exist.
The library is deliberately structured to avoid generic, scaled landing copy. A page earns its place only when it specifies a different operational job and enough detail to plan a pilot.
Distinct operational intent
Every workflow has a unique trigger, evidence set, output packet, review owner, quality bar, failure condition, and KPI. Team names are not swapped into one generic template.
Executable boundaries
Each page includes a private deterministic-DAG manifest, a role topology, path-level workspace scopes, a scoped tool grant, and an explicit point where the agent must stop.
Product-truth contract
Receipt copy follows the a2a_pack ExecutionReceipt schema. It does not call receipts hash-chained, does not put platform economics inside the signed token, and does not promise automatic deterministic re-execution.
Human accountability
Every pattern is read/propose by default. The named owner approves publication, payment, access, production changes, or any other consequential side effect.
primary product references
from pattern to pilot
Choose a workflow whose success a skeptical reviewer can inspect.
Attach real but bounded evidence, define the acceptance test, keep external writes human-gated, and compare the result against the current process before expanding scope.