{
  "title": "Holding company subsidiary snapshot data for AI",
  "source_page": "https://fiund.com/industries/holding-company-subsidiary-snapshot-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Separate a disclosed relationship from a proposed acquisition",
    "context": "An invented holding company has similarly named affiliates. Its package contains a dated disclosure, a proposal and one completed transaction record. The assistant must keep the evidence for each relationship separate.",
    "records": [
      [
        "LIST-D1",
        "Original fictional disclosure",
        "At day 1, Harbor Holdings lists Pine Works LLC as its subsidiary. Pine Works Services LLC is not listed."
      ],
      [
        "PROPOSE-D3",
        "Invented planning note",
        "A team proposes acquiring Pine Works Services LLC. The note is labeled unapproved and supplies no closing date."
      ],
      [
        "CLOSE-D8",
        "Original completion record",
        "A completed transaction on day 8 concerns Pine Works Distribution LLC. Its exact legal name differs from both other entities."
      ],
      [
        "LIST-D10",
        "Later fictional disclosure",
        "At day 10, the list names Pine Works LLC and Pine Works Distribution LLC. It makes no statement about Pine Works Services LLC."
      ]
    ],
    "question": "Which two subsidiary relationships are supported by LIST-D10? Does the package establish that Pine Works Services LLC became a subsidiary?",
    "answer": "LIST-D10 supports the stated day-10 listing of Pine Works LLC and Pine Works Distribution LLC. CLOSE-D8 supplies a separate completed event for Distribution. Nothing supplied establishes a completed acquisition or listed relationship for Services. PROPOSE-D3 is a planning note, and the similar names do not connect Services to Distribution's transaction. Preserve the exact entity names and the disclosure date. The absence of Services from a list also does not establish every possible legal or economic relationship involving it.",
    "failureModes": [
      "Merging the Services and Distribution entities because their names share a prefix.",
      "Converting the proposed acquisition into a completed relationship.",
      "Using the day-1 disclosure to answer an explicitly day-10 listing question."
    ],
    "fields": [
      [
        "Exact entity identity",
        "Keep a stable fictional identifier in addition to the displayed name."
      ],
      [
        "Disclosure date",
        "State which snapshot supports the answer."
      ],
      [
        "Event status",
        "Preserve the difference between a proposal and a supplied completion record."
      ],
      [
        "Relationship scope",
        "Describe only the listed relationship, without inferring reporting or beneficial-ownership treatment."
      ]
    ],
    "holdout": "Replace CLOSE-D8 with a canceled transaction and leave the later list unavailable. Test whether the assistant retains the earlier supported listing and leaves the new relationship unresolved.",
    "boundary": "All names and transactions are invented for source-matching practice. The example provides no legal ownership determination, filing advice or disclosure of an actual corporate structure. Real archives need source-specific authority and transaction-confidentiality review."
  }
}