{
  "title": "Boat-building data for AI hull and build identifiers",
  "source_page": "https://fiund.com/industries/boat-hull-build-identifier-views-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Do not merge two views without a stable hull key",
    "context": "Original paper hulls use neutral mock identifiers deliberately unlike actual registrations.",
    "records": [
      [
        "1",
        "Build ledger",
        "H17 and H71 are separate hull props of the same style."
      ],
      [
        "2",
        "Bow image",
        "Readable H17 identifier."
      ],
      [
        "3",
        "Stern image",
        "Identifier partly hidden as H?7; folder says H71."
      ]
    ],
    "question": "Can the stern view be labeled as a confirmed second view of H17?",
    "answer": "No. Record 2 confirms H17 for the bow, but record 3 supplies a partial mark and a conflicting folder suggestion. Record 1 establishes multiple similar hulls. Keep the stern identity unresolved and request a clearer mark or valid capture manifest.",
    "failureModes": [
      "Grouping by matching silhouette",
      "Using folder labels as physical identifier proof"
    ],
    "fields": [
      [
        "visible_identifier",
        "Records readable characters only"
      ],
      [
        "capture_view",
        "Distinguishes bow and stern evidence"
      ],
      [
        "identity_join_status",
        "Prevents merging uncertain images"
      ]
    ],
    "holdout": "Add a capture manifest linking both views to H17 and retain the folder conflict as metadata.",
    "boundary": "No actual vessel registration, locations, customer data, seaworthiness or build plans."
  }
}