paliad/docs/feature-roadmap.md

patholo.de Feature Roadmap

Author: cronus (inventor) | Date: 2026-04-14
Task: t-patholo-011

---

Strategic Position

patholo.de is a knowledge platform, not case management. KanzlAI handles case tracking, deadlines, billing. patholo.de is where HL patent lawyers go to find tools, templates, guides, and answers — the internal Wikipedia + toolkit for patent practice.

The goal: every new associate's first bookmark, every partner's quick-reference, every PA's template source.

Audience

• Patent lawyers and PAs across 7 offices (Munich, Dusseldorf, Hamburg, Amsterdam, London, Paris, Milan)
• Mix of German and English speakers
• Range from senior partners to new associates
• Daily work: drafting submissions, calculating costs, tracking deadlines, researching case law

What We Have (v1)

Feature	Status
Supabase auth (@hoganlovells.com)	Live
Prozesskostenrechner (DE/UPC/EPA)	Live
Fristenrechner (deadlines with holiday adjustment)	Live
Downloads (HL Patents Style.dotm)	Live
Sidebar navigation	Live
i18n DE/EN	Live
Lime green branding	Live

Design Principles

1. Content is king — tools bring people in, content keeps them coming back
2. Self-serve over manual curation — prefer structured data + search over hand-maintained pages
3. Complement, don't compete — KanzlAI does case management; patholo does knowledge
4. Ship incrementally — each feature is independently useful
5. German content quality matters — proper Umlaute, legal precision, no machine-translation feel

---

Phase 1: Foundation (Low effort, High impact)

These features can each be built in a single session. They fill obvious gaps and immediately increase the platform's daily utility.

1.1 Link Hub ("Nützliche Links")

What: Curated, categorized page of external links relevant to daily patent practice.

Categories:

• Gerichte & Ämter — UPC CMS (cms.unifiedpatentcourt.org), UPC Register, EPO (epo.org), DPMA (dpma.de), BPatG
• Recherche — Espacenet, DPMA-Register, DEPATISnet, Google Patents, Patentscope (WIPO)
• UPC — Rules of Procedure, Schedule of Fees, Practice Directions, UPC website, Bristows UPC Hub
• Gesetze — PatG, EPÜ, UPCA, GKG, RVG, ZPO (dejure.org links)
• HL Intern — SharePoint UPC Vault, UPC Playbook, UPC Knowledge Bank, DraftXPress

Why: Lawyers waste time finding the right URL. A curated link page with one-click access is the simplest high-value feature. Every major law firm knowledge platform starts here.

Implementation:

• New page: /links
• Static data in Go (map of categories -> links), served as JSON
• TSX page with category sections, each link as a card with icon + title + short description
• Add to sidebar navigation
• i18n for category names and descriptions

Effort: ~2 hours | Impact: High (daily use)

---

1.2 More Downloads

What: Expand the downloads page with more templates and documents from mWorkRepo.

Files to add (immediate candidates):

• HL Patents Style.dotm (already live)
• BuildingBlocks library files (from mWorkRepo/6 - material/Templates/Word/Blocks/)
• Legal writing templates (from mWorkRepo/6 - material/Legal Writing/)
• Patentprozesskostenrechner.xlsm (the original Excel calculator — some people prefer Excel)

Why: The downloads page exists but has only one file. The file proxy infrastructure is already built and supports multiple files via the registry. Adding files is literally adding map entries.

Implementation:

• Add entries to fileRegistry in internal/handlers/files.go
• Update downloads page TSX with cards per file
• Group downloads by category (Templates, Rechner, Leitfäden)

Effort: ~1 hour | Impact: Medium (removes a SharePoint dependency)

---

1.3 Gebührentabellen (Fee Schedule Reference)

What: Browsable, interactive fee tables for GKG, RVG, PatKostG, and UPC fee schedules.

Content:

• GKG fee brackets (2005, 2013, 2021, 2025, Aktuell) — what's the 1.0 fee for a given Streitwert?
• RVG fee brackets (same versions)
• UPC fee schedule (pre-2026 vs. 2026+, with SME discount)
• EPA fees (opposition, appeal, grant)
• Common multipliers reference (3.0x LG, 4.0x OLG, etc.)
• PatKostG fixed fees (BPatG, DPMA)

