Turfi Platform Documentation

Pre-Validation Handling

• Invalid lookup and relationship values should be intercepted before the row reaches database validation.
• The import engine may pause rows with structured mismatch context instead of immediately failing them when review is supported.

Enum / Lookup Mismatch Flow

• Detect unknown or ambiguous values before write payload assembly.
• Offer a canonical mapped value where a safe operator decision is possible.
• Persist the canonical key/id only after the mapping choice is explicit.

Mapping Examples

• A source value such as completed does not belong in a constrained status field unless it is intentionally remapped to a documented lifecycle value such as archived through operator review.
• Human-readable relationship values such as league or organization names should be mapped to canonical records before the import resumes.

User Interaction Expectations

• Operators should see which field failed, which raw value was supplied, and which target entity or lookup was expected.
• Repeated unresolved values should reuse the same import-scoped mapping when possible.
• Broken critical relationships must not be auto-ignored or silently written as nulls.