Serial Number Registry & As-Built Record

The problem this kills

A customer calls with a serial number and a warranty claim. Now the scramble starts: which revision shipped on that unit? Which batch of boards went in? Did it pass final test, and who signed off? The answers live in a binder, three spreadsheets, and someone's memory - and that someone is on vacation.

When a recall or a field failure hits, this gets dangerous. You can't tell which units have the suspect component lot, so you over-recall (expensive) or under-recall (worse). Traceability that exists only in scattered files isn't traceability - it's a liability.

This tool turns every finished unit into a permanent, searchable record: its serial, its exact as-built configuration, its component genealogy, its test results, and the human who approved its release.

What you'll build

A simple internal web app where your team can:

• Assign a serial number to a finished unit using your own format and rules (the tool enforces uniqueness so the same serial can't be issued twice).
• Record the as-built configuration - which component serials and lot numbers went in, which hardware/firmware revision, the final test results, and the ship-to.
• Send it through a QA gate - a supervisor or quality engineer reviews the as-built record and approves it before the unit is released and the serial is committed to the registry.
• Search any serial and instantly see its full history and genealogy - including which other units share a suspect component lot.
• Export the serial registry as a clean CSV in the exact columns your downstream systems expect.

What's inside the Implementation Plan

The plan is a complete, paste-and-go runbook for Claude Code. The very first thing it does is interview you about your business - your serial format, what goes into a build record, your test and approval rules, your volumes, and your messy edge cases - then it reads back a short tailored spec for your thumbs-up before building anything. You get a tool shaped around how you actually build and ship, not a generic template.

Inside you'll find: a discovery interview, a tailored data model for units and component genealogy, the serial-assignment and uniqueness rules, the as-built capture screens, the QA approval gate, the serial search, and the CSV import/export fallback - each build step ending in a ready-to-paste prompt.

The governance it includes (this is the point)

This isn't a toy spreadsheet replacement. Governance is built in from the start:

• Login so only your team can use the tool.
• Row-level security so each organization only ever sees its own units and records.
• A complete audit trail - who assigned the serial, who entered the build record, who approved it, and exactly when.
• A hard human-in-the-loop approval gate - the as-built record is drafted, a supervisor/QA reviews and approves, and only then is the serial committed to the registry.
• Duplicate guards - unique serial enforcement so the same serial can't be issued twice and the same build can't be committed twice.

Who it's for

Quality engineers, production leads, and service/warranty teams responsible for serialized products - anyone who needs to answer "what's the exact history of this unit?" without a fire drill. No coding experience required.

You've got this - paste the first prompt and let the agent interview you.