Codes 320/323/324/997 need RE knowledge. A local fixture snapshot makes those checks enforceable in a stateless browser session — no database and no FINTRAC registry API.
FINTRAC rejects reports when a contact or location is not on file for the reporting entity, or when a report reference is not unique for that RE. Those facts are not on the public validation HTML pages.
Practical local approach
Paste a JSON snapshot with contacts[], locations[], and usedReportReferences[] on Form or Bulk (string IDs or rich objects with contactId / locationId / reportReferenceId). The engine evaluates external rules against that list in memory. Missing snapshot → warning that registry checks were not evaluated — not a silent pass counted as coverage.
The app is entirely stateless and does not maintain database connections. There is no live FINTRAC registry lookup — only the fixture or profile you supply for the current session (including the built-in pilot sample for demos).
This still does not file. It does not register contacts with FINTRAC and does not submit reports. Keep the snapshot aligned with what you actually maintain with the Centre.