Stage 3: Pattern Selection
Stage 3: Pattern Selection
Owner: Ada (Agentic Pattern Designer) Reviewer: Pablo (Production Line Architect) Blueprint stage: Stage 3 -- Pattern Selection
Trigger
Solution specification received from Pablo (Stage 2 gate passed).
Inputs
| Source | What |
|---|---|
| Pablo (Stage 2) | Solution specification with capability-to-skill mapping |
| Ada | Pattern catalog (21 patterns across 6 categories) |
| Ada | Component taxonomy — selection criteria for all 8 component categories (TFD-0014) |
| Ada | Model routing catalog — per-skill model assignment guidance |
| Work order (if exists) | Pre-selected patterns for known product types |
| Framework library | Available framework packages (production-lines/digital-talent/frameworks/) |
| Ivan | Integration catalog — available MCP servers and tool connections |
Activities
3.1 Match Capabilities to Patterns
For each capability in the solution spec, identify which pattern(s) from Ada's catalog best implement it. Consider:
- Orchestration patterns -- Does the product need prompt chaining, orchestrator-workers, routing, parallelization?
- Reasoning patterns -- Does the product need plan-then-execute, reflection, evaluator-optimizer?
- Tool use patterns -- File I/O, diagram generation, API calls, quality gates?
- Memory patterns -- Per-request persistence, RAG, shared state?
- Human-in-the-loop patterns -- Escalation, approval gates, feedback loops?
3.2 Select Models & Routing
Using Ada's model routing catalog, assign model recommendations:
- Per-skill model tier (Opus/Sonnet/Haiku) based on task complexity
- Cost optimization strategy based on work order budget tier
- Privacy routing if client has data sensitivity requirements
3.3 Select Integrations
Using Ivan's integration catalog, identify required integrations:
- Work order specifies client tools → check catalog for available MCP servers
- Work order specifies publication target → check catalog for write access
- Flag any integrations not in catalog to Ivan for evaluation
3.4 Document Pattern Selections
For each selected pattern:
- Why this pattern fits the capability
- What customizations are needed for this client
- How it interacts with other selected patterns
3.5 Verify Pattern Compatibility
Check that selected patterns do not conflict. Common compatible combinations:
- Prompt Chaining + Orchestrator-Workers (orchestrator drives the chain)
- Quality Gates + Approval Gate (mechanism + human checkpoint)
- Evaluator-Optimizer + Quality Gates (evaluator drives improvement, gate enforces threshold)
3.6 Select Frameworks
Pablo checks the framework library (production-lines/digital-talent/frameworks/) for frameworks required by this engagement:
- Review the macroscope's Methodology & Frameworks section for required/recommended frameworks
- Check the library for available framework packages in the relevant capability folder
- If a needed framework package exists: select it and note any client-specific customizations
- If a needed framework package is missing: Pablo triggers Francois (Framework Specialist) to build the package — Stage 3 blocks until the package is ready
- Record selected frameworks alongside pattern selections in the output document
3.7 Document Excluded Patterns
For each pattern NOT selected, document why -- helps future maintainers understand design decisions.
Outputs
| Deliverable | Format | Destination |
|---|---|---|
| Pattern selection document | Markdown | Confirmed by Pablo |
| Framework selection | Markdown (within pattern selection doc) | Confirmed by Pablo |
Contains: selected patterns table, customization notes, interaction map, excluded patterns with rationale, selected frameworks with library package references.
Quality Gate
Gate: Component selection confirmed by Pablo as buildable within timeline.
Criteria: Primary patterns selected (min 3), each capability maps to a pattern, customization scope clear, no conflicts, timeline achievable, required frameworks selected (or Francois build triggered), model routing assigned per skill, integrations identified (or Ivan evaluation triggered).
Evidence: Pattern selection document with model assignments, integration plan, and Pablo confirmation.
Reference: Component taxonomy at departments/it-architecture/agentic-pattern-designer-ada/ — use selection criteria from each category catalog.