IT asset register with padded tags, assignment history, warranty alerts, disposal rules, and site-scoped access
asset-tracking · 3600 s per turn · source
The ask
I run IT for a freight company with offices in Denver, Salt Lake City, Boise, and Omaha, and I need to track every laptop, monitor, phone, and piece of network kit we own. I've attached our asset register and the assignment history; our asset tags are IT- followed by six digits, but some came through with the zeros stripped or the prefix missing. I want to see who has each asset now and who had it before, a list of warranties running out in the next 60 days, and a dashboard with the total value of what we own (purchase cost, not counting anything disposed of). Nothing can be disposed of while it's still assigned to someone, and laptops and phones need a confirmed data wipe first. Each site manager should see only their own site's assets, our auditor needs a read-only login, and I want an admin login for me and a login for Owen Pratt, our Boise site manager.
Seed files the agent must import: assets.csv</code>, <code>assignments.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, 20, 23.
| Tag | Items |
|---|---|
| Exact | 9 |
| Permission | 3 |
| Rule | 3 |
| Automation | 2 |
| Dashboard | 2 |
| Delivery | 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
On the dashboard, break asset value down by type for each site, with the number of assets behind each figure.
Change 2 · 3 new checklist items
When a laptop comes back from someone, it should go into a wipe-pending state on its own, and it can't go out to anyone else until IT marks it wiped.
Change 3 · 3 new checklist items
Site managers should be able to ask for something to be disposed of, but only I approve it, and the value shouldn't drop until I do. Show me the requests that are waiting.
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.