{
"templates": [
{
"slug": "a-b-testing-workflow",
"title": "A B Testing Workflow",
"description": "This workflow models comparing two versions to see which performs better.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"a",
"b",
"testing",
"patterns"
],
"sourcePath": "patterns/a-b-testing",
"repoPath": "uncategorized/patterns/a-b-testing-workflow"
},
{
"slug": "ab-test-setup-workflow",
"title": "Ab Test Setup Workflow",
"description": "A/B test setup workflow with hypothesis definition, variant creation, traffic allocation, statistical analysis, and winner deployment.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "onboarding",
"secondaryUseCases": [],
"useCases": [
"onboarding"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"ab-testing",
"experimentation",
"split-testing",
"statistical-significance",
"conversion-optimization",
"optimizely"
],
"sourcePath": "business-operations/ab-test-setup",
"repoPath": "onboarding/business-operations/ab-test-setup-workflow"
},
{
"slug": "access-review-workflow",
"title": "Access Review Workflow",
"description": "Quarterly user access review workflow with manager certification, separation of duties validation, remediation tracking, and compliance reporting for audit purposes.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "approval",
"secondaryUseCases": [
"compliance"
],
"useCases": [
"approval",
"compliance"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 3,
"tags": [
"access-review",
"user-access-certification",
"quarterly-review",
"manager-approval",
"compliance",
"sod-violations",
"audit"
],
"sourcePath": "devops/access-review",
"repoPath": "approval/devops/access-review-workflow"
},
{
"slug": "account-deletion-workflow",
"title": "Account Deletion Workflow",
"description": "Account deletion workflow with cancellation reason capture, retention offer, subscription termination, data cleanup, and confirmation email.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "offboarding",
"secondaryUseCases": [
"billing"
],
"useCases": [
"offboarding",
"billing"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"account-deletion",
"user-offboarding",
"data-cleanup",
"subscription-cancel",
"retention-offer",
"exit-survey"
],
"sourcePath": "business-operations/account-deletion",
"repoPath": "offboarding/business-operations/account-deletion-workflow"
},
{
"slug": "api-gateway-workflow",
"title": "Api Gateway Workflow",
"description": "API Gateway pattern with request authentication, rate limiting, request routing to backend services, response aggregation, and error handling.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "handoff",
"secondaryUseCases": [
"security",
"mcp"
],
"useCases": [
"handoff",
"security",
"mcp"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"api-gateway",
"microservices",
"rate-limiting",
"request-routing",
"authentication",
"load-balancing"
],
"sourcePath": "patterns/api-gateway",
"repoPath": "handoff/patterns/api-gateway-workflow"
},
{
"slug": "api-key-rotation-workflow",
"title": "Api Key Rotation Workflow",
"description": "API key rotation workflow with new key generation, dual-key transition period, client notification, old key deprecation, and audit logging.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "security",
"secondaryUseCases": [
"compliance"
],
"useCases": [
"security",
"compliance"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"api-key-rotation",
"security",
"credential-management",
"zero-downtime",
"secrets-manager",
"compliance"
],
"sourcePath": "business-operations/api-key-rotation",
"repoPath": "security/business-operations/api-key-rotation-workflow"
},
{
"slug": "audit-trail-workflow",
"title": "Audit Trail Workflow",
"description": "This workflow models logging all important actions for compliance.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"audit",
"trail",
"patterns",
"decision",
"loop"
],
"sourcePath": "patterns/audit-trail",
"repoPath": "compliance/patterns/audit-trail-workflow"
},
{
"slug": "authentication-flow-workflow",
"title": "Authentication Flow Workflow",
"description": "User authentication workflow with credential validation, MFA challenge, JWT token generation, session creation, and failed attempt tracking.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "security",
"secondaryUseCases": [],
"useCases": [
"security"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"authentication",
"login",
"jwt",
"oauth",
"mfa",
"session-management"
],
"sourcePath": "patterns/authentication-flow",
"repoPath": "security/patterns/authentication-flow-workflow"
},
{
"slug": "authorization-flow-workflow",
"title": "Authorization Flow Workflow",
"description": "This workflow models checking user permissions before actions run.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "approval",
"secondaryUseCases": [
"security"
],
"useCases": [
"approval",
"security"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"authorization",
"flow",
"patterns"
],
"sourcePath": "patterns/authorization-flow",
"repoPath": "approval/patterns/authorization-flow-workflow"
},
{
"slug": "background-check-workflow",
"title": "Background Check Workflow",
"description": "Pre-employment background check workflow with criminal history search, employment verification, education verification, and drug screening coordination.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"background-check",
"pre-employment",
"criminal-history",
"employment-verification",
"education-verification",
"drug-screening"
],
"sourcePath": "hr/background-check",
"repoPath": "uncategorized/hr/background-check-workflow"
},
{
"slug": "backup-restore-workflow",
"title": "Backup Restore Workflow",
"description": "Backup and restore workflow with scheduled backups, offsite replication, retention policy enforcement, restore testing, and RTO/RPO validation.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"backup-restore",
"disaster-recovery",
"rpo-rto",
"snapshot",
"data-protection",
"recovery-testing"
],
"sourcePath": "devops/backup-restore",
"repoPath": "delivery/devops/backup-restore-workflow"
},
{
"slug": "bank-reconciliation-workflow",
"title": "Bank Reconciliation Workflow",
"description": "Bank reconciliation workflow with automated transaction matching, variance reporting, discrepancy research, and journal entry creation for timing differences and bank errors.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 18,
"numLanes": 3,
"tags": [
"bank-reconciliation",
"gl-matching",
"variance-analysis",
"journal-entries",
"auto-matching",
"discrepancy-resolution"
],
"sourcePath": "finance/bank-reconciliation",
"repoPath": "uncategorized/finance/bank-reconciliation-workflow"
},
{
"slug": "batch-processing-workflow",
"title": "Batch Processing Workflow",
"description": "Batch processing pattern with job scheduling, chunk-based processing, checkpoint/restart capability, error handling, and completion reporting.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"batch-processing",
"scheduled-jobs",
"bulk-operations",
"etl",
"chunk-processing",
"job-scheduler"
],
"sourcePath": "patterns/batch-processing",
"repoPath": "uncategorized/patterns/batch-processing-workflow"
},
{
"slug": "billing-dispute-workflow",
"title": "Billing Dispute Workflow",
"description": "Billing dispute workflow with dispute intake, transaction review, fraud analysis, resolution decision, and chargeback response handling.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "approval",
"secondaryUseCases": [
"billing"
],
"useCases": [
"approval",
"billing"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"billing-dispute",
"chargeback",
"refund-request",
"dispute-resolution",
"fraud-review",
"stripe"
],
"sourcePath": "business-operations/billing-dispute",
"repoPath": "approval/business-operations/billing-dispute-workflow"
},
{
"slug": "blue-green-deploy-workflow",
"title": "Blue Green Deploy Workflow",
"description": "Blue-green deployment pattern with parallel environment setup, smoke testing, load balancer traffic switch, and instant rollback capability.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"blue-green-deployment",
"zero-downtime",
"traffic-switching",
"rollback",
"load-balancer",
"release-management"
],
"sourcePath": "patterns/blue-green-deploy",
"repoPath": "delivery/patterns/blue-green-deploy-workflow"
},
{
"slug": "bonus-allocation-workflow",
"title": "Bonus Allocation Workflow",
"description": "Annual bonus allocation workflow with budget pool distribution, performance-based calculation, manager calibration, executive approval, and payroll processing.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"bonus-allocation",
"annual-bonus",
"performance-bonus",
"budget-pool",
"calibration",
"payout"
],
"sourcePath": "hr/bonus-allocation",
"repoPath": "uncategorized/hr/bonus-allocation-workflow"
},
{
"slug": "budget-approval-workflow",
"title": "Budget Approval Workflow",
"description": "Corporate budget approval workflow with tiered approval routing based on amount thresholds (CFO < $100K, CEO $100K-$1M, Board > $1M), prior year comparison, and fund allocation.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "approval",
"secondaryUseCases": [],
"useCases": [
"approval"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 3,
"tags": [
"budget-approval",
"financial-planning",
"tiered-approval",
"cfo-approval",
"ceo-approval",
"board-approval",
"fund-allocation"
],
"sourcePath": "finance/budget-approval",
"repoPath": "approval/finance/budget-approval-workflow"
},
{
"slug": "cache-aside-workflow",
"title": "Cache Aside Workflow",
"description": "Cache-aside pattern with cache lookup, database fallback on miss, cache population, TTL-based expiration, and write-through invalidation.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"cache-aside",
"lazy-loading",
"cache-miss",
"cache-invalidation",
"redis",
"performance"
],
"sourcePath": "patterns/cache-aside",
"repoPath": "uncategorized/patterns/cache-aside-workflow"
},
{
"slug": "callback-pattern-workflow",
"title": "Callback Pattern Workflow",
"description": "This workflow models an async operation that notifies a callback when done.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"callback",
"pattern",
"patterns",
"decision",
"loop"
],
"sourcePath": "patterns/callback-pattern",
"repoPath": "uncategorized/patterns/callback-pattern-workflow"
},
{
"slug": "canary-deploy-workflow",
"title": "Canary Deploy Workflow",
"description": "Canary deployment pattern with gradual traffic shifting, real-time metrics monitoring, automatic rollback triggers, and progressive rollout to full production.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "incident",
"secondaryUseCases": [
"delivery"
],
"useCases": [
"incident",
"delivery"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"canary-deployment",
"progressive-rollout",
"traffic-splitting",
"metrics-monitoring",
"gradual-release",
"feature-flags"
],
"sourcePath": "patterns/canary-deploy",
"repoPath": "incident/patterns/canary-deploy-workflow"
},
{
"slug": "candidate-rejection-workflow",
"title": "Candidate Rejection Workflow",
"description": "Candidate rejection workflow with stage-appropriate messaging, personalized rejection letters, talent pool consideration, ATS status update, and candidate experience feedback.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"candidate-rejection",
"hiring-decision",
"rejection-letter",
"talent-pool",
"candidate-experience",
"ats-update"
],
"sourcePath": "hr/candidate-rejection",
"repoPath": "uncategorized/hr/candidate-rejection-workflow"
},
{
"slug": "carrier-selection-workflow",
"title": "Carrier Selection Workflow",
"description": "Carrier selection workflow with rate shopping, transit time comparison, service level matching, carrier performance scoring, and optimal carrier assignment.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"carrier-selection",
"rate-shopping",
"transit-time",
"service-level",
"tms",
"freight-optimization"
],
"sourcePath": "logistics/carrier-selection",
"repoPath": "uncategorized/logistics/carrier-selection-workflow"
},
{
"slug": "cash-flow-forecast-workflow",
"title": "Cash Flow Forecast Workflow",
"description": "Cash flow forecasting workflow with AR/AP projections, working capital analysis, liquidity gap identification, and short-term financing recommendations.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"cash-flow-forecast",
"liquidity-planning",
"working-capital",
"ar-collections",
"ap-disbursements",
"treasury"
],
"sourcePath": "finance/cash-flow-forecast",
"repoPath": "uncategorized/finance/cash-flow-forecast-workflow"
},
{
"slug": "certificate-renewal-workflow",
"title": "Certificate Renewal Workflow",
"description": "SSL/TLS certificate renewal workflow with expiration monitoring, certificate request by type (DV/OV/EV), domain validation, deployment to load balancers, and health check verification with rollback.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "security",
"secondaryUseCases": [],
"useCases": [
"security"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 3,
"tags": [
"ssl-certificate",
"tls-renewal",
"lets-encrypt",
"certificate-authority",
"domain-validation",
"load-balancer",
"health-check"
],
"sourcePath": "devops/certificate-renewal",
"repoPath": "security/devops/certificate-renewal-workflow"
},
{
"slug": "chaos-engineering-workflow",
"title": "Chaos Engineering Workflow",
"description": "Chaos engineering workflow with hypothesis definition, steady-state monitoring, controlled fault injection, blast radius limitation, and resilience validation.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"chaos-engineering",
"fault-injection",
"resilience-testing",
"game-day",
"blast-radius",
"steady-state"
],
"sourcePath": "devops/chaos-engineering",
"repoPath": "uncategorized/devops/chaos-engineering-workflow"
},
{
"slug": "ci-cd-pipeline-workflow",
"title": "Ci Cd Pipeline Workflow",
"description": "Full CI/CD pipeline with code checkout, linting, unit tests, artifact building, staging deployment, smoke tests, production deployment, and automatic rollback on failure.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 4,
"numNodes": 22,
"numLanes": 3,
"tags": [
"ci-cd",
"continuous-integration",
"continuous-deployment",
"github-actions",
"artifact-registry",
"staging",
"production",
"rollback"
],
"sourcePath": "devops/ci-cd-pipeline",
"repoPath": "delivery/devops/ci-cd-pipeline-workflow"
},
{
"slug": "circuit-breaker-workflow",
"title": "Circuit Breaker Workflow",
"description": "Circuit breaker resilience pattern with closed, open, and half-open states for protecting services from cascading failures with automatic recovery testing.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 3,
"tags": [
"circuit-breaker",
"resilience",
"fault-tolerance",
"microservices",
"hystrix",
"half-open",
"fallback"
],
"sourcePath": "patterns/circuit-breaker",
"repoPath": "mcp/patterns/circuit-breaker-workflow"
},
{
"slug": "claim-check-workflow",
"title": "Claim Check Workflow",
"description": "This workflow models keeping large payloads external and only passing references.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"claim",
"check",
"patterns"
],
"sourcePath": "patterns/claim-check",
"repoPath": "uncategorized/patterns/claim-check-workflow"
},
{
"slug": "cohort-analysis-workflow",
"title": "Cohort Analysis Workflow",
"description": "Cohort analysis workflow with user segmentation by signup date, retention curve calculation, LTV projection, and behavioral pattern identification.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"cohort-analysis",
"retention-analysis",
"user-behavior",
"ltv",
"churn-prediction",
"analytics"
],
"sourcePath": "business-operations/cohort-analysis",
"repoPath": "uncategorized/business-operations/cohort-analysis-workflow"
},
{
"slug": "cold-chain-monitoring-workflow",
"title": "Cold Chain Monitoring Workflow",
"description": "Cold chain monitoring workflow with IoT temperature sensors, real-time alerts, excursion documentation, corrective action triggers, and compliance reporting.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "incident",
"secondaryUseCases": [],
"useCases": [
"incident"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"cold-chain",
"temperature-monitoring",
"iot-sensors",
"excursion-alert",
"pharmaceutical",
"perishables"
],
"sourcePath": "logistics/cold-chain-monitoring",
"repoPath": "incident/logistics/cold-chain-monitoring-workflow"
},
{
"slug": "community-moderation-workflow",
"title": "Community Moderation Workflow",
"description": "Community content moderation workflow with AI auto-flagging, user reports, human review queue, action enforcement, and appeals handling.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"community-moderation",
"content-moderation",
"user-reports",
"trust-safety",
"ai-moderation",
"appeals"
],
"sourcePath": "business-operations/community-moderation",
"repoPath": "uncategorized/business-operations/community-moderation-workflow"
},
{
"slug": "compensation-transaction-workflow",
"title": "Compensation Transaction Workflow",
"description": "This workflow models rolling back work when a later step fails.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"compensation",
"transaction",
"patterns",
"decision",
"loop"
],
"sourcePath": "patterns/compensation-transaction",
"repoPath": "uncategorized/patterns/compensation-transaction-workflow"
},
{
"slug": "conflict-resolution-workflow",
"title": "Conflict Resolution Workflow",
"description": "Workplace conflict resolution workflow with complaint intake, HR investigation, mediation sessions, resolution documentation, and follow-up monitoring.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "billing",
"secondaryUseCases": [],
"useCases": [
"billing"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"conflict-resolution",
"workplace-dispute",
"mediation",
"hr-investigation",
"employee-relations",
"grievance"
],
"sourcePath": "hr/conflict-resolution",
"repoPath": "billing/hr/conflict-resolution-workflow"
},
{
"slug": "consent-management-workflow",
"title": "Consent Management Workflow",
"description": "User consent management workflow with cookie banner, preference center, consent recording, downstream system sync, and audit trail.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"consent-management",
"gdpr",
"cookie-consent",
"privacy-preferences",
"opt-in-opt-out",
"compliance"
],
"sourcePath": "business-operations/consent-management",
"repoPath": "compliance/business-operations/consent-management-workflow"
},
{
"slug": "container-loading-workflow",
"title": "Container Loading Workflow",
"description": "Container loading workflow with load plan optimization, weight distribution, cube utilization maximization, seal application, and bill of lading generation.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"container-loading",
"load-planning",
"weight-distribution",
"cube-utilization",
"seal-verification",
"ocean-freight"
],
"sourcePath": "logistics/container-loading",
"repoPath": "uncategorized/logistics/container-loading-workflow"
},
{
"slug": "content-enricher-workflow",
"title": "Content Enricher Workflow",
"description": "This workflow models adding extra data from other sources.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"content",
"enricher",
"patterns",
"decision"
],
"sourcePath": "patterns/content-enricher",
"repoPath": "uncategorized/patterns/content-enricher-workflow"
},
{
"slug": "cost-center-workflow",
"title": "Cost Center Workflow",
"description": "This workflow models managing cost center budgets.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"cost",
"center",
"finance",
"decision"
],
"sourcePath": "finance/cost-center",
"repoPath": "uncategorized/finance/cost-center-workflow"
},
{
"slug": "cqrs-workflow",
"title": "Cqrs Workflow",
"description": "CQRS (Command Query Responsibility Segregation) pattern with separate command and query paths, domain event publishing, read model synchronization, and DTO transformation.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 19,
"numLanes": 4,
"tags": [
"cqrs",
"command-query-separation",
"event-sourcing",
"read-model",
"write-model",
"domain-events",
"eventual-consistency"
],
"sourcePath": "patterns/cqrs",
"repoPath": "uncategorized/patterns/cqrs-workflow"
},
{
"slug": "credit-control-workflow",
"title": "Credit Control Workflow",
"description": "Customer credit control workflow with credit limit assessment, credit scoring, order hold management, collections escalation, and payment plan negotiation.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"credit-control",
"credit-limit",
"customer-credit",
"credit-scoring",
"collections",
"accounts-receivable"
],
"sourcePath": "finance/credit-control",
"repoPath": "uncategorized/finance/credit-control-workflow"
},
{
"slug": "cross-docking-workflow",
"title": "Cross Docking Workflow",
"description": "Cross-docking workflow with inbound scheduling, sortation by destination, outbound consolidation, and direct transfer without storage for just-in-time delivery.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"cross-docking",
"flow-through",
"dock-scheduling",
"sortation",
"consolidation",
"just-in-time"
],
"sourcePath": "logistics/cross-docking",
"repoPath": "uncategorized/logistics/cross-docking-workflow"
},
{
"slug": "crud-user-browser-server-workflow",
"title": "Crud User Browser Server Workflow",
"description": "This workflow models user creates, reads, updates, and deletes data through a browser and server.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"crud",
"user",
"browser",
"server",
"patterns"
],
"sourcePath": "patterns/crud-user-browser-server",
"repoPath": "uncategorized/patterns/crud-user-browser-server-workflow"
},
{
"slug": "customs-clearance-workflow",
"title": "Customs Clearance Workflow",
"description": "International customs clearance workflow with importer documentation, customs broker HS code classification, duty calculation, customs authority inspection, and clearance certificate issuance.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 19,
"numLanes": 3,
"tags": [
"customs-clearance",
"international-trade",
"customs-broker",
"hs-codes",
"import-export",
"duties-taxes",
"inspection"
],
"sourcePath": "logistics/customs-clearance",
"repoPath": "uncategorized/logistics/customs-clearance-workflow"
},
{
"slug": "cycle-counting-workflow",
"title": "Cycle Counting Workflow",
"description": "Inventory cycle counting workflow with ABC classification, count scheduling, variance investigation, adjustment approval, and inventory accuracy tracking.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"cycle-counting",
"inventory-accuracy",
"abc-analysis",
"variance-investigation",
"perpetual-inventory",
"audit"
],
"sourcePath": "logistics/cycle-counting",
"repoPath": "compliance/logistics/cycle-counting-workflow"
},
{
"slug": "damaged-goods-workflow",
"title": "Damaged Goods Workflow",
"description": "Damaged goods processing workflow with damage documentation, carrier claim filing, disposition decision (salvage/dispose), inventory adjustment, and loss tracking.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"damaged-goods",
"damage-claim",
"inventory-write-off",
"carrier-claim",
"disposition",
"loss-prevention"
],
"sourcePath": "logistics/damaged-goods",
"repoPath": "uncategorized/logistics/damaged-goods-workflow"
},
{
"slug": "data-export-workflow",
"title": "Data Export Workflow",
"description": "User data export workflow with export request, async job processing, data aggregation, secure file generation, and download link delivery.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"data-export",
"data-portability",
"gdpr",
"bulk-export",
"async-job",
"download-link"
],
"sourcePath": "business-operations/data-export",
"repoPath": "compliance/business-operations/data-export-workflow"
},
{
"slug": "database-migration-workflow",
"title": "Database Migration Workflow",
"description": "Database schema migration workflow with CI testing, DBA review and approval, maintenance window scheduling, backup snapshots, migration execution, data integrity verification, and automatic rollback.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "approval",
"secondaryUseCases": [
"delivery"
],
"useCases": [
"approval",
"delivery"
],
"complexity": 4,
"numNodes": 20,
"numLanes": 4,
"tags": [
"database-migration",
"schema-changes",
"flyway",
"liquibase",
"rollback",
"dba-approval",
"maintenance-window"
],
"sourcePath": "devops/database-migration",
"repoPath": "approval/devops/database-migration-workflow"
},
{
"slug": "dead-letter-queue-workflow",
"title": "Dead Letter Queue Workflow",
"description": "Dead letter queue pattern for handling failed messages with retry exhaustion detection, DLQ routing, manual inspection, and reprocessing capability.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"dead-letter-queue",
"dlq",
"message-retry",
"poison-message",
"error-handling",
"message-queue"
],
"sourcePath": "patterns/dead-letter-queue",
"repoPath": "uncategorized/patterns/dead-letter-queue-workflow"
},
{
"slug": "decision-diamond-workflow",
"title": "Decision Diamond Workflow",
"description": "This workflow models an if or then style branch for approval or rejection.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"decision",
"diamond",
"patterns"
],
"sourcePath": "patterns/decision-diamond",
"repoPath": "uncategorized/patterns/decision-diamond-workflow"
},
{
"slug": "delivery-confirmation-workflow",
"title": "Delivery Confirmation Workflow",
"description": "Delivery confirmation workflow with proof of delivery capture, signature collection, photo documentation, order status update, and customer notification.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"delivery-confirmation",
"pod",
"signature-capture",
"order-completion",
"customer-notification",
"tracking-update"
],
"sourcePath": "logistics/delivery-confirmation",
"repoPath": "uncategorized/logistics/delivery-confirmation-workflow"
},
{
"slug": "deployment-rollback-workflow",
"title": "Deployment Rollback Workflow",
"description": "Deployment rollback workflow with issue detection, rollback decision, previous version restoration, health verification, and post-mortem documentation.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "incident",
"secondaryUseCases": [
"delivery"
],
"useCases": [
"incident",
"delivery"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"deployment-rollback",
"version-revert",
"incident-response",
"kubernetes",
"helm-rollback",
"service-recovery"
],
"sourcePath": "devops/deployment-rollback",
"repoPath": "incident/devops/deployment-rollback-workflow"
},
{
"slug": "diversity-initiative-workflow",
"title": "Diversity Initiative Workflow",
"description": "This workflow models promoting workplace diversity.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"diversity",
"initiative",
"hr"
],
"sourcePath": "hr/diversity-initiative",
"repoPath": "uncategorized/hr/diversity-initiative-workflow"
},
{
"slug": "dunning-flow-workflow",
"title": "Dunning Flow Workflow",
"description": "Dunning collection workflow with escalating reminder emails, grace period management, account suspension, and payment recovery tracking.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "billing",
"secondaryUseCases": [],
"useCases": [
"billing"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"dunning-flow",
"collections",
"overdue-payment",
"payment-reminder",
"account-suspension",
"revenue-recovery"
],
"sourcePath": "business-operations/dunning-flow",
"repoPath": "billing/business-operations/dunning-flow-workflow"
},
{
"slug": "email-campaign-workflow",
"title": "Email Campaign Workflow",
"description": "Email marketing campaign workflow with audience segmentation, A/B testing, send scheduling, deliverability monitoring, and engagement analytics.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"email-campaign",
"marketing-automation",
"mailchimp",
"segmentation",
"a-b-testing",
"deliverability"
],
"sourcePath": "business-operations/email-campaign",
"repoPath": "uncategorized/business-operations/email-campaign-workflow"
},
{
"slug": "employee-engagement-workflow",
"title": "Employee Engagement Workflow",
"description": "This workflow models measuring and improving engagement.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"employee",
"engagement",
"hr",
"parallel"
],
"sourcePath": "hr/employee-engagement",
"repoPath": "uncategorized/hr/employee-engagement-workflow"
},
{
"slug": "enricher-workflow",
"title": "Enricher Workflow",
"description": "This workflow models adding metadata to messages before passing them on.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"enricher",
"patterns"
],
"sourcePath": "patterns/enricher",
"repoPath": "uncategorized/patterns/enricher-workflow"
},
{
"slug": "error-retry-loop-workflow",
"title": "Error Retry Loop Workflow",
"description": "This workflow models a failed operation that retries with backoff.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"error",
"retry",
"loop",
"patterns"
],
"sourcePath": "patterns/error-retry-loop",
"repoPath": "uncategorized/patterns/error-retry-loop-workflow"
},
{
"slug": "escalation-pattern-workflow",
"title": "Escalation Pattern Workflow",
"description": "This workflow models escalating issues to higher authority when needed.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"escalation",
"pattern",
"patterns"
],
"sourcePath": "patterns/escalation-pattern",
"repoPath": "handoff/patterns/escalation-pattern-workflow"
},
{
"slug": "event-driven-workflow",
"title": "Event Driven Workflow",
"description": "This workflow models reacting to incoming business events.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"event",
"driven",
"patterns"
],
"sourcePath": "patterns/event-driven",
"repoPath": "uncategorized/patterns/event-driven-workflow"
},
{
"slug": "event-sourcing-workflow",
"title": "Event Sourcing Workflow",
"description": "Event sourcing pattern with event capture, event store persistence, aggregate reconstruction, snapshot optimization, and temporal state queries.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"event-sourcing",
"event-store",
"aggregate",
"replay",
"audit-log",
"temporal-query"
],
"sourcePath": "patterns/event-sourcing",
"repoPath": "compliance/patterns/event-sourcing-workflow"
},
{
"slug": "expense-allocation-workflow",
"title": "Expense Allocation Workflow",
"description": "This workflow models allocating costs to departments.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"expense",
"allocation",
"finance"
],
"sourcePath": "finance/expense-allocation",
"repoPath": "uncategorized/finance/expense-allocation-workflow"
},
{
"slug": "expense-approval-workflow",
"title": "Expense Approval Workflow",
"description": "Employee expense approval workflow with receipt validation, policy compliance check, tiered approval based on amount, and reimbursement processing.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "approval",
"secondaryUseCases": [
"compliance"
],
"useCases": [
"approval",
"compliance"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"expense-approval",
"travel-expenses",
"receipt-validation",
"policy-compliance",
"tiered-approval",
"reimbursement"
],
"sourcePath": "hr/expense-approval",
"repoPath": "approval/hr/expense-approval-workflow"
},
{
"slug": "expense-claim-workflow",
"title": "Expense Claim Workflow",
"description": "Employee expense reimbursement workflow with receipt submission, manager approval, finance review, policy compliance check, and direct deposit payment.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "approval",
"secondaryUseCases": [],
"useCases": [
"approval"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"expense-reimbursement",
"employee-expenses",
"receipt-upload",
"manager-approval",
"finance-review",
"direct-deposit"
],
"sourcePath": "finance/expense-claim",
"repoPath": "approval/finance/expense-claim-workflow"
},
{
"slug": "fan-out-fan-in-workflow",
"title": "Fan Out Fan In Workflow",
"description": "Fan-out/fan-in pattern with work distribution to parallel workers, concurrent execution, result aggregation, and error handling for partial failures.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "ai-orchestration",
"secondaryUseCases": [],
"useCases": [
"ai-orchestration"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"fan-out-fan-in",
"scatter-gather",
"parallel-processing",
"aggregation",
"map-reduce",
"concurrency"
],
"sourcePath": "patterns/fan-out-fan-in",
"repoPath": "ai-orchestration/patterns/fan-out-fan-in-workflow"
},
{
"slug": "feature-toggle-workflow",
"title": "Feature Toggle Workflow",
"description": "Feature toggle pattern with flag configuration, user targeting rules, percentage rollouts, and instant kill-switch capability for production features.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"feature-toggle",
"feature-flags",
"dark-launch",
"a-b-testing",
"gradual-rollout",
"kill-switch"
],
"sourcePath": "patterns/feature-toggle",
"repoPath": "uncategorized/patterns/feature-toggle-workflow"
},
{
"slug": "filter-workflow",
"title": "Filter Workflow",
"description": "This workflow models removing items that do not meet criteria.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"filter",
"patterns",
"decision",
"loop"
],
"sourcePath": "patterns/filter",
"repoPath": "uncategorized/patterns/filter-workflow"
},
{
"slug": "financial-reporting-workflow",
"title": "Financial Reporting Workflow",
"description": "Financial reporting workflow with GAAP-compliant statement preparation, management review, audit committee approval, and SEC filing for public companies.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"financial-reporting",
"gaap-compliance",
"income-statement",
"balance-sheet",
"cash-flow-statement",
"sec-filing"
],
"sourcePath": "finance/financial-reporting",
"repoPath": "compliance/finance/financial-reporting-workflow"
},
{
"slug": "fixed-assets-workflow",
"title": "Fixed Assets Workflow",
"description": "Fixed asset management workflow with asset capitalization, depreciation scheduling, physical inventory verification, and asset disposal/retirement processing.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"fixed-assets",
"asset-tracking",
"depreciation",
"capitalization",
"asset-disposal",
"physical-inventory"
],
"sourcePath": "finance/fixed-assets",
"repoPath": "uncategorized/finance/fixed-assets-workflow"
},
{
"slug": "fleet-maintenance-workflow",
"title": "Fleet Maintenance Workflow",
"description": "Fleet maintenance workflow with preventive maintenance scheduling, vehicle inspection, work order creation, parts ordering, and DOT compliance tracking.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"fleet-maintenance",
"preventive-maintenance",
"vehicle-inspection",
"work-order",
"dot-compliance",
"telematics"
],
"sourcePath": "logistics/fleet-maintenance",
"repoPath": "compliance/logistics/fleet-maintenance-workflow"
},
{
"slug": "gdpr-deletion-workflow",
"title": "Gdpr Deletion Workflow",
"description": "GDPR data deletion workflow with identity verification, data inventory scan, PII removal across systems, backup purging, and deletion confirmation.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"gdpr-deletion",
"right-to-be-forgotten",
"data-privacy",
"pii-removal",
"compliance",
"dsar"
],
"sourcePath": "business-operations/gdpr-deletion",
"repoPath": "compliance/business-operations/gdpr-deletion-workflow"
},
{
"slug": "hazmat-handling-workflow",
"title": "Hazmat Handling Workflow",
"description": "Hazardous materials handling workflow with UN classification, SDS documentation, proper labeling, certified handler assignment, and emergency response procedures.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "incident",
"secondaryUseCases": [
"compliance"
],
"useCases": [
"incident",
"compliance"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"hazmat-handling",
"dangerous-goods",
"un-classification",
"sds-documentation",
"dot-compliance",
"emergency-response"
],
"sourcePath": "logistics/hazmat-handling",
"repoPath": "incident/logistics/hazmat-handling-workflow"
},
{
"slug": "idempotent-consumer-workflow",
"title": "Idempotent Consumer Workflow",
"description": "This workflow models processing each message safely only once.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"idempotent",
"consumer",
"patterns"
],
"sourcePath": "patterns/idempotent-consumer",
"repoPath": "uncategorized/patterns/idempotent-consumer-workflow"
},
{
"slug": "in-app-message-workflow",
"title": "In App Message Workflow",
"description": "In-app messaging workflow with trigger conditions, audience targeting, message display, user interaction tracking, and conversion measurement.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"in-app-message",
"product-tours",
"tooltips",
"announcements",
"user-engagement",
"intercom"
],
"sourcePath": "business-operations/in-app-message",
"repoPath": "uncategorized/business-operations/in-app-message-workflow"
},
{
"slug": "incident-response-workflow",
"title": "Incident Response Workflow",
"description": "Production incident response workflow with severity-based routing, war room coordination, incident commander assignment, customer communication, root cause analysis, and postmortem scheduling.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "incident",
"secondaryUseCases": [],
"useCases": [
"incident"
],
"complexity": 5,
"numNodes": 23,
"numLanes": 4,
"tags": [
"incident-management",
"on-call",
"pagerduty",
"war-room",
"severity-levels",
"postmortem",
"sre"
],
"sourcePath": "devops/incident-response",
"repoPath": "incident/devops/incident-response-workflow"
},
{
"slug": "infrastructure-provisioning-workflow",
"title": "Infrastructure Provisioning Workflow",
"description": "Infrastructure as Code provisioning workflow with Terraform plan, approval gates, state management, resource creation, and drift detection.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"infrastructure-provisioning",
"terraform",
"iac",
"cloud-resources",
"gitops",
"state-management"
],
"sourcePath": "devops/infrastructure-provisioning",
"repoPath": "delivery/devops/infrastructure-provisioning-workflow"
},
{
"slug": "insurance-claim-workflow",
"title": "Insurance Claim Workflow",
"description": "Insurance claim processing workflow with incident documentation, claim filing, adjuster assignment, damage assessment, and settlement negotiation.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "approval",
"secondaryUseCases": [],
"useCases": [
"approval"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"insurance-claim",
"claim-filing",
"adjuster-review",
"settlement",
"property-damage",
"liability"
],
"sourcePath": "finance/insurance-claim",
"repoPath": "approval/finance/insurance-claim-workflow"
},
{
"slug": "internal-controls-workflow",
"title": "Internal Controls Workflow",
"description": "Internal controls testing workflow with risk assessment, control design evaluation, operating effectiveness testing, deficiency identification, and remediation tracking.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"internal-controls",
"sox-compliance",
"control-testing",
"segregation-of-duties",
"risk-assessment",
"remediation"
],
"sourcePath": "finance/internal-controls",
"repoPath": "compliance/finance/internal-controls-workflow"
},
{
"slug": "internship-program-workflow",
"title": "Internship Program Workflow",
"description": "This workflow models managing an internship program.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"internship",
"program",
"hr"
],
"sourcePath": "hr/internship-program",
"repoPath": "uncategorized/hr/internship-program-workflow"
},
{
"slug": "interview-process-workflow",
"title": "Interview Process Workflow",
"description": "Multi-stage interview process with resume screening, phone screen, technical interview, onsite panel, team consensus decision, and offer/rejection handling.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 22,
"numLanes": 3,
"tags": [
"interview-process",
"hiring",
"phone-screen",
"technical-interview",
"onsite-panel",
"talent-acquisition",
"offer-management"
],
"sourcePath": "hr/interview-process",
"repoPath": "uncategorized/hr/interview-process-workflow"
},
{
"slug": "inventory-receipt-workflow",
"title": "Inventory Receipt Workflow",
"description": "Inventory receiving workflow with ASN verification, PO matching, quantity count, damage inspection, and WMS inventory update.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"inventory-receipt",
"goods-receiving",
"po-matching",
"asn-verification",
"dock-scheduling",
"wms"
],
"sourcePath": "logistics/inventory-receipt",
"repoPath": "uncategorized/logistics/inventory-receipt-workflow"
},
{
"slug": "invoice-processing-workflow",
"title": "Invoice Processing Workflow",
"description": "Accounts payable invoice automation with OCR data extraction, three-way PO matching, tiered approval workflow, and automated payment processing with GL updates.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "approval",
"secondaryUseCases": [
"billing"
],
"useCases": [
"approval",
"billing"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 4,
"tags": [
"accounts-payable",
"invoice-automation",
"ocr",
"po-matching",
"approval-workflow",
"payment-processing",
"three-way-match"
],
"sourcePath": "finance/invoice-processing",
"repoPath": "approval/finance/invoice-processing-workflow"
},
{
"slug": "job-posting-workflow",
"title": "Job Posting Workflow",
"description": "Job posting workflow with requisition approval, job description drafting, multi-channel posting (LinkedIn, Indeed, career sites), AI resume screening, and ATS candidate tracking.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 19,
"numLanes": 3,
"tags": [
"job-posting",
"job-requisition",
"ats",
"linkedin",
"indeed",
"ai-screening",
"talent-acquisition"
],
"sourcePath": "hr/job-posting",
"repoPath": "uncategorized/hr/job-posting-workflow"
},
{
"slug": "kitting-process-workflow",
"title": "Kitting Process Workflow",
"description": "Kit assembly workflow with BOM explosion, component picking, assembly verification, kit labeling, and inventory conversion from components to finished kit.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"kitting-process",
"kit-assembly",
"bom",
"component-picking",
"value-added-services",
"bundling"
],
"sourcePath": "logistics/kitting-process",
"repoPath": "uncategorized/logistics/kitting-process-workflow"
},
{
"slug": "knowledge-base-workflow",
"title": "Knowledge Base Workflow",
"description": "Knowledge base management workflow with article creation, review approval, SEO optimization, version control, and search analytics tracking.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "support",
"secondaryUseCases": [],
"useCases": [
"support"
],
"complexity": 3,
"numNodes": 13,
"numLanes": 4,
"tags": [
"knowledge-base",
"help-center",
"documentation",
"self-service",
"article-management",
"zendesk"
],
"sourcePath": "business-operations/knowledge-base",
"repoPath": "support/business-operations/knowledge-base-workflow"
},
{
"slug": "last-mile-delivery-workflow",
"title": "Last Mile Delivery Workflow",
"description": "Last mile delivery workflow with route optimization, real-time GPS tracking, delivery attempt handling, proof of delivery capture, and customer notification.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"last-mile-delivery",
"route-optimization",
"proof-of-delivery",
"delivery-exception",
"customer-notification",
"gps-tracking"
],
"sourcePath": "logistics/last-mile-delivery",
"repoPath": "uncategorized/logistics/last-mile-delivery-workflow"
},
{
"slug": "load-testing-workflow",
"title": "Load Testing Workflow",
"description": "Load testing workflow with test scenario design, gradual ramp-up, performance metrics collection, bottleneck identification, and capacity recommendations.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"load-testing",
"performance-testing",
"stress-testing",
"k6",
"jmeter",
"capacity-planning"
],
"sourcePath": "devops/load-testing",
"repoPath": "delivery/devops/load-testing-workflow"
},
{
"slug": "materialized-view-workflow",
"title": "Materialized View Workflow",
"description": "This workflow models serving queries from a precomputed view.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"materialized",
"view",
"patterns",
"decision",
"loop"
],
"sourcePath": "patterns/materialized-view",
"repoPath": "uncategorized/patterns/materialized-view-workflow"
},
{
"slug": "message-queue-workflow",
"title": "Message Queue Workflow",
"description": "This workflow models asynchronous processing of work via a queue.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"message",
"queue",
"patterns",
"decision"
],
"sourcePath": "patterns/message-queue",
"repoPath": "uncategorized/patterns/message-queue-workflow"
},
{
"slug": "monitoring-alert-workflow",
"title": "Monitoring Alert Workflow",
"description": "Monitoring and alerting workflow with metric collection, threshold evaluation, alert routing, escalation policies, and incident creation.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "incident",
"secondaryUseCases": [],
"useCases": [
"incident"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"monitoring-alerting",
"prometheus",
"pagerduty",
"threshold-alerts",
"anomaly-detection",
"on-call"
],
"sourcePath": "devops/monitoring-alert",
"repoPath": "incident/devops/monitoring-alert-workflow"
},
{
"slug": "monthly-close-workflow",
"title": "Monthly Close Workflow",
"description": "Corporate month-end financial close process including transaction posting, bank reconciliation, accruals, depreciation, trial balance validation, and financial statement generation.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 22,
"numLanes": 4,
"tags": [
"monthly-close",
"financial-reporting",
"accounting",
"reconciliation",
"trial-balance",
"period-close"
],
"sourcePath": "finance/monthly-close",
"repoPath": "uncategorized/finance/monthly-close-workflow"
},
{
"slug": "nested-decisions-workflow",
"title": "Nested Decisions Workflow",
"description": "This workflow models multiple layers of decisions before completion.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"nested",
"decisions",
"patterns",
"decision",
"loop"
],
"sourcePath": "patterns/nested-decisions",
"repoPath": "uncategorized/patterns/nested-decisions-workflow"
},
{
"slug": "normalizer-workflow",
"title": "Normalizer Workflow",
"description": "This workflow models converting varied inputs to a standard format.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"normalizer",
"patterns"
],
"sourcePath": "patterns/normalizer",
"repoPath": "uncategorized/patterns/normalizer-workflow"
},
{
"slug": "notification-pattern-workflow",
"title": "Notification Pattern Workflow",
"description": "This workflow models sending alerts via multiple channels.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"notification",
"pattern",
"patterns"
],
"sourcePath": "patterns/notification-pattern",
"repoPath": "uncategorized/patterns/notification-pattern-workflow"
},
{
"slug": "oauth-flow-workflow",
"title": "Oauth Flow Workflow",
"description": "OAuth 2.0 authorization code flow with redirect handling, code exchange, token storage, refresh token rotation, and scope management.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "approval",
"secondaryUseCases": [
"security"
],
"useCases": [
"approval",
"security"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"oauth-flow",
"oauth2",
"authorization-code",
"token-exchange",
"sso",
"third-party-auth"
],
"sourcePath": "business-operations/oauth-flow",
"repoPath": "approval/business-operations/oauth-flow-workflow"
},
{
"slug": "offboarding-workflow",
"title": "Offboarding Workflow",
"description": "Employee offboarding workflow with exit interview, knowledge transfer, asset collection, access revocation, final pay processing, and benefits continuation.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "handoff",
"secondaryUseCases": [
"offboarding"
],
"useCases": [
"handoff",
"offboarding"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"employee-offboarding",
"exit-interview",
"access-revocation",
"asset-return",
"knowledge-transfer",
"final-paycheck"
],
"sourcePath": "hr/offboarding",
"repoPath": "handoff/hr/offboarding-workflow"
},
{
"slug": "on-call-rotation-workflow",
"title": "On Call Rotation Workflow",
"description": "On-call rotation workflow with schedule creation, shift handoffs, override management, escalation policies, and fair rotation distribution.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "handoff",
"secondaryUseCases": [
"incident",
"security"
],
"useCases": [
"handoff",
"incident",
"security"
],
"complexity": 3,
"numNodes": 13,
"numLanes": 4,
"tags": [
"on-call-rotation",
"incident-management",
"pagerduty",
"escalation",
"schedule-management",
"handoff"
],
"sourcePath": "devops/on-call-rotation",
"repoPath": "handoff/devops/on-call-rotation-workflow"
},
{
"slug": "onboarding-workflow",
"title": "Onboarding Workflow",
"description": "Complete employee onboarding workflow covering offer acceptance, HR record creation, benefits enrollment, background check verification, IT account provisioning, equipment setup, and first day orientation.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "onboarding",
"secondaryUseCases": [
"delivery"
],
"useCases": [
"onboarding",
"delivery"
],
"complexity": 4,
"numNodes": 20,
"numLanes": 3,
"tags": [
"employee-onboarding",
"new-hire",
"hr-workflow",
"background-check",
"it-provisioning",
"benefits-enrollment"
],
"sourcePath": "hr/onboarding",
"repoPath": "onboarding/hr/onboarding-workflow"
},
{
"slug": "packing-process-workflow",
"title": "Packing Process Workflow",
"description": "Order packing workflow with carton selection, item verification, packing slip insertion, weight check, and package sealing for shipment.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"order-packing",
"box-selection",
"packing-slip",
"weight-verification",
"cartonization",
"fulfillment"
],
"sourcePath": "logistics/packing-process",
"repoPath": "uncategorized/logistics/packing-process-workflow"
},
{
"slug": "parallel-execution-workflow",
"title": "Parallel Execution Workflow",
"description": "This workflow models multiple tasks that run at the same time.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"parallel",
"execution",
"patterns",
"loop"
],
"sourcePath": "patterns/parallel-execution",
"repoPath": "uncategorized/patterns/parallel-execution-workflow"
},
{
"slug": "payment-failure-workflow",
"title": "Payment Failure Workflow",
"description": "Failed payment recovery workflow with smart retry scheduling, dunning email sequence, payment method update prompts, and involuntary churn prevention.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "billing",
"secondaryUseCases": [],
"useCases": [
"billing"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"payment-failure",
"dunning",
"retry-logic",
"card-decline",
"revenue-recovery",
"stripe"
],
"sourcePath": "business-operations/payment-failure",
"repoPath": "billing/business-operations/payment-failure-workflow"
},
{
"slug": "payment-run-workflow",
"title": "Payment Run Workflow",
"description": "Accounts payable payment run workflow with batch creation, tiered approval (single/dual based on amount), ACH file generation, check printing, and vendor record updates.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "handoff",
"secondaryUseCases": [
"approval",
"billing"
],
"useCases": [
"handoff",
"approval",
"billing"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 3,
"tags": [
"payment-run",
"accounts-payable",
"ach-payments",
"check-run",
"dual-approval",
"bank-transfer",
"vendor-payments"
],
"sourcePath": "finance/payment-run",
"repoPath": "handoff/finance/payment-run-workflow"
},
{
"slug": "payroll-processing-workflow",
"title": "Payroll Processing Workflow",
"description": "Complete payroll processing workflow with timesheet collection, gross pay calculation, overtime, tax withholding (federal, state, FICA), benefits deductions, compliance validation, and ACH direct deposit.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 5,
"numNodes": 24,
"numLanes": 4,
"tags": [
"payroll-processing",
"salary-calculation",
"tax-withholding",
"fica",
"ach-direct-deposit",
"benefits-deductions",
"compliance"
],
"sourcePath": "finance/payroll-processing",
"repoPath": "compliance/finance/payroll-processing-workflow"
},
{
"slug": "performance-review-workflow",
"title": "Performance Review Workflow",
"description": "Annual performance review workflow with self-assessment, manager evaluation, 360 feedback collection, calibration sessions, and merit increase recommendations.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "approval",
"secondaryUseCases": [],
"useCases": [
"approval"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"performance-review",
"annual-evaluation",
"goal-setting",
"360-feedback",
"calibration",
"merit-increase"
],
"sourcePath": "hr/performance-review",
"repoPath": "approval/hr/performance-review-workflow"
},
{
"slug": "personalization-engine-workflow",
"title": "Personalization Engine Workflow",
"description": "Make.com automation scenario for real-time personalization using Segment events, ML recommendation API, and Braze campaign delivery across email and push channels.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 20,
"numLanes": 3,
"tags": [
"make-com",
"personalization",
"segment",
"braze",
"ml-recommendations",
"content-delivery",
"marketing-automation"
],
"sourcePath": "business-operations/personalization-engine",
"repoPath": "uncategorized/business-operations/personalization-engine-workflow"
},
{
"slug": "picking-process-workflow",
"title": "Picking Process Workflow",
"description": "Warehouse order picking workflow with pick list generation, zone routing, batch picking optimization, barcode scanning verification, and pick completion confirmation.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"order-picking",
"warehouse-management",
"pick-list",
"batch-picking",
"wave-picking",
"wms"
],
"sourcePath": "logistics/picking-process",
"repoPath": "uncategorized/logistics/picking-process-workflow"
},
{
"slug": "plan-downgrade-workflow",
"title": "Plan Downgrade Workflow",
"description": "Subscription plan downgrade workflow with retention offer, feature restriction warning, data migration handling, and end-of-period scheduling.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "billing",
"secondaryUseCases": [
"delivery"
],
"useCases": [
"billing",
"delivery"
],
"complexity": 3,
"numNodes": 13,
"numLanes": 4,
"tags": [
"plan-downgrade",
"retention",
"feature-restriction",
"data-migration",
"churn-prevention",
"billing"
],
"sourcePath": "business-operations/plan-downgrade",
"repoPath": "billing/business-operations/plan-downgrade-workflow"
},
{
"slug": "plan-upgrade-workflow",
"title": "Plan Upgrade Workflow",
"description": "Subscription plan upgrade workflow with feature comparison, proration calculation, immediate feature unlock, and billing adjustment.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "billing",
"secondaryUseCases": [],
"useCases": [
"billing"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"plan-upgrade",
"upsell",
"proration",
"feature-unlock",
"expansion-revenue",
"billing"
],
"sourcePath": "business-operations/plan-upgrade",
"repoPath": "billing/business-operations/plan-upgrade-workflow"
},
{
"slug": "polling-pattern-workflow",
"title": "Polling Pattern Workflow",
"description": "This workflow models periodically checking status until work is done.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"polling",
"pattern",
"patterns",
"loop"
],
"sourcePath": "patterns/polling-pattern",
"repoPath": "uncategorized/patterns/polling-pattern-workflow"
},
{
"slug": "process-manager-workflow",
"title": "Process Manager Workflow",
"description": "This workflow models orchestrating multiple services to complete a process.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"process",
"manager",
"patterns"
],
"sourcePath": "patterns/process-manager",
"repoPath": "uncategorized/patterns/process-manager-workflow"
},
{
"slug": "procurement-card-workflow",
"title": "Procurement Card Workflow",
"description": "This workflow models managing company credit cards.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"procurement",
"card",
"finance"
],
"sourcePath": "finance/procurement-card",
"repoPath": "uncategorized/finance/procurement-card-workflow"
},
{
"slug": "promotion-process-workflow",
"title": "Promotion Process Workflow",
"description": "Employee promotion workflow with performance validation, job level assessment, compensation adjustment, title change, and announcement coordination.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"promotion-process",
"career-advancement",
"job-leveling",
"title-change",
"compensation-adjustment",
"succession-planning"
],
"sourcePath": "hr/promotion-process",
"repoPath": "uncategorized/hr/promotion-process-workflow"
},
{
"slug": "pto-request-workflow",
"title": "Pto Request Workflow",
"description": "PTO request workflow with balance verification, manager approval, calendar blocking, and team coverage check before approval.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "approval",
"secondaryUseCases": [],
"useCases": [
"approval"
],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"pto-request",
"time-off",
"vacation",
"leave-management",
"manager-approval",
"accrual-balance"
],
"sourcePath": "hr/pto-request",
"repoPath": "approval/hr/pto-request-workflow"
},
{
"slug": "pub-sub-workflow",
"title": "Pub Sub Workflow",
"description": "This workflow models one publisher notifying many subscribers of events.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"pub",
"sub",
"patterns"
],
"sourcePath": "patterns/pub-sub",
"repoPath": "uncategorized/patterns/pub-sub-workflow"
},
{
"slug": "purchase-order-workflow",
"title": "Purchase Order Workflow",
"description": "Procurement purchase order workflow with requisition creation, budget validation, vendor sourcing, competitive bidding, and tiered approval routing based on amount thresholds.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "approval",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"approval",
"ai-orchestration"
],
"complexity": 4,
"numNodes": 22,
"numLanes": 3,
"tags": [
"purchase-order",
"procurement",
"requisition",
"vendor-sourcing",
"competitive-bidding",
"tiered-approval",
"budget-validation"
],
"sourcePath": "finance/purchase-order",
"repoPath": "approval/finance/purchase-order-workflow"
},
{
"slug": "push-notification-workflow",
"title": "Push Notification Workflow",
"description": "Mobile push notification workflow with audience targeting, platform routing (iOS/Android), delivery tracking, and engagement analytics.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"push-notification",
"mobile-engagement",
"firebase-fcm",
"apns",
"segmentation",
"deep-linking"
],
"sourcePath": "business-operations/push-notification",
"repoPath": "uncategorized/business-operations/push-notification-workflow"
},
{
"slug": "put-away-process-workflow",
"title": "Put Away Process Workflow",
"description": "Warehouse put-away workflow with location assignment, slotting optimization, forklift routing, barcode confirmation, and WMS location update.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"put-away",
"warehouse-storage",
"location-assignment",
"slotting",
"wms",
"inventory-placement"
],
"sourcePath": "logistics/put-away-process",
"repoPath": "uncategorized/logistics/put-away-process-workflow"
},
{
"slug": "quality-inspection-workflow",
"title": "Quality Inspection Workflow",
"description": "Incoming quality inspection workflow with AQL sampling, defect classification, hold/release decision, supplier notification, and quality metrics tracking.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"quality-inspection",
"incoming-inspection",
"aql-sampling",
"defect-tracking",
"supplier-quality",
"hold-release"
],
"sourcePath": "logistics/quality-inspection",
"repoPath": "uncategorized/logistics/quality-inspection-workflow"
},
{
"slug": "rate-limiter-workflow",
"title": "Rate Limiter Workflow",
"description": "This workflow models preventing too many requests from being processed.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"rate",
"limiter",
"patterns"
],
"sourcePath": "patterns/rate-limiter",
"repoPath": "uncategorized/patterns/rate-limiter-workflow"
},
{
"slug": "reference-check-workflow",
"title": "Reference Check Workflow",
"description": "Professional reference check workflow with reference collection, outreach scheduling, structured interview questions, feedback documentation, and hiring recommendation.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"reference-check",
"employment-verification",
"professional-references",
"hiring-decision",
"candidate-vetting",
"feedback-collection"
],
"sourcePath": "hr/reference-check",
"repoPath": "uncategorized/hr/reference-check-workflow"
},
{
"slug": "referral-program-workflow",
"title": "Referral Program Workflow",
"description": "Customer referral program workflow with unique link generation, referral tracking, conversion validation, and dual-sided reward fulfillment.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 13,
"numLanes": 4,
"tags": [
"referral-program",
"viral-growth",
"referral-tracking",
"reward-fulfillment",
"affiliate",
"word-of-mouth"
],
"sourcePath": "business-operations/referral-program",
"repoPath": "uncategorized/business-operations/referral-program-workflow"
},
{
"slug": "relocation-assistance-workflow",
"title": "Relocation Assistance Workflow",
"description": "This workflow models helping employees relocate.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"relocation",
"assistance",
"hr",
"decision"
],
"sourcePath": "hr/relocation-assistance",
"repoPath": "uncategorized/hr/relocation-assistance-workflow"
},
{
"slug": "reorder-process-workflow",
"title": "Reorder Process Workflow",
"description": "Inventory reorder workflow with reorder point monitoring, economic order quantity calculation, safety stock consideration, and automatic purchase requisition generation.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"reorder-process",
"reorder-point",
"safety-stock",
"eoq",
"demand-planning",
"auto-replenishment"
],
"sourcePath": "logistics/reorder-process",
"repoPath": "uncategorized/logistics/reorder-process-workflow"
},
{
"slug": "request-reply-workflow",
"title": "Request Reply Workflow",
"description": "This workflow models a synchronous request that waits for a reply.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"request",
"reply",
"patterns"
],
"sourcePath": "patterns/request-reply",
"repoPath": "uncategorized/patterns/request-reply-workflow"
},
{
"slug": "retry-with-backoff-workflow",
"title": "Retry With Backoff Workflow",
"description": "Exponential backoff retry pattern for API calls with configurable retry limits, delay calculation, retryable error detection, and graceful degradation on permanent failures.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 20,
"numLanes": 3,
"tags": [
"retry-pattern",
"exponential-backoff",
"fault-tolerance",
"api-resilience",
"transient-errors",
"http-retry",
"jitter"
],
"sourcePath": "patterns/retry-with-backoff",
"repoPath": "uncategorized/patterns/retry-with-backoff-workflow"
},
{
"slug": "returns-processing-workflow",
"title": "Returns Processing Workflow",
"description": "Customer returns processing workflow with RMA generation, return receipt, quality inspection, disposition decision, and refund or exchange processing.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "billing",
"secondaryUseCases": [],
"useCases": [
"billing"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"returns-processing",
"rma",
"refund",
"restocking",
"quality-inspection",
"reverse-logistics"
],
"sourcePath": "logistics/returns-processing",
"repoPath": "billing/logistics/returns-processing-workflow"
},
{
"slug": "reverse-logistics-workflow",
"title": "Reverse Logistics Workflow",
"description": "Reverse logistics workflow with return authorization, product grading, refurbishment decision, recycling coordination, and secondary market disposition.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"reverse-logistics",
"product-returns",
"refurbishment",
"recycling",
"disposition",
"sustainability"
],
"sourcePath": "logistics/reverse-logistics",
"repoPath": "uncategorized/logistics/reverse-logistics-workflow"
},
{
"slug": "review-collection-workflow",
"title": "Review Collection Workflow",
"description": "Customer review collection workflow with post-purchase trigger, review request email, rating submission, moderation, and public display.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "approval",
"secondaryUseCases": [],
"useCases": [
"approval"
],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"review-collection",
"customer-feedback",
"nps",
"ratings",
"social-proof",
"testimonials"
],
"sourcePath": "business-operations/review-collection",
"repoPath": "approval/business-operations/review-collection-workflow"
},
{
"slug": "router-workflow",
"title": "Router Workflow",
"description": "This workflow models routing messages based on their content.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"router",
"patterns",
"decision"
],
"sourcePath": "patterns/router",
"repoPath": "uncategorized/patterns/router-workflow"
},
{
"slug": "routing-slip-workflow",
"title": "Routing Slip Workflow",
"description": "This workflow models having messages carry their own routing instructions.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"routing",
"slip",
"patterns"
],
"sourcePath": "patterns/routing-slip",
"repoPath": "handoff/patterns/routing-slip-workflow"
},
{
"slug": "saga-pattern-workflow",
"title": "Saga Pattern Workflow",
"description": "Saga orchestration pattern for distributed transactions across Order, Payment, and Shipping services with automatic compensation rollback on failures.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "delivery",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"delivery",
"ai-orchestration"
],
"complexity": 5,
"numNodes": 20,
"numLanes": 4,
"tags": [
"saga-pattern",
"distributed-transactions",
"microservices",
"compensation",
"orchestration",
"eventual-consistency",
"rollback"
],
"sourcePath": "patterns/saga-pattern",
"repoPath": "delivery/patterns/saga-pattern-workflow"
},
{
"slug": "salary-increase-workflow",
"title": "Salary Increase Workflow",
"description": "Salary increase workflow with market analysis, comp ratio review, budget validation, tiered approval based on increase percentage, and payroll system update.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "approval",
"secondaryUseCases": [],
"useCases": [
"approval"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"salary-increase",
"compensation",
"merit-raise",
"market-adjustment",
"budget-approval",
"comp-ratio"
],
"sourcePath": "hr/salary-increase",
"repoPath": "approval/hr/salary-increase-workflow"
},
{
"slug": "search-optimization-workflow",
"title": "Search Optimization Workflow",
"description": "Search optimization workflow with query analysis, relevance tuning, synonym management, click-through tracking, and A/B testing of ranking algorithms.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"search-optimization",
"elasticsearch",
"relevance-tuning",
"query-analysis",
"algolia",
"search-analytics"
],
"sourcePath": "business-operations/search-optimization",
"repoPath": "uncategorized/business-operations/search-optimization-workflow"
},
{
"slug": "secret-rotation-workflow",
"title": "Secret Rotation Workflow",
"description": "Automated secret rotation workflow with HashiCorp Vault for API keys, database passwords, and certificates including Kubernetes secret updates and rolling service restarts.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "security",
"secondaryUseCases": [],
"useCases": [
"security"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 3,
"tags": [
"secret-rotation",
"vault",
"kubernetes-secrets",
"api-keys",
"database-passwords",
"certificates",
"security"
],
"sourcePath": "devops/secret-rotation",
"repoPath": "security/devops/secret-rotation-workflow"
},
{
"slug": "security-scan-workflow",
"title": "Security Scan Workflow",
"description": "Security scanning workflow with SAST, DAST, dependency vulnerability scanning, finding triage, and remediation tracking in CI/CD pipeline.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "security",
"secondaryUseCases": [],
"useCases": [
"security"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"security-scanning",
"sast",
"dast",
"dependency-check",
"snyk",
"devsecops"
],
"sourcePath": "devops/security-scan",
"repoPath": "security/devops/security-scan-workflow"
},
{
"slug": "shipping-process-workflow",
"title": "Shipping Process Workflow",
"description": "Order shipping workflow with carrier selection, rate shopping, label generation, tracking number assignment, and dispatch confirmation.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "security",
"secondaryUseCases": [],
"useCases": [
"security"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"shipping-process",
"order-fulfillment",
"carrier-selection",
"label-generation",
"tracking-number",
"dispatch"
],
"sourcePath": "logistics/shipping-process",
"repoPath": "security/logistics/shipping-process-workflow"
},
{
"slug": "sms-verification-workflow",
"title": "Sms Verification Workflow",
"description": "SMS phone verification workflow with OTP generation, rate limiting, code validation, retry handling, and verification status tracking.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "security",
"secondaryUseCases": [],
"useCases": [
"security"
],
"complexity": 3,
"numNodes": 13,
"numLanes": 4,
"tags": [
"sms-verification",
"otp",
"twilio",
"phone-verification",
"2fa",
"fraud-prevention"
],
"sourcePath": "business-operations/sms-verification",
"repoPath": "security/business-operations/sms-verification-workflow"
},
{
"slug": "snapshot-pattern-workflow",
"title": "Snapshot Pattern Workflow",
"description": "This workflow models taking periodic snapshots of important state.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"snapshot",
"pattern",
"patterns",
"decision",
"loop"
],
"sourcePath": "patterns/snapshot-pattern",
"repoPath": "uncategorized/patterns/snapshot-pattern-workflow"
},
{
"slug": "state-machine-workflow",
"title": "State Machine Workflow",
"description": "This workflow models tracking object state changes over time.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"state",
"machine",
"patterns",
"parallel"
],
"sourcePath": "patterns/state-machine",
"repoPath": "uncategorized/patterns/state-machine-workflow"
},
{
"slug": "stock-transfer-workflow",
"title": "Stock Transfer Workflow",
"description": "Internal stock transfer workflow with transfer request, source location pick, destination put-away, and inventory record updates across locations.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"stock-transfer",
"inventory-movement",
"location-transfer",
"bin-to-bin",
"wms",
"inventory-rebalancing"
],
"sourcePath": "logistics/stock-transfer",
"repoPath": "handoff/logistics/stock-transfer-workflow"
},
{
"slug": "strangler-fig-workflow",
"title": "Strangler Fig Workflow",
"description": "This workflow models gradually replacing an old system with a new one.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"strangler",
"fig",
"patterns",
"decision"
],
"sourcePath": "patterns/strangler-fig",
"repoPath": "uncategorized/patterns/strangler-fig-workflow"
},
{
"slug": "subscription-lifecycle-workflow",
"title": "Subscription Lifecycle Workflow",
"description": "SaaS subscription lifecycle workflow with trial signup, conversion nurturing, payment processing, renewal management, and churn prevention campaigns.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "billing",
"secondaryUseCases": [],
"useCases": [
"billing"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"subscription-lifecycle",
"saas",
"trial-conversion",
"renewal",
"churn-prevention",
"stripe"
],
"sourcePath": "business-operations/subscription-lifecycle",
"repoPath": "billing/business-operations/subscription-lifecycle-workflow"
},
{
"slug": "support-ticket-workflow",
"title": "Support Ticket Workflow",
"description": "Customer support ticket workflow with auto-categorization, SLA tracking, agent assignment, escalation rules, and satisfaction survey.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "handoff",
"secondaryUseCases": [
"support"
],
"useCases": [
"handoff",
"support"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"support-ticket",
"helpdesk",
"zendesk",
"sla",
"ticket-routing",
"customer-service"
],
"sourcePath": "business-operations/support-ticket",
"repoPath": "handoff/business-operations/support-ticket-workflow"
},
{
"slug": "tax-filing-workflow",
"title": "Tax Filing Workflow",
"description": "Corporate tax filing workflow with taxable income calculation, deductions, tax credits, variance review, and electronic or paper filing to IRS with receipt confirmation.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 3,
"tags": [
"tax-filing",
"corporate-tax",
"tax-calculation",
"irs-efile",
"tax-credits",
"deductions",
"compliance"
],
"sourcePath": "finance/tax-filing",
"repoPath": "compliance/finance/tax-filing-workflow"
},
{
"slug": "termination-process-workflow",
"title": "Termination Process Workflow",
"description": "Employee termination workflow handling voluntary and involuntary separations with legal review, separation agreements, final pay calculation, COBRA notices, and severance processing.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "approval",
"secondaryUseCases": [
"offboarding"
],
"useCases": [
"approval",
"offboarding"
],
"complexity": 4,
"numNodes": 20,
"numLanes": 3,
"tags": [
"employee-termination",
"offboarding",
"separation-agreement",
"final-pay",
"cobra",
"severance",
"legal-review"
],
"sourcePath": "hr/termination-process",
"repoPath": "approval/hr/termination-process-workflow"
},
{
"slug": "timeout-pattern-workflow",
"title": "Timeout Pattern Workflow",
"description": "This workflow models an operation that times out after a delay.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"timeout",
"pattern",
"patterns"
],
"sourcePath": "patterns/timeout-pattern",
"repoPath": "uncategorized/patterns/timeout-pattern-workflow"
},
{
"slug": "training-enrollment-workflow",
"title": "Training Enrollment Workflow",
"description": "Training enrollment workflow with course catalog browsing, manager approval, LMS registration, completion tracking, and certification management.",
"kind": "workflow",
"sourceDomain": "hr",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"training-enrollment",
"learning-management",
"lms",
"professional-development",
"compliance-training",
"certification"
],
"sourcePath": "hr/training-enrollment",
"repoPath": "compliance/hr/training-enrollment-workflow"
},
{
"slug": "transactional-outbox-workflow",
"title": "Transactional Outbox Workflow",
"description": "This workflow models writing data and publishing messages in one transaction.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 13,
"numLanes": 4,
"tags": [
"transactional",
"outbox",
"patterns",
"parallel"
],
"sourcePath": "patterns/transactional-outbox",
"repoPath": "uncategorized/patterns/transactional-outbox-workflow"
},
{
"slug": "transform-workflow",
"title": "Transform Workflow",
"description": "This workflow models converting messages into a new shape.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"transform",
"patterns"
],
"sourcePath": "patterns/transform",
"repoPath": "uncategorized/patterns/transform-workflow"
},
{
"slug": "treasury-management-workflow",
"title": "Treasury Management Workflow",
"description": "Corporate treasury management workflow with cash pooling, FX exposure hedging, short-term investment decisions, and bank relationship management.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"treasury-management",
"cash-pooling",
"fx-hedging",
"investment-portfolio",
"bank-relationships",
"liquidity"
],
"sourcePath": "finance/treasury-management",
"repoPath": "uncategorized/finance/treasury-management-workflow"
},
{
"slug": "two-factor-setup-workflow",
"title": "Two Factor Setup Workflow",
"description": "Two-factor authentication setup workflow with method selection (TOTP/SMS), QR code generation, backup codes, and verification confirmation.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "onboarding",
"secondaryUseCases": [
"security"
],
"useCases": [
"onboarding",
"security"
],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"two-factor-auth",
"mfa",
"totp",
"authenticator-app",
"security",
"account-protection"
],
"sourcePath": "business-operations/two-factor-setup",
"repoPath": "onboarding/business-operations/two-factor-setup-workflow"
},
{
"slug": "user-onboarding-workflow",
"title": "User Onboarding Workflow",
"description": "New user onboarding workflow with welcome email, profile setup, product tour, first action prompt, and activation milestone tracking.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "onboarding",
"secondaryUseCases": [],
"useCases": [
"onboarding"
],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"user-onboarding",
"activation",
"product-tour",
"welcome-email",
"first-time-user",
"time-to-value"
],
"sourcePath": "business-operations/user-onboarding",
"repoPath": "onboarding/business-operations/user-onboarding-workflow"
},
{
"slug": "user-segmentation-workflow",
"title": "User Segmentation Workflow",
"description": "User segmentation workflow with attribute collection, behavioral event tracking, segment rule definition, dynamic membership, and downstream sync.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"user-segmentation",
"audience-targeting",
"behavioral-cohorts",
"customer-segments",
"segment",
"marketing-automation"
],
"sourcePath": "business-operations/user-segmentation",
"repoPath": "uncategorized/business-operations/user-segmentation-workflow"
},
{
"slug": "validator-workflow",
"title": "Validator Workflow",
"description": "This workflow models checking that incoming data is valid.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"validator",
"patterns",
"parallel"
],
"sourcePath": "patterns/validator",
"repoPath": "uncategorized/patterns/validator-workflow"
},
{
"slug": "vendor-onboarding-workflow",
"title": "Vendor Onboarding Workflow",
"description": "Vendor onboarding workflow with application review, W-9/W-8BEN verification, insurance certificate validation, background checks, and compliance approval before vendor activation.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "onboarding",
"secondaryUseCases": [
"billing",
"compliance"
],
"useCases": [
"onboarding",
"billing",
"compliance"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 3,
"tags": [
"vendor-onboarding",
"supplier-management",
"w9-verification",
"insurance-compliance",
"background-check",
"payment-terms",
"procurement"
],
"sourcePath": "finance/vendor-onboarding",
"repoPath": "onboarding/finance/vendor-onboarding-workflow"
},
{
"slug": "vulnerability-patch-workflow",
"title": "Vulnerability Patch Workflow",
"description": "Security vulnerability patching workflow with CVE scanning, severity-based triage (critical/high/medium), patch testing, staging deployment, and production rollout with rollback capability.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "security",
"secondaryUseCases": [
"compliance",
"delivery"
],
"useCases": [
"security",
"compliance",
"delivery"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 3,
"tags": [
"vulnerability-management",
"security-patching",
"cve-triage",
"cvss-scoring",
"patch-testing",
"rollback",
"compliance"
],
"sourcePath": "devops/vulnerability-patch",
"repoPath": "security/devops/vulnerability-patch-workflow"
},
{
"slug": "warehouse-transfer-workflow",
"title": "Warehouse Transfer Workflow",
"description": "Inter-warehouse transfer workflow with transfer order creation, shipping from source DC, in-transit tracking, and receiving at destination warehouse.",
"kind": "workflow",
"sourceDomain": "logistics",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"warehouse-transfer",
"inter-facility",
"transfer-order",
"in-transit-inventory",
"network-optimization",
"distribution"
],
"sourcePath": "logistics/warehouse-transfer",
"repoPath": "handoff/logistics/warehouse-transfer-workflow"
},
{
"slug": "webhook-integration-workflow",
"title": "Webhook Integration Workflow",
"description": "Webhook integration workflow with endpoint registration, payload signing, delivery attempt, retry with backoff, and delivery status tracking.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"webhook",
"event-driven",
"http-callback",
"integration",
"retry-logic",
"payload-signing"
],
"sourcePath": "business-operations/webhook-integration",
"repoPath": "uncategorized/business-operations/webhook-integration-workflow"
},
{
"slug": "webhook-pattern-workflow",
"title": "Webhook Pattern Workflow",
"description": "This workflow models an HTTP callback when an event occurs.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"webhook",
"pattern",
"patterns",
"decision",
"loop"
],
"sourcePath": "patterns/webhook-pattern",
"repoPath": "uncategorized/patterns/webhook-pattern-workflow"
},
{
"slug": "webinar-registration-workflow",
"title": "Webinar Registration Workflow",
"description": "Webinar registration workflow with signup form, calendar invite, reminder email sequence, attendance tracking, and post-event follow-up.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "onboarding",
"secondaryUseCases": [],
"useCases": [
"onboarding"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"webinar",
"event-registration",
"zoom",
"calendar-invite",
"reminder-sequence",
"lead-capture"
],
"sourcePath": "business-operations/webinar-registration",
"repoPath": "onboarding/business-operations/webinar-registration-workflow"
},
{
"slug": "yearly-audit-workflow",
"title": "Yearly Audit Workflow",
"description": "Annual financial audit workflow with external auditor engagement, document preparation, fieldwork coordination, findings remediation, and management letter response.",
"kind": "workflow",
"sourceDomain": "finance",
"primaryUseCase": "compliance",
"secondaryUseCases": [],
"useCases": [
"compliance"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 3,
"tags": [
"annual-audit",
"external-auditors",
"sox-compliance",
"financial-statements",
"audit-findings",
"management-letter"
],
"sourcePath": "finance/yearly-audit",
"repoPath": "compliance/finance/yearly-audit-workflow"
},
{
"slug": "shopify-universal-commerce-protocol",
"title": "Shopify Universal Commerce Protocol",
"description": "End-to-end agentic commerce workflow showing how an AI assistant (ChatGPT) orchestrates product search, checkout, and payment through Shopify's Universal Commerce Protocol (UCP) gateway, enabling conversational shopping experiences.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "billing",
"secondaryUseCases": [
"agentic"
],
"useCases": [
"billing",
"agentic"
],
"complexity": 4,
"numNodes": 47,
"numLanes": 5,
"tags": [
"shopify",
"ucp",
"universal-commerce-protocol",
"agentic-commerce",
"ai-shopping",
"chatgpt",
"e-commerce",
"checkout",
"payment"
],
"sourcePath": "business-operations/shopify-universal-commerce-protocol",
"repoPath": "billing/business-operations/shopify-universal-commerce-protocol"
},
{
"slug": "microservices-api-gateway-architecture",
"title": "Microservices API Gateway Architecture",
"description": "A microservices API gateway architecture diagram showing request routing, JWT authentication, rate limiting, service discovery, and response aggregation across distributed backend services. This template models the entry point for all client traffic in a microservices ecosystem, enforcing security policies before requests reach internal services. Ideal for platform engineers designing scalable API infrastructure with centralized cross-cutting concerns.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "security",
"secondaryUseCases": [
"mcp"
],
"useCases": [
"security",
"mcp"
],
"complexity": 4,
"numNodes": 17,
"numLanes": 3,
"tags": [
"microservices",
"api-gateway",
"jwt-authentication",
"rate-limiting",
"service-discovery",
"load-balancing",
"architecture-diagram",
"distributed-systems"
],
"sourcePath": "",
"repoPath": "security/architecture/microservices-api-gateway-architecture"
},
{
"slug": "microservices-service-mesh-architecture",
"title": "Microservices Service Mesh Architecture",
"description": "A service mesh architecture diagram with Istio or Linkerd sidecar proxies handling mTLS encryption, traffic policies, circuit breaking, and distributed tracing across microservices. This template visualizes how a service mesh abstracts networking concerns away from application code, enabling zero-trust communication between services. Essential for teams adopting service mesh infrastructure to improve observability and security.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 3,
"tags": [
"service-mesh",
"istio",
"linkerd",
"mtls",
"sidecar-proxy",
"distributed-tracing",
"traffic-management",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "mcp/architecture/microservices-service-mesh-architecture"
},
{
"slug": "microservices-database-per-service-architecture",
"title": "Microservices Database-Per-Service Architecture",
"description": "A database-per-service architecture diagram where each microservice owns its dedicated data store, with event-driven synchronization via Kafka for cross-service data consistency. This template demonstrates the core microservices data isolation principle, showing how PostgreSQL and MongoDB coexist in a polyglot persistence strategy. Critical for architects enforcing service autonomy while maintaining eventual consistency.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 16,
"numLanes": 4,
"tags": [
"database-per-service",
"polyglot-persistence",
"microservices",
"kafka",
"event-driven",
"data-isolation",
"eventual-consistency",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/microservices-database-per-service-architecture"
},
{
"slug": "microservices-decomposition-by-business-capability",
"title": "Microservices Decomposition by Business Capability",
"description": "A microservices decomposition architecture diagram organized by business capabilities: Identity, Product Catalog, Pricing, and Order Fulfillment, each with independent data stores and APIs. This template shows how to break a monolith into services aligned with business domains, using a Backend-for-Frontend (BFF) pattern for client-specific aggregation. Useful for architects planning domain-driven microservice boundaries.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 17,
"numLanes": 5,
"tags": [
"microservices-decomposition",
"business-capability",
"bff",
"domain-driven-design",
"service-boundaries",
"monolith-to-microservices",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/microservices-decomposition-by-business-capability"
},
{
"slug": "microservices-strangler-fig-migration",
"title": "Microservices Strangler Fig Migration Architecture",
"description": "A strangler fig migration architecture diagram showing the incremental replacement of a legacy monolith with new microservices, using a routing layer to split traffic between old and new systems. This template models the proven migration strategy where new features are built as microservices while legacy endpoints are gradually retired. Essential for teams modernizing legacy systems without risky big-bang rewrites.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 4,
"numNodes": 16,
"numLanes": 4,
"tags": [
"strangler-fig",
"legacy-migration",
"monolith-decomposition",
"anti-corruption-layer",
"incremental-migration",
"modernization",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "delivery/architecture/microservices-strangler-fig-migration"
},
{
"slug": "microservices-service-discovery-architecture",
"title": "Microservices Service Discovery Architecture",
"description": "A service discovery architecture diagram with Consul or Eureka registry, client-side load balancing, health check heartbeats, and automatic instance registration and deregistration. This template visualizes how microservices dynamically locate each other without hardcoded endpoints, enabling elastic scaling and self-healing infrastructure. Key for platform teams building resilient service-to-service communication.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 3,
"numNodes": 16,
"numLanes": 3,
"tags": [
"service-discovery",
"consul",
"eureka",
"health-check",
"client-side-load-balancing",
"service-registry",
"dynamic-routing",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "handoff/architecture/microservices-service-discovery-architecture"
},
{
"slug": "microservices-sidecar-pattern-architecture",
"title": "Microservices Sidecar Pattern Architecture",
"description": "A sidecar pattern architecture diagram showing Envoy proxy, log collector, and config watcher sidecars running alongside application containers in a Kubernetes pod, with a control plane managing configuration. This template demonstrates how auxiliary concerns like logging, monitoring, and configuration are deployed as co-located containers. Foundational for teams adopting cloud-native container orchestration patterns.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 4,
"numNodes": 13,
"numLanes": 3,
"tags": [
"sidecar-pattern",
"envoy-proxy",
"kubernetes",
"container-pattern",
"observability",
"control-plane",
"cloud-native",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "mcp/architecture/microservices-sidecar-pattern-architecture"
},
{
"slug": "microservices-backend-for-frontend-architecture",
"title": "Microservices Backend-for-Frontend (BFF) Architecture",
"description": "A Backend-for-Frontend architecture diagram with separate BFF layers for web and mobile clients, each optimizing API responses for their specific platform while sharing common backend microservices. This template shows how to avoid one-size-fits-all APIs by tailoring data aggregation and payload optimization per client type. Recommended for teams serving multiple frontend platforms from a shared microservices backend.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 12,
"numLanes": 3,
"tags": [
"backend-for-frontend",
"bff-pattern",
"mobile-api",
"web-api",
"api-aggregation",
"payload-optimization",
"microservices",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/microservices-backend-for-frontend-architecture"
},
{
"slug": "event-driven-publish-subscribe-architecture",
"title": "Event-Driven Publish-Subscribe Architecture",
"description": "An event-driven publish-subscribe architecture diagram with Kafka or RabbitMQ message broker, event serialization, topic partitioning, fan-out delivery to multiple consumers, and dead letter queue error handling. This template models the foundational async messaging pattern where producers and consumers are fully decoupled through a message broker. Essential for architects building loosely coupled, scalable event-driven systems.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 17,
"numLanes": 3,
"tags": [
"publish-subscribe",
"event-driven",
"kafka",
"rabbitmq",
"message-broker",
"fan-out",
"dead-letter-queue",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/event-driven-publish-subscribe-architecture"
},
{
"slug": "event-driven-event-sourcing-architecture",
"title": "Event-Driven Event Sourcing Architecture",
"description": "An event sourcing architecture diagram where all state changes are stored as an immutable sequence of domain events, with read projections built from the event stream and snapshot optimization for fast aggregate loading. This template shows how event sourcing eliminates data loss by preserving the complete history of every state transition. Critical for systems requiring full audit trails, temporal queries, and event replay capabilities.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"event-sourcing",
"immutable-events",
"event-store",
"projections",
"snapshot",
"aggregate",
"temporal-query",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/event-driven-event-sourcing-architecture"
},
{
"slug": "event-driven-cqrs-with-event-store-architecture",
"title": "Event-Driven CQRS with Event Store Architecture",
"description": "A CQRS architecture diagram combining separate command and query APIs with an event bus for asynchronous read model synchronization, including projectors that build denormalized views from domain events. This template demonstrates the full CQRS+ES stack where writes go through domain validation and reads are served from optimized materialized views. Ideal for high-throughput systems where read and write workloads have fundamentally different scaling requirements.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"cqrs",
"event-store",
"command-query-separation",
"read-model",
"write-model",
"projector",
"eventual-consistency",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/event-driven-cqrs-with-event-store-architecture"
},
{
"slug": "event-driven-choreography-architecture",
"title": "Event-Driven Choreography Architecture",
"description": "An event-driven choreography architecture diagram where microservices coordinate through events without a central orchestrator, with Order, Payment, Inventory, and Shipping services reacting to each other's domain events. This template models the decentralized coordination pattern where each service knows only its own responsibilities and publishes events for others to consume. Best for teams favoring autonomous services over centralized workflow control.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 19,
"numLanes": 5,
"tags": [
"choreography",
"event-driven",
"decentralized-coordination",
"domain-events",
"microservices",
"autonomous-services",
"pub-sub",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/event-driven-choreography-architecture"
},
{
"slug": "event-driven-event-streaming-pipeline-architecture",
"title": "Event-Driven Streaming Pipeline Architecture",
"description": "A real-time event streaming pipeline architecture diagram with IoT sensors, application logs, and clickstream data flowing through Kafka into Apache Flink for window aggregation, anomaly detection, and multi-sink output to data lakes and dashboards. This template visualizes end-to-end stream processing from ingestion through transformation to storage and alerting. Essential for data engineers building real-time analytics and monitoring platforms.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"event-streaming",
"kafka",
"apache-flink",
"stream-processing",
"real-time-analytics",
"iot",
"data-pipeline",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "delivery/architecture/event-driven-event-streaming-pipeline-architecture"
},
{
"slug": "event-driven-domain-events-architecture",
"title": "Event-Driven Domain Events Architecture",
"description": "A domain events architecture diagram showing how aggregate roots raise domain events that are dispatched both in-process to local handlers and cross-boundary to integration event consumers in other bounded contexts. This template models the DDD event pattern where domain logic triggers side effects through a clean event dispatcher, maintaining separation between domain and infrastructure concerns. Key for teams implementing Domain-Driven Design with event-based integration.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "security",
"secondaryUseCases": [],
"useCases": [
"security"
],
"complexity": 4,
"numNodes": 17,
"numLanes": 4,
"tags": [
"domain-events",
"ddd",
"aggregate-root",
"bounded-context",
"event-dispatcher",
"integration-events",
"domain-driven-design",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "security/architecture/event-driven-domain-events-architecture"
},
{
"slug": "event-driven-cdc-change-data-capture-architecture",
"title": "Event-Driven CDC (Change Data Capture) Architecture",
"description": "A Change Data Capture architecture diagram using Debezium to tail database transaction logs and publish change events to Kafka, feeding downstream consumers that update search indexes, invalidate caches, load data warehouses, and write audit logs. This template shows how CDC eliminates dual-write problems by capturing changes at the database level without modifying application code. Critical for data synchronization across heterogeneous systems.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 17,
"numLanes": 4,
"tags": [
"change-data-capture",
"cdc",
"debezium",
"transaction-log",
"kafka-connect",
"data-synchronization",
"dual-write",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/event-driven-cdc-change-data-capture-architecture"
},
{
"slug": "event-driven-dead-letter-queue-architecture",
"title": "Event-Driven Dead Letter Queue Architecture",
"description": "A dead letter queue architecture diagram with retry policies, exponential backoff, max retry thresholds, DLQ routing for failed messages, operations alerting, and manual reprocessing workflows. This template models the critical error handling pattern for asynchronous messaging systems, ensuring no message is silently lost when processing fails. Essential for building reliable event-driven systems with proper failure recovery mechanisms.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "incident",
"secondaryUseCases": [
"compliance"
],
"useCases": [
"incident",
"compliance"
],
"complexity": 3,
"numNodes": 16,
"numLanes": 3,
"tags": [
"dead-letter-queue",
"dlq",
"retry-policy",
"message-processing",
"error-handling",
"operations-alerting",
"message-reliability",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "incident/architecture/event-driven-dead-letter-queue-architecture"
},
{
"slug": "cqrs-read-write-separation-architecture",
"title": "CQRS Read-Write Separation Architecture",
"description": "A CQRS read-write separation architecture diagram with dedicated command and query paths, PostgreSQL for writes, Redis or Elasticsearch for optimized reads, and an event-driven synchronization layer with lag monitoring. This template demonstrates the core CQRS principle of separating read and write models to independently scale and optimize each path. Ideal for applications with asymmetric read/write ratios where query performance is critical.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"cqrs",
"read-write-separation",
"command-query",
"postgresql",
"redis",
"elasticsearch",
"read-model-sync",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/cqrs-read-write-separation-architecture"
},
{
"slug": "cqrs-materialized-view-architecture",
"title": "CQRS Materialized View Architecture",
"description": "A CQRS materialized view architecture diagram with multiple projectors building purpose-specific read models: order summaries, customer dashboards, analytics cubes, and search indexes, all fed from a single event stream. This template shows how to create multiple optimized query views from the same write events, each tailored to a specific use case with sub-millisecond read latency. Perfect for systems requiring diverse query patterns from a single data source.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"materialized-view",
"cqrs",
"projectors",
"read-model",
"denormalization",
"query-optimization",
"event-stream",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/cqrs-materialized-view-architecture"
},
{
"slug": "cqrs-task-based-ui-architecture",
"title": "CQRS Task-Based UI Architecture",
"description": "A CQRS task-based UI architecture diagram where the frontend captures user intent as explicit commands, submits them asynchronously with optimistic updates, and receives real-time confirmations via WebSocket when the read model is synchronized. This template models the modern UI pattern that replaces CRUD forms with intent-driven commands, enabling responsive user experiences with eventual consistency. Recommended for teams building reactive frontends on CQRS backends.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 19,
"numLanes": 4,
"tags": [
"task-based-ui",
"cqrs",
"optimistic-update",
"websocket",
"command-pattern",
"idempotency",
"reactive-ui",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/cqrs-task-based-ui-architecture"
},
{
"slug": "serverless-api-backend-architecture",
"title": "Serverless API Backend Architecture",
"description": "A serverless API backend architecture diagram with API Gateway, Lambda authorizer functions, business logic functions, and managed cloud services including DynamoDB, S3, SQS, and SNS for a fully managed, auto-scaling backend. This template models the serverless-first approach where infrastructure management is eliminated entirely, with pay-per-invocation pricing and automatic scaling to zero. Essential for startups and teams building cost-efficient, event-driven API backends.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 3,
"numNodes": 15,
"numLanes": 3,
"tags": [
"serverless",
"aws-lambda",
"api-gateway",
"dynamodb",
"cloud-architecture",
"auto-scaling",
"pay-per-use",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "mcp/architecture/serverless-api-backend-architecture"
},
{
"slug": "serverless-event-processing-architecture",
"title": "Serverless Event Processing Architecture",
"description": "A serverless event processing architecture diagram with S3, DynamoDB Streams, API Gateway, and CloudWatch triggers invoking Lambda functions, orchestrated by Step Functions with fan-out via SQS and dead letter queue error handling. This template shows how to build complex event processing pipelines entirely from managed serverless components, with no servers to provision or manage. Ideal for data processing workflows that need elastic scaling and built-in fault tolerance.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 17,
"numLanes": 4,
"tags": [
"serverless",
"event-processing",
"step-functions",
"lambda-triggers",
"sqs",
"s3-events",
"dynamodb-streams",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/serverless-event-processing-architecture"
},
{
"slug": "serverless-step-functions-orchestration-architecture",
"title": "Serverless Step Functions Orchestration Architecture",
"description": "An AWS Step Functions orchestration architecture diagram with state machine workflows including choice states, parallel processing, wait-for-callback patterns, and compensation rollback for failed steps. This template models serverless workflow orchestration where complex multi-step processes are defined as state machines with built-in error handling and retry logic. Critical for teams building reliable serverless workflows that require human approval or long-running processes.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "incident",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"incident",
"ai-orchestration"
],
"complexity": 4,
"numNodes": 17,
"numLanes": 3,
"tags": [
"step-functions",
"serverless-orchestration",
"state-machine",
"workflow-automation",
"callback-pattern",
"compensation",
"aws",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "incident/architecture/serverless-step-functions-orchestration-architecture"
},
{
"slug": "serverless-edge-computing-architecture",
"title": "Serverless Edge Computing Architecture",
"description": "A serverless edge computing architecture diagram with CloudFront or Cloudflare edge locations, Lambda@Edge functions for A/B testing and geo-personalization, origin shield request collapsing, and cache-first response strategies. This template visualizes how computation moves to the network edge for ultra-low latency responses, with edge functions modifying requests and responses before they reach the origin. Essential for performance-critical applications serving global audiences.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 3,
"numNodes": 15,
"numLanes": 3,
"tags": [
"edge-computing",
"lambda-at-edge",
"cloudfront",
"cloudflare",
"cdn",
"geo-routing",
"cache-strategy",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "handoff/architecture/serverless-edge-computing-architecture"
},
{
"slug": "serverless-data-pipeline-architecture",
"title": "Serverless Data Pipeline Architecture",
"description": "A serverless data pipeline architecture diagram with Kinesis ingestion, Lambda transformation functions, S3 data lake storage zones (raw and curated), Glue catalog registration, and Athena query engine feeding QuickSight dashboards and SageMaker ML models. This template models a complete serverless ETL pipeline from data ingestion through transformation, cataloging, and analytics without managing any infrastructure. Ideal for data teams building cost-effective analytics platforms.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 4,
"numNodes": 17,
"numLanes": 4,
"tags": [
"serverless-data-pipeline",
"kinesis",
"glue",
"athena",
"s3-data-lake",
"etl",
"sagemaker",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "delivery/architecture/serverless-data-pipeline-architecture"
},
{
"slug": "serverless-multi-cloud-architecture",
"title": "Serverless Multi-Cloud Architecture",
"description": "A multi-cloud serverless architecture diagram with DNS-based traffic routing between AWS and Azure regions, automatic failover on health check failures, and bi-directional data replication with conflict resolution across cloud providers. This template models the multi-cloud strategy for maximum availability and vendor independence, using serverless services from both AWS (Lambda, DynamoDB) and Azure (Functions, Cosmos DB). Critical for enterprises requiring cloud provider redundancy.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"multi-cloud",
"aws",
"azure",
"cloud-failover",
"dns-routing",
"data-replication",
"vendor-independence",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "handoff/architecture/serverless-multi-cloud-architecture"
},
{
"slug": "saga-orchestration-pattern-architecture",
"title": "Saga Orchestration Pattern Architecture",
"description": "A saga orchestration architecture diagram with a central orchestrator coordinating multi-step distributed transactions across Order, Inventory, and Payment services, with a dedicated compensation chain for rollback on failure. This template models the orchestration-based saga pattern where a single coordinator manages the transaction lifecycle and triggers compensating actions when any step fails. Essential for architects implementing reliable distributed transactions without two-phase commit.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"delivery",
"ai-orchestration"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 5,
"tags": [
"saga-pattern",
"orchestration",
"distributed-transaction",
"compensation",
"microservices",
"rollback",
"consistency",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "delivery/architecture/saga-orchestration-pattern-architecture"
},
{
"slug": "saga-choreography-pattern-architecture",
"title": "Saga Choreography Pattern Architecture",
"description": "A saga choreography architecture diagram where Order, Payment, and Inventory services coordinate through domain events without a central orchestrator, with each service publishing and subscribing to events that drive the transaction forward or trigger compensation. This template models the decentralized saga approach where services autonomously react to events, reducing single points of failure at the cost of increased complexity in tracking saga state. Best for teams preferring service autonomy over centralized control.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 18,
"numLanes": 5,
"tags": [
"saga-choreography",
"event-driven-saga",
"decentralized",
"domain-events",
"compensation",
"autonomous-services",
"distributed-transaction",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/saga-choreography-pattern-architecture"
},
{
"slug": "saga-distributed-transaction-architecture",
"title": "Saga Distributed Transaction Architecture",
"description": "A distributed transaction architecture diagram implementing the two-phase commit protocol with a transaction coordinator sending prepare and commit messages to participating services, with global abort on any vote failure. This template visualizes the classic 2PC protocol used when strong consistency is required across multiple services, showing the prepare, vote, and commit/abort phases. Important for understanding distributed consensus trade-offs in microservices architectures.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "ai-orchestration",
"secondaryUseCases": [],
"useCases": [
"ai-orchestration"
],
"complexity": 4,
"numNodes": 17,
"numLanes": 4,
"tags": [
"distributed-transaction",
"two-phase-commit",
"2pc",
"transaction-coordinator",
"consensus",
"strong-consistency",
"prepare-commit",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "ai-orchestration/architecture/saga-distributed-transaction-architecture"
},
{
"slug": "saga-travel-booking-architecture",
"title": "Saga Travel Booking Architecture",
"description": "A travel booking saga architecture diagram orchestrating flight, hotel, and car rental reservations as a single distributed transaction, with automatic compensation to cancel all bookings if any reservation step fails. This template models the classic saga use case where multiple independent services must either all succeed or all roll back, ensuring travelers never end up with partial bookings. Perfect for demonstrating saga patterns with a real-world business scenario.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "ai-orchestration",
"secondaryUseCases": [],
"useCases": [
"ai-orchestration"
],
"complexity": 4,
"numNodes": 17,
"numLanes": 5,
"tags": [
"saga-pattern",
"travel-booking",
"flight-reservation",
"hotel-booking",
"compensation",
"distributed-transaction",
"orchestration",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "ai-orchestration/architecture/saga-travel-booking-architecture"
},
{
"slug": "saga-order-fulfillment-architecture",
"title": "Saga Order Fulfillment Architecture",
"description": "An order fulfillment saga architecture diagram with four sequential steps: customer verification, inventory reservation, payment authorization, and shipment creation, with a compensation chain that reverses completed steps on failure. This template models the end-to-end order lifecycle as a saga, showing how each service participates in the transaction and how compensating actions maintain data consistency. Ideal for e-commerce architects designing reliable order processing pipelines.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "approval",
"secondaryUseCases": [
"billing",
"security"
],
"useCases": [
"approval",
"billing",
"security"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 3,
"tags": [
"order-fulfillment",
"saga-pattern",
"e-commerce",
"payment-authorization",
"inventory-reservation",
"compensation-chain",
"distributed-transaction",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "approval/architecture/saga-order-fulfillment-architecture"
},
{
"slug": "circuit-breaker-resilience-architecture",
"title": "Circuit Breaker Resilience Architecture",
"description": "A circuit breaker resilience architecture diagram showing the complete state machine with closed, open, and half-open states, failure threshold tracking, recovery timer, and fallback response strategies for protecting services from cascading failures. This template visualizes the circuit breaker pattern in detail, including how the breaker transitions between states based on success and failure counts. Essential for building fault-tolerant microservices that degrade gracefully under load.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 3,
"tags": [
"circuit-breaker",
"resilience",
"fault-tolerance",
"cascading-failure",
"half-open-state",
"fallback",
"state-machine",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "mcp/architecture/circuit-breaker-resilience-architecture"
},
{
"slug": "bulkhead-isolation-architecture",
"title": "Bulkhead Isolation Architecture",
"description": "A bulkhead isolation architecture diagram with separate thread pools for critical, standard, and batch workloads, each with independent connection pools, exhaustion detection, and backpressure strategies to prevent one workload from starving others. This template models the bulkhead pattern inspired by ship hull compartments, where resource isolation ensures that a failure or overload in one component cannot cascade to others. Critical for systems requiring guaranteed availability for high-priority operations.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"bulkhead-pattern",
"resource-isolation",
"thread-pool",
"backpressure",
"fault-isolation",
"resilience",
"priority-routing",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "handoff/architecture/bulkhead-isolation-architecture"
},
{
"slug": "retry-with-exponential-backoff-architecture",
"title": "Retry with Exponential Backoff Architecture",
"description": "A retry with exponential backoff architecture diagram showing the complete retry policy engine with retryable vs non-retryable error classification, exponential delay calculation with jitter, max retry thresholds, and graceful exhaustion handling. This template models the essential resilience pattern for handling transient failures in distributed systems, preventing thundering herd problems through randomized backoff delays. Foundational for any service-to-service communication in cloud architectures.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 17,
"numLanes": 3,
"tags": [
"retry-pattern",
"exponential-backoff",
"jitter",
"transient-failure",
"resilience",
"error-handling",
"thundering-herd",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/retry-with-exponential-backoff-architecture"
},
{
"slug": "rate-limiter-architecture",
"title": "Rate Limiter Architecture",
"description": "A rate limiter architecture diagram implementing the token bucket algorithm with Redis-backed distributed counters, sliding window logs, API key identification, rate limit headers, and multi-node synchronization for consistent enforcement. This template shows how to protect APIs from abuse and ensure fair usage across clients, with proper HTTP 429 responses and Retry-After headers. Essential for API platform teams building production-grade rate limiting infrastructure.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 17,
"numLanes": 4,
"tags": [
"rate-limiter",
"token-bucket",
"sliding-window",
"redis",
"api-protection",
"throttling",
"distributed-rate-limiting",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/rate-limiter-architecture"
},
{
"slug": "health-check-pattern-architecture",
"title": "Health Check Pattern Architecture",
"description": "A health check pattern architecture diagram with load balancer probes, deep health checks verifying database, cache, disk, and dependency status, automatic instance rotation, and alerting integration with PagerDuty for consecutive failures. This template models the health monitoring infrastructure that enables self-healing systems, where unhealthy instances are automatically removed from rotation and operations teams are alerted. Key for building production-ready services with proper observability.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "incident",
"secondaryUseCases": [
"security"
],
"useCases": [
"incident",
"security"
],
"complexity": 3,
"numNodes": 19,
"numLanes": 4,
"tags": [
"health-check",
"load-balancer",
"self-healing",
"monitoring",
"pagerduty",
"instance-rotation",
"deep-health-check",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "incident/architecture/health-check-pattern-architecture"
},
{
"slug": "hexagonal-ports-adapters-architecture",
"title": "Hexagonal (Ports and Adapters) Architecture",
"description": "A hexagonal architecture diagram showing the clean separation between domain core, inbound adapters (REST, GraphQL, CLI, message consumers), outbound adapters (PostgreSQL, Stripe, email, Redis), and the port interfaces that connect them. This template visualizes the ports and adapters pattern where the domain core has zero dependencies on infrastructure, making it fully testable and technology-agnostic. Foundational for teams adopting clean architecture principles in their codebase.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 16,
"numLanes": 4,
"tags": [
"hexagonal-architecture",
"ports-and-adapters",
"clean-architecture",
"dependency-inversion",
"domain-core",
"testability",
"technology-agnostic",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/hexagonal-ports-adapters-architecture"
},
{
"slug": "clean-architecture-layers",
"title": "Clean Architecture Layers",
"description": "A clean architecture layers diagram showing the four concentric layers: Entities (domain), Use Cases (application), Interface Adapters (controllers, presenters, repositories), and Frameworks & Drivers (web server, database, cloud SDK). This template models Uncle Bob's Clean Architecture with the dependency rule where inner layers never depend on outer layers, ensuring the domain model remains pure and framework-independent. Essential reference for software architects enforcing architectural boundaries.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 16,
"numLanes": 4,
"tags": [
"clean-architecture",
"uncle-bob",
"dependency-rule",
"layered-architecture",
"use-cases",
"entities",
"interface-adapters",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/clean-architecture-layers"
},
{
"slug": "domain-driven-design-bounded-contexts-architecture",
"title": "Domain-Driven Design Bounded Contexts Architecture",
"description": "A DDD bounded contexts architecture diagram with Order, Customer, Shipping, and Billing contexts connected through an anti-corruption layer, shared kernel, and context map defining integration relationships. This template visualizes the strategic DDD patterns for decomposing complex domains into autonomous bounded contexts that communicate through well-defined integration events. Critical for architects applying Domain-Driven Design to large-scale enterprise systems.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 18,
"numLanes": 5,
"tags": [
"domain-driven-design",
"bounded-context",
"anti-corruption-layer",
"context-map",
"shared-kernel",
"strategic-ddd",
"aggregate",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/domain-driven-design-bounded-contexts-architecture"
},
{
"slug": "api-composition-pattern-architecture",
"title": "API Composition Pattern Architecture",
"description": "An API composition architecture diagram with a composer service that fans out parallel requests to multiple microservices, collects responses with timeout handling, and merges results into a single unified response with partial fallback support. This template models the API composition pattern used when a single client query requires data from multiple services, avoiding the need for direct service-to-service calls. Useful for teams building aggregation layers in microservices architectures.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "incident",
"secondaryUseCases": [],
"useCases": [
"incident"
],
"complexity": 3,
"numNodes": 16,
"numLanes": 3,
"tags": [
"api-composition",
"response-aggregation",
"fan-out",
"parallel-requests",
"timeout-handling",
"partial-response",
"microservices",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "incident/architecture/api-composition-pattern-architecture"
},
{
"slug": "outbox-pattern-reliable-messaging-architecture",
"title": "Outbox Pattern for Reliable Messaging Architecture",
"description": "A transactional outbox architecture diagram where domain writes and event publishing happen in the same database transaction, with a relay process polling the outbox table and publishing events to a message broker with guaranteed delivery. This template solves the dual-write problem where updating a database and publishing an event are not atomic, ensuring exactly-once event delivery without distributed transactions. Critical for event-driven architectures requiring reliable message publishing.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"outbox-pattern",
"transactional-outbox",
"reliable-messaging",
"dual-write",
"exactly-once",
"debezium",
"event-publishing",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/outbox-pattern-reliable-messaging-architecture"
},
{
"slug": "ambassador-pattern-architecture",
"title": "Ambassador Pattern Architecture",
"description": "An ambassador pattern architecture diagram with a local proxy sidecar handling authentication header injection, circuit breaking, retry logic, and metrics collection for outbound requests to external third-party APIs. This template models the ambassador pattern where a helper service running alongside the application offloads cross-cutting concerns for external communication. Useful for teams integrating with unreliable third-party services that need resilience wrappers.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 3,
"numNodes": 15,
"numLanes": 3,
"tags": [
"ambassador-pattern",
"sidecar-proxy",
"external-api",
"retry-logic",
"circuit-breaker",
"metrics-collection",
"cross-cutting-concerns",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "mcp/architecture/ambassador-pattern-architecture"
},
{
"slug": "graphql-federation-architecture",
"title": "GraphQL Federation Architecture",
"description": "A GraphQL federation architecture diagram with an Apollo Gateway building query plans and fanning out to User, Product, and Review subgraphs, each owning its schema and database, with response stitching into a unified GraphQL result. This template models the federated GraphQL approach where multiple teams independently develop and deploy their subgraphs while clients see a single unified API. Ideal for organizations scaling GraphQL across multiple teams and services.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 3,
"numNodes": 15,
"numLanes": 3,
"tags": [
"graphql-federation",
"apollo-gateway",
"subgraph",
"schema-stitching",
"query-plan",
"federated-api",
"graphql",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "mcp/architecture/graphql-federation-architecture"
},
{
"slug": "zero-trust-security-architecture",
"title": "Zero Trust Security Architecture",
"description": "A zero trust security architecture diagram with device posture checks, MFA identity verification, risk-based policy decisions, short-lived JWT tokens, micro-segmentation, mTLS encryption, least-privilege access enforcement, and continuous monitoring. This template models the 'never trust, always verify' security paradigm where every request is authenticated and authorized regardless of network location. Essential for security architects implementing modern zero-trust frameworks in cloud-native environments.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "security",
"secondaryUseCases": [],
"useCases": [
"security"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 4,
"tags": [
"zero-trust",
"security-architecture",
"mfa",
"micro-segmentation",
"mtls",
"least-privilege",
"continuous-verification",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "security/architecture/zero-trust-security-architecture"
},
{
"slug": "multi-tenant-saas-architecture",
"title": "Multi-Tenant SaaS Architecture",
"description": "A multi-tenant SaaS architecture diagram with tenant identification, tier-based routing (shared vs dedicated pools), row-level security, per-tenant encryption keys, and isolated backup strategies for standard and enterprise isolation models. This template models the architecture decisions for building SaaS platforms that serve multiple customers from shared infrastructure while maintaining strict data isolation. Critical for SaaS architects balancing cost efficiency with enterprise security requirements.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "security",
"secondaryUseCases": [
"delivery"
],
"useCases": [
"security",
"delivery"
],
"complexity": 4,
"numNodes": 17,
"numLanes": 4,
"tags": [
"multi-tenant",
"saas-architecture",
"tenant-isolation",
"row-level-security",
"shared-infrastructure",
"enterprise-tier",
"data-isolation",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "security/architecture/multi-tenant-saas-architecture"
},
{
"slug": "kubernetes-container-orchestration-architecture",
"title": "Kubernetes Container Orchestration Architecture",
"description": "A Kubernetes container orchestration architecture diagram showing the control plane (API Server, etcd, Scheduler, Controller Manager), worker nodes (Kubelet, container runtime, kube-proxy, pods), networking layer (Ingress, Network Policy, Service Mesh), and persistent storage with CSI drivers. This template provides a comprehensive view of the Kubernetes architecture stack from control plane to storage layer. Foundational reference for DevOps engineers and platform teams managing Kubernetes clusters.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "ai-orchestration",
"secondaryUseCases": [],
"useCases": [
"ai-orchestration"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 4,
"tags": [
"kubernetes",
"container-orchestration",
"k8s",
"control-plane",
"worker-node",
"ingress",
"persistent-storage",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "ai-orchestration/architecture/kubernetes-container-orchestration-architecture"
},
{
"slug": "data-mesh-architecture",
"title": "Data Mesh Architecture",
"description": "A data mesh architecture diagram with domain-oriented data ownership across Sales, Marketing, and Finance domains, each exposing self-serve data products through APIs with quality SLAs, governed by a federated data platform with a shared catalog and cross-domain query engine. This template models the paradigm shift from centralized data teams to domain-owned data products, applying microservices principles to data architecture. Essential for organizations scaling data operations beyond centralized data warehouse bottlenecks.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 17,
"numLanes": 4,
"tags": [
"data-mesh",
"domain-ownership",
"data-product",
"self-serve-data",
"federated-governance",
"data-platform",
"data-architecture",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/data-mesh-architecture"
},
{
"slug": "cell-based-architecture",
"title": "Cell-Based Architecture",
"description": "A cell-based architecture diagram with geographic routing to independent, self-contained cells (US-East, EU-West), each with its own gateway, compute, database, cache, and message queue, plus shared services for cross-cell replication and global configuration. This template models the cell architecture pattern used by hyperscale systems to achieve blast radius isolation, where failures in one cell cannot affect users in another. Key for architects designing systems that require extreme availability and fault isolation.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "handoff",
"secondaryUseCases": [],
"useCases": [
"handoff"
],
"complexity": 4,
"numNodes": 20,
"numLanes": 4,
"tags": [
"cell-based-architecture",
"blast-radius",
"geographic-routing",
"fault-isolation",
"independent-cells",
"cross-cell-replication",
"hyperscale",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "handoff/architecture/cell-based-architecture"
},
{
"slug": "observability-three-pillars-architecture",
"title": "Observability Three Pillars Architecture",
"description": "An observability architecture diagram implementing the three pillars (metrics, traces, logs) with OpenTelemetry SDK instrumentation, OTLP collector pipeline, Prometheus, Jaeger, and Loki backends, Grafana dashboards, SLO/SLI tracking, and PagerDuty alerting integration. This template provides a complete observability stack reference showing how telemetry data flows from application instrumentation through collection, storage, visualization, and incident response. Essential for SRE teams building production monitoring infrastructure.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 17,
"numLanes": 4,
"tags": [
"observability",
"three-pillars",
"opentelemetry",
"prometheus",
"jaeger",
"loki",
"grafana",
"slo-sli",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/observability-three-pillars-architecture"
},
{
"slug": "gitops-deployment-architecture",
"title": "GitOps Deployment Architecture",
"description": "A GitOps deployment architecture diagram with developer Git workflow, CI/CD pipeline building and pushing container images, ArgoCD or Flux detecting Git manifest changes, drift detection, automatic cluster synchronization, and rolling update deployment to Kubernetes. This template models the GitOps paradigm where Git is the single source of truth for both application code and infrastructure state, enabling declarative, auditable, and reproducible deployments. Critical for teams adopting GitOps practices for Kubernetes deployments.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [],
"useCases": [
"delivery"
],
"complexity": 4,
"numNodes": 19,
"numLanes": 4,
"tags": [
"gitops",
"argocd",
"flux",
"kubernetes-deployment",
"declarative-infrastructure",
"drift-detection",
"rolling-update",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "delivery/architecture/gitops-deployment-architecture"
},
{
"slug": "ai-native-single-agent-architecture",
"title": "AI-Native Single Agent Architecture",
"description": "A single-agent AI architecture where one agent handles everything: parsing requests, reasoning, calling tools via MCP, and generating responses. This is the default architecture for prototypes and simple automations—easy to debug but hits context-window limits quickly and is hard to parallelize. Ideal for MVPs and solo builders shipping fast.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration",
"mcp"
],
"useCases": [
"agentic",
"ai-orchestration",
"mcp"
],
"complexity": 2,
"numNodes": 11,
"numLanes": 3,
"tags": [
"ai-native",
"single-agent",
"agentic-ai",
"mcp",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-native-single-agent-architecture"
},
{
"slug": "ai-native-sequential-pipeline-architecture",
"title": "AI-Native Sequential Pipeline Architecture",
"description": "A sequential pipeline architecture chaining multiple agents in a fixed order (parse → enrich → analyze → format), which is a common 'LLM microservices' setup when each step can be isolated. This structure is often used in document processing and ETL-like workflows because each step is testable and predictable.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [
"agentic",
"ai-orchestration"
],
"useCases": [
"delivery",
"agentic",
"ai-orchestration"
],
"complexity": 2,
"numNodes": 7,
"numLanes": 2,
"tags": [
"ai-native",
"sequential-pipeline",
"agentic-ai",
"llm-microservices",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "delivery/architecture/ai-native-sequential-pipeline-architecture"
},
{
"slug": "ai-native-orchestrator-worker-architecture",
"title": "AI-Native Orchestrator-Worker Architecture",
"description": "An orchestrator-worker architecture where an orchestrator agent breaks a goal into subtasks, dispatches to specialized workers, then synthesizes a final response. This is the most common 'agent orchestration' architecture—powerful but the orchestrator can become a bottleneck as the number of workers grows. Frameworks like LangGraph focus on explicit routing/state to manage this.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"agentic",
"ai-orchestration"
],
"complexity": 3,
"numNodes": 14,
"numLanes": 4,
"tags": [
"ai-native",
"orchestrator-worker",
"agentic-ai",
"langgraph",
"multi-agent",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-native-orchestrator-worker-architecture"
},
{
"slug": "ai-native-hierarchical-architecture",
"title": "AI-Native Hierarchical Architecture",
"description": "A hierarchical multi-agent architecture that scales orchestration by stacking supervisors and team leads (a tree structure), which mirrors enterprise org structures and helps partition context. This is the 'enterprise-grade agentic AI architecture' when a single orchestrator cannot manage all workers directly. Ideal for large enterprises and multi-domain workflows.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"agentic",
"ai-orchestration"
],
"complexity": 4,
"numNodes": 16,
"numLanes": 4,
"tags": [
"ai-native",
"hierarchical",
"agentic-ai",
"enterprise",
"multi-agent",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-native-hierarchical-architecture"
},
{
"slug": "ai-native-parallel-fan-out-architecture",
"title": "AI-Native Parallel Fan-Out Architecture",
"description": "A parallel fan-out architecture that runs multiple agents simultaneously on independent checks (style, security, performance) and then merges results. This is a standard multi-agent design approach for throughput, mapping cleanly to CI/CD, incident response, and research. Fan-in reconciliation becomes the subtle part.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [
"agentic",
"ai-orchestration"
],
"useCases": [
"delivery",
"agentic",
"ai-orchestration"
],
"complexity": 3,
"numNodes": 11,
"numLanes": 2,
"tags": [
"ai-native",
"parallel-fan-out",
"agentic-ai",
"map-reduce",
"ci-cd",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "delivery/architecture/ai-native-parallel-fan-out-architecture"
},
{
"slug": "ai-native-event-driven-kafka-architecture",
"title": "AI-Native Event-Driven Kafka Architecture",
"description": "An event-driven agentic AI architecture that replaces the central orchestrator with Kafka/PubSub topics: agents subscribe, react, and publish new events. This aligns multi-agent systems with proven microservices choreography and is ideal for real-time, high-throughput systems and 'agent mesh' setups.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration",
"mcp"
],
"useCases": [
"agentic",
"ai-orchestration",
"mcp"
],
"complexity": 3,
"numNodes": 12,
"numLanes": 5,
"tags": [
"ai-native",
"event-driven",
"agentic-ai",
"kafka",
"pub-sub",
"agent-mesh",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-native-event-driven-kafka-architecture"
},
{
"slug": "ai-native-generator-critic-architecture",
"title": "AI-Native Generator-Critic Architecture",
"description": "A competitive / generator-critic architecture where multiple generators produce independent answers, then an evaluator agent scores and selects the best output. This approach improves quality and reduces single-model brittleness. It's costlier (multiple LLM calls) but pays off when correctness or creativity matters more than latency.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"agentic",
"ai-orchestration"
],
"complexity": 3,
"numNodes": 9,
"numLanes": 3,
"tags": [
"ai-native",
"generator-critic",
"agentic-ai",
"tournament-mode",
"multi-agent",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-native-generator-critic-architecture"
},
{
"slug": "event-driven-notification-hub-architecture",
"title": "Event-Driven Notification Hub Architecture",
"description": "An event-driven notification hub architecture diagram with multi-source event ingestion, template-based message rendering, user preference routing across email (SendGrid/SES), push (FCM), SMS (Twilio), and Slack channels, with delivery tracking and retry mechanisms. This template models a centralized notification system that decouples business services from delivery infrastructure, supporting multi-channel communication with user-controlled preferences. Ideal for platform teams building scalable notification infrastructure.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 4,
"numNodes": 20,
"numLanes": 3,
"tags": [
"notification-hub",
"multi-channel",
"event-driven",
"sendgrid",
"firebase-cloud-messaging",
"twilio",
"delivery-tracking",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "uncategorized/architecture/event-driven-notification-hub-architecture"
},
{
"slug": "agentic-supervisor-worker",
"title": "Agentic Supervisor-Worker Architecture",
"description": "A supervisor-worker multi-agent architecture where an orchestrator agent receives a high-level goal, breaks it into subtasks, delegates each to specialist worker agents (researcher, writer, QA), monitors execution, handles failures, and synthesizes results. The orchestrator manages but does not execute tasks itself.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [],
"useCases": [
"agentic"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 4,
"tags": [
"agentic",
"supervisor-worker",
"multi-agent",
"orchestrator",
"architecture-diagram",
"ai-team"
],
"sourcePath": "",
"repoPath": "agentic/architecture/agentic-supervisor-worker"
},
{
"slug": "agentic-sequential-pipeline",
"title": "Agentic Sequential Pipeline Architecture",
"description": "A sequential pipeline multi-agent architecture where agents are arranged in a strict sequence. Each agent transforms or enriches the output of the previous one, then passes it forward. No central orchestrator — the flow is deterministic like an assembly line.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [
"agentic",
"ai-orchestration"
],
"useCases": [
"delivery",
"agentic",
"ai-orchestration"
],
"complexity": 2,
"numNodes": 5,
"numLanes": 5,
"tags": [
"agentic",
"sequential-pipeline",
"multi-agent",
"assembly-line",
"architecture-diagram",
"ai-team"
],
"sourcePath": "",
"repoPath": "delivery/architecture/agentic-sequential-pipeline"
},
{
"slug": "agentic-swarm",
"title": "Agentic Swarm Architecture",
"description": "A swarm multi-agent architecture where multiple agents work on the same or related tasks simultaneously, with no central coordinator. Their outputs are then aggregated, voted on, or merged by a dedicated aggregator node. Agents may compete — the best output wins.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [],
"useCases": [
"agentic"
],
"complexity": 3,
"numNodes": 6,
"numLanes": 5,
"tags": [
"agentic",
"swarm",
"multi-agent",
"parallel",
"aggregator",
"architecture-diagram",
"ai-team"
],
"sourcePath": "",
"repoPath": "agentic/architecture/agentic-swarm"
},
{
"slug": "agentic-hierarchical",
"title": "Agentic Hierarchical Architecture",
"description": "A hierarchical multi-agent architecture with multi-level organizational structure. A top-level executive agent manages mid-level team lead agents, who each manage their own pool of specialist workers. Teams within teams — the hierarchy maps to domain separation.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [],
"useCases": [
"agentic"
],
"complexity": 4,
"numNodes": 8,
"numLanes": 7,
"tags": [
"agentic",
"hierarchical",
"multi-agent",
"enterprise",
"architecture-diagram",
"ai-team"
],
"sourcePath": "",
"repoPath": "agentic/architecture/agentic-hierarchical"
},
{
"slug": "agentic-team-of-rivals",
"title": "Agentic Team of Rivals Architecture",
"description": "The most architecturally sophisticated multi-agent pattern. Agents are assigned not just roles but opposing incentives. A Planner is optimistic about goal completion. A Critic is constitutionally skeptical and holds veto authority. Errors get caught through adversarial pressure rather than trusting a single model's self-assessment.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [],
"useCases": [
"agentic"
],
"complexity": 3,
"numNodes": 5,
"numLanes": 3,
"tags": [
"agentic",
"team-of-rivals",
"multi-agent",
"critic",
"veto",
"architecture-diagram",
"ai-team"
],
"sourcePath": "",
"repoPath": "agentic/architecture/agentic-team-of-rivals"
},
{
"slug": "ai-orchestration-single-agent",
"title": "AI Orchestration - Single Agent (Monolith)",
"description": "The simplest AI-native architecture — a single agent that receives user input, reasons, plans, decides on tool calls, processes results, and generates responses. Direct MCP connection over stdio or HTTP. Best for MVPs and when low latency matters.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "ai-orchestration",
"secondaryUseCases": [
"mcp"
],
"useCases": [
"ai-orchestration",
"mcp"
],
"complexity": 2,
"numNodes": 12,
"numLanes": 3,
"tags": [
"ai-native",
"single-agent",
"monolith",
"mcp",
"architecture-diagram",
"orchestration"
],
"sourcePath": "",
"repoPath": "ai-orchestration/architecture/ai-orchestration-single-agent"
},
{
"slug": "ai-orchestration-sequential-pipeline",
"title": "AI Orchestration - Sequential Pipeline",
"description": "An assembly-line architecture where agents are arranged in a strict sequence. Each agent transforms or enriches the output of the previous one, then passes it forward. Best for tasks with clear sequential dependencies — document processing, content production pipelines, compliance workflows.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "delivery",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"delivery",
"ai-orchestration"
],
"complexity": 2,
"numNodes": 5,
"numLanes": 2,
"tags": [
"ai-native",
"sequential-pipeline",
"assembly-line",
"architecture-diagram",
"orchestration"
],
"sourcePath": "",
"repoPath": "delivery/architecture/ai-orchestration-sequential-pipeline"
},
{
"slug": "ai-orchestration-orchestrator-worker",
"title": "AI Orchestration - Orchestrator-Worker",
"description": "A conductor-style architecture where one orchestrator agent receives a complex task, breaks it into subtasks, dispatches each to specialist worker agents (research, code, review), collects results, and synthesizes the final answer. Best for complex multi-step tasks with dynamic decomposition.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"agentic",
"ai-orchestration"
],
"complexity": 3,
"numNodes": 15,
"numLanes": 5,
"tags": [
"ai-native",
"orchestrator-worker",
"conductor",
"multi-agent",
"architecture-diagram",
"orchestration"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-orchestration-orchestrator-worker"
},
{
"slug": "ai-orchestration-hierarchical",
"title": "AI Orchestration - Hierarchical (Org Chart)",
"description": "An org-chart architecture with multi-level structure. A top-level supervisor manages team leads, who each manage their own pool of specialist workers. Teams within teams. Best for enterprise-scale automation with 10+ specialized agents spanning multiple domains.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"agentic",
"ai-orchestration"
],
"complexity": 4,
"numNodes": 17,
"numLanes": 5,
"tags": [
"ai-native",
"hierarchical",
"org-chart",
"enterprise",
"multi-agent",
"architecture-diagram",
"orchestration"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-orchestration-hierarchical"
},
{
"slug": "ai-orchestration-parallel-fan-out",
"title": "AI Orchestration - Parallel Fan-Out (Map-Reduce)",
"description": "A map-reduce style architecture where a coordinator fans out tasks to multiple parallel worker agents (style check, security audit, performance analysis), gathers all results, and makes an aggregate decision. Best for PR reviews, code reviews, and multi-dimensional analysis.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"agentic",
"ai-orchestration"
],
"complexity": 3,
"numNodes": 9,
"numLanes": 3,
"tags": [
"ai-native",
"parallel-fan-out",
"map-reduce",
"coordinator",
"multi-agent",
"architecture-diagram",
"orchestration"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-orchestration-parallel-fan-out"
},
{
"slug": "ai-orchestration-event-driven-mesh",
"title": "AI Orchestration - Event-Driven Mesh (Kafka-First)",
"description": "An event-driven agent mesh architecture using a Kafka-style event broker. Multiple agents subscribe to topics (orders, alerts, analytics), process events independently, and publish results back to the bus. Best for real-time event processing and decoupled service architectures.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "ai-orchestration",
"secondaryUseCases": [
"mcp"
],
"useCases": [
"ai-orchestration",
"mcp"
],
"complexity": 3,
"numNodes": 13,
"numLanes": 5,
"tags": [
"ai-native",
"event-driven",
"kafka",
"agent-mesh",
"pub-sub",
"architecture-diagram",
"orchestration"
],
"sourcePath": "",
"repoPath": "ai-orchestration/architecture/ai-orchestration-event-driven-mesh"
},
{
"slug": "ai-orchestration-competitive-generator-critic",
"title": "AI Orchestration - Competitive Generator-Critic",
"description": "A tournament-mode architecture where multiple generator agents produce independent outputs in parallel, then an evaluator agent scores and selects the best. Quality threshold checking with refinement loops. Best when correctness or creativity matters more than latency.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"ai-orchestration"
],
"useCases": [
"agentic",
"ai-orchestration"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"ai-native",
"competitive",
"generator-critic",
"tournament",
"multi-agent",
"architecture-diagram",
"orchestration"
],
"sourcePath": "",
"repoPath": "agentic/architecture/ai-orchestration-competitive-generator-critic"
},
{
"slug": "mcp-direct-connect",
"title": "MCP Direct Connect Architecture",
"description": "The simplest MCP pattern — direct connection between host application and MCP server over stdio or HTTP. No extra hops, lowest latency, easiest debugging. Perfect for MVPs, hackathons, and single-team setups where security governance is not yet a concern.",
"kind": "architecture",
"sourceDomain": "DevOps",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 1,
"numNodes": 6,
"numLanes": 2,
"tags": [
"mcp",
"direct-connect",
"stdio",
"http",
"architecture-diagram",
"production-grade"
],
"sourcePath": "",
"repoPath": "mcp/devops/mcp-direct-connect"
},
{
"slug": "mcp-gateway-proxy",
"title": "MCP Gateway Proxy Architecture",
"description": "An API gateway pattern that sits between agents and MCP servers to handle authentication, rate limits, and auditing. The gateway enforces OAuth 2.0, SAML, SSO, tool-level rate limiting, and team-based quotas. Essential for multi-team or multi-tenant MCP deployments.",
"kind": "architecture",
"sourceDomain": "DevOps",
"primaryUseCase": "security",
"secondaryUseCases": [
"compliance",
"mcp"
],
"useCases": [
"security",
"compliance",
"mcp"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 3,
"tags": [
"mcp",
"gateway",
"proxy",
"oauth",
"rate-limiting",
"audit",
"architecture-diagram",
"production-grade"
],
"sourcePath": "",
"repoPath": "security/devops/mcp-gateway-proxy"
},
{
"slug": "mcp-tool-router",
"title": "MCP Tool Router Architecture",
"description": "A routing pattern that puts a semantic router in front of MCP tools so the LLM only sees the subset it needs. Uses vector embeddings and cosine similarity to match user intent to tools dynamically. Achieves up to 96% reduction in input tokens when dealing with large tool catalogs.",
"kind": "architecture",
"sourceDomain": "DevOps",
"primaryUseCase": "handoff",
"secondaryUseCases": [
"mcp"
],
"useCases": [
"handoff",
"mcp"
],
"complexity": 3,
"numNodes": 8,
"numLanes": 4,
"tags": [
"mcp",
"tool-router",
"semantic-routing",
"embeddings",
"token-optimization",
"architecture-diagram",
"production-grade"
],
"sourcePath": "",
"repoPath": "handoff/devops/mcp-tool-router"
},
{
"slug": "mcp-agent-mesh",
"title": "MCP Agent Mesh Architecture",
"description": "A multi-agent mesh pattern where agents communicate through a shared context broker backed by MCP. Enables coordinated tool access and state synchronization across multiple specialized agents (planner, coder, reviewer, operator). Supports both orchestrated and choreographed interaction patterns.",
"kind": "architecture",
"sourceDomain": "DevOps",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"mcp"
],
"useCases": [
"agentic",
"mcp"
],
"complexity": 4,
"numNodes": 10,
"numLanes": 4,
"tags": [
"mcp",
"agent-mesh",
"shared-context",
"multi-agent",
"broker",
"architecture-diagram",
"production-grade"
],
"sourcePath": "",
"repoPath": "agentic/devops/mcp-agent-mesh"
},
{
"slug": "mcp-circuit-breaker",
"title": "MCP Circuit Breaker Architecture",
"description": "A resilience pattern that wraps MCP calls with health-aware gates using three states: Closed (normal), Open (failures detected, fast-fail), and Half-Open (testing recovery). Prevents cascading failures when tools become unresponsive. Essential for production-grade reliability.",
"kind": "architecture",
"sourceDomain": "DevOps",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 3,
"numNodes": 9,
"numLanes": 3,
"tags": [
"mcp",
"circuit-breaker",
"resilience",
"fault-tolerance",
"health-check",
"architecture-diagram",
"production-grade"
],
"sourcePath": "",
"repoPath": "mcp/devops/mcp-circuit-breaker"
},
{
"slug": "mcp-context-proxy",
"title": "MCP Context Proxy Architecture",
"description": "A caching and compression layer that sits between agents and MCP servers, intercepting redundant context requests before they hit the wire. Uses TTL-based cache invalidation, Brotli compression, and semantic caching. Can achieve up to 95%+ token reduction and significantly lower LLM bills.",
"kind": "architecture",
"sourceDomain": "DevOps",
"primaryUseCase": "mcp",
"secondaryUseCases": [],
"useCases": [
"mcp"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 3,
"tags": [
"mcp",
"context-proxy",
"caching",
"compression",
"token-optimization",
"architecture-diagram",
"production-grade"
],
"sourcePath": "",
"repoPath": "mcp/devops/mcp-context-proxy"
},
{
"slug": "context-session-memory",
"title": "Context Management - Session Memory",
"description": "Short-term context pattern where the channel sends new messages plus recent history. The agent runtime merges that with local session state, assembles the prompt, and persists the response back into history. Simple but cost and latency grow with history length.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "context-management",
"secondaryUseCases": [],
"useCases": [
"context-management"
],
"complexity": 2,
"numNodes": 9,
"numLanes": 3,
"tags": [
"context-management",
"session-memory",
"short-term",
"memory",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "context-management/architecture/context-session-memory"
},
{
"slug": "context-rolling-summary-memory",
"title": "Context Management - Rolling Summary Memory",
"description": "Compressed history pattern that keeps full history for a while, then when a threshold is hit, summarizes the last chunk and replaces detailed turns with a shorter summary message. Dramatically reduces prompt size on long-running chats while maintaining gist continuity.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "context-management",
"secondaryUseCases": [],
"useCases": [
"context-management"
],
"complexity": 3,
"numNodes": 8,
"numLanes": 4,
"tags": [
"context-management",
"rolling-summary",
"compression",
"memory",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "context-management/architecture/context-rolling-summary-memory"
},
{
"slug": "context-profile-memory",
"title": "Context Management - Profile Memory",
"description": "Identity-style memory pattern where profile data is loaded at session start. Each prompt combines system persona, user profile, and current message. New facts can be written back to profile memory. Small predictable overhead with big UX lift — the agent remembers your name, stack, tone, and constraints.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "context-management",
"secondaryUseCases": [],
"useCases": [
"context-management"
],
"complexity": 2,
"numNodes": 7,
"numLanes": 3,
"tags": [
"context-management",
"profile-memory",
"identity",
"user-profile",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "context-management/architecture/context-profile-memory"
},
{
"slug": "context-semantic-memory",
"title": "Context Management - Semantic Memory",
"description": "Vector-based memory pattern where text is chunked, embedded, and stored in a vector database. On query, the question is embedded, a vector search is run, candidates are reranked, and top results are injected into the prompt. Where the agent feels like it remembers everything without hallucinating.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "context-management",
"secondaryUseCases": [],
"useCases": [
"context-management"
],
"complexity": 3,
"numNodes": 9,
"numLanes": 4,
"tags": [
"context-management",
"semantic-memory",
"vector-db",
"embeddings",
"rag",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "context-management/architecture/context-semantic-memory"
},
{
"slug": "context-episodic-memory",
"title": "Context Management - Episodic Memory",
"description": "Learning-from-experience pattern where every task run becomes an episode with input, actions, and outcome. Before tackling a new task, the agent fetches similar episodes and uses them as hints. Over time, the agent feels like it's learning instead of repeating the same failed plans.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "context-management",
"secondaryUseCases": [],
"useCases": [
"context-management"
],
"complexity": 3,
"numNodes": 11,
"numLanes": 4,
"tags": [
"context-management",
"episodic-memory",
"learning",
"experience",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "context-management/architecture/context-episodic-memory"
},
{
"slug": "context-hybrid-retrieval-memory",
"title": "Context Management - Hybrid Retrieval Memory",
"description": "Multi-modal retrieval pattern combining semantic search, exact/keyword search, and recency search in parallel. Results are merged and reranked into a single context set. Much higher recall because the agent can find both fuzzy references and exact entities. Essential for comprehensive knowledge retrieval.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "context-management",
"secondaryUseCases": [],
"useCases": [
"context-management"
],
"complexity": 4,
"numNodes": 11,
"numLanes": 5,
"tags": [
"context-management",
"hybrid-retrieval",
"semantic",
"keyword",
"recency",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "context-management/architecture/context-hybrid-retrieval-memory"
},
{
"slug": "context-shared-memory",
"title": "Context Management - Shared Memory",
"description": "Multi-agent coordination pattern where an orchestrator breaks work into subtasks, specialist agents pull from and push to a shared state store, and the orchestrator composes the final answer from that shared state. Multi-agent setups feel coherent instead of each assistant having its own inconsistent memory.",
"kind": "architecture",
"sourceDomain": "Architecture",
"primaryUseCase": "agentic",
"secondaryUseCases": [
"context-management"
],
"useCases": [
"agentic",
"context-management"
],
"complexity": 3,
"numNodes": 9,
"numLanes": 4,
"tags": [
"context-management",
"shared-memory",
"multi-agent",
"orchestrator",
"architecture-diagram"
],
"sourcePath": "",
"repoPath": "agentic/architecture/context-shared-memory"
}
]
}
{
"templates": [
{
"slug": "a-b-testing-workflow",
"title": "A B Testing Workflow",
"description": "This workflow models comparing two versions to see which performs better.",
"kind": "workflow",
"sourceDomain": "patterns",
"primaryUseCase": "uncategorized",
"secondaryUseCases": [],
"useCases": [],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"a",
"b",
"testing",
"patterns"
],
"sourcePath": "patterns/a-b-testing",
"repoPath": "uncategorized/patterns/a-b-testing-workflow"
},
{
"slug": "ab-test-setup-workflow",
"title": "Ab Test Setup Workflow",
"description": "A/B test setup workflow with hypothesis definition, variant creation, traffic allocation, statistical analysis, and winner deployment.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "onboarding",
"secondaryUseCases": [],
"useCases": [
"onboarding"
],
"complexity": 3,
"numNodes": 10,
"numLanes": 3,
"tags": [
"ab-testing",
"experimentation",
"split-testing",
"statistical-significance",
"conversion-optimization",
"optimizely"
],
"sourcePath": "business-operations/ab-test-setup",
"repoPath": "onboarding/business-operations/ab-test-setup-workflow"
},
{
"slug": "access-review-workflow",
"title": "Access Review Workflow",
"description": "Quarterly user access review workflow with manager certification, separation of duties validation, remediation tracking, and compliance reporting for audit purposes.",
"kind": "workflow",
"sourceDomain": "devops",
"primaryUseCase": "approval",
"secondaryUseCases": [
"compliance"
],
"useCases": [
"approval",
"compliance"
],
"complexity": 4,
"numNodes": 18,
"numLanes": 3,
"tags": [
"access-review",
"user-access-certification",
"quarterly-review",
"manager-approval",
"compliance",
"sod-violations",
"audit"
],
"sourcePath": "devops/access-review",
"repoPath": "approval/devops/access-review-workflow"
},
{
"slug": "account-deletion-workflow",
"title": "Account Deletion Workflow",
"description": "Account deletion workflow with cancellation reason capture, retention offer, subscription termination, data cleanup, and confirmation email.",
"kind": "workflow",
"sourceDomain": "business-operations",
"primaryUseCase": "offboarding",
"secondaryUseCases": [
"billing"
],
"useCases": [
"offboarding",
"billing"
],
"complexity": 3,
"numNodes": 7,
"numLanes": 2,
"tags": [
"account-deletion",
"user-offboarding",
"data-cleanup",
"subscription-cancel",
"retention-offer",