Rules & Regulations

Four core models drive the domain. RuleDocument represents a regulation (FIPJP playing rules, national supplement, regional bylaw); RuleVersion holds each immutable revision with a structured diff against its predecessor; RuleInterpretation classifies clarifications as faq, case_law or guidance and chains them through a precedent_of relationship so an interpretation can quote and extend earlier ones; RuleChangeSubscription expresses 'tenant X wants notified when rule Y or any rule in domain Z changes'. Every RuleDocument moves through a workflow draft → proposed → approved → archived.

While in proposed, the change goes through the normal commission process from F01.02 (motion → discussion → adoption decision); once approved the new RuleVersion becomes effective on its activation date. Translation status is tracked per language (43 supported), with explicit pending/in_review/published states so a multilingual federation can see which articles still need to be translated before activation. Search is multilingual and returns hits across the whole repository; cross-reference walking uses a BFS graph so an operator can trace 'show me every regulation that references FIPJP article 19' two or three hops out.

The interpretation database supports the same search and exposes a precedent chain view. When a RuleVersion is published, the change-event fan-out runs: it loads every RuleChangeSubscription that matches, writes a RuleChangeEvent (per-tenant, audit-grade), and emits a FEDERATION_CIRCULAR notification through the F01.05 correspondence channel. The whole surface is scoped per tenant — an SBF rule supplement is invisible to FFPJP unless a public sharing flag is explicitly set.