Federation & Governance

54 features · 6 subsystems

Management of the global petanque organizational hierarchy from FIPJP down to individual clubs, including governance structures, commissions, elections, and inter-federation coordination.

Federation Hierarchy Management

F01.01

Platform+

Management of the federation structure using **standalone tenants** — every federation (national, continental, FIPJP) is independent. Combined with **OrgNodes** for clubs within each national tenant.

ID	Status	Features
F01.01.01	Platform	Standalone tenant per federation (national, continental, world)
F01.01.02	Platform	Tenant creation, configuration, branding
F01.01.03	Platform+	Federation profile pages (logo, address, contacts, statutes, history)
F01.01.04	Planned	Federation type classification (continental, national, world)
F01.01.05	Planned	Public API for cross-tenant interactions (license verification, ITC, squad submission)
F01.01.06	Planned	Federation status tracking (active, suspended, provisional, expelled)
F01.01.07	Planned	Federation founding date, affiliation date, recognition history
F01.01.08	Planned	Federation directory (public listing of known federations and their API endpoints)
F01.01.09	Planned	Federation map visualization (geographic boundaries)
F01.01.10	Planned	Federation statistics dashboard (members, clubs, competitions per level)
F01.01.11	Platform+	Clubs as OrgNodes under their district in the OrgNode hierarchy
F01.01.12	Planned	District management (OrgNodes with authority — sanction, DM, boards)
F01.01.13	Planned	Configurable district hierarchy depth per tenant (0 levels: Norway; 1 level: Sweden/Germany; 2+ levels: France ligue→comité)
F01.01.14	Platform+	District-based scope filtering (district admin sees clubs in their OrgNode subtree)
F01.01.15	Planned	Configurable OrgNode capabilities per level — each OrgNode level can be granted: can_sanction (and which competition levels), can_set_license_price, has_discipline_body, can_issue_licenses, has_own_league. This supports Spain's autonomous federations (near-tenant power), France's comités (sanction + discipline), and Sweden's districts (sanction local/DM only).
F01.01.16	Planned	OrgNode type registry per tenant — tenant defines its OrgNode types with localized names (e.g., Sweden: "distrikt"/"klubb", France: "ligue"/"comité"/"club", Germany: "Landesverband"/"Verein", Spain: "federación autonómica"/"club")

Governance Bodies & Commissions

F01.02

Planned

ID	Status	Features
F01.02.01	Planned	Commission/committee registry (disciplinary, umpire, medical, selection, etc.)
F01.02.02	Planned	Commission membership management (chair, members, terms)
F01.02.03	Planned	Commission mandate and scope definition
F01.02.04	Planned	Meeting management (agenda, minutes, decisions)
F01.02.05	Planned	Decision tracking and publication
F01.02.06	Planned	Term limits and rotation tracking
F01.02.07	Planned	Conflict of interest declarations
F01.02.08	Platform	Audit trail on all governance actions

Elections & Voting

F01.03

Shipped

Implemented in PL-1601. API: `specs/api/endpoints/elections.md`.

ID	Status	Features
F01.03.01	Shipped	Election scheduling and announcement
F01.03.02	Shipped	Candidate registration and profile
F01.03.03	Shipped	Voter eligibility rules per federation level
F01.03.04	Shipped	Secure online voting (anonymous, verifiable)
F01.03.05	Shipped	Vote counting and result publication
F01.03.06	Shipped	Proxy voting support
F01.03.07	Shipped	Audit trail on voting processes

Rules & Regulations

F01.04

Planned

Implemented in PL-1602. API: `RuleDocument`, `RuleVersion`, `RuleInterpretation` models with full CRUD, versioning with diff, workflow (draft→proposed→approved→archived), translation status tracking, search, cross-references, and interpretation database. Spec: `specs/api/endpoints/rules.md`.

ID	Status	Features
F01.04.01	Planned	Rule repository with versioning (FIPJP official rules) ✅
F01.04.02	Planned	National/regional rule variations and supplements ✅
F01.04.03	Planned	Rule change proposal workflow ✅
F01.04.04	Planned	Rule translation management (multi-language) ✅
F01.04.05	Planned	Rule search and cross-reference ✅
F01.04.06	Planned	Rule interpretation database (FAQs, case law) ✅
F01.04.07	Planned	Notification of rule changes to affected federations ⏳ Future (requires notification integration)

Inter-Federation Communication

F01.05

Platform+

ID	Status	Features
F01.05.01	Platform+	Official correspondence system (federation to federation)
F01.05.02	Planned	Circular distribution (FIPJP to all members)
F01.05.03	Platform+	Document sharing between federation levels
F01.05.04	Planned	Calendar synchronization across federation levels
F01.05.05	Planned	Congress/general assembly management
F01.05.06	Planned	Resolution tracking and compliance monitoring

Club Management

F01.06

Platform+

Clubs are **OrgNodes** under their district in the OrgNode hierarchy.

ID	Status	Features
F01.06.01	Platform+	Club registration as OrgNode under district in the OrgNode hierarchy
F01.06.02	Planned	Club profile (name, logo, venue, contact, founding year)
F01.06.03	Planned	Club board/officers management (president, secretary, treasurer, etc.)
F01.06.04	Planned	Club affiliation status and annual renewal
F01.06.05	Planned	Club member roster management
F01.06.06	Planned	Club statistics (members, competitions hosted, results)
F01.06.07	Planned	Club-to-club communication
F01.06.08	Planned	Club search/directory (by district, facilities, level)
F01.06.09	Planned	Club document management (statutes, insurance, permits)
F01.06.10	Planned	Safeguarding officer designation and tracking

Next domain

02 Identity & Access Management