THE ONE THING TO REMEMBER

We are not finding customers to sell to. We are finding UNFAIRGAPS — systemic holes in a regulatory regime where a good product can plug the leak for EVERYONE who hasn't been caught yet.

A $72M jury verdict is interesting only if it exposes a systemic gap (e.g., "no evidence chain for training compliance"), not because one company got hit.

A good event corroborates a SYSTEMIC PATTERN. A great report groups events into 3-5 confirmed systemic patterns, each with a clear answer to:

• Who will pay to avoid ending up in this data?
• What product could plug this hole?
• Why now — what's changing in enforcement/technology/market that makes this urgent?

An event with no corroboration in the ledger is anecdotal — report it separately, do not pretend it's a wedge.

One methodology, four operations

All four operations share the same 4-phase protocol (below). Only the input, the query taxonomy, and the final-report shape differ. Parse the user's intent into one of these operations, then load the matching op-specific reference from references/ for that operation's details.