Scenario: Agent Screens, Then Designation
The freshness-race scenario - screen at sign, version every result.
The setup
Your agent screens a counterparty at 10:00 - clean. OFAC designates the wallet at 10:30. The agent signs the payment at 11:00 without re-screening.
The gap
- The screen result is stale - logged against an earlier list version
- The payment settles to a now-designated wallet
- Designations land between releases - this is the freshness race
The control
- Screen at the moment of signing, not earlier in the flow
- Record the list version with every result
- Re-screen when the flow spans time (queue delays, approvals)
- Hourly sync keeps the list current
The takeaway
A screen is a point-in-time result against a specific list version. Screen at sign, version every result, and re-screen when time passes.