ADR: a ship checklist the agent (and a rep) can actually finish

[YIKUAIBANZI]

Adds adrs/agent-ship-checklist.md.

The Agent tab can research forever. This proposes a small, versioned ship checklist of observed evidence gates (not model confidence) so a contact / company / deal can actually be marked ready — or blocked — in a way a rep can trust.

Happy to keep it as an ADR until you want the schema; I can implement the smallest slice (contact-only, four gates) if the idea fits.

---

Summary by cubic

Adds an ADR proposing a ship checklist that uses observed evidence gates instead of confidence scores, so the agent can mark a record ready or blocked in a way reps can trust.

• Each gate is observed, missing, blocked, or waived; only a human can waive a gate, and a waiver never counts as observed evidence.
• Contact gates start with identity matched, employer observed (not inferred from email domain), a real thread or meeting on the ledger, and a next action with a why.

^{Written for commit 0b106f8. Summary will update on new commits.}

[vercel]

@YIKUAIBANZI is attempting to deploy a commit to the Comp AI - PoC Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Retargeted this onto main.

release is the default branch so that a plain clone runs the last tagged release, but nothing merges into it — it is fast-forwarded onto the tag by the Release workflow and that is all. Changes go to main, and reach release when a release is cut.

Nothing is wrong with your branch. If the diff now shows commits that are already on main, rebase and force-push:

git fetch origin main
git rebase origin/main
git push --force-with-lease

[cubic-dev-ai]

All reported issues were addressed across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}