Reading and Debugging Counterexample Traces

What this topic teaches

Reading and Debugging Counterexample Traces converts formal concepts into release-ready verification decisions. Counterexample debug should begin at the first point of semantic divergence, not at the final failing cycle where symptoms are visible.

Senior-engineer framing question

When non-vacuous closure rate, counterexample turnaround, and residual-risk trend by requirement class regresses, can you isolate the first failing assumption/property boundary, prove causality, assign owner, and close with auditable risk?

FORMAL EXECUTION FLOW - Reading and Debugging Counterexample Traces

requirement intent and risk class
      |
      v
property and assumption modeling
      |
      v
proof engine exploration and trace extraction
      |
      v
counterexample classification and fix hypothesis
      |
      v
re-proof, coverage audit, and signoff decision

Evidence to collect

• Primary metric: non-vacuous closure rate, counterexample turnaround, and residual-risk trend by requirement class.

• Primary artifact: closure packet for Reading and Debugging Counterexample Traces: assumptions audit, proof status matrix, and replay-ready divergence trace.

• Owners to include: formal verification owner, rtl owner, Methodology & Debug owner.

• One reproducible failing trace and one stable comparator run.

• One fixed metadata run with assumptions and tool settings locked.

Ownership layers

OWNERSHIP LAYERS - Reading and Debugging Counterexample Traces

+----------------------+--------------------------------+--------------------------------+
| Team                 | Primary responsibility         | Closure artifact               |
+----------------------+--------------------------------+--------------------------------+
| formal verification owner | property and model integrity      | assumptions and proof packet   |
| rtl owner | implementation root-cause closure | RTL fix and replay evidence    |
| Methodology & Debug owner | signoff governance and rollout    | risk memo + acceptance gates   |
+----------------------+--------------------------------+--------------------------------+

Decision matrix

EVIDENCE MATRIX - Reading and Debugging Counterexample Traces

+-----------------------------+--------------------------------+--------------------------------+---------------------------+
| Evidence                    | Tells you                      | Does not prove                 | Next action               |
+-----------------------------+--------------------------------+--------------------------------+---------------------------+
| property status by class    | closure shape by requirement   | model realism                  | pair with cover reachability |
| vacuity and trigger checks  | assertion meaningfulness       | full legal-path exploration    | inspect assumptions       |
| counterexample traces       | concrete divergence path       | complete bug-space closure     | classify and replay       |
| assumption audit trail      | model boundary confidence      | implementation correctness     | review spec traceability  |
| before/after trend packet   | mitigation movement quality    | long-window stability          | run broader matrix        |
+-----------------------------+--------------------------------+--------------------------------+---------------------------+

Key takeaways

• Start with first-divergence classification before broad model edits.

• Tie each claim to one proving artifact and one owner action.

• Close with residual-risk statement and rollback-safe criteria.

Common pitfalls

• Treating green status as correctness without vacuity and reachability audits.

• Changing assumptions and RTL together, destroying causality.

• Declaring closure without replaying representative legal scenarios.

Formal deep dive

Formal methodology scales when ownership, triage policy, and CI automation are explicit and stable.

Concept diagram

METHODOLOGY LOOP

plan -> run in CI -> triage -> fix -> revalidate -> signoff dashboard

Metric graph

FLOW MATURITY SIGNALS

triage latency           ████
reopened proofs          ███
deterministic closure    ███████

Metrics and artifacts to collect

• requirement matrix freshness

• counterexample turnaround SLA

• inconclusive aging by risk tier

• reopened proof trend after RTL churn

Mini case study

Integrating formal into daily CI cut reopened-property surprises near release by enforcing vacuity and waiver policies.

Debug branches

• Start debug at first semantic divergence cycle.

• Tag every failure with owner and risk tier immediately.

• Automate stale inconclusive and vacuity alerts.

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.