route-legal-fact-pattern-l0cka

Route Legal Fact Pattern

Turn a described matter into an ordered list of the skills to run, and say what stays with a human at each step. The router is a map, not an adviser: every routed skill keeps its own scope, fail-closed rules and review points.

Read references/skill-map.md before routing. It is generated from the marketplace registry and is the only list of skills the router may name; never route to a skill that is not in it. The map lists every shipped skill, not the skills installed in this session: each plugin installs separately, and the map records which plugins a plugin requires or hands off to.

Workflow

1. Extract the routing facts.
   • Record, with the user's wording: parties and their roles (entity type, listed or regulated status, individual or organisation); sector and regulator overlays; jurisdiction or jurisdictions; the events and their dates; existing profiles, registers or approved materials the user already holds; and the deliverable sought.
   • Record cannot be determined for any routing fact the description does not supply. Ask one bounded question only where the answer changes the plan; otherwise route on stated assumptions and label them.
2. Match facts to skills.
   • For each fact, list every skill in the map whose description is triggered by it and note which of its stated exclusions might apply.
   • Prefer the most specific skill. Where an orchestrating skill exists (for example a breach assessment that itself calls the APP checker and the legislation verifiers), route to the orchestrator and list its dependencies as prerequisites rather than as separate steps.
   • Where a fact engages a practice area with no skill in the map, record a gap. Never route it to the nearest skill.
   • Add each routed plugin's required plugins from the map as prerequisites. Add a hand-off plugin only when a fact engages it.
3. Check availability.
   • For each routed skill, record installed when it appears in this session's available skills, not installed when the session's skill list is visible and it is absent, and cannot be determined when the session does not expose its skill list.
   • Collect every not installed plugin, required prerequisites included, under "Install first". A missing plugin is not a gap: keep its step in the plan and never replace it with an installed skill that looks close.
4. Sequence the plan.
   • Order: (a) configuration and profile skills the routed skills require; (b) official-source verification of the legislation and case law the later steps rely on; (c) assessment, mapping and computation skills; (d) deliverable and record skills (registers, chronologies, drafts, board papers).
   • Mark each step with its inputs (including outputs of earlier steps), the plugin it belongs to, and the human decision owner who must act on its output before the next step runs.
   • Mark any step whose skill fails closed on a missing profile or unverified table, so the user runs the prerequisite first.
5. Report using the result contract.