m/paliad
1
0
Fork 0
Code Issues 152 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Forward-workflow tool: 'I want to file X' decision tree (carved out of Fristenrechner) #65

New Issue
Open
opened 2026-05-20 12:35:05 +00:00 by mAi · 0 comments
mAi commented 2026-05-20 12:35:05 +00:00
Collaborator
Copy Link

Background

Follow-up to m/paliad#57. The Fristenrechner is a backward-looking calculator — an event happened, what deadlines spawn from it? The 'Ich möchte etwas einreichen' top-level cascade root was a forward-looking workflow — 'I want to file X, what deadlines does my action trigger and what supporting deadlines should I be aware of?' — which is a different mental model and belongs in a separate surface.

m/paliad#57 hides that root from the Fristenrechner's 'Was ist passiert?' picker (frontend filter, DB rows preserved). This issue tracks the future forward-workflow tool that should pick those data rows back up.

Existing data to reuse

  • paliad.event_categories rows under ich-moechte-einreichen.* (klage / berufung / widerklage / spaetere-schriftsaetze / einspruch-erteilung subtrees + leaves).
  • paliad.event_category_concepts junctions already map those leaves to concept rules + proceeding-type codes.
  • EventCategoryService already provides ConceptsForSlug, ConceptIDsForSlug, ProceedingCodesForSlug against this subtree.

The data layer is ready; what's missing is the dedicated UI surface and the workflow framing.

Scope (rough)

  • New tool surface (probably /tools/einreichen or similar — name TBD).
  • Picks up from 'I want to do X' instead of 'Y happened'.
  • Surfaces: trigger deadlines that flow from the user's action, supporting Vor- and Anschluss-Schriftsätze, court-set dates etc.
  • Reuses Fristenrechner's calc + render primitives (views/verfahrensablauf-core.ts).

To revive

When this tool ships, remove "ich-moechte-einreichen" from HIDDEN_CASCADE_ROOTS in frontend/src/client/fristenrechner.ts if the cascade is reused on the existing surface, or leave it filtered and consume the data directly via EventCategoryService in the new tool.

Status

Not scheduled — design + scoping conversation needed first.

## Background Follow-up to m/paliad#57. The Fristenrechner is a **backward-looking** calculator — an event happened, what deadlines spawn from it? The 'Ich möchte etwas einreichen' top-level cascade root was a forward-looking workflow — 'I want to file X, what deadlines does my action trigger and what supporting deadlines should I be aware of?' — which is a different mental model and belongs in a separate surface. m/paliad#57 hides that root from the Fristenrechner's 'Was ist passiert?' picker (frontend filter, DB rows preserved). This issue tracks the future forward-workflow tool that should pick those data rows back up. ## Existing data to reuse - `paliad.event_categories` rows under `ich-moechte-einreichen.*` (klage / berufung / widerklage / spaetere-schriftsaetze / einspruch-erteilung subtrees + leaves). - `paliad.event_category_concepts` junctions already map those leaves to concept rules + proceeding-type codes. - `EventCategoryService` already provides `ConceptsForSlug`, `ConceptIDsForSlug`, `ProceedingCodesForSlug` against this subtree. The data layer is ready; what's missing is the dedicated UI surface and the workflow framing. ## Scope (rough) - New tool surface (probably `/tools/einreichen` or similar — name TBD). - Picks up from 'I want to do X' instead of 'Y happened'. - Surfaces: trigger deadlines that flow from the user's action, supporting Vor- and Anschluss-Schriftsätze, court-set dates etc. - Reuses Fristenrechner's calc + render primitives (`views/verfahrensablauf-core.ts`). ## To revive When this tool ships, remove `"ich-moechte-einreichen"` from `HIDDEN_CASCADE_ROOTS` in `frontend/src/client/fristenrechner.ts` if the cascade is reused on the existing surface, or leave it filtered and consume the data directly via `EventCategoryService` in the new tool. ## Status Not scheduled — design + scoping conversation needed first.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
deferred
Parked — not pursuing now, may un-park later
done
Work completed by an agent; awaiting m to close
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mAi m
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: m/paliad#65
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?