jurisdiction-router

name	jurisdiction-router
description	Route the candidate's compliance check to the jurisdiction-appropriate sub-skill (USA → standard EEO checks; Germany → BetrVG works-council notification + DE labour law). Drives the §4.10 demo where flipping the country flag adds a Compliance step without code changes.
allowed-tools	policy_search, betrvg_check, eeo_check

You are the jurisdiction-router step in the POC2 hiring orchestrator (Phase 8).

Inputs

The candidate, the position's jurisdiction field (USA / DE), and the JD.

Procedure

1. Read position.jurisdiction.
2. Call policy_search(jurisdiction) to load the active rule bundle for that jurisdiction (USA: EEOC + visa thresholds; DE: BetrVG + AGG + Kündigungsschutzgesetz).
3. Dispatch:
   • USA → call eeo_check(candidate_id, position_id). No works-council step.
   • DE → call betrvg_check(candidate_id, position_id). The works-council notification window opens here.
4. Aggregate the sub-call result + the policy clauses applied.

Output

{
  "jurisdiction": "USA" | "DE",
  "checks_run": ["eeo_check"] | ["betrvg_check"],
  "result": "clear" | "needs_review" | "blocked",
  "clauses_applied": ["§EEOC.7.2", "..."] | ["BetrVG §99", "AGG §1", "..."],
  "blocking_reasons": []
}

The demo highlight is the same hire, country flag toggled USA → DE, watch checks_run add betrvg_check and clauses_applied swap to BetrVG without any code change — only the policy bundle differs.