Read src/frontends/gguf/docs/debugging_accuracy.md — the coarse-to-fine bisection strategy, the ggml-CPU oracle technique, the catalogue of bug archetypes with their generalizable lessons, the debug env vars, and the checklist.
Apply its one governing rule before anything else: every accuracy claim is a comparison against the real llama.cpp CPU implementation, never a hand-derived reference. If you are about to write out an op's math to form an expectation, generate it from ggml instead.
Work the bisection steps in order and do not open a debugger until they have cornered the bug. Check the bug archetypes first when a cosine cliff or dynamic-shape crash points near one.
After any fix to a shared path — especially a VIEW or op_case predicate — re-run the other supported architectures and confirm their classification and output are unchanged.

ov-gguf-debug-accuracy