Updated ARTICLE 3 & 4 to be more pacific

docs/CONTRACT.md

@@ -84,39 +84,42 @@ C.  Client desires to engage Developer to perform such software development and
 
 ## ARTICLE 3: SYSTEM SPECIFICATIONS AND ARCHITECTURE
 
-3.1 **User Interface (UI) Layout and Flow:** The general layout principles and high-level component relationships for the System's user interface are conceptually depicted in **Exhibit A (User Interface Flow Diagram)**, incorporated herein by reference. Key layout components include a persistent Header, a contextual Sidebar (where applicable), a Main Content Area, and a Footer. Specific screen designs and detailed UI specifications will be developed and refined during the Sprints, subject to Client review and feedback.
+3.1 **User Interface (UI) Layout and Flow:** The general layout principles and high-level component relationships for the System's user interface are conceptually depicted in **Exhibit A (User Interface Flow Diagram)**, incorporated herein by reference. Key layout components include a persistent Header, a contextual Sidebar (where applicable), a Main Content Area, and a Footer. Specific screen designs and detailed UI specifications will be developed and refined during the Sprints, subject to Client review and feedback during Sprint Reviews.
 
-3.2 **Backend Architecture:** The high-level backend architecture, illustrating the interaction between the Actix framework, database (MariaDB), and other core components within the planned containerized environment, is conceptually depicted in **Exhibit B (Backend Architecture Diagram)**, incorporated herein by reference. *(<!-- FOR INTERNAL TEAM USE: Exhibit B is based on the Mermaid diagram provided. Ensure final Exhibit accurately reflects implementation. Note Auth Middleware & Production State Management as items needing completion/refinement -->)*.
+3.2 **Backend Architecture:** The high-level backend architecture, illustrating the interaction between the Actix framework, MariaDB database, OPAQUE authentication flow, and other core components within the planned containerized environment, is conceptually depicted in **Exhibit B (Backend Architecture Diagram)**, incorporated herein by reference.
 
-3.3 **Technical Specifications:** *(<!-- PLACEHOLDER: Reference a separate document or Exhibit detailing more granular technical specifications if available/required, e.g., API specifications, detailed data models, specific performance benchmarks -->)*.
+3.3 **Technical Specifications:** Detailed technical specifications, including specific API endpoint definitions, data model schemas, and performance guidelines, may be documented collaboratively by the Parties during the project lifecycle, potentially in a shared repository or document store ([Specify if needed, e.g., "maintained in the project's shared Confluence space"]), and referenced herein upon mutual agreement. Initial database schema is based on requirements outlined during project initiation.
 
 ## ARTICLE 4: PROJECT TIMELINE AND DELIVERABLES
 
-4.1 **Estimated Timeline:** The estimated timeline for the completion of the Services is approximately **[Calculate total weeks from Gantt, e.g., 35 weeks]**, commencing from the Effective Date or an otherwise agreed-upon project start date. A detailed breakdown of phases, estimated task durations, and dependencies is illustrated in the Gantt chart provided as **Exhibit C (Project Timeline Gantt Chart)**, incorporated herein by reference.
+4.1 **Estimated Timeline:** The estimated timeline for the completion of the Services is approximately **Thirty-Five (35) weeks**, commencing from the agreed-upon project start date. A detailed breakdown of phases, estimated task durations, and dependencies is illustrated in the Gantt chart provided as **Exhibit C (Project Timeline Gantt Chart)**, incorporated herein by reference.
 
-4.2 **Acknowledgement of Estimates:** Client acknowledges that the timeline provided in Exhibit C is an estimate based on the initial Scope of Services and the Agile methodology. Timelines may be adjusted based on the evolution of requirements, Client feedback, unforeseen complexities, or mutually agreed-upon changes processed via the Change Management procedure (Article 6).
+4.2 **Acknowledgement of Estimates:** Client acknowledges that the timeline provided in Exhibit C is an estimate based on the initial Scope of Services, assumptions about requirements stability, and the Agile methodology. Timelines may be adjusted based on the outcomes of Sprints, the complexity of features prioritized, Client feedback responsiveness, unforeseen technical challenges, or mutually agreed-upon Change Requests processed via the Change Management procedure (Article 6). Developer shall promptly communicate any anticipated significant deviations from the estimated timeline.
 
 4.3 **Key Deliverables:** Major deliverables under this Agreement include:
 
-  > a.  Access to incremental System builds for review at the end of relevant Sprints.
+  > a.  Access to functional System increments for review and feedback at the conclusion of relevant Sprints (typically via a staging environment).
   >
-  > b.  The final, deployed System software meeting the Acceptance Criteria (Article 5).
+  > b.  The final, deployed System software meeting the Acceptance Criteria (Article 5), delivered to the agreed production environment.
   >
   > c.  The Video Demonstration (as per Section 2.4).
   >
-  > d.  System Documentation, including user guides for administrators, instructors, and learners, and technical documentation sufficient for ongoing maintenance and operation. *(<!-- PLACEHOLDER: Specify level of detail required for documentation -->)*.
+  > d.  System Documentation, comprising:
+  > >   i. User Manuals: Guides for administrators, instructors, and learners covering core functionalities.
+  > >
+  > >   ii. Technical Documentation: Including deployment instructions, system architecture overview, API endpoint documentation (e.g., generated OpenAPI spec), and database schema description, sufficient to enable technically skilled personnel to operate, maintain, and potentially extend the System. The specific level of detail shall be **[e.g., "standard industry practice for systems of similar complexity" or specify further detail if required]**.
   >
-  > e.  Source Code for the developed System. *(<!-- PLACEHOLDER: Confirm source code escrow requirements if any -->)*.
+  > e.  Source Code for the custom-developed portions of the System delivered under this Agreement, provided via **[Specify method, e.g., access to a Git repository, digital media transfer]**. Source code escrow requirements, if any, must be separately agreed upon in writing.
   >
-  > f.  Training materials and sessions as specified in Section 4.4.
+  > f.  Training materials and delivery of training sessions as specified in Section 4.4.
 
-4.4 **Training and Handover:** Upon successful deployment, Developer shall provide:
+4.4 **Training and Handover:** Upon successful deployment (Go-Live milestone in Exhibit C), Developer shall provide:
 
-  > a.  Training for Client's designated administrators and instructors. *(<!-- PLACEHOLDER: Specify format, duration, and number of sessions/attendees -->)*.
+  > a.  Training for Client's designated administrators and instructors, covering system administration, course management, user management, and key instructional features. This training shall consist of **[Specify format, duration, number of sessions, e.g., "up to two (2) remote training sessions, each lasting approximately three (3) hours, for a maximum of ten (10) Client attendees per session"]**.
   >
-  > b.  Onboarding materials (e.g., documentation, potentially videos) for learners.
+  > b.  Onboarding materials suitable for learners, such as a concise user guide document and potentially referencing the Video Demonstration.
   >
-  > c.  A formal handover process concluding the development phase.
+  > c.  A formal handover meeting and documentation transfer concluding the development and deployment phases outlined in Exhibit C.
 
 ## ARTICLE 5: TESTING AND ACCEPTANCE