Federation System Integration

Each federation that already runs a homegrown registry, ranking engine, or licensing portal is modelled as a FederationIntegrationConfig with a draft→active→paused→decommissioned lifecycle, a versioned field-mapping document, and a sync-state snapshot that records last-pulled cursor, last-pushed sequence, and resolved schema version. Legacy data lands through the file-import service: a FileFormatDefinition declares the format (CSV, XML, or fixed-width), column boundaries, encoding, and per-column transforms; POST /parse streams the upload, the fixed-width column parser materialises rows, and an ImportValidationReport runs a configurable rule engine (required, type, format, range, uniqueness) before any record touches a domain collection. Errors are streamable, filterable, and re-runnable.

For FIPJP exchange, FipjpSubmission wraps payloads in the canonical envelope (header, signed body, attachments), validates per submission type (player, license, transfer, ranking), and tracks lifecycle draft→submitted→accepted/rejected with the FIPJP receipt id stamped back on success. Continental bodies (CEP and others) use ContinentalExchangeSession to coordinate multi-tenant data drops with per-participant tracking and an initiated→in_progress→completed/failed/cancelled lifecycle. Federations that need both pull and push run a BidirectionalSyncSession that interleaves pulling, pushing, and resolving_conflicts states; conflicts are detected via row-level hash comparison, surfaced with local/remote diff payloads, and resolved via configurable strategies (last-write-wins, manual, prefer-local, prefer-remote).

One-shot legacy onboarding uses MigrationJob, which validates first, then runs in batched transactions with dry-run, progress streaming, and full rollback if the post-migration assertion suite fails.