## STRUCTURED OBLIGATION REGISTER Reliable processing is possible because the executed agreement and the supplied supporting schedules are available. No controlled failure condition applies. | Obligation ID | Responsible Party | Obligation | Trigger | Deadline / Timing | Frequency | Conditions | Exceptions | Source Document | Source Clause / Section | Evidence Reference | QA / Uncertainty Flags | Human Review Required | | ------------- | ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | OBL-001 | Provider — Meridian Cloud Systems Ltd. | Provide Customer with access to the Meridian Fleet Analytics platform and related support services during the Subscription Term. | During the Subscription Term | During Subscription Term | Continuous during term | Services are the Meridian Fleet Analytics platform and related support services; Schedule A identifies Fleet Analytics Platform as the Service Scope. | — | Master Software Subscription and Services Agreement; Schedule A | §1 Services; Schedule A — Service Scope | Agreement §1; Schedule A “Service Scope: Fleet Analytics Platform” and “Service Start Date: April 1, 2026” | — | No | | OBL-002 | Provider | Deliver a monthly service report to Customer containing system availability, material service interruptions, support-ticket volumes, and unresolved Severity 1 incidents. | Each reporting month | No later than the fifth Business Day of the following month | Monthly | Report must include the four specified categories. | — | Master Software Subscription and Services Agreement | §2 Monthly Usage Report | §2 | — | No | | OBL-003 | Provider | Notify Customer in writing of a qualifying Security Incident and include, to the extent then known, the nature of the incident, affected systems, categories of information involved, and containment measures taken. | After confirming a Security Incident that materially affects Customer Data | Without undue delay and in any event within 24 hours after confirmation | Event-based | Incident must materially affect Customer Data; notice is written. Schedule B confirms that such incidents are subject to §3. | — | Master Software Subscription and Services Agreement; Schedule B | §3 Security Incident Notice; Schedule B — Security Requirements | §3; Schedule B bullet “Security incidents affecting Customer Data are subject to the notice requirement in Section 3.” | HUMAN REVIEW REQUIRED | Yes — assessment of whether an incident is confirmed and materially affects Customer Data may require professional judgment. | | OBL-004 | Customer — Harborline Distribution Ltd. | Provide Provider with reasonably necessary technical information and designated administrator contacts required for implementation and ongoing support. | When information or administrator contacts are required for implementation or ongoing support | Not stated | As required | Information and contacts must be reasonably necessary and required for the stated purposes. | — | Master Software Subscription and Services Agreement | §4 Customer Responsibilities | §4 | — | No | | OBL-005 | Provider | Maintain commercially reasonable business continuity and disaster recovery procedures applicable to the Services. | During provision of the Services | During Subscription Term / applicable service period | Ongoing | Procedures must be applicable to the Services and commercially reasonable. | — | Master Software Subscription and Services Agreement | §5 Business Continuity | §5 | — | No | | OBL-006 | Provider | Review the business continuity and disaster recovery procedures applicable to the Services. | — | At least annually | Annual | Review applies to the procedures maintained under §5. | — | Master Software Subscription and Services Agreement | §5 Business Continuity | §5 | — | No | | OBL-007 | Provider | Upon reasonable written notice, provide Customer with documentation reasonably necessary to demonstrate compliance with the information-security obligations expressly stated in the Agreement. | Customer gives reasonable written notice | Upon reasonable written notice; no separate response deadline stated | Event-based | Documentation must be reasonably necessary; subject to confidentiality and security restrictions; limited to expressly stated information-security obligations. | Confidentiality and security restrictions | Master Software Subscription and Services Agreement | §6 Audit Support | §6 | — | No | | OBL-008 | Provider | Maintain commercial general liability insurance during the Subscription Term. | During the Subscription Term | Throughout Subscription Term | Continuous during term | Coverage must be commercial general liability insurance. | — | Master Software Subscription and Services Agreement | §7 Insurance | §7 | — | No | | OBL-009 | Provider | Maintain technology errors and omissions coverage during the Subscription Term. | During the Subscription Term | Throughout Subscription Term | Continuous during term | Coverage must be technology errors and omissions coverage. | — | Master Software Subscription and Services Agreement | §7 Insurance | §7 | — | No | | OBL-010 | Provider | Provide Customer with certificates of insurance evidencing the required coverage. | Customer makes a reasonable request | Upon reasonable request; no separate response deadline stated | Event-based | Request must be reasonable; certificates evidence the required coverage. | — | Master Software Subscription and Services Agreement | §7 Insurance | §7 | — | No | | OBL-011 | Either party, if electing non-renewal | Provide written notice of non-renewal if the party does not want the Agreement to renew. | Party elects not to renew | At least 60 days before the end of the then-current Subscription Term | Each applicable renewal cycle | Applies when either party elects non-renewal; otherwise the Agreement automatically renews for successive 12-month periods. | Automatic renewal applies absent timely non-renewal notice | Master Software Subscription and Services Agreement; Schedule A | §8 Renewal; Schedule A — Initial Subscription Term | §8; Schedule A “Initial Subscription Term: 24 months”; “Service Start Date: April 1, 2026” | — | No | | OBL-012 | Each party | Protect Confidential Information received from the other party. | Receipt of Confidential Information from the other party | Not stated | Ongoing while applicable Confidential Information is held | Applies to Confidential Information received from the other party. | — | Master Software Subscription and Services Agreement | §9 Confidentiality | §9 | — | No | | OBL-013 | Each party | Use Confidential Information received from the other party only for purposes of performing or receiving services under the Agreement. | Receipt/use of Confidential Information | During the permitted use period; no separate duration stated | As applicable to each use | Use must be for performing or receiving services under the Agreement. | — | Master Software Subscription and Services Agreement | §9 Confidentiality | §9 | — | No | | OBL-014 | Each party, when delivering an Agreement notice | Deliver notices under the Agreement to the designated legal contacts by email and courier at the addresses stated in the Order Form. | Delivery of a notice under the Agreement | When notice is given; no general notice deadline stated in §10 | Event-based | Delivery is to designated legal contacts using email and courier and the addresses stated in the Order Form. | — | Master Software Subscription and Services Agreement; Schedule A | §10 Notices; Schedule A — Subscription Order Form | §10; Schedule A | MISSING INFORMATION; INCOMPLETE EVIDENCE; HUMAN REVIEW REQUIRED | Yes — the supplied Order Form identifies a Customer Legal Contact email but does not provide the designated Provider legal contact or the courier/address details referenced by §10. | | OBL-015 | Provider | Maintain access controls for production systems. | During operation of production systems | Not stated | Ongoing | Applies to production systems. | — | Schedule B — Security Requirements | Schedule B | Schedule B bullet “Provider must maintain access controls for production systems.” | — | No | | OBL-016 | Provider | Retain security logs for at least 12 months. | Creation/retention of security logs | At least 12 months | Continuous retention requirement | Applies to security logs. | — | Schedule B — Security Requirements | Schedule B | Schedule B bullet “Provider shall retain security logs for at least 12 months.” | — | No | ### QA observations embedded in the register The main evidence limitation is **§10 Notices**. The supplied Schedule A contains a Customer Legal Contact email and a Provider Security Contact email, but §10 specifically refers to **designated legal contacts** and **addresses stated in the Order Form**. The supplied material does not establish the complete notice-address information needed to operationalize that requirement. The Provider Security Contact should not be substituted for a Provider Legal Contact because that would be an unsupported assumption. The **24/7 Severity 1 Support Channel** in Schedule A was not elevated into a separate confirmed obligation. It is a supported contractual service parameter, but the supplied text does not expressly formulate it as a standalone duty. Converting it into one would require an interpretive step not necessary for the register. **Amendment 1 — Not Applicable** does not create an additional obligation and does not create an evidence gap for this supplied contract set. ### Final Validation ✓ Included obligations are supported by the supplied contractual evidence. ✓ Obligation candidates were qualified before inclusion. ✓ Source document and section traceability is preserved. ✓ Schedule B is linked to the §3 security-incident obligation rather than improperly treated as a duplicate. ✓ Missing notice information has not been fabricated. ✓ The notice evidence gap is explicitly flagged. ✓ No material contractual conflict was identified in the supplied documents. ✓ No unsupported assumption has been converted into a contractual fact. ✓ Duplicate obligations were separated where the underlying duties differ operationally. ✓ Human-review requirements are visible where judgment is materially implicated. ✓ The register remains within the defined extraction and QA scope.