X-Propagation and Reset Verification with Formal: Reports and Metrics

Reports and metrics

Reports and Metrics for X-Propagation and Reset Verification with Formal is anchored on non-vacuous closure rate, counterexample turnaround, and residual-risk trend by requirement class. Convert outcomes into assumption-aware, evidence-backed actions.

A useful report explains why closure quality moved, not only that status changed.

Evidence matrix

EVIDENCE MATRIX - X-Propagation and Reset Verification with Formal

+-----------------------------+--------------------------------+--------------------------------+---------------------------+
| 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        |
+-----------------------------+--------------------------------+--------------------------------+---------------------------+

• Track non-vacuous closure rate, counterexample turnaround, and residual-risk trend by requirement class by requirement class and risk tier.

• Include assumption and tool metadata in every report header.

• Correlate status with vacuity and cover reachability movement.

• Call out contradictory evidence explicitly.

Formal deep dive

Formal apps generate high confidence when app-specific assumptions mirror integration and firmware behavior.

Concept diagram

FORMAL APPS MAP

connectivity + csr + progress + reset/x checks -> integrated SoC confidence

Metric graph

APPS CLOSURE QUALITY

functional app closure   ███████
environment realism      █████
waiver pressure          ███

Metrics and artifacts to collect

• connectivity route reachability

• CSR semantic correctness matrix

• progress guarantee closure by interface

• reset/X convergence confidence

Mini case study

Deadlock traces were resolved by tightening fairness assumptions to architecture contracts, not by weakening liveness guarantees.

Debug branches

• Validate mode and configuration constraints for each app.

• Pair safety and liveness checks for progress-sensitive logic.

• Add first-transaction covers for reset-sensitive interfaces.

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.

Report interpretation

Report status with vacuity, cover reachability, and assumption influence side by side.

Promote only when trend data supports reproducible closure behavior.