Why: Lawyers regularly need to look up a specific fee without running the full calculator. The Kostenrechner is great for full scenarios, but sometimes you just need "what's the 1.0 RVG fee for Streitwert 2M?" — a reference table answers that in 2 seconds.

Implementation:

• New page: /tools/gebuehrentabellen
• Reuse data from internal/calc/fee_tables.go — expose via new API endpoint
• TSX page with tabbed view (GKG | RVG | UPC | EPA | PatKostG)
• Streitwert input for quick lookup
• Sortable/filterable table per schedule version

Effort: ~4 hours | Impact: Medium-High (replaces Excel lookup)

---

1.4 Patentglossar (Patent Glossary DE/EN)

What: Searchable bilingual glossary of patent law terminology.

Content (examples):

• Streitwert / Amount in dispute
• Nichtigkeitsklage / Nullity action
• Patentverletzung / Patent infringement
• Unterlassungsanspruch / Injunctive relief
• Schadensersatz / Damages
• Beschwerde / Appeal
• Einspruch / Opposition
• Schriftsatz / Written submission
• Merkmalsgliederung / Feature breakdown
• Vertraulichkeitsklub / Confidentiality club
• Einstweilige Verfügung / Preliminary injunction
• Gebrauchsmuster / Utility model
• ... (50-100 terms initially)

Why: Cross-border teams constantly need precise DE<->EN translations for legal terms. Google Translate is dangerous for legal terminology. A curated glossary prevents mistranslations in submissions.

Implementation:

• New page: /glossar
• Data: JSON file with terms, loaded at startup
• Client-side search (instant filter as you type)
• Show DE term, EN term, optional short definition
• Category tags (prosecution, litigation, UPC, EPA)

Effort: ~3 hours (code) + ~2 hours (content curation) | Impact: Medium (frequent use for cross-border work)

---

1.5 Kostenrechner Enhancements

What: Improve the existing Kostenrechner with frequently-requested features.

Enhancements:

• PDF Export — generate a branded summary PDF of the calculation result (for client budgets, internal memos)
• Scenario Comparison — side-by-side comparison of two scenarios (e.g., DE-only vs. UPC, different Streitwerte)
• URL Sharing — encode calculator state in URL parameters so calculations can be bookmarked/shared
• Prozesskostensicherheit — add the security-for-costs calculation (currently only in the Excel version, and buggy there)

Why: The Kostenrechner is patholo's flagship feature. Making it PDF-exportable turns it into a client-facing tool. Scenario comparison is the #1 use case for cost calculators (should we litigate at UPC or LG?). The original Excel version's Prozesskostensicherheit section has bugs — patholo can do it right.

Implementation:

• PDF: client-side using window.print() with @media print CSS (simple) or server-side PDF generation (more polished)
• Scenario comparison: duplicate the calculator form side-by-side, show diff
• URL sharing: serialize form state to URL query params
• Prozesskostensicherheit: new calc in Go, formula from Kühnen 16th ed. Rn. E.47 ff. (fix the VAT bug from the Excel version)

Effort: ~6 hours total | Impact: High (makes the tool client-presentable)

---

Phase 2: Content Hub (Medium effort, High impact)

These features require content creation alongside code. They transform patholo from a toolkit into a knowledge platform.

2.1 Verfahrensleitfäden (Procedure Guides)

What: Step-by-step interactive guides for common patent procedures.

Initial guides:

• UPC Infringement Action (Statement of Claim -> Defence -> Reply -> Rejoinder -> Hearing -> Decision)
• UPC Revocation Action
• UPC Provisional Measures
• German Infringement (LG -> OLG -> BGH)
• German Nullity (BPatG -> BGH)
• EPA Opposition
• EPA Appeal

Per guide:

• Visual timeline/flowchart (like the UPC Course of Proceedings Excalidraw in mWorkRepo)
• Step descriptions with party, deadline, rule reference
• Tips and practical notes from experienced practitioners
• Links to relevant model documents, templates
• Cross-links to Fristenrechner (pre-filled for this proceeding type)

Why: New associates ask "how does a UPC infringement action work?" constantly. A visual, interactive guide replaces the ad-hoc training that senior lawyers currently provide. The content already exists in mWorkRepo (UPC Know-How, UPC Training sessions) — it just needs to be structured and presented.

Implementation:

