School district purchase requests with amount-based two-step approval, budget lines, and PO numbers
purchase-requests-approvals · 3600 s per turn · source
The ask
I run the business office for a school district, and I want purchase requests, approvals, and department budgets in one place instead of paper forms, with a dashboard. Attached are this year's budget lines, our vendor list, and the requests entered so far this school year. Every request is charged to one of its own department's budget lines; under $2,500 it needs only the department head's approval, $2,500 or more also needs the business office after the department head, and only a fully approved request gets the next PO number and counts against its budget line. Staff see only their own requests, department heads see and approve their own department's, our auditor can read everything without changing anything, and I manage users and settings. Give me an admin login and a login for Denise Harlan, our transportation director.
Seed files the agent must import: budgets.csv</code>, <code>vendors.csv</code>, <code>requests.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, 19, 21, 22.
| Tag | Items |
|---|---|
| Exact | 8 |
| Permission | 4 |
| Rule | 4 |
| Dashboard | 2 |
| Delivery | 2 |
| Sharing | 2 |
| API | 1 |
| Audit | 1 |
| Automation | 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
I need a budget report by department for the board: adopted budget, what's approved, what's still waiting for approval, what's left, and the percent used, with a district total.
Change 2 · 3 new checklist items
Don't let a request be fully approved if it would take its budget line below zero. The department head can still sign off on their step; the final approval is what gets blocked, and no PO number gets used.
Change 3 · 3 new checklist items
Anything $25,000 or more also needs the superintendent to sign off, after the business office. Only the superintendent can give that approval, not me, and the PO number comes after the superintendent signs.
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.