Skip to content

Addendum to Development Proposal

This Addendum serves as an integral and legally binding extension of the accompanying Development Proposal for the Whiskers and Wheels platform. By signing this Addendum, both parties affirm their acceptance of the terms herein, which are designed to define key concepts, operational procedures, and additional legal protections. All definitions and provisions in this Addendum are to be interpreted in concert with the Development Proposal.

1. Definition of a "Deliverable"

A Deliverable is a defined and tangible outcome or set of features that fulfills a component of the agreed-upon scope of work.

Requirements for Deliverable Completion:

  • Must meet all functional, technical, and design specifications set forth in the Development Proposal or its amendments.
  • Must successfully pass all relevant tests (see Section 3a).
  • Must be formally submitted to the Company and acknowledged in writing.

Examples Include:

  • A fully operational booking system with integrated backend APIs.
  • Implementation of real-time ride tracking using a mapping service.
  • Secure and compliant payment processing via Stripe or PayPal.

2. Definition of a "Milestone"

A Milestone represents a defined point in the project timeline at which one or more deliverables are completed, reviewed, and approved. Milestones are tied to project planning and bonus eligibility.

Milestone Completion Criteria:

  • All relevant deliverables must be completed and accepted in writing.
  • All applicable QA, performance, and functionality tests must pass without material defect.

Examples Include:

  • Completion and acceptance of the full Booking System.
  • Deployment of the platform to the staging server with user authentication enabled.

3. Definition of a Successful Git Commit

A Successful Git Commit is a source code submission that demonstrates measurable progress toward a defined goal.

Requirements:

  • Must address a known issue, feature, or task from the project tracker.
  • Must include descriptive and meaningful commit messages.
  • Must not introduce any critical errors or regressions.

3a. Required Tests for a Successful Commit

Each commit must satisfy the following criteria:

  1. Unit Tests – Verify correctness of individual components.
  2. Integration Tests – Validate end-to-end functionality between multiple components.
  3. End-to-End Tests – Confirm real-world user workflows behave as intended.
  4. Linting and Formatting – Ensure code style compliance.
  5. Manual Review – Validate frontend or UX work via visual/functional walkthroughs.

4. Definition of "Front-End Development" Tasks

Front-End Development includes all tasks related to implementing user-facing functionality.

Primary Responsibilities:

  • Development of responsive layouts and SPA components using Vue.js and Inertia.js.
  • Implementation of booking forms, dashboards, and ride tracking interfaces.
  • Cross-browser and mobile optimization.

Additional Responsibilities:

  • Accessibility compliance (WCAG 2.1).
  • Frontend performance tuning, lazy loading, and responsive interactions.

5. Definition of "Back-End Development" Tasks

Back-End Development includes server-side functionality, business logic, and database operations.

Core Responsibilities:

  • RESTful API development for all platform functionality.
  • MySQL database schema design and optimization.
  • Payment processing integration with Stripe or PayPal.

Additional Responsibilities:

  • WebSocket server for real-time features.
  • Role-based access middleware.
  • Async task management for notifications, payments, and background jobs.

6. Definition of "Infrastructure Tasks"

Infrastructure Tasks relate to setting up, securing, and maintaining system environments.

Core Responsibilities:

  • Configuration of production and staging environments.
  • Setup of CI/CD pipelines.
  • SSL certificates and web server (Nginx or Apache) configuration.

Additional Responsibilities:

  • Monitoring and alerting (Sentry, CloudWatch, etc.).
  • Load balancing and autoscaling strategies.
  • Redis or equivalent caching layers.

7. Clarification of "Overtime"

7a. Definition of Overtime

Overtime is defined as hours worked beyond the standard 16-hour weekly commitment.

7b. Requesting Overtime

  • Must be submitted by the Service Provider in writing.
  • Must include:
  • Detailed task description.
  • Estimated additional hours.
  • Submitted via email or agreed project management tool.

7c. Approving Overtime

  • Must be approved in writing by the Company within 24 hours.
  • Acceptance must be confirmed via email or approved comment in a shared tool.

7d. Overtime Rate

  • Approved overtime shall be billed at 1.5x the applicable hourly rate per task.

8. Warranties

8a. Performance Warranty

The Service Provider warrants that all deliverables:

  • Shall materially conform to the specifications in the Development Proposal.
  • Shall be free from material defects for a period of thirty (30) days post-acceptance.

8b. Compliance Warranty

The Service Provider shall comply with all applicable laws and shall not knowingly infringe on any third-party IP.

8c. Limitations

Warranty does not cover issues arising from:

  • Client-side modifications.
  • Integration of unauthorized third-party tools.
  • Misuse or unsupported usage patterns.

9. Indemnification

9a. By Service Provider

The Service Provider agrees to indemnify and hold harmless the Company from any third-party claims resulting from:

  • IP infringement caused by custom code.
  • Willful misconduct or gross negligence.

9b. By Company

The Company agrees to indemnify and hold harmless the Service Provider from any claims arising from:

  • Client-provided data or materials.
  • Unauthorized use or alteration of deliverables.

10. Data Ownership

10a. Ownership of Content and Data

All Company-provided content and data remain the sole property of the Company. The Service Provider shall use such data exclusively to fulfill project requirements.

10b. Work Product Ownership

All deliverables custom-built for the Company become its exclusive property upon final payment.

10c. Pre-Existing IP

The Service Provider retains ownership of any tools, libraries, or frameworks developed prior to or outside the scope of this project.

10d. Aggregated Anonymous Data

Non-personal, anonymized data may be used by the Service Provider for analytics, provided it does not include confidential or identifiable content.

11. Dispute Resolution

  • Initial Resolution: Disputes shall be addressed within seven (7) business days of written notice via collaborative meetings.
  • Mediation: If unresolved, mediation shall occur in Pennsylvania, with costs shared equally.
  • Legal Jurisdiction: This Agreement shall be governed by the laws of the Commonwealth of Pennsylvania, with jurisdiction in Allegheny County.

12. Acknowledgment and Agreement

This Addendum, together with the Development Proposal and any signed amendments, constitutes the full agreement between the parties.

By signing below, the Company and Service Provider affirm their understanding and agreement to all terms herein.

Signatures

Developer (Service Provider):

Name: _______

Date: _______

Authorized Company Representative:

Name: _______

Title: _______

Date: _______