• New section: /guides with sub-pages per guide
• Data: structured JSON per guide (steps, durations, parties, rules)
• TSX: timeline component with expandable steps
• Deep-link to Fristenrechner with pre-selected proceeding type
• i18n for all content

Effort: ~8 hours (code) + ~6 hours (content per guide) | Impact: Very High (training + daily reference)

---

2.2 Gerichtsverzeichnis (Court Directory)

What: Reference page with details for every relevant court, division, and office.

Content per entry:

• Court name (DE + EN)
• Type (UPC Local Division, UPC Central Division, LG, OLG, BGH, BPatG, DPMA, EPA)
• Address, phone, fax
• Filing details (electronic filing system, accepted formats)
• Key judges (for UPC divisions — public info from UPC website)
• Link to court website / registry
• HL contacts for that jurisdiction
• Practical notes (e.g., "Munich LD prefers oral hearings on Wednesdays")

Courts to include:

• UPC: Munich CD, Paris CD (Seat), Luxembourg CD, all Local Divisions (Munich, Düsseldorf, Hamburg, Mannheim, The Hague, Paris, Milan, Brussels, Helsinki, etc.), Court of Appeal (Luxembourg)
• Germany: LG Munich I, LG Düsseldorf, LG Mannheim, LG Hamburg, OLG Düsseldorf (+ Senat), OLG Munich, BGH (X. Zivilsenat), BPatG
• EPO: Boards of Appeal, Opposition Division
• National: NL (The Hague), UK (Patents Court, IPEC), FR (TGI Paris), IT (Milan, Turin)

Why: "What's the filing address for the UPC Local Division Hamburg?" — this question gets asked weekly. A central directory with practical filing info saves time and prevents errors.

Implementation:

• New page: /gerichte
• Data: JSON with structured court entries
• Client-side search + filter by type/country
• Map view (optional, using coordinates)
• Print-friendly format for travel

Effort: ~4 hours (code) + ~4 hours (data collection) | Impact: Medium-High (weekly use)

---

2.3 UPC Rechtsprechungsübersicht (UPC Case Law Dashboard)

What: Curated overview of significant UPC decisions with summaries and key takeaways.

Features:

• List of decisions, newest first
• Per decision: case number, parties, division, date, topic tags, 2-3 sentence summary, key takeaway
• Filter by: division, topic (infringement, validity, preliminary injunction, costs, procedure), date range
• Search by party name or case number
• Link to full decision (UPC register) and to youpc.org if available

Content source: mWorkRepo already has youpc-summaries/ with 8+ recent case summaries. The youpc.org database has 1,600+ decisions. Start with curated highlights, not a full database.

Why: UPC case law is developing rapidly (court opened June 2023). Staying current is critical for practitioners. The UPC website's register is hard to navigate. A curated, searchable overview with HL-relevant takeaways is enormously valuable.

Implementation:

• New page: /upc/rechtsprechung
• Data: JSON file with curated entries (start with 20-30 key decisions, add monthly)
• Admin: simple way to add new entries (could be a JSON file in the repo, updated via PR)
• TSX: filterable card list with topic tags
• Optional: API integration with youpc.org for broader search

Effort: ~6 hours (code) + ~8 hours (initial curation) | Impact: Very High (weekly/daily for UPC practitioners)

---

2.4 Checklisten (Interactive Checklists)

What: Interactive, printable checklists for common patent workflows.

Initial checklists:

• UPC Statement of Claim — required elements per RoP
• UPC Statement of Defence — required elements per RoP
• UPC Confidentiality Application — requirements
• UPC Registration as Representative — documents needed
• Patent nullity action (BPatG) — filing requirements
• EPA Opposition — formal requirements and deadlines
• nUPCMS filing — step-by-step for electronic submission

Per checklist:

• Checkbox items (persistent in localStorage per user)
• Category groupings (formal requirements, content requirements, annexes)
• Notes/tips per item
• Print-friendly layout
• Reset button

Why: Filing requirements are complex and vary by court. Missing a formal requirement means rejection or delay. Checklists prevent errors. The HL Model Documents project in mWorkRepo already has checklist content (CHECKLIST.md with 63 BuildingBlock entries).

Implementation:

• New section: /checklisten
• Data: JSON per checklist
• Client-side state (localStorage) for checkbox persistence
• Print with checked/unchecked state visible

