mAi
a33060e600
Wires the project context into the Determinator row stack so a UPC INF
matter doesn't need to be hand-walked through five obvious cascade picks.
Auto-walk descends single-option chains as `is-prefilled` rows, the inbox
row vanishes for UPC matters (CMS implied), and the first prefilled row
carries the project reference inline ("aus Akte: HL-2024-001").
Backend: `internal/services/proceeding_mapping.go` adds
MapLitigationToFristenrechner — single source of truth for bridging the
litigation conceptual codes (INF / REV / APP / CCR / AMD / APM / OPP) onto
fristenrechner codes (UPC_INF / DE_INF / EPA_OPP / …). Ambiguous combos
(APP+DE, ZPO_CIVIL, AMD+DE) return ok=false; callers degrade to "no
narrowing" instead of guessing. Table-driven test covers every documented
mapping plus the ambiguous-degrade cases.
Frontend: `buildRowStack` filters cascade children by project context
along the proceeding axis (kebab segment lookup against the project's
fristenrechner code); auto-walks while filtered scope narrows to one;
caps depth via `cascadeAutoWalkStopAfter` after an "ändern" on a prefilled
row so the user lands at an active chip set without the auto-walk
re-engaging. Result panel narrows on the post-auto-walk effective slug,
not the URL slug. A one-time inline tooltip ("Diese Schritte ergeben sich
aus Ihrer Akte") surfaces when ≥2 rows render prefilled — dismissal flag
persists in localStorage.
Narrowing is purely additive: an Akte without a fristenrechner code
(11/11 live projects pre-Slice-5 were NULL) degrades to today's
forum-only behaviour. Slice 3 (mobile polish + search relocation) follows.
Refs: docs/design-determinator-row-cascade-2026-05-13.md §10 Slice 2 + §4 + §5.
88 lines
3.3 KiB
Go
88 lines
3.3 KiB
Go
package services
|
|
|
|
// proceeding_mapping bridges the two proceeding-type vocabularies in the
|
|
// codebase: the **litigation** conceptual category (INF / REV / APP /
|
|
// CCR / AMD / APM / ZPO_CIVIL) used by the historical project-binding
|
|
// + Pipeline-A rules, and the **fristenrechner** code category (UPC_INF
|
|
// / DE_INF / EPA_OPP / …) used by the Determinator cascade + rule
|
|
// engine. Post-Phase-3-Slice-5 (t-paliad-186) projects bind to
|
|
// fristenrechner codes directly, but the litigation→fristenrechner
|
|
// mapping is still needed for the ~40 Pipeline-A rules that remain on
|
|
// litigation proceedings and for any other surface that thinks in
|
|
// litigation terms.
|
|
//
|
|
// The mapping table here is the single source of truth — see
|
|
// docs/design-determinator-row-cascade-2026-05-13.md §4.2 for the
|
|
// design rationale + ambiguity notes. **Never silent FK promotion**:
|
|
// every ambiguous case returns ok=false so callers can degrade
|
|
// gracefully ("no narrowing") instead of guessing.
|
|
|
|
// MapLitigationToFristenrechner returns the fristenrechner code +
|
|
// condition flags implied by a (litigationCode, jurisdiction) pair.
|
|
//
|
|
// Inputs are case-sensitive — pass the canonical upper-snake form
|
|
// (e.g. "INF", "UPC"). Unrecognised codes or genuinely ambiguous
|
|
// combinations (APP+DE, ZPO_CIVIL+DE) return ok=false with a zero
|
|
// fristenrechner code; callers should treat that as "no narrowing"
|
|
// and leave the cascade wide-open rather than auto-pick.
|
|
//
|
|
// Condition flags are returned as a slice so callers can apply them
|
|
// alongside the fristenrechner code (CCR+UPC → UPC_INF + with_ccr,
|
|
// AMD+UPC → UPC_INF + with_amend). An empty slice means no flag
|
|
// context applies.
|
|
func MapLitigationToFristenrechner(litigationCode, jurisdiction string) (fristenrechnerCode string, conditionFlags []string, ok bool) {
|
|
switch litigationCode {
|
|
case "INF":
|
|
switch jurisdiction {
|
|
case "UPC":
|
|
return "UPC_INF", nil, true
|
|
case "DE":
|
|
return "DE_INF", nil, true
|
|
}
|
|
case "REV":
|
|
switch jurisdiction {
|
|
case "UPC":
|
|
return "UPC_REV", nil, true
|
|
case "DE":
|
|
return "DE_NULL", nil, true
|
|
}
|
|
case "CCR":
|
|
// Counterclaim revocation — UPC fold-in is structural (the
|
|
// counterclaim lives inside an UPC_INF proceeding with the
|
|
// with_ccr flag). DE Nichtigkeit is conceptually the same
|
|
// adversarial-validity test, no separate flag.
|
|
switch jurisdiction {
|
|
case "UPC":
|
|
return "UPC_INF", []string{"with_ccr"}, true
|
|
case "DE":
|
|
return "DE_NULL", nil, true
|
|
}
|
|
case "AMD":
|
|
// Amendment-application bundled into UPC_INF via with_amend.
|
|
// No DE / EPA / DPMA analogue today.
|
|
if jurisdiction == "UPC" {
|
|
return "UPC_INF", []string{"with_amend"}, true
|
|
}
|
|
case "APP":
|
|
// Appeal is ambiguous in DE (OLG vs BGH) and the project
|
|
// model doesn't carry the instance hint we'd need to
|
|
// disambiguate. UPC is unambiguous.
|
|
if jurisdiction == "UPC" {
|
|
return "UPC_APP", nil, true
|
|
}
|
|
case "APM":
|
|
// Preliminary injunction / urgency procedure — UPC-only
|
|
// concept in the fristenrechner taxonomy.
|
|
if jurisdiction == "UPC" {
|
|
return "UPC_PI", nil, true
|
|
}
|
|
case "OPP":
|
|
// Opposition — primarily EPA. DPMA has DPMA_OPP but it
|
|
// doesn't surface from the litigation vocabulary today.
|
|
if jurisdiction == "EPA" {
|
|
return "EPA_OPP", nil, true
|
|
}
|
|
}
|
|
return "", nil, false
|
|
}
|