ChipMeld

MELDPROOF / EARLY TECHNICAL PREVIEW

See which proofs an RTL change may disturb.

MeldProof is revision-aware formal regression decision support for bounded SystemVerilog blocks. It is being developed to produce an auditable impact set and dependency rationale before proof execution continues in the customer’s authorized environment.

See the workflowDiscuss an evaluation

REVISION IMPACT

Formal regressions start with a change, not a blank slate.

A revision can disturb assumptions, dependencies, and properties. MeldProof is being developed to help engineers decide where to look again and why, within a supported boundary, without treating the resulting view as exhaustive or as a proof result.

ILLUSTRATIVE REVISION IMPACT

Make the dependency rationale reviewable.

The illustrated flow separates a supported change path from relationships that appear unchanged and cases the analysis leaves undetermined.

Illustrative synthetic workflow. Not a solver result.

Revision impact workflowRevision A and Revision B identify a changed RTL structure. Solid orange paths show supported dependency relationships to candidate properties, a gray dashed path shows an unchanged illustrated relationship, and an amber dotted path marks an undetermined relationship before engineer review.REVISION A / BKnown-good Artl@a17cCandidate Brtl@b204 · changedSUPPORTED CONEPotentially affectedstate_q → grant_oUnchanged herereset_n pathPROPERTY CANDIDATESCandidatep_grant_stableUndeterminedp_mode_escapeUnchanged herep_reset_releaseREVIEWEngineerreviewdecide next step

Equivalent text view

Changed RTL
Candidate revision B contains the illustrated supported change.
Potentially affected
Supported dependency paths nominate properties for review.
Unchanged within the illustrated relationship
The shown reset relationship is not connected to the highlighted change.
Undetermined or outside supported analysis
The workflow preserves uncertainty instead of turning it into a conclusion.
Engineer review
An engineer reviews the candidates and rationale before deciding what to rerun.

MELDPROOF WORKFLOW

From revision context to an engineer-reviewed handoff.

ChipMeld means auditable evidence for chip-engineering decisions.

  1. 01

    Compare revisions

    Identify supported changes within the bounded analysis scope.

  2. 02

    Trace dependencies

    Analyze supported relationships between changed logic and candidate properties.

  3. 03

    Prepare the impact view

    Surface candidate properties and rationale for engineer review.

  4. 04

    Continue in the authorized flow

    Engineers decide what to rerun and continue proof execution in their authorized formal environment.

CONCEPTUAL INTEGRATION

Keep the decision inside the authorized workflow.

Revision inputs, analysis, impact review, and the downstream formal flow stay within the illustrated customer-controlled environment. MeldProof prepares a reviewable handoff; the engineer decides what happens next.

Illustrative synthetic workflow. Not a solver result.

Customer-controlled formal workflowInside one customer-controlled environment, RTL revisions, a property set, and configuration enter MeldProof analysis. A reviewable impact view goes to an engineer, who decides what to hand to the customer’s authorized formal flow.CUSTOMER-CONTROLLED ENVIRONMENTINPUTSRTL revisionsA / BProperty setsupported scopeConfigurationanalysis boundaryMeldProofanalysissupported relationships+ explicit uncertaintyIMPACT VIEWCandidatesRationaleUncertaintyEngineer reviewand decisionhuman-controlledCustomer’s authorized formal flowproof execution continues under engineer control

Equivalent text view

  1. RTL revisions, the property set, and configuration remain inputs inside the customer-controlled environment.
  2. MeldProof analyzes only supported relationships and preserves uncertainty.
  3. The output is a reviewable impact view with candidates and rationale.
  4. Engineer review and decision remain between the impact view and proof execution.
  5. The engineer may continue in the customer’s authorized formal flow.

SUPPORTED ROLE

A narrow decision-support layer.

Proof execution, review, and signoff remain with existing tools and engineers.

What it is

  • Revision-aware impact triage for a supported bounded block.
  • Reviewable rationale connecting a revision to candidate properties.
  • Decision support for an engineer-controlled regression workflow.

What it is not

  • Proof that the revised design is correct.
  • A signoff result.
  • An autonomous formal-regression system.
  • Full-chip or unrestricted SystemVerilog support.
  • A substitute for a formal solver or engineering judgment.

BOUNDED EVALUATION

Review the scope before the results.

Start with one bounded block, known revisions, and an engineer-owned review path.

Discuss a bounded evaluation