Select directed litmus tests from the named architecture/memory model and product risks, with explicit initial values and operation semantics. Add concurrent coherent stress and formal properties where their assumptions and bounds are tractable. No finite suite covers every execution of every ordering promise.
Verification components must observe/model the snoop, response and data behaviours needed by each checked requirement; one VIP configuration may not cover all boundaries.
Retain cache-line state and uniquely correlate concurrent transactions using the selected protocol's node/transaction context; repeated accesses must not overwrite each other.
Trace each implemented shareability/domain behaviour to risk-based scenarios, checkers and reviewed evidence.