AI definition of done — a template you can actually accept against
Harbor ships against a short “done means…” checklist agreed before build. Acceptance is pass/fail on that list — not open-ended polish. This page gives you a blank shape and an anonymized Docs Pilot example.
How this maps to how we work
On How we work, Discover · Build · Review means: align on package and a draft checklist before payment, build after deposit clears, then accept in writing against the checklist. Change orders are written. A 14-day bugfix covers defects in agreed behavior — not new features.
Composite studio quotes elsewhere on the site are illustrative — not attributed client testimonials. Case studies use Harbor project codenames for timeline, scope, and handoff style.
Blank DoD template
Copy this into a shared doc, or use the blank markdown starter Harbor publishes for GitHub:
Project: [name]
Package: [e.g. Docs Pilot / FAQ Support Bot / Workflow Agent]
Buyer owner: [name]
Harbor owner: [role]
Target calendar: [weeks from catalog]
Done means (pass/fail):
1. [Deliverable behavior #1]
2. [Deliverable behavior #2]
3. [Acceptance tests / golden scenarios]
4. [Handoff: env, rebuild, known limits]
5. [Out of scope remains out — list must-never]
Inputs we will provide by kickoff:
- [...]
Change orders:
- Anything outside this list requires written price + timing before extra work.
Acceptance:
- Pass/fail email or signed note against items 1–5.
- Balance due per package payment terms after written acceptance.
A blank checklist starter lives in the local GitHub starters folder Rex pushes when ready
(harbor-github-starters/ai-acceptance-checklist/). Org
github.com/harborartificial may not exist yet — create the org/repo, then push.
Anonymized Docs Pilot example
Using live catalog numbers for Docs Pilot (RAG): $4,000 sticker · 2 weeks · 50/50. Illustrative only — not a client quote or performance claim.
Project: Internal policy Q&A pilot (anonymized)
Package: Docs Pilot (RAG)
Done means:
1. Bounded corpus ingest for the agreed document sample
2. Retrieval path returns answers with citation links to source chunks
3. Refusal behavior on out-of-corpus questions (no invented policy)
4. Acceptance tests cover golden questions + at least 3 refusal cases
5. Handoff runbook: env vars, rebuild steps, known limits
Out of scope (must never):
- Zero-hallucination guarantee
- Enterprise SSO / multi-tenant auth
- HIPAA / clinical corpus
Acceptance: written pass/fail on the five items above.
See also the illustrative Ledgerly Docs Pilot case study for how a Docs Pilot handoff is framed on the work page.
Next step
Draft your checklist, pick a package on /packages/, or email harborartificial@pm.me with your draft “done means…” list.
Harbor Artificial is not Harbor Cloud, tryharbor.ai, or Protected Harbor. We refuse HIPAA/clinical work, regulated finance systems of record, realtime voice, and open-ended founding-engineer retainers. No profit guarantees.
FAQ
Guide FAQ
What is a written definition of done at Harbor?
A short pass/fail checklist you agree before build. Acceptance is against that list — not open-ended polish. See How we work for Discover · Build · Review, deposits, change orders, and the 14-day bugfix.
Is there a blank template I can copy?
Yes. Harbor publishes a blank AI acceptance checklist starter (markdown) you can fork or copy into your repo. Link it from the guide CTA and GitHub starters folder Rex pushes when ready.
Does a DoD guarantee zero hallucinations or profit?
No. Harbor engineers grounded behavior and honest refusals against a checklist. We do not guarantee zero hallucinations, trading profit, returns, or win rates.
Want to see if a package fits?
Share what you’re trying to ship, your timing, and any constraints you already know. We’ll reply from harborartificial@pm.me.