Skip to main content

🦤 Delivery Definition of Done

This document is a checklist to help decide when a task/feature is done and ready to ship. Every item should be considered during delivery, but not every item will apply every time.

Design & cross-surface impact​

  • Impact assessed across relevant surfaces:
    • Autonomous / Guided
    • Web app / Extension
    • Clouds (AWS, GCP, …)
  • Backward compatibility assessed (especially Extension + APIs/contracts)
  • Security implications reviewed (auth, data access, permissions/scopes)
  • AI implications discussed with the AI team, especially if the feature introduces a new AI task
  • Design/implementation review with the team for significant changes

Quality​

  • UX review before build (flows/states) and UX validation before rollout
  • Tests added/updated as applicable
    • Unit tests
    • E2E tests for critical paths
  • Observability
    • Logs + traces with end-to-end correlation context
    • Monitors/alerts with actionable thresholds

AI (if applicable)​

  • Evals added or updated
  • Model fallback / degradation behavior defined and tested

Rollout & recovery​

  • Rollout plan defined (internal → small % → full) when needed
  • Rollback plan / kill switch in place when needed

Documentation​

  • User-facing docs updated if behavior changes
  • Internal docs/runbook updated (debugging + recovery)