Dmytro Galko · open-source tools
The same file arrives twice and the ledger survives
A lender exports a loan tape and sends it again - tomorrow, twice in one day, sometimes with one field corrected, sometimes the same rows in a different order. Any system that receives data from someone else has this problem, and the cost of getting it wrong is a ledger nobody can reconcile. The import stays safe on every repeat.
28 self-checks on the import - idempotency, quarantine, audit, tenant isolation - and 28 graded cases on the classifier, covering accuracy, human routing and invented dates. Both green. Standard library only; the SQL targets Postgres and runs unchanged on SQLite, so the tests need no server.
idempotent import loan tape, append-only audit trail, re-import same file safely, quarantine bad rows, borrower reply classifier escalate not guess, multi tenant isolation.
If that is your week and you would rather someone else did it, write to hello@dkautomation.dev or open an issue.