FVL-04 — Data Onboarding Through Existing Data Exchange

[Sekiph82]

Tracker: docs/FORMULAB_V1_TASK_TRACKER.md#fvl-04--data-onboarding-through-existing-data-exchange

Use the existing Data Exchange Center (24-template registry) for material master, supplier, TDS/SDS, specifications, price history, inventory, exchange rates, process parameters, and regulatory rule/evidence content imports. No crawler, no parallel import framework. 12 tasks (FVL-04.001..012).

Acceptance criteria: every required template confirmed sufficient or extended within the existing registry; regulatory seed rules stay not_verified until real qualified content is supplied; real sample-file acceptance per template.

Dependencies: none blocking (can run alongside FVL-02/03 per dependency graph, not started as a separate parallel top-level effort).

Scope freeze rule: see docs/FORMULAB_V1_FINAL_SCOPE.md — no supplier web crawler.

[Sekiph82]

FVL-04 scope expanded from 12 to 26 tasks (documentation/tracker-only session, 2026-08-18 — no implementation).

Approved: enterprise external-source connector/mapping/crosswalk onboarding (FVL-04.013-.025) plus a human-readable literature/formulation artifact naming convention (FVL-04.026). Full detail in docs/FORMULAB_V1_TASK_TRACKER.md's FVL-04 section.

Architecture (audited existing Data Exchange first — confirmed no alias/header-mapping, external-ID crosswalk, or schema-discovery capability exists today, so this is genuinely new, not a duplicate):

Customer/External System -> read-only Connector/Extractor -> Source Staging -> Schema Discovery -> Customer Mapping Profile -> Transformation/Crosswalk Resolution -> canonical FormuLab import objects -> EXISTING Data Exchange preview -> EXISTING validation -> human review -> EXISTING explicit commit -> EXISTING import history.

• Existing Data Exchange Center remains the sole preview/validation/commit/history authority — this is NOT a second import platform.
• External-ID crosswalk required (sourceSystem/sourceEntity/sourceRecordId -> canonicalEntity/canonicalRecordId); stable IDs preferred over display-name matching, no name-only silent matching.
• Reusable, versioned customer mapping profiles — one source entity can fan into multiple canonical record types (e.g. one raw-material row -> RawMaterial + Supplier + MaterialSupplier + MaterialPrice + InventoryRecord).
• File (CSV/XLSX/JSON/XML), generic read-only database, and REST API extraction — generic connector architecture only; no vendor-specific ERP connector unless separately approved later.
• Formula/recipe and laboratory/test-result migration bridges into the EXISTING Formulation/FormulationVersion/FormulationLine and LaboratoryTrial/TestResult records — never a second laboratory platform (FVL-06 still owns the structured measured-response expansion).
• Incremental re-import/conflict handling: same external record -> same canonical identity every time, no duplicate records, dry-run/preview before commit.
• FVL-04.026: deterministic LIT_/FORM_ filename conventions plus separate human-readable display titles for literature and formulation artifacts — original source filename, DOI/URL, acquisition timestamp and content hash always preserved as provenance, never destroyed by display renaming.

Also corrected a stale completion-count summary table in the tracker (FVL-03's row and the Total row hadn't been recomputed since FVL-03.002-.008 closed) — recomputed directly from the tracker's own per-task status cells: 59/171 tasks completed (34.5%), overall total 157 -> 171.

No FVL-12 created. All 14 new FVL-04 tasks remain blank — no implementation started. Current execution pointer unchanged: FVL-03.009, NOT STARTED.

Commit: 94f04f0. Pushed to origin/feature/laboratory-stability.