traffic-case-router

name

traffic-case-router

description

Use this skill whenever ANTIPENALTY must classify a Russian traffic fine, постановление, protocol, parking fine, evacuation case, accident case, or authority document before legal analysis. This skill determines case_source and issuing_authority, flags missing facts, and blocks wrong playbooks such as applying GIBDD camera logic to MADI or AMPP cases. Use it before any evidence audit, defense strategy, court routing, or complaint drafting.

Traffic Case Router

Classify the traffic case before any legal strategy is selected.

This skill protects the workflow from using the wrong playbook. A wrong classification can create a legally unsafe complaint even if the text looks plausible.

Required References

Read:

• ../../shared/legal-taxonomy/traffic-case-taxonomy.md
• ../../shared/contracts/case_classification.schema.json
• ../../shared/fail-closed-rules/fail-closed-rules.md

Inputs

Use whatever is available:

• issuing authority text
• document header
• article
• UIN prefix
• location
• document type
• OCR text
• user statements
• source document names

Classification Rules

Return unknown when signals conflict or critical evidence is missing.

Strong signals:

• MADI header, Moscow administrative road inspection, or Moscow parking/standing article -> parking_madi, madi.
• AMPP or paid parking non-payment context -> parking_ampp, ampp.
• CAPAF/GIBDD, auto camera, special technical means, photo/video fixation -> auto_camera, gibdd.
• protocol, inspector signature, rights explanation, on-site decision -> inspector_on_site or protocol_then_decision.
• суд or judicial act header -> court_decision, court.
• evacuation, detention protocol, impound documents -> evacuation.
• accident scheme or ДТП materials -> accident.

Wrong Playbook Guards

• Do not apply GIBDD auto-camera playbook to MADI or AMPP cases.
• Do not apply parking payment defenses to GIBDD moving violations.
• Do not classify from UIN alone when the authority text contradicts it.
• Do not classify postal delivery recipient as issuing authority.
• Do not infer the case source from account holder profile data.

Output Format

case_source:
issuing_authority:
confidence:
missing_facts:
forbidden_playbooks:
source_notes:
next_step:

Fail-Closed Behavior

If classification is uncertain:

• set case_source: unknown
• set issuing_authority: unknown or the narrowest supported value
• list missing facts
• forbid unsafe playbooks
• route to traffic-evidence-auditor or ask for the original document