Timing exceptions

Timing exceptions (triage). The default single-cycle analysis flags a pile of violations. Your job is to triage each path into what it really is:

• single-cycle - an ordinary path that is fine as reported.
• multicycle-N - the data is only sampled every N clocks (a slow pipeline, a config word updated every few cycles). Read the note for the exact N.
• false path - never a real functional path: a synchronizer stage, a scan/test-only path, an asynchronous or quasi-static crossing.
• REAL violation - a genuine single-cycle functional path that is simply too slow. This is a real bug: it goes back for a fix (resize, restructure), you do not exception it.

Read each path's note and classify it. The trap: false-pathing a real functional violation makes the number green but hides a bug that will fail in silicon. Triage them all, then Submit triage.