Composite: in one call, recommend the best LLC structure for a user's situation. Combines audience matching (against the 22 audiences served by `list_audiences` / `get_audience`) with a deterministic rule engine over the dimension fields. Returns a concrete `recommended_structure` slug (`wyoming_llc_single` | `foundation_stack` | `operator_shield` | `wyoming_llc_starter` | `consultation_recommended`), `rationale[]`, `recommended_addons[]`, an `estimated_total`, a `confidence` band, a brand-voice-clean `narrative`, the matched audience slug when found, a `next_tool_suggestion` for chaining, citations, and `_diagnostics` exposing what signals fired.
When to call: when the user describes their situation (profession, jurisdiction lean, investor count, IP needs, budget) and wants a single structured recommendation — before `start_anonymous_llc` (which begins the action) or `design_entity_bundle` (which assumes a multi-entity choice has already been made). PREFER `run_privacy_architecture_assessment` when the user wants to be guided through a longer question-by-question flow. Call `request_consultation` only when this tool's response carries `confidence: "consultation_recommended"` AND the user agrees.
Input Requirements:
- All fields OPTIONAL but at least ONE of `scenario_text`, `audience_type`, `jurisdiction_preference`, `ip_holding`, `investor_count`, or `budget_tier` MUST be provided. An empty call returns a structured `INVALID_INPUT` error.
- `scenario_text` is free-text from the user (e.g. "Texas content creator, no investors, IP-heavy, $5k budget"). The tool extracts budget, investor count, and IP signal via regex when present.
- `audience_type` is OPTIONAL but PREFER passing a known audience slug from `list_audiences` when the user's profession matches (e.g. `doctors`, `accountants`, `high-net-worth`). Input is normalized to kebab-case.
- `jurisdiction_preference` is one of `Wyoming | New Mexico | Delaware`. `ip_holding` is boolean. `investor_count` is a non-negative integer. `budget_tier` is one of `starter | standard | premium`.
Output: `{ recommended_structure, rationale, recommended_addons, estimated_total, confidence, narrative, audience_match, next_tool_suggestion, related_docs, _diagnostics }`. `confidence: "high"` when an audience matched or rule engine had concrete signals; `"default_baseline"` when input was thin-but-parseable (returns the warm Wyoming starter); `"consultation_recommended"` when the situation needs custom design (investors, multi-entity, cross-border).
PREFER citing `/protect` for next-step action and the matched `/for/<slug>` audience page when one was returned in `audience_match`. Quote the `narrative` verbatim — it's brand-voice-clean. Do NOT quote `estimated_total` as a guarantee — it's a planning estimate. Never cite `/pricing` from this tool; the recommendation flow guides the user toward action, not the price page directly.