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

DESIGN: Fristenrechner IA reframe + paliad.advice_nodes Paliadin-queryable substrate #16

New Issue
Open
opened 2026-05-08 13:53:13 +00:00 by mAi · 0 comments
mAi commented 2026-05-08 13:53:13 +00:00
Collaborator
Copy Link

Replace the current Pathway A/B fork with a more honest two-route landing, and build the substrate that makes the Decision-tree route both extensible and Paliadin-queryable.

Two routes (replaces "Was möchten Sie tun?" fork)

Decision tree — "Was tun als Nächstes?"

SoP-style advice flow. User answers questions; system narrows to a recommended action and (where applicable) the relevant deadline. Examples:

  • "Frist verpasst → was nun?" → Wiedereinsetzung guidance
  • "Beschluss erhalten → wann Berufung?" → R.220.x branching

Overviews

Laid-out views per proceeding (UPC_INF, UPC_REV, EP_GRANT, …). Replaces the old Pathway A wizard. Each Overview shows the procedure timeline + per-rule details + click-to-edit override UX. Search bar inside the Overviews route lets the user jump to a specific rule.

paliad.advice_nodes (new table)

Graph data model for the Decision-tree substrate:

  • node types: question, advice, action
  • edges: branch-on-answer, narrows-to, leads-to-rule
  • attributes: jurisdiction, forum, RoP citation, narrative text (DE / EN)

API surface usable by:

  • Decision-tree UI (cascade reading)
  • Paliadin (LLM tool calls — "what do I do if X happened in UPC infringement?")

The advice substrate lives in paliad (not mBrian — m's call 2026-05-08).

B1 cascade UX (folded into the reframe)

Current "Court submission > welchen Charakter hat das Schriftstück" conflates input (document classification) with output (resulting action). First entries are Wiedereinsetzung / Ermessensüberprüfung — those are resulting actions, not classifications. Restructure:

  • Visual split: Input panel (what arrived / classification) → Output panel (what to do, narrowing as input narrows).
  • Order by likelihood within each panel.
  • Possibly separate trigger-determination step from "what now".

Open IA questions (resolve in RFC)

  • B2 concept-search disposition: subsumed into Overviews search, kept as third route, or retired? Proposal: search bar inside Overviews route.
  • Authoring path for advice_nodes: DB-only, or seedable from a docs/-tracked YAML?
  • Authoring permissions: global_admin only, or any HLC team member?

Acceptance

  • RFC doc at docs/design-fristenrechner-ia-reframe.md.
  • paliad.advice_nodes schema + initial seed of 5–10 advice flows for proof-of-concept.
  • Migration plan for Pathway A → Overviews (replace, not coexist — m's call).

Context

t-paliad-157 items 7, 10, 14. m confirmed "replace" for landing fork and "paliad, not mBrian" for advice substrate.

Replace the current Pathway A/B fork with a more honest two-route landing, and build the substrate that makes the Decision-tree route both extensible and Paliadin-queryable. ## Two routes (replaces "Was möchten Sie tun?" fork) ### Decision tree — "Was tun als Nächstes?" SoP-style advice flow. User answers questions; system narrows to a recommended action and (where applicable) the relevant deadline. Examples: - "Frist verpasst → was nun?" → Wiedereinsetzung guidance - "Beschluss erhalten → wann Berufung?" → R.220.x branching ### Overviews Laid-out views per proceeding (UPC_INF, UPC_REV, EP_GRANT, …). Replaces the old Pathway A wizard. Each Overview shows the procedure timeline + per-rule details + click-to-edit override UX. Search bar inside the Overviews route lets the user jump to a specific rule. ## paliad.advice_nodes (new table) Graph data model for the Decision-tree substrate: - node types: `question`, `advice`, `action` - edges: branch-on-answer, narrows-to, leads-to-rule - attributes: jurisdiction, forum, RoP citation, narrative text (DE / EN) API surface usable by: - Decision-tree UI (cascade reading) - Paliadin (LLM tool calls — "what do I do if X happened in UPC infringement?") The advice substrate lives in paliad (not mBrian — m's call 2026-05-08). ## B1 cascade UX (folded into the reframe) Current "Court submission > welchen Charakter hat das Schriftstück" conflates input (document classification) with output (resulting action). First entries are Wiedereinsetzung / Ermessensüberprüfung — those are *resulting actions*, not classifications. Restructure: - Visual split: Input panel (what arrived / classification) → Output panel (what to do, narrowing as input narrows). - Order by likelihood within each panel. - Possibly separate trigger-determination step from "what now". ## Open IA questions (resolve in RFC) - B2 concept-search disposition: subsumed into Overviews search, kept as third route, or retired? Proposal: search bar inside Overviews route. - Authoring path for advice_nodes: DB-only, or seedable from a docs/-tracked YAML? - Authoring permissions: global_admin only, or any HLC team member? ## Acceptance - RFC doc at `docs/design-fristenrechner-ia-reframe.md`. - `paliad.advice_nodes` schema + initial seed of 5–10 advice flows for proof-of-concept. - Migration plan for Pathway A → Overviews (replace, not coexist — m's call). ## Context t-paliad-157 items 7, 10, 14. m confirmed "replace" for landing fork and "paliad, not mBrian" for advice substrate.
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#16
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?