KanzlAI-mGMT

m/KanzlAI-mGMT

Fork 0

Commit Graph

Author	SHA1	Message	Date
m	54c6eb8dae	feat: 15 UPC proceeding types in 3 groups + category field Added 10 new UPC types: DNI, EPO, AMD, CCI, EVP, DAM, COS, REH, DEF, RST. Grouped as: Hauptverfahren / Verfahren im Verfahren / Rechtsbehelfe. Frontend dropdown shows sub-groups within jurisdiction. German names throughout.	2026-03-30 19:34:07 +02:00
m	a89ef26ebd	feat: UPC deadline determination — event-driven model with proceeding timeline Full event-driven deadline determination system ported from youpc.org: Backend: - DetermineService: walks proceeding event tree, calculates cascading dates with holiday adjustment and conditional logic - GET /api/proceeding-types/{code}/timeline — full event tree structure - POST /api/deadlines/determine — calculate timeline with conditions - POST /api/cases/{caseID}/deadlines/batch — batch-create deadlines - DeadlineRule model: added is_spawn, spawn_label fields - GetFullTimeline: recursive CTE following cross-type spawn branches - Conditional deadlines: condition_rule_id toggles alt_duration/rule_code (e.g. Reply changes from RoP.029b to RoP.029a when CCR is filed) - Seed SQL with full UPC event trees (INF, REV, CCR, APM, APP, AMD) Frontend: - DeadlineWizard: interactive proceeding timeline with step-by-step flow 1. Select proceeding type (visual cards) 2. Enter trigger event date 3. Toggle conditional branches (CCR, Appeal, Amend) 4. See full calculated timeline with color-coded urgency 5. Batch-create all deadlines on a selected case - Visual timeline tree with party icons, rule codes, duration badges - Kept existing DeadlineCalculator as "Schnell" quick mode Also resolved merge conflicts across 6 files (auth, router, handlers) merging role-based permissions + audit trail features.	2026-03-30 11:33:59 +02:00
m	1fc0874893	feat: add database schema and backend foundation Part 1 - Database (kanzlai schema in Supabase): - Tenant-scoped tables: tenants, user_tenants, cases, parties, deadlines, appointments, documents, case_events - Global reference tables: proceeding_types, deadline_rules, holidays - RLS policies on all tenant-scoped tables - Seed: UPC proceeding types, 32 deadline rules (INF/CCR/REV/PI/APP), ZPO civil rules (Berufung, Revision, Einspruch), 2026 holidays Part 2 - Backend skeleton: - config: env var loading (DATABASE_URL, SUPABASE_*, ANTHROPIC_API_KEY) - db: sqlx connection pool with kanzlai search_path - auth: JWT verification middleware adapted from youpc.org, context helpers - models: Go structs for all tables with sqlx/json tags - router: route registration with auth middleware, /health + placeholder API routes - Updated main.go to wire everything together	2026-03-25 13:17:33 +01:00

Author

SHA1

Message

Date

54c6eb8dae

feat: 15 UPC proceeding types in 3 groups + category field

Added 10 new UPC types: DNI, EPO, AMD, CCI, EVP, DAM, COS, REH, DEF, RST.
Grouped as: Hauptverfahren / Verfahren im Verfahren / Rechtsbehelfe.
Frontend dropdown shows sub-groups within jurisdiction. German names throughout.

2026-03-30 19:34:07 +02:00

a89ef26ebd

feat: UPC deadline determination — event-driven model with proceeding timeline

Full event-driven deadline determination system ported from youpc.org:

Backend:
- DetermineService: walks proceeding event tree, calculates cascading
  dates with holiday adjustment and conditional logic
- GET /api/proceeding-types/{code}/timeline — full event tree structure
- POST /api/deadlines/determine — calculate timeline with conditions
- POST /api/cases/{caseID}/deadlines/batch — batch-create deadlines
- DeadlineRule model: added is_spawn, spawn_label fields
- GetFullTimeline: recursive CTE following cross-type spawn branches
- Conditional deadlines: condition_rule_id toggles alt_duration/rule_code
  (e.g. Reply changes from RoP.029b to RoP.029a when CCR is filed)
- Seed SQL with full UPC event trees (INF, REV, CCR, APM, APP, AMD)

Frontend:
- DeadlineWizard: interactive proceeding timeline with step-by-step flow
  1. Select proceeding type (visual cards)
  2. Enter trigger event date
  3. Toggle conditional branches (CCR, Appeal, Amend)
  4. See full calculated timeline with color-coded urgency
  5. Batch-create all deadlines on a selected case
- Visual timeline tree with party icons, rule codes, duration badges
- Kept existing DeadlineCalculator as "Schnell" quick mode

Also resolved merge conflicts across 6 files (auth, router, handlers)
merging role-based permissions + audit trail features.

2026-03-30 11:33:59 +02:00

1fc0874893

feat: add database schema and backend foundation

Part 1 - Database (kanzlai schema in Supabase):
- Tenant-scoped tables: tenants, user_tenants, cases, parties,
  deadlines, appointments, documents, case_events
- Global reference tables: proceeding_types, deadline_rules, holidays
- RLS policies on all tenant-scoped tables
- Seed: UPC proceeding types, 32 deadline rules (INF/CCR/REV/PI/APP),
  ZPO civil rules (Berufung, Revision, Einspruch), 2026 holidays

Part 2 - Backend skeleton:
- config: env var loading (DATABASE_URL, SUPABASE_*, ANTHROPIC_API_KEY)
- db: sqlx connection pool with kanzlai search_path
- auth: JWT verification middleware adapted from youpc.org, context helpers
- models: Go structs for all tables with sqlx/json tags
- router: route registration with auth middleware, /health + placeholder API routes
- Updated main.go to wire everything together

2026-03-25 13:17:33 +01:00

3 Commits