Watch a property get proven.
Testing samples inputs. An observer checks a requirement at every step. Pick a safety property below, run it over a signal trace, and watch the verdict resolve, or watch testing miss the one counterexample that breaks it.
This is how requirements-based testing works in a formal setting: each requirement becomes a formal specification-pattern observer that runs in parallel to the system and emits a Boolean Valid signal at every step. While the property holds, the observer sits in an accepting state. The moment a behaviour violates it, the observer enters its single failure state and hands you the exact step, the counterexample.
Name one property your system must always hold.
If you can state it in a sentence, we can turn it into an observer and prove it over your model and recorded traces, not just sample it. That is where an engagement starts.