Vessel particulars

ADMINISTRATOR The Ship's Particulars PDF is the single source of truth for top-level vessel facts. On approval of the extracted Particulars, IMO and DWT (Summer Salt Water) propagate to the vessels table and become authoritative.

Where it lives

• vessel_particulars — JSON blob with general particulars + nested equipment + nested tanks
• vessel_particulars.source_doc_ids[] — JSON array of source-doc IDs that contributed (added by migration 0100)
• vessel_particulars_provenance(vessel_id, field_path, source_document_id, provenance_quality) — per-field provenance
• vessels.particulars_pdf_id — pointer to the source doc (added by migration 0085)

Particulars priority rule (v2.23.1)

When the operator approves the extracted particulars:

1. The wizard form fields (IMO + DWT) are written to vessels
2. An audit_log entry records the propagation
3. Any subsequent inline edit on the vessel-profile page that disagrees with the doc value flips the field to provenance_quality='manual_override' AND writes a field_overrides_log row

Backfill provenance

For pre-v2.31.0.19 vessels, POST /api/admin/backfill/vessel-particulars-provenance {} — coarse heuristic from vessel_particulars.source_doc_ids[]. Idempotent.