2026 — ongoing

petrol-receipts

The reference implementation for the whole fleet — fuel receipts in, structured per-vehicle records out.

Private repository — the writing here describes the approach rather than linking to code.

  • TypeScript
  • SQLite
  • Claude tool-use
  • OCR

The smallest useful version of the problem, and therefore the one where the pattern was worked out: fuel receipts for two vehicles, ingested from scans and emailed PDFs, extracted into typed records, filed per vehicle.

The extraction pipeline here — OCR, then PDF text, then model tool-use with position heuristics and tiered fallback — is what the other tools copy. So is the tiered backup retention, and the shape of the CLI. When a sibling project needs a piece it has not built yet, this is where it looks first.

Being the reference implementation is a responsibility I have not entirely lived up to. It currently has no test suite, which is a worse fact than it would be in any of the others precisely because they are told to copy from it. That is the next thing to fix here.

The repository is private.