Predictable formal verification sign-off for critical digital IP and SoCs

Every successful verification project begins with understanding. During discovery, our engineering team develops a comprehensive grasp of the design under verification by reviewing the available documentation, specifications, architecture, interfaces, and design intent. Whether we will be verifying a cache, floating-point unit, controller, or another subsystem, the objective is to establish a shared understanding of what is being verified, what information is available, and, especially, what the customer's broader engineering objectives are.

This shared understanding establishes the foundation upon which all subsequent planning and verification decisions are made. The process is designed to require minimal effort from the customer: once the available design materials have been provided, LUBIS independently reviews and synthesizes the documentation to develop the technical context needed for the engagement. Customer input can then focus on clarifying specific questions and confirming broader engineering objectives, rather than guiding the discovery process itself. The result is an informed foundation for planning that establishes alignment and trust without placing an additional burden on the customer's engineering team.

Planning transforms understanding into execution strategy. Based on the knowledge gained during discovery, the verification team defines verification objectives, identifies technical risks, determines the appropriate verification approach which includes abstraction techniques, end-to-end vs. whitebox checks, as well as assumptions on the convergence of the proofs and coverage, allocates responsibilities, establishes milestones, and defines the evidence required to support sign-off confidence.

Thorough preparation ensures that the project will not only get off to a smooth start, but also proceed efficiently and consistently. Verification environments are configured, required assets assembled, assumptions reviewed, constraints developed, workflows established, and engineering teams aligned before execution begins.

Execution is where formal verification produces engineering evidence. Engineers develop and run properties, analyze results, debug failing assertions, investigate failures, refine abstractions, improve coverage, and continuously adapt the verification strategy as new information emerges. Where appropriate, automation and AI can accelerate many individual activities—but engineering judgment remains central to thoughtfully applying these efficiencies, interpreting results, and determining appropriate next steps.

Sign-off is not simply the conclusion of execution: it is the disciplined evaluation of whether sufficient evidence exists to demonstrate that all verification objectives have been achieved. Engineers review properties, constraints, coverage, cover pass, remaining risks, and outstanding issues before determining that the design is ready to proceed. LUBIS also supports customers in integrating formal verification results into their regression flows, helping preserve the value of the verification effort as the design continues to evolve.

The output of this stage is a formal sign-off package: a structured, reviewable body of evidence covering scope, assumptions and their validation, per-property proof status, the coverage and completeness argument, documented abstractions, residual risk, and an explicit register of known gaps. It is what allows a sign-off decision to be reviewed and trusted by people who did not perform the verification themselves.