Edit Summary

HkbVnNTy8-hmZ2zOnl1vmDQNfjjD6Yb6vvXGGCWANJ-guCb2ibIK9HAXTwY_7s3SbxZEdjZaGs28zBNTIE9oGCqODHFeyNPN8cgUhUF2PwI4FLCg1yVAYD0xE-U3

Back

Edit the source note directly. Frontmatter stays at the top.

---
Meeting Date: Unknown
Meeting Type: 1x1
Note Type: Summary
Attendees:
  - Scott Warner
  - Amity Sendama
---

## 1.  Meeting Summary

I used this 1x1 with Amity to debrief the recent bankruptcy hearing involving Matt King and discuss a few operational items across SAP, AdaptDx, and IT support.  The bankruptcy discussion was the most substantive topic.  Key outcome from the hearing was an agreement for Matt King to receive compensation at a $360,000 annualized rate, lower than his historical pay level of roughly $450,000, in exchange for moving forward with a CRO.  The cash collateral issue appears likely to move ahead following submission of the required reporting, but the larger open question remains whether the DIP financing should be supported.  My takeaway is that the CRO will be critical to establishing whether the business has any long-term viability and whether the underlying financials can be trusted.

We also discussed claim strategy and legal process.  Amity is setting up time with counsel on Monday to review how we should present our claim, especially given the confidential settlement agreement.  Current legal guidance is that we should not attach the agreement directly, but instead reference that the claim is supported by a confidential agreement available upon request.  There was also clear alignment that no release of personal fraud-related exposure should be considered.

On the operations side, I updated Amity on the SAP outage response.  The logistics team is largely stable, but UPS manifest gaps remain a significant issue because we cannot reliably determine what was loaded to which truck.  More broadly, HQ appears to have made progress overnight, and the issue may be more manageable than initially feared, although root cause still needs to be investigated.  We also aligned on AdaptDx governance, where I am pulling together a consolidated list of open items ahead of the ELT check-in since several privacy and related cross-functional topics sit with me.

Finally, I helped Amity assess a suspicious invoice email.  I confirmed it was phishing, advised her not to engage with attachments, and walked her through reporting it through our phishing reporting tool so our email security system can learn from it.

## 2.  Attendee List

- Scott Warner
- Amity Sendama

## 3.  Action Items

- [Amity] Schedule and lead Monday discussion with counsel regarding bankruptcy claim strategy and treatment of the confidential settlement agreement.
- [Amity] Prepare the claim documentation and have the underlying agreement ready for review with counsel.
- [Legal / Counsel] Advise on claim language that references the confidential agreement without attaching it directly.
- [Scott] Continue supporting the SAP recovery effort with the operations team, particularly logistics.
- [Scott] Work with logistics to manually reconstruct shipment details where UPS manifest data cannot be regenerated.
- [Scott] Consolidate AdaptDx open topics and prepare an organized update ahead of the ELT check-in.
- [Scott] Continue supporting Lisa on meeting recording and information capture for interviews/reports.
- [Scott] Obtain requested reports for Lisa, as approved by Amity.
- [Amity] Report suspicious invoice email as phishing.
- [IT / Email Security] Review why the phishing email bypassed controls and use the submission to improve future filtering.

## 4.  Relevant Timelines

- Monday - Amity to meet with counsel to review bankruptcy claim approach and confidentiality handling.
- Next couple of days - Expected target for CRO appointment, pending agreement among the committee, Tiger, and Matt King.
- After CRO is in place - CRO to assess the business and help inform whether DIP financing makes sense.
- Due immediately / same day - Suspicious invoice email claimed payment was due that day, but it was confirmed as phishing and should be disregarded.
- Today - I planned to test the recording process with Lisa after our discussion.
- Ongoing / near term - AdaptDx ELT check-ins are now set for every other week.

## 5.  Additional Notes

- The overall tone from the hearing suggested very low confidence in Matt King's reporting credibility.
- Tiger's counsel was openly critical of the quality of reporting, which reinforced the concern that reliable operating and financial visibility is still missing.
- Fraud-related issues appear likely to remain separate from the bankruptcy resolution process, with potential follow-on claims afterward.
- The CRO appears to be the most important near-term control mechanism because that role should provide access, independent assessment, and fiduciary accountability across stakeholders.
- There is still some uncertainty around why a top-tier law firm would pursue the matter unless there is a stronger recovery path than is currently obvious.
- SAP disruption appears to have originated from a Poland-related change, reportedly tied to a legal or finance update, though the precise root cause is still unclear.
- For logistics, the biggest SAP-related operational exposure is not whether shipments occurred, but the inability to map specific items to specific trucks due to manifest regeneration issues.
- AdaptDx continues to create meeting overhead, but the recurring ELT cadence should help keep leadership aligned on cross-functional issues, especially privacy-related items in my area.
- The phishing example was a good reminder that these messages are getting more convincing, likely aided by AI, and that user reporting remains important even when something looks obviously suspicious at first glance.