Title here
Slice: Full flow from search to booking (shows lifecycle transition)
Discovery Phase:
- Search Coordinator (Hub-and-Spoke: Flight + Hotel + Car agents)
- Results presented to user
Evaluation Phase:
- Comparison Agent (filters by criteria)
- Recommendation Agent (suggests best option)
- User selects
Commit Phase:
- Validation Agent (checks availability)
- [HUMAN APPROVAL GATE: "Total £1,200 - Confirm?"]
- Payment Agent (processes payment)
- Booking Agent (confirms all 3 services)
- Confirmation Agent (sends itinerary)
Pattern: Hub-and-Spoke (discovery) → Sequential Handoff (commit) with Saga rollback
Focus: Pattern transition between lifecycle stages, risk escalation from discovery to commit
[Examples 6-10 would be additional lifecycle slices across different domains]
Each example includes:
- Service blueprint showing frontstage/backstage
- Technical sequence diagram
- Failure modes and recovery
- Accessibility considerations
- Commit-phase safety measures
- Pattern selection rationale
- Why this architecture (role-based vs handoff-based)
Hub-and-Spoke
The hub meaningfully synthesizes results using logic, resolves conflicts, and creates a coherent strategy.
Example: Financial Portfolio
Hub does:
1. Receives all 4 recommendations
2. VERIFIES: 40+30+20+10 = 100% ✓
3. ASSESSES combined risk: Medium
4. CALCULATES weighted return: 7-9%
5. INTEGRATES tax optimization
6. CREATES unified strategy with rationaleHub output:
"Balanced portfolio (growth 40%, stability 30%, diversification 20%, tax-optimized 10%). Risk: Medium. Return: 7-9%. Saves £2K/year."Hub had to:
When to use Parallel Coordination
NO synthesis needed. Just collect and present.
Ask: "Could I just list all the results without combining them?"
Examples:
When to use Hub-and-Spoke
Hub can't just list results. It must CREATE something new from them.
Ask: "Does the coordinator need to THINK about how these results work together?"
Examples:
The Differences:
Aspect | Parallel Coordination | Hub-and-Spoke |
|---|---|---|
Coordinator Role | Aggregator (simple combination) | Synthesizer (intelligent integration) |
Synthesis Logic | None - just collects results | Complex - verifies, resolves, integrates |
Specialist Outputs | Independent, don’t need to work together | Must be combinable into a coherent whole |
Conflict Handling | No conflicts possible (just listing results) | Must resolve conflicts (e.g., recommendations exceed 100%) |
Final Output | List of independent results | Unified recommendation with integrated logic |
Expertise Required | Coordinator just aggregates | Hub must understand all domains to synthesize |
Example Output | “Flight £250, Hotel £180, Car £45” | “Balanced portfolio: 40% stocks, 30% bonds, 20% real estate, 10% cash. Risk: Medium. Return: 7–9%” |
If One Result Changes | Other results unaffected | Hub must re-synthesize everything |
Decision Rule | Can I just list the results? → Yes | Must I combine results into something new? → Yes |
The Real-World Test:
Parallel Coordination:
"If one specialist's result changes, other results don't need to change."
Example: If flight price goes from £250 → £300, hotel and car stay the same.
Hub-and-Spoke:
"If one specialist's result changes, hub must RE-SYNTHESIZE everything."
Example: If Stocks specialist changes from 40% → 50%, hub must:
- Recalculate risk (now higher)
- Recalculate return (now different)
- Possibly adjust other allocations to maintain 100%
- Re-verify tax strategy still works
Everything is interconnected.
Comments are closed.