Pick a test case, change something on one of the documents, and see what the checker does. It lists each problem with the document, the field and the rule it breaks, drafts the refusal notice, works out the deadline, and saves a record before showing you anything.
The real checker, not a mock-up. It is the same code that produced the results on the About page, and tests check that this demo reports exactly what the checker returned and reaches the same result as the scoring code on all fourteen cases. No AI model is involved, so each check takes a few milliseconds.
Things to try: change a value on the bill of lading, such as the port of discharge, so it no longer matches the credit. Have it read a generated PDF instead of the raw data, then pick the form with no labels. Set the notice date after the deadline. Or alter one entry in the record and check it again.
All documents are made up, and your changes last only for the one check that uses them. The names of real shipping lines, banks and traders on the blocklist are turned away.
This changes one saved entry without updating its fingerprint, then checks the chain again, which catches the edit. It shows that an edit is detected. It does not stop someone who holds this code from rewriting the whole record and recomputing every fingerprint.