Properties and Assertions: Safety, Liveness, and Sound Modeling: Theory Deep Dive

Foundational theory

Properties and Assertions: Safety, Liveness, and Sound Modeling is a core topic in Formal Verification Foundations. Treat each proof result as evidence under a modeled world, not a context-free truth statement.

Core concepts explained

• A safety property states that something bad never happens, such as illegal FSM transitions, protocol exclusivity violations, or write-without-grant behavior. A liveness property states that something good eventually happens, such as eventual response completion, progress out of retry states, or forward movement under fair arbitration. Assertion quality depends on precise antecedents, bounded or unbounded temporal intent, and explicit treatment of reset and X-propagation semantics. For liveness, fairness assumptions are often required so the proof engine can distinguish genuine deadlock from an unconstrained hostile environment that can starve progress forever. Teams must actively check vacuity, because a property can pass trivially if its trigger never activates. A robust property set therefore combines interface-level assumptions, design guarantees, cover directives for reachability, and periodic peer review to ensure properties express architectural intent rather than accidental implementation detail.

• Primary metric: non-vacuous closure rate, counterexample turnaround time, and requirement-level residual risk trend

• Primary artifact: formal closure packet: assumptions audit, proof status matrix, counterexample classification, and requirement traceability

• Owners: formal verification owner, rtl owner, verification lead

• Proof quality includes vacuity and reachability, not pass/fail status only.

• Assumption discipline is part of design correctness, not tool setup.

Why this matters in formal signoff

Formal foundations are strongest when assumptions, reset semantics, and requirement intent are all explicit and reviewable. Teams that formalize this posture reduce false passes and late-stage surprises.

Mental model

PROOF VS SIMULATION

Spec intent -------------------------------> complete state space
       |                                               |
       |                               Formal proof: explores all legal paths
       |
       +--> Testbench stimulus ---> Simulation traces (sampled paths only)

Simulation finds witnessed bugs.
Formal can prove absence of bug within constraints.

Worked intuition

1. Define requirement slice and property intent class (safety, liveness, or reachability).

2. Audit assumptions and reset model before trusting any status outcome.

3. Track movement in non-vacuous closure rate, counterexample turnaround time, and requirement-level residual risk trend with requirement-level ownership.

4. Collect formal closure packet: assumptions audit, proof status matrix, counterexample classification, and requirement traceability before signoff or waiver decisions.

5. Apply one bounded model or RTL change per debug hypothesis.

6. Publish closure with residual risk and rollback conditions.

Common misconceptions

• Safety properties imply forward progress automatically.

• Eventuality checks are meaningful without fairness assumptions.

• Pass status means antecedent triggered in relevant traffic modes.

Formal deep dive

FPV foundations are reliable only when assumptions, reset semantics, and requirement intent are explicitly modeled and audited.

Concept diagram

FPV FOUNDATION LOOP

requirements -> property set -> assumptions and reset model -> prove/fail traces -> closure audit

Metric graph

FOUNDATION HEALTH

vacuous passes         ████
reachable proofs       ███████
inconclusive backlog   █████
reopened properties    ███

Metrics and artifacts to collect

• assumption traceability matrix

• vacuity and reachability status

• proof core relevance summary

• counterexample classification trend

Mini case study

A green-looking run was invalidated after legal-mode covers failed, exposing assumptions that removed realistic traffic.

Debug branches

• Validate requirement-to-property mapping before tuning runtime.

• Check legal scenario reachability after every assumption change.

• Classify first divergence as model issue or RTL bug.

Senior review question

Ask: which requirement intent is proven, under which assumptions, and what residual risk remains?

Key takeaways

• Tie each proof claim to assumption boundaries and reachability evidence.

• Prefer minimal reversible fixes and preserve legal behavior visibility.

Common pitfalls

• Treating runtime reduction as proof-quality improvement without audits.

• Declaring closure while critical covers remain unreachable.

• Using broad waivers instead of first-divergence root-cause ownership.

Theory reinforcement

Theory matters only when it predicts observed traces and closure movement.

Use precise terminology for safety, liveness, boundedness, and vacuity.