PROMPT
You see spec feature coverage, compliance pass rate, waiver count on Compliance & Coverage Plan. Walk through root cause and fix.

STRONG ANSWER
1. Names the layer and transaction identity.
2. Explains compliance maps spec requirements to tests, assertions, coverage bins, exclusions, and signed waivers.
3. Requests requirement trace matrix, coverage dashboard, waiver log.
4. Proposes one reduced sequence and one system regression.

WEAK ANSWER
Jumps to widening the interface, increasing FIFO depth, or blaming firmware without evidence.

COMPLIANCE TRACE MATRIX

spec clause ──> test(s) ──> assertion(s) ──> coverage bin ──> status
  4.2.1          t_axi_07     a_resp_ok        cov_resp        PASS
  4.3.5          t_axi_12     a_order          cov_order       WAIVED (id=W3)
  4.4.0          (none)        (none)           (none)          GAP  <- find these

A gap row is the most valuable output of the plan.

ROOT-CAUSE TREE — Compliance & Coverage Plan

spec feature coverage, compliance pass rate, waiver count looks wrong
        |
   reproducible?
     /        \
   no          yes
   |            |
 flaky env   same first transaction every time?
 / seed         /            \
              yes             no
               |               |
        protocol rule     timing/reset/PVT
        or config bug     or load-dependent

VERIFICATION CLOSURE LOOP

spec clause -> test -> assertion -> coverage -> waiver -> signoff
                  ^                           |
                  +--------- gap found --------+

COVERAGE vs ESCAPE RATE

escapes
  |*
  | *
  |  *
  |   **  <- knee: more random helps
  |     ****
  +----------------> constrained-random depth