Part 14 answers: When are we done?
Sign-off is a decision about risk, made with incomplete evidence. A good sign-off states what was verified, how, what was waived and why, and what risk remains, so the people deciding to tape out know exactly what they are accepting.
This part covers what sign-off means, criteria, waivers, stating residual risk, running a tape-out review, and the finale of the project: DCRouter's complete evidence ledger and bug-catch matrix.
Define sign-off criteria for a block or chip.
Write waivers and a residual-risk statement that hold up in review.
Run a tape-out review that decides on evidence.
Answer each in your head before opening it. If two or more feel shaky, revisit Part 13: Debug first.
Observe: reproduce the failure and collect the facts before forming a hypothesis.
Bisect the change history (or shrink the input with delta debugging) until one change or a minimal case remains.
Check the failing expectation against the specification and an independent model before blaming either.
# | Lesson | Level | Status |
|---|---|---|---|
14.1 | S · Senior | Ready | |
14.2 | S · Senior | Ready | |
14.3 | P · Principal | Ready | |
14.4 | P · Principal | Ready | |
14.5 | P · Principal | Ready | |
14.6 | S · Senior | Ready | |
— | all levels | Ready |
Every lesson in this part is ready. Work through them in order: each one sets up the problem the next one solves.
This course teaches the decisions behind verification. These lessons teach the tools and syntax that carry them out, so this part links to them instead of repeating them.