system: You are a contract-analysis assistant performing a span-extraction task. You are given an excerpt from a commercial contract and the name of a clause type to locate within it.

Return the exact text of the requested clause, copied verbatim from the excerpt — identical wording and punctuation, with no paraphrasing, summarising, explanation, or added commentary.

The excerpt is one window of a much longer contract and often will not contain the requested clause. If the requested clause does not appear in this excerpt, respond with exactly: Not found.

Output only the extracted clause text, or the exact string `Not found.` — nothing else.

user: Contract excerpt:
"""
SOFTWARE DEVELOPMENT AGREEMENT THIS SOFTWARE DEVELOPMENT AGREEMENT (Agreement ) is made December 3rd, 2018 (the Effective Date) by and between DOT COM LLC, OBA Seattle Software Developers, a Delaware limited liability company (Developer ), and (Client) Pelican Delivers Inc. for the performance of software design services and software development as detailed herein (Developer and Client are individually referred to herein as a Party, and collectively as the Parties). 1. Term Unless otherwise provided herein, this Agreement will commence on the Effective Date and continue through the completion or termination of Developer's services and work product as mutually agreed upon between the Parties (the Project). 2. Statement of Work Developer will design, develop, and deliver, satisfactory to Client, the "Pelican Delivers Application Phase 1" (collectively, the Subject Program), and all elated Project services (collectively, the Services), Project work product (collectively, the Deliverables), and user manuals and other written material that describe he functionality or assist in the use of the Subject Program (collectively, the Documentation), pursuant to the Project specifications detailed in the SO (collectively, Specifications), as described in the enclosed statement of work (the SOW; as provided in APPENDIX A hereto). The Parties may execute multiple SOWs should there be multiple or separate Projects. In the event of any conflict or inconsistency between the terms of this Agreement and any SOW, the terms of this Agreement will control. 3. Delivery Schedule; Acceptance; Change Orders 3.1 DELIVERY SCHEDULE; MILESTONES Each SOW will include a delivery schedule for Services and Deliverables (the Delivery Schedule) that will identify mutual agreed upon Project time deadlines concerning the performance of Services, delivery of Deliverables, Client testing of the same (collectively, Milestones), as well as a final Subject Program delivery date (Final Delivery Date). 12 Source: PELICAN DELIVERS, INC., S-1, 2/11/2020 3.2 PROJECT DELIVERY AND INSTALLATION As detailed in a SOW hereto, Developer will provide certain Services, Deliverables and Documentation to Client upon a designated Milestone in accordance with such Milestone's specific Specifications (collectively, Specific Specifications). Prior to completing a Milestone, Developer will: (a) inform Client of the availability of each portion of a Deliverable otherwise required be delivered by such Milestone date for testing by Client (he Acceptance Test Date); and (b) deliver to Client sue Deliverable (each a Milestone Deliverable) including the source code and object code form compatible with the platform(s) described in the SOW for such Milestone Deliverable. 3.3 ACCEPTANCE AND BETA TESTS Within the time periods designated in the SOW, Client shall perform any tests or evaluation of the Subject Program (collectively, the Acceptance Tests) after the Acceptance Test Date, to determine whether each Deliverable: (a) conforms to the SOW; and (b) performs repetitively on an appropriate variety of data and platforms, without failure, as more fully described in the Specifications. Upon completion of II Deliverables, the Acceptance Tests shall be performed on the Subject Program in its entirety in order to determine whether the Subject Program (i) meets the Specifications and (ii) operates with internal consistency. 3.4 ACCEPTANCE OF MILESTONE DELIVERABLE; CHANGE REQUESTS Client will notify Developer in writing of any failure of a Milestone Deliverable to comply with the Specifications, or of any other objections, corrections, changes or amendments required (a Change Request), within ten (10) days of such Milestone's Acceptance Test Date. Any Change Request shall be sufficient to identify, with clarity, any objection, correction, change or amendment to such Milestone Deliverable. In the absence of a Change Request from Client within the time periods detailed herein, the Milestone Deliverable will be deemed accepted by Client. 3.5 REJECTION OF MILESTONE DELIVERABLE If any Milestone Deliverable does not satisfy the Client's Acceptance Test and Client provides Developer a Change Request concerning the same, Developer will have twenty (20) days from the receipt of such Change Request to correct the deficiencies, errors, corrections, modifications, bug- fixes or changes to the Deliverables as identified in the Change Request. Upon Client's receipt of a Milestone Deliverable following Developer's modification pursuant to Change Request (a Modified Deliverable), Client will have five (5) days to inspect, test and reevaluate such Modified Deliverable to determine acceptance. If Client does not notify Developer of any further failures, objections, changes, defects, or bugs in such Modified Deliverable, the Modified Deliverable will be deemed accepted by Client. 13 Source: PELICAN DELIVERS, INC., S-1, 2/11/2020 3.6 FAILURE OF DEVELOPER TO CORRECT DEFECTS Should Developer reasonably fail to meet the requirements of Section 3. or Section 3.5 of this Agreement such that a Milestone Deliverable or Modified Deliverable does not
"""

Extract the exact clause related to "Document Name" from the excerpt above.

assistant: SOFTWARE DEVELOPMENT AGREEMENT