Vendor onboarding app with document checklists, approval stages, and insurance alerts
vendor-onboarding · 3600 s per turn · source
The ask
We're the procurement team at Bellhaven Foods, and every new supplier goes through New, Documents, Review, and then Approved or Rejected. Our vendor list and the documents we've collected so far are attached; the list came out of two old systems, so some vendors are in there twice under different vendor numbers. Every vendor needs a W-9, a certificate of insurance, and a signed code of conduct before approval (ingredient suppliers also need a food safety certificate), and once the paperwork is complete the vendor should move to Review on its own, but only I approve. Our category managers should only see vendors in their own categories (Rosa Delgado has Ingredients and Packaging, Dev Malhotra has Logistics, Mei Chen has Facilities, Tom Okafor has IT & Services), and accounts payable just needs to look vendors up without changing anything. I want a dashboard with our approved vendors, what we spend with them, and any approved vendor whose insurance has lapsed or runs out in the next 30 days, so send me an admin login and one for Rosa.
Seed files the agent must import: vendors.csv</code>, <code>documents.csv. The agent must leave a RESULT.json with a reachable URL, an admin login, and the named restricted login.
Acceptance checklist
26 binary items. The first 14 are the enterprise baseline shared by every build task (delivery, invitations, roles, server-side authorization, scoped live dashboard, exact lists and exports, audit metadata, validation, persistence); the rest are application-specific. Core items, which together define "first usable": 1, 3, 5, 6, 8, 14, 15, 19, 21.
| Tag | Items |
|---|---|
| Exact | 10 |
| Permission | 3 |
| Automation | 2 |
| Dashboard | 2 |
| Delivery | 2 |
| Rule | 2 |
| Sharing | 2 |
| API | 1 |
| Audit | 1 |
| Persistence | 1 |
The full checklist with per-item "how to check" instructions and expected figures is in checklist.md. Testers see it; the agent never does.
Change requests
Each change is a new one-shot turn on the carried-forward workspace. Only the owner's text below is sent; the tester items are withheld. After each change the full checklist is rerun, so regressions count.
Change 1 · 3 new checklist items
Put our approved spend by category on the dashboard, and give me an insurance report grouped by category manager so I know who to chase.
Change 2 · 3 new checklist items
When an approved vendor's insurance has lapsed or runs out within 30 days, give that vendor's category manager a renewal task automatically, and close the task once a new certificate is in.
Change 3 · 3 new checklist items
Add a Compliance stage between Review and Approved: our compliance officer has to sign off there before I can approve, and she should see every vendor but not be able to change anything except that sign-off.
No published score. Build runs need a human acceptance pass on a live URL, and no arm has completed one for the full set. Automated probes generate a tester sheet; they do not substitute for it. Results will be published as a separately labeled release when an arm completes.