Effort: ~4 hours (code) + ~3 hours (content per checklist) | Impact: High (prevents costly filing errors)

---

Phase 3: Platform Features (Higher effort, Transformative)

These features require more architecture but move patholo from "useful tool" to "indispensable platform."

3.1 Suchfunktion (Global Search)

What: Search across all patholo content — glossary terms, court entries, case law, guides, checklists, links.

Why: Once patholo has significant content, users need to find things fast. A search bar in the sidebar that searches everything is the difference between "I'll check patholo" and "I'll just Google it."

Implementation:

• Search index built at startup from all JSON data sources
• API endpoint: GET /api/search?q=...
• Client: search input in sidebar, results overlay
• Highlight matching text in results

Effort: ~6 hours | Impact: High (scales with content)

---

3.2 Vorlagenbibiothek (Template Library)

What: Browsable library of document templates with preview and download.

Content:

• HL Patents Style.dotm (already live)
• BuildingBlocks from mWorkRepo (Tables, Headings, Phrases, Elements — 63 blocks)
• Model documents (Statement of Claim, Defence, etc. — from HL Model Documents project)
• Legal writing templates (research memo, client letter)
• Court-specific cover sheets

Per template:

• Name, description, category
• Preview (rendered HTML or screenshot)
• Download (via existing file proxy)
• Usage instructions
• Version info (last updated)

Why: The current downloads page is a flat list. As the template library grows, it needs categorization, preview, and proper metadata. This is the distribution channel for the HL Model Documents project.

Implementation:

• Expand /downloads into a proper library
• Template metadata in JSON (or extend fileRegistry)
• Preview generation (could be pre-rendered screenshots stored in Gitea)
• Category filters (Schriftsätze, Vorlagen, Tabellen, Blöcke)

Effort: ~8 hours | Impact: High (central template distribution)

---

3.3 Schulungsbereich (Training Hub)

What: Onboarding and continuing education section for patent team members.

Content:

• "Getting Started" guide for new associates
• UPC Training materials (from mWorkRepo UPC Training sessions)
• Video guide links (from mWorkRepo UPC Video Guides)
• HL Patents Style tutorial (how to use the template)
• nUPCMS user guide (filing in the new CMS)
• FAQ section

Why: Onboarding a new associate to UPC practice currently requires multiple senior-lawyer meetings. A self-serve training section lets associates learn the basics before those meetings, making the meetings more productive.

Implementation:

• New section: /schulung
• Static content pages with structured lessons
• Progress tracking (optional, via localStorage)
• Embedded video links
• Quiz/self-check elements (optional)

Effort: ~6 hours (code) + ~10 hours (content) | Impact: Medium-High (onboarding efficiency)

---

