| name | traffic-court-router |
| description | Use this skill whenever ANTIPENALTY must decide where a Russian traffic-fine complaint should be filed or whether court/addressee routing must remain unresolved. This skill is mandatory before complaint drafting when a court, authority, address, jurisdiction, MADI/AMPP route, GIBDD route, or place-of-violation issue appears. It prevents invented courts and returns fail-closed unresolved output when location or routing source is insufficient. |
Traffic Court Router
Resolve the complaint route only when supported. If support is insufficient, return unresolved.
Required References
Read:
../../shared/fail-closed-rules/fail-closed-rules.md../../shared/contracts/case_fact.schema.json../../shared/fail-closed-rules/legal-source-policy.md
Inputs
- case classification
- issuing authority
- violation location
- place of consideration if present
- article
- region
- current court dictionary result, if any
- user confirmation, if any
Routing Principles
- For MADI/AMPP parking cases, routing usually depends on the place of violation, not the authority office.
- For GIBDD auto-camera cases, do not assume a court from the authority address unless the legal route is supported.
- If address is vague, incomplete, contradictory, or unsupported, return unresolved.
- If the court dictionary has low confidence, require user confirmation.
- If the user manually enters a court, mark source as
manual_input and require confirmation.
Output Format
court_route:
status:
court_name:
court_address:
source:
confidence:
needs_user_confirmation:
missing_facts:
warnings:
generation_blocked:
block_reasons:
next_step:
Fail-Closed Rules
Set court_route.status: unresolved when:
- no violation address exists
- only the authority address exists and it is not enough
- the location cannot be mapped to a court
- region is unsupported by current dictionary
- the route is based only on model inference
Do not invent court names. A plausible court name is still unsafe if the route source is missing.
