This page explains the intended structure of a signed project agreement. It is not a substitute for a completed, reviewed contract. The executed proposal or statement of work must identify the parties and include the project terms below.

Required project schedule

• Legal names, contacts, effective date, and governing law.
• Project background, in-scope workflow, deliverables, and out-of-scope items.
• Fees, taxes, payment schedule, third-party costs, and late-payment terms.
• Client dependencies, access method, decision owners, and response expectations.
• Milestones, acceptance criteria, review periods, and correction window.
• Security, confidentiality, privacy, data-processing, and incident responsibilities.
• Intellectual-property ownership and licence terms.
• Change control, suspension, termination, refunds, and transition.
• Warranties, liability, indemnity, dispute resolution, and notices.

Default delivery principles

Work begins after written scope approval and any required deposit. The engagement follows qualification, discovery, workflow documentation, baseline measurement where available, proposed solution and acceptance criteria, implementation, security review, client review, deployment, handover, monitoring, and results review.

Acceptance criteria

Acceptance criteria must be observable and agreed before development. A typical project specifies tested inputs, expected outputs, error routing, permitted systems, human approval points, logging, documentation, and named test users. Acceptance should not depend on an unverifiable business outcome controlled by market conditions or third-party performance.

Client ownership and handover

The preferred default is client ownership of accounts, data, client-specific workflows, configuration exports where available, documentation, and credentials at handover. Stealth Overlay may retain reusable methods, generic templates, and know-how. Access must use client-approved secure channels and be revoked after handover.

Third-party outages and AI uncertainty

Project obligations must account for provider outages, API changes, model behavior changes, rate limits, and input quality. AI outputs remain probabilistic. Production use requires suitable validation, human review, logging, and fallback behavior as agreed in the scope.

Operational contact

Contract and project questions: support@stealthoverlay.com. See the website terms, privacy notice, and cancellation policy.