Assume vs Assert: Constraint Hygiene and Over-Constraint Risk: Theory Deep Dive

Foundational theory

Assume vs Assert: Constraint Hygiene and Over-Constraint Risk is a core topic in Property Development & Constraints. Treat each proof result as evidence under a modeled world, not a context-free truth statement.

Core concepts explained

• A practical rule is: assume environment behavior, assert design obligations. Inputs driven by a testbench model (external protocol timing, fairness, legal command encodings) are candidates for `assume`; internal guarantees (state transition legality, handshake completion, exclusivity) belong in `assert`. Over-constraint risk appears when assumptions remove legal but difficult scenarios, producing fast green runs that do not represent silicon reality. Constraint quality review should include: assumption traceability to spec text, cover checks for key legal scenarios, and periodic assumption-to-assert mutation checks (temporarily flip suspect assumptions into assertions to detect hidden design dependencies). ```systemverilog // Environment assumption: requester holds req until grant assume property (@(posedge clk) disable iff (!rst_n) req && !gnt |=> req ); // Design assertion: grant implies resource not busy next cycle assert property (@(posedge clk) disable iff (!rst_n) gnt |=> !busy ); // Reachability guard: legal retry scenario must remain possible cover property (@(posedge clk) disable iff (!rst_n) req ##1 !gnt ##1 req ##1 gnt ); ``` If the cover never hits after adding assumptions, investigate over-constraint before trusting proof results.

• 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

Property development is architecture translation work: requirement intent must survive decomposition, abstraction, and reuse. Teams that formalize this posture reduce false passes and late-stage surprises.

Mental model

CONE OF INFLUENCE REDUCTION

Full RTL graph:
  inputs -> decode -> datapath -> control -> outputs
                \         |
                 \------ checker signal

COI for property:
  inputs -> decode -> checker signal -> property

Prune unrelated logic to reduce solver state space.

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

• Green proof status always means silicon-safe behavior.

• Faster convergence always means better model quality.

• Unreachable cover goals are acceptable if safety assertions pass.

• Bounded depth is equivalent to full proof unless a failure appears.

Formal deep dive

Property and constraint engineering is successful when decomposition, reuse, and abstraction preserve legal behavior.

Concept diagram

PROPERTY DEVELOPMENT PIPELINE

spec clause -> decomposed properties -> constraints -> covers -> closure packet

Metric graph

CONSTRAINT HYGIENE TREND

over-constraint risk    ████
cover reachability      ███████
library consistency     █████

Metrics and artifacts to collect

• assume/assert separation coverage

• critical cover reachability score

• checker library adoption and drift

• over-constraint warning trend

Mini case study

A reusable checker library reduced regression noise after assumptions were explicitly documented and reviewed per IP.

Debug branches

• Review every assumption against a spec citation.

• Use covers to confirm legal corner scenarios remain reachable.

• Track abstraction choices in a rollback-ready ledger.

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.