The Definition of Done (DoD) is the minimum quality and delivery standard that all sellers must meet before an automation is considered complete and escrow funds are released.

It serves as a binding agreement between buyers, sellers, and the Autonoms marketplace to ensure trust, quality, and accountability.

1. Functional Requirements

• The automation should work with the tools agreed upon during the consultation call and captured in the project workspace.
  
• The automation must execute the intended workflow end-to-end as agreed upon with reasonable error margin.
  
• The workflow should be repeatable, stable, and reliable (not a one-time demo).
  

2. Customization & Scope Alignment

• The automation must reflect the customizations agreed upon between buyer and seller.
  
• Sellers must exercise due diligence:
  
  • If a buyer requests changes beyond the one-time purchase scope, sellers should communicate feasibility early.
    
  • Out-of-scope work can transition into a new milestone-based, contract-based, or ongoing engagement within Autonoms.
    
• Both parties must align on what is possible vs. out-of-scope before deployment.
  

3. Buyer Sign-Off & Escrow Release

• Escrow funds remain locked until the buyer confirms the automation meets DoD.
  
• The buyer must approve completion inside the platform after a live demo and final test.
  
• If a dispute arises, Autonoms’ conflict resolution system reviews whether DoD has been met.
  

4. Tooling & Subscription Responsibility

• The seller is responsible for ensuring the automation runs properly in tools such as n8n, Make.com, Zapier, or other approved platforms.
  
• Premium subscription responsibility:
  
  • Sellers must use their own accounts for building and testing.
    
  • Buyers are responsible for maintaining their own active subscriptions to run the automation post-deployment.
    
  • Sellers must clearly document any required third-party costs (subscriptions, APIs) before purchase.
    

5. Secure Deployment to Buyer Environment

• The seller must deploy the automation directly to the buyer’s environment, not keep it hosted privately.
  
• Deployment must use secure connections (e.g., OAuth, API tokens), never raw credentials.
  
• Buyer must have full administrative access to the deployed automation.
  

6. Buyer Ownership

• Once deployed, the buyer fully owns the automation.
  
• Ownership includes:
  
  • The source automation/workflow.
    
  • Documentation and instructions for ongoing use.
    
  • Ability to edit, extend, or transfer ownership of the automation.
    
• Sellers may not retain control of the deployed workflow.
  

7. Post-Deployment Support

• Sellers must provide at least 1 week of post-deployment support for:
  
  • Bug fixes.
    
  • Minor optimizations.
    
  • Adaptations needed for the agreed workflow.
    
• Support must be delivered through the in-app project workspace for accountability.
  
• After the 1-week support period, buyers can re-engage sellers through:
  
  • Milestone-based engagements.
    
  • Contract-based work.
    
  • AI-Ops-as-a-Service (monthly retainer).
    

8. Documentation & Handover

Every completed automation must include:

• Setup guide (step-by-step).
  
• List of required tools and subscriptions (with links).
  
• Instructions for connecting integrations.
  
• Known limitations or caveats (e.g., rate limits, paid APIs).
  
• Optional: Short demo video of workflow running.
  

9. Quality Standards

• Automation must meet Autonoms approval workflow standards:
  
  • Functionality verified.
    
  • Deployment repeatability.
    
  • Documentation completeness.
    
  • Security checks passed (no exposed PII, no insecure sharing of credentials).
    

10. Conflict Resolution Triggers

If disputes arise, Autonoms AI will step in if:

• Buyer claims automation doesn’t meet agreed scope.
  
• Seller claims buyer is requesting out-of-scope changes.
  
• Automation fails functionality tests.
  
• Seller refuses post-deployment support.
  

Autonoms will review:

• Project workspace records.
  
• Demo/test session recordings.
  
• Documentation & deployment logs.
  

📌 Summary Checklist of DoD

✅ Works with agreed tools.

✅ Executes agreed workflow + customizations (within scope).

✅ Buyer approves completion.

✅ Deployed securely in buyer’s environment.

✅ Buyer owns automation after deployment.

✅ Seller provides 1-week support.

✅ Documentation & setup guide delivered.

✅ Meets marketplace quality & security standards.

✨ With this Definition of Done, both buyers and sellers know exactly when a project is complete, preventing disputes and ensuring escrow is only released for real, working value.