Dispute Resolution Policy

Applies to buyer disputes, operator escalation, payment holds/status events, revision disagreements, and final delivery review.

Draft dispute process for scope disagreements, deliverable review, acceptance criteria, audit evidence, and operator escalation.

Buyers should first use revision controls where a deliverable can be brought into scope. If the issue cannot be resolved through revision, the buyer may open a dispute with specific reasons tied to package scope or acceptance criteria.

Operators review the workspace record, order events, generated files, messages, and payment state before deciding next steps.

The project workspace is the primary operational record. Messages, files, lifecycle events, generated artifacts, invoices, and payment events may be considered.

This draft policy does not establish final legal dispute terms for public production.

Disputes should collect reason, order ID, project ID, package scope, lifecycle state, payment status, and evidence links.

Operators must avoid deleting or rewriting audit history during dispute review.

Public production dispute handling requires counsel review.

Formal arbitration, venue, and jurisdiction terms are placeholders.

Evidence export and user notification workflows need production hardening.