3.4 Benachrichtigungen (What's New)

What: Simple notification system showing what's been added or updated on patholo.

Features:

• "What's New" badge on sidebar when new content exists
• Changelog page with dated entries
• Optional: browser push notifications for major updates

Why: Content platforms die when users stop checking for new content. A visible "new content" indicator brings people back.

Implementation:

• JSON file with changelog entries
• Last-seen timestamp in localStorage per user
• Badge counter in sidebar
• Simple changelog page

Effort: ~3 hours | Impact: Medium (retention mechanism)

---

Phase 4: Advanced (High effort, Long-term)

These are ambitious features that require significant investment but would make patholo truly indispensable.

4.1 KI-Recherche (AI-Powered Research)

What: Claude-powered research assistant for patent law questions.

Features:

• Chat interface for patent law questions
• Grounded in patholo content (glossary, guides, case law, fee tables)
• Can answer: "What's the deadline for filing a defence in UPC infringement?" or "What are the court fees for Streitwert 5M at LG?"
• Sources cited for every answer

Why: This is the endgame — a patent law assistant that knows HL's practice. But it requires a solid content foundation (Phases 1-3) to be useful, and careful guardrails to avoid hallucination in a legal context.

Effort: ~20 hours | Impact: Transformative (if done right)

---

4.2 Fristenkalender (Deadline Calendar)

What: Integration between the Fristenrechner and external calendar systems.

Features:

• Export calculated deadlines as .ics file (for import into Outlook/Google Calendar)
• Optional: CalDAV sync (write deadlines directly to a shared calendar)
• Reminders with configurable lead time

Why: The Fristenrechner calculates deadlines but doesn't connect to where lawyers actually manage their time. Calendar export closes this gap.

Effort: ~8 hours | Impact: High (workflow integration)

---

4.3 Collaborative Annotations

What: Allow users to add notes, tips, and corrections to patholo content.

Features:

• Comment/note button on guides, checklists, case law entries
• Notes visible to all patholo users
• Upvoting for useful notes
• Moderation (flag inappropriate content)

Why: The best knowledge comes from practitioners. Allowing annotations turns patholo from a one-way publication into a living knowledge base. But this requires a database (Supabase) and moderation.

Effort: ~15 hours | Impact: High (knowledge capture)

---

4.4 Mandantenkosten-Report (Client Cost Report)

What: Generate branded PDF cost estimates for clients using Kostenrechner data.

Features:

• Kostenrechner -> "Generate Report" button
• Branded PDF with HL logo, date, matter reference
• Scenario comparison in the report
• Customizable cover letter text
• Downloadable as PDF

Why: Partners need to send cost estimates to clients. Currently they use the Excel calculator and manually format a memo. A one-click branded PDF saves hours and looks professional.

Effort: ~10 hours | Impact: Medium-High (client-facing)

---

Prioritized Backlog (Summary)

#	Feature	Phase	Effort	Impact	Priority
1.1	Link Hub	1	2h	High	P0
1.2	More Downloads	1	1h	Medium	P0
1.3	Gebührentabellen	1	4h	Med-High	P0
1.5	Kostenrechner Enhancements	1	6h	High	P1
1.4	Patentglossar	1	5h	Medium	P1
2.4	Checklisten	2	7h	High	P1
2.1	Verfahrensleitfäden	2	14h	Very High	P2
2.3	UPC Rechtsprechung	2	14h	Very High	P2
2.2	Gerichtsverzeichnis	2	8h	Med-High	P2
3.4	Benachrichtigungen	3	3h	Medium	P2
3.1	Suchfunktion	3	6h	High	P3
3.2	Vorlagenbibliothek	3	8h	High	P3
3.3	Schulungsbereich	3	16h	Med-High	P3
4.2	Fristenkalender	4	8h	High	P3
4.4	Mandantenkosten-Report	4	10h	Med-High	P4
4.3	Collaborative Annotations	4	15h	High	P4
4.1	KI-Recherche	4	20h	Transformative	P5

---

Architecture Notes

Data Strategy

Most Phase 1 and 2 features use static JSON data loaded at Go server startup. This keeps the stack simple (no new database tables needed) and content is version-controlled in git. Content updates = git commits = automatic deploy.

When content grows beyond what's practical in JSON files (Phase 3+), migrate to Supabase tables with a simple admin API.

Content Pipeline

New content follows this flow:

1. Practitioner identifies need (or new case law / template)
2. Content written/curated (by knowledge lawyer or contributor)
3. Added to patholo repo as JSON/markdown
4. PR reviewed and merged
5. Auto-deploy via Dokploy webhook

Navigation Expansion

The sidebar currently has: Home, Kostenrechner, Fristenrechner, Downloads. With new pages, reorganize into groups:

Werkzeuge
  Kostenrechner
  Fristenrechner
  Gebührentabellen

Wissen
  Verfahrensleitfäden
  Rechtsprechung
  Glossar
  Checklisten

Ressourcen
  Downloads / Vorlagen
  Nützliche Links
  Gerichte
  Schulung

What patholo Is NOT

• Not a case management system — that's KanzlAI
• Not a document management system — that's SharePoint/netDocuments
• Not a billing tool — that's the firm's practice management system
• Not a CMS — content lives in git, not a database with a CMS UI

patholo is a knowledge platform and toolkit: curated content, practical tools, quick reference. Fast, focused, friction-free.

---

Recommendation

I can implement Phase 1 features myself — I have the deepest context from this design work. The Link Hub (1.1) and More Downloads (1.2) are particularly quick wins that could ship today. The Gebührentabellen (1.3) and Glossar (1.4) need some content curation but the code is straightforward.

Phase 2 features need content collaboration (practitioner input for guides, case law curation). The code can be built by a coder worker, but the content requires domain expertise.

Decision for head: assign implementation to me (with coder role) or hand off to a separate coder?