We're building an internal tool that reads uploaded invoices — PDF and image — and turns them into structured, reviewable records, so the finance team stops hand-keying vendor bills into the ledger. A clerk uploads a batch and walks away; the system extracts the fields, scores its own confidence, and routes anything uncertain to a human instead of guessing.
This repository is the specification for that tool — there is no application code here yet, and
none is expected. The specs live in resources/, split into goals and constraints, requirements
(user stories, acceptance criteria, formal EARS obligations, auth, data model, API contracts),
and architecture. Read the one file that answers your question rather than the whole folder;
CLAUDE.md has the routing guide.