Static snapshot. A frozen copy of the operator dashboard, safe to open anywhere. The buttons below are drawn but inert — recording a verification and being refused the release is a state change, so it runs on the live app: python src/demo.py --serve.
- From
- payments@saicorpdelhi.com
- Received
- 28 Jun 2026, 10:13
- Subject
- PO-4421
- Reply to
- not a reply
- Thread
- THRN08055
The message
The consignment against PO-4421 left our Pune depot this morning.
What the sender resolved to
- Supplier
- VEND0067
- Matched on
- Known sender
- Because
- the email domain is in our supplier records
- Domain matched
- saicorpdelhi.com
- Triage decision
- Not about payment details
- Change request filed
- none
nothing in the subject or body refers to a payment destination (deterministic pre-read only — no classifier supplied)
Sender matching decides whether a message is read in full. It never decides a payment on its own — a lookalike domain is a reason to look, not a reason to reject.