Files
paliad/internal/db/migrations/050_bilateral_rules_backfill.down.sql
m 4d820892e8 feat(t-paliad-133): Phase A — event taxonomy schema + seed + bilateral flag
Three migrations land the data layer for the Fristenrechner v3 decision
tree (Pathway B / B1) plus the bilateral-rule flag for the new party-
perspective selector. All purely additive — no breaking changes to the
v2 (t-paliad-131) corpus.

Migration 048 — schema:
- paliad.event_categories: recursive taxonomy tree (parent_id self-FK,
  unique slug as materialised dot-path, step_question_de/en on internal
  nodes, is_leaf bool, optional emoji icon).
- paliad.event_category_concepts: many-to-many junction (leaf →
  deadline_concepts) with optional proceeding_type_code narrowing.
  UNIQUE NULLS NOT DISTINCT prevents duplicate (leaf, concept, NULL)
  rows (PG 15+).
- paliad.deadline_rules.is_bilateral bool: when true AND
  primary_party='both', the rule mirrors into both party columns of
  the v3 columns view; otherwise 'both' resolves single-side via the
  perspective selector.

Migration 049 — seed taxonomy:
6 root buckets (cms-eingang, muendl-verhandlung, beschluss-entscheidung,
frist-verpasst, ich-moechte-einreichen, sonstiges) with 70+ leaves and
115+ junction rows. Tree depth reaches 4 today (cms-eingang › gericht
› endentscheidung › <leaf>) but the schema supports unlimited depth
per design lock §10 Q2. Coverage gate at the end raises if any
category='submission' concept is unreachable from a leaf, except the
3 pure-administrative slugs (filing, request-for-examination,
approval-and-translation) that live on Pathway A only.

Migration 050 — bilateral backfill:
Tags exactly 4 genuinely-bilateral rules:
- de_null.stellungnahme (Stellungnahme zum Hinweisbeschluss, PatG §83.2)
- epa_opp.r79_further (Stellungnahme weiterer Beteiligter)
- epa_opp.r116, epa_app.r116 (Eingaben vor mündl. Verhandlung)
All other primary_party='both' rules (Berufungsfristen, Anschlussberufung,
…) are role-swap appeals that resolve via the perspective selector at
render time.

Schema dry-run validated end-to-end against Supabase PG 15.8.

Design ref: docs/plans/unified-fristenrechner-v3.md §4.1 + §10 Q12.
2026-05-05 10:49:18 +02:00

10 lines
243 B
SQL

-- t-paliad-133 Phase A bilateral-tag rollback.
UPDATE paliad.deadline_rules
SET is_bilateral = false
WHERE code IN (
'de_null.stellungnahme',
'epa_opp.r79_further',
'epa_opp.r116',
'epa_app.r116'
);