Inter-Federation Communication

Five document types underpin the domain. Correspondence captures peer-to-peer official letters between two federations with sender, recipient, subject, body, attachments and a delivery state. The same model handles circulars: instead of one recipient, FIPJP (or a continental body) broadcasts to every member federation in scope, and each recipient gets its own delivery row so read-receipts are tracked per tenant.

SharedDocument stores documents that one federation level publishes to another (FIPJP statutes shared down to nationals, a national supplement shared down to districts) with explicit versioning so the consumer always knows which revision they are looking at. CalendarSyncSubscription drives federation→district calendar fan-out; each subscription holds an event-type allow-list, so a district can pull only national championships and not, say, internal training camps. Congress is the heaviest object: a state machine plan → convene → start → complete (or cancel) with agenda items, handlingar, decisions and adopted resolutions.

Each Resolution has a follow-up plan with a deadline; the dedicated /resolution-compliance router aggregates all adopted resolutions across the federation's congresses and reports follow-up counters per state (not_started, in_progress, completed, overdue) plus a compliance_rate. An idempotent refresh-overdue sweep transitions resolutions whose deadline has passed into the overdue bucket so dashboards stay current without human intervention. Cross-tenant traffic uses the public API surface — a circular sent from FIPJP to FFPJP arrives in FFPJP's tenant via the public correspondence endpoint, never via direct database read.