Dispatch 134
Week ↗

Sunday NPU bug, documented and locked in

Sunday, 11/23 was a one-commit day but the commit carried the weight. I spent it documenting a critical bug in the NPU Mel kernel and validating the baseline performance so the team isn't left guessing what…

Commits
1
Systems
1
Read
1min
Field photo

Shared memory — suite architecture in the lab.

Sunday, 11/23 was a one-commit day but the commit carried the weight. I spent it documenting a critical bug in the NPU Mel kernel and validating the baseline performance so the team isn't left guessing what went wrong.

The Mel kernel has a known critical issue and it's been sitting under-documented. I wrote up what the bug does, where it lives, and what the baseline looks like when the kernel is running in its current state. That means adding a CRITICAL_FINDING_NOV23.md with the technical details, a PERFORMANCE_SUMMARY_NOV23.md capturing the baseline numbers, updating the Mel preprocessing entrypoint, and patching the attention integration file so the doc changes land in the right place. The diff was 581 lines added and 15 removed across four files.

Writing documentation for a bug can feel like paperwork, but when the kernel is in a fragile state the docs are the thing that keeps people from losing time reproducing what we already know. The critical finding doc spells out the issue. The performance summary gives the reference point so anyone checking the NPU path on Monday morning has something to compare against.

I wrote up what the bug does, where it lives, and what the baseline looks like when the kernel is running in its current state.

It was a quiet day by commit count. One repo, one commit. But the kind of one-commit day where the single thing actually matters.

Tomorrow there are probably more commits. Today there was clarity.