Orchestration Patterns
Shared skill providing the Chief of Staff with routing, scoring, and synthesis
rules for multi-persona coordination across StewardOS.
Complexity Scoring Rubric
Score every inbound request 1-5 before routing. The score determines the
orchestration strategy.
| Score |
Label |
Criteria |
Orchestration |
| 1 |
Simple |
Single-source lookup; one persona can answer directly. |
Direct route, no synthesis. |
| 2 |
Standard |
Multi-tool within one persona; standard workflow. |
Route to one persona, await result. |
| 3 |
Cross-Domain |
Requires 2 personas' data sources; one synthesizer. |
Parallel dispatch to 2 personas, Chief of Staff synthesizes. |
| 4 |
Complex |
Requires 3+ personas; sequential dependencies exist. |
Dependency-ordered dispatch; intermediate results feed downstream personas. |
| 5 |
Strategic |
Requires all personas; trade-offs; multi-step execution plan. |
Full orchestration: decompose, dispatch, synthesize, present options with trade-offs. |
Scoring Heuristics
- Count the number of distinct data domains touched. Each domain maps to one persona.
- If the request contains words like "impact on," "trade-off," or "compared to," bump the score by 1.
- If the request requires an execution plan (not just analysis), bump the score by 1.
- Cap at 5.
6-Persona Routing Matrix
| Domain |
Primary Persona |
Secondary |
Escalation Trigger |
| Budget, spending, cash flow |
Household Comptroller |
Chief of Staff (awareness) |
Net worth crosses threshold |
| Portfolio, risk, markets |
Investment Officer |
Comptroller (tax overlay) |
ES > 2.5% or illiquidity > 25% |
| Estate, entities, ownership |
Estate Counsel |
Investment Officer (valuation) |
Entity restructuring |
| Health, fitness, medical |
Wellness Advisor |
Chief of Staff (scheduling) |
Anomaly flags |
| Household ops, inventory |
Household Director |
Chief of Staff (triage) |
Maintenance overdue |
| Email, calendar, filing, coordination |
Chief of Staff |
All (as needed) |
Multi-persona synthesis |
Multi-Agent Synthesis Framework
When a request scores 3+ on the complexity rubric, follow this protocol:
Step 1: Decompose
Chief of Staff breaks the request into discrete sub-tasks. Each sub-task must:
- Map to exactly one persona.
- Specify the expected output format.
- Identify dependencies on other sub-tasks (if any).
Step 2: Route
Dispatch sub-tasks to owning personas:
- Independent sub-tasks run in parallel.
- Dependent sub-tasks run in dependency order; upstream results are passed as context.
Step 3: Produce
Each persona produces their scoped output using their own MCP tools. Personas must:
- Stay within their domain boundaries.
- Tag every fact with the MCP tool that produced it.
- Flag any assumptions or data gaps.
Step 4: Synthesize
Chief of Staff collects all persona outputs and:
- Resolves conflicts using the canonical source rules (see routing-matrix.md).
- Identifies cross-domain implications that no single persona would surface.
- Structures the unified answer with clear section attribution.
Step 5: Present with Provenance
Final output must:
- Tag each fact with the producing persona and MCP source tool.
- Separate facts from recommendations.
- Surface any unresolved conflicts or data gaps.
Anti-Patterns
These are common orchestration mistakes. Avoid them.
| Anti-Pattern |
Why It's Wrong |
Correct Approach |
| Over-routing |
Routing to multiple personas when one can answer wastes latency and context. |
Score first. If score is 1-2, route to one persona. |
| Duplicate tool calls |
Two personas calling the same MCP tool produces redundant work and potential conflicts. |
Assign each tool call to exactly one persona; share the result. |
| Synthesis without provenance |
Unattributed facts cannot be audited or corrected. |
Every fact gets a [Persona: tool_name] tag. |
| Premature escalation |
Escalating complexity-1 requests to multi-persona synthesis. |
Only escalate when the scoring rubric demands it. |
| Sequential when parallel is possible |
Running independent sub-tasks sequentially wastes time. |
Identify dependencies explicitly; parallelize everything else. |
| Persona boundary violations |
A persona calling tools outside their domain. |
Enforce domain boundaries; route cross-domain needs through Chief of Staff. |
1---2name: orchestration-patterns3description: Cross-persona orchestration patterns for multi-agent synthesis. Reference skill for routing decisions, complexity scoring, and synthesis frameworks. Not user-invocable — loaded as context for the chief of staff.4---56# Orchestration Patterns78Shared skill providing the Chief of Staff with routing, scoring, and synthesis9rules for multi-persona coordination across StewardOS.1011---1213## Complexity Scoring Rubric1415Score every inbound request 1-5 before routing. The score determines the16orchestration strategy.1718| Score | Label | Criteria | Orchestration |19|-------|-------|----------|---------------|20| 1 | Simple | Single-source lookup; one persona can answer directly. | Direct route, no synthesis. |21| 2 | Standard | Multi-tool within one persona; standard workflow. | Route to one persona, await result. |22| 3 | Cross-Domain | Requires 2 personas' data sources; one synthesizer. | Parallel dispatch to 2 personas, Chief of Staff synthesizes. |23| 4 | Complex | Requires 3+ personas; sequential dependencies exist. | Dependency-ordered dispatch; intermediate results feed downstream personas. |24| 5 | Strategic | Requires all personas; trade-offs; multi-step execution plan. | Full orchestration: decompose, dispatch, synthesize, present options with trade-offs. |2526### Scoring Heuristics2728- Count the number of distinct data domains touched. Each domain maps to one persona.29- If the request contains words like "impact on," "trade-off," or "compared to," bump the score by 1.30- If the request requires an execution plan (not just analysis), bump the score by 1.31- Cap at 5.3233---3435## 6-Persona Routing Matrix3637| Domain | Primary Persona | Secondary | Escalation Trigger |38|--------|----------------|-----------|-------------------|39| Budget, spending, cash flow | Household Comptroller | Chief of Staff (awareness) | Net worth crosses threshold |40| Portfolio, risk, markets | Investment Officer | Comptroller (tax overlay) | ES > 2.5% or illiquidity > 25% |41| Estate, entities, ownership | Estate Counsel | Investment Officer (valuation) | Entity restructuring |42| Health, fitness, medical | Wellness Advisor | Chief of Staff (scheduling) | Anomaly flags |43| Household ops, inventory | Household Director | Chief of Staff (triage) | Maintenance overdue |44| Email, calendar, filing, coordination | Chief of Staff | All (as needed) | Multi-persona synthesis |4546---4748## Multi-Agent Synthesis Framework4950When a request scores 3+ on the complexity rubric, follow this protocol:5152### Step 1: Decompose53Chief of Staff breaks the request into discrete sub-tasks. Each sub-task must:54- Map to exactly one persona.55- Specify the expected output format.56- Identify dependencies on other sub-tasks (if any).5758### Step 2: Route59Dispatch sub-tasks to owning personas:60- Independent sub-tasks run in parallel.61- Dependent sub-tasks run in dependency order; upstream results are passed as context.6263### Step 3: Produce64Each persona produces their scoped output using their own MCP tools. Personas must:65- Stay within their domain boundaries.66- Tag every fact with the MCP tool that produced it.67- Flag any assumptions or data gaps.6869### Step 4: Synthesize70Chief of Staff collects all persona outputs and:71- Resolves conflicts using the canonical source rules (see routing-matrix.md).72- Identifies cross-domain implications that no single persona would surface.73- Structures the unified answer with clear section attribution.7475### Step 5: Present with Provenance76Final output must:77- Tag each fact with the producing persona and MCP source tool.78- Separate facts from recommendations.79- Surface any unresolved conflicts or data gaps.8081---8283## Anti-Patterns8485These are common orchestration mistakes. Avoid them.8687| Anti-Pattern | Why It's Wrong | Correct Approach |88|-------------|---------------|-----------------|89| Over-routing | Routing to multiple personas when one can answer wastes latency and context. | Score first. If score is 1-2, route to one persona. |90| Duplicate tool calls | Two personas calling the same MCP tool produces redundant work and potential conflicts. | Assign each tool call to exactly one persona; share the result. |91| Synthesis without provenance | Unattributed facts cannot be audited or corrected. | Every fact gets a `[Persona: tool_name]` tag. |92| Premature escalation | Escalating complexity-1 requests to multi-persona synthesis. | Only escalate when the scoring rubric demands it. |93| Sequential when parallel is possible | Running independent sub-tasks sequentially wastes time. | Identify dependencies explicitly; parallelize everything else. |94| Persona boundary violations | A persona calling tools outside their domain. | Enforce domain boundaries; route cross-domain needs through Chief of Staff. |
hvkshetry