semantic-persona-routingsolid

# Semantic Persona Routing Route by capability first and apply personality second. Build a portable map that keeps semantic role choice, deterministic endpoint lookup and provider-specific loading separate. ## Routing model ```text request -> semantic domain/coordinator role -> expert capability -> explicit or live-resolved skill endpoint -> optional persona overlay -> provider adapter loads and executes ``` A persona controls communication style, priorities and interaction patterns. It does not grant tools, permissions or subject-matter capability. A role coordinates; an expert narrows the domain; a skill is the executable endpoint. ## Build the routing map Use explicit metadata as authority and lexical similarity only as a candidate: ```bash python scripts/build_routing_map.py \ --roles-dir path/to/roles \ --personas-dir path/to/personas \ --skills-dir path/to/skills \ --out routing-map.json ``` The builder understands common `SKILL.md` fields such as `type`, `orchestrates.experts`, `parent_agents`, `skills`, descriptions and provenance. It produces a runtime map without requiring the source system to be installed. Read [routing-map-schema.md](references/routing-map-schema.md) before extending the format. Do not automatically promote `candidate_skills`. Confirm them against a live skill resolver or source metadata first. ## Route a request ### 1. Select the coordinator role semantically Compare the request with role names, descriptions and use