Feature · Readiness

One clear answer: is this constraint set ready for review?

Ṛta scores your constraints across seven dimensions and gives one honest verdict: blocked, needs review, or ready, with the specific actions to take next.

In plain words

What does "readiness" mean?

A constraint file can have 2 errors or 50, but what does that mean for your review? Readiness turns the raw findings into one actionable status across seven dimensions, each with a verdict and recommended actions.

Dimension	What it measures	Verdict example
Analysis trust	How completely the input was analyzed	REVIEW_REQUIRED: 2 findings
Clocks	Clock definitions, duplicates, period sanity	READY
Consistency	Interactions: duplicates, overrides, contradictions	READY
Coverage	Object-level constraint coverage	READY: all ports covered
Design context	Object resolution against the netlist	VALIDATED: design-aware
Exceptions	False paths, multicycles, rationale	REVIEW_REQUIRED: 1 finding
I/O	Input/output delay completeness	READY

Real-world example

From "which file was worse?" to "start here"

A review used to mean reading a long findings list and deciding what mattered. With readiness, the same review starts at the P0 blockers and works down, because Ṛta has already prioritized the findings into actions.

✓P0 / P1 / P2 priorities: blockers outrank review items outrank advisories.

✓Gate-ready: the verdict maps directly to CI gate policies.

◈Never overclaims: the output repeats that this is readiness review, not STA signoff.


$ rta check top.sdc --netlist top.v --top top
Constraint readiness: REVIEW_REQUIRED
  CLOCKS      READY
  CONSISTENCY READY
  COVERAGE    READY
  EXCEPTIONS  REVIEW_REQUIRED - 1 finding
  ANALYSIS    REVIEW_REQUIRED - 2 findings

actions: P2 REVIEW_CLOCK_MODEL,
         P2 REVIEW_EXCEPTION
NOTE: readiness review, not STA signoff.

One status, not a wall of text

Seven dimensions collapsed into a verdict a reviewer can act on immediately.

Actions, not just status

Every non-ready dimension carries prioritized next steps.

Honest boundary

READY means ready for review, never a timing signoff claim.

Try it

Score your constraint set

Readiness review

$ rta check your_block.sdc --verbose
$ rta check your_block.sdc --gate STRICT # fail CI on any finding

Try it in the app ↗ All features