"Two holders never hold the lock at once" is which kind?
- A performance goal
- A liveness property
- A safety property
Which kind of property is refuted by a single finite trace?
- Safety
- Liveness
- Neither kind
An invariant must hold at the start and survive every step.
Circle one: True False
Your proof step breaks the invariant. What must happen?
- Ship the proof anyway
- Fix step or weaken claim
- Drop the base case instead
"Every request is eventually answered" is which kind?
- An invariant
- Safety
- Liveness
A dead program never sends a bad message. What is missing from that spec?
- Liveness for progress
- A stronger safety ban
- A longer finite trace
A counter starts at 0 and each step adds 2. Is "the count is even" preserved?
- No, 0 is not even
- Yes, +2 stays even
- Only on steps that add 4
Jo shows one snapshot of a waiting requester and claims liveness refuted. What is wrong?
- Snapshots can only prove liveness
- The waiter might still be served later
- Waiting requesters prove safety instead
Forbid the bad, demand the good W1-mt_4_KaoDSHZF-s1
- A safety property · It forbids a bad state outright.
- Safety · The trace exhibits the bad thing happening.
- True · Both checks together power the induction.
- Fix step or weaken claim · A broken link voids the induction.
- Liveness · It demands a good event in the fullness of time.
- Liveness for progress · Pure prohibition blesses idleness.
- Yes, +2 stays even · The start is even and each step keeps it even.
- The waiter might still be served later · Refuting eventually needs forever, not a moment.