## From:

Sent: 
To: 
Subject:

Karyna Shuliak <blackened out>
Friday, January 4, 2019 2:44 PM
Caroline O Ryan
Re: 10F

Ok, thank you

- Participants: Person A (email sender in multiple messages), Person B (replying), Person C (third party referenced). Several email addresses/lines are redacted as [redacted].

- Thread timeline (concise):
  - Jan 3, 2019, 4:22 PM — Person A: Spoke with Person C about meeting progress; crew just back from vacation; tomorrow Person C will have a full crew in 10F, so they will meet at end of day. Note: "1/11 Tub is scheduled to be reglazed."
  - Jan 3, 2019, 7:14 PM — Person B: Thanks for update; asks what time the meeting with Person C is tomorrow.
  - Jan 4, 2019, 1:35 AM — Person A: No set time yet but expects to go over around 2:00 PM; will text Person C in the morning.
  - Jan 4, 2019, 9:25 AM — Person B: Asks to be informed when Person A is heading there; will try to meet as well.
  - Jan 4, 2019, 9:43 AM — Person A: Texted Person C and will update when he responds; will be at the apartment approx 1:45–2:00 PM.

- Key items: planned meeting on Jan 4 around 1:45–2:00 PM / ~2:00 PM; crew working in unit 10F tomorrow; tub reglazing scheduled for 1/11; multiple redacted email addresses/lines.

## From: (cont.)

Key entities and information from the image:

*   **Emails:**
    *   Karyna Shuliak to Caroline (Dec 28, 2018, 3:01 PM): Thank you and happy new year
    *   Caroline O Ryan to Karyna (Dec 28, 2018, 2:23 PM):Met with Andrew to review items, will meet again next week.
    *   Karyna Shuliak to Caroline (Dec 28, 2018, 2:13 PM): Christmas wishes and asking about "10F".
*  **Additional Data**: includes XML version, encoding, and keys such as conversation-id, date-last-viewed, and date-received.

## From: (cont.)

<key>flags</key>

<integer>8590195713</integer>

<key>remote-id</key>

<string>15086</string>

</dict>
</plist>