Publish checklist

Done means four things

Publishing is not the end state. The checklist has four items: the post is live at a stable URL; the README links to it from a section a reader can find; the artifact has a DOI and the post links to it; and the feedback channel exists and is triaged. A post with three of the four is a draft that escaped.

[ ] post URL returns 200 from a logged-out browser
[ ] README "Writeups" section links the canonical URL
[ ] artifact DOI resolves to the tagged commit
[ ] feedback template asks for rig, versions, command, numbers; every report is labelled

Run a link check over every URL in the post, including the artifact and the sources. Canonical documentation links move, and a 404 in a citation is the cheapest credibility loss available.

Feedback is work, not applause

The template should ask for the things without which a report cannot be reproduced: host CPU, QEMU CPU string, LLVM and MLIR versions, the exact command, the observed numbers and the expected ones. A report that says “slower on my machine” costs a round trip and usually dies there.

Triage means each report becomes either a bug with a reproduction or a next-phase issue with a label, and the reporter gets a reply saying which. Feedback that lives in an inbox is not filed, and the phase boundary is exactly where it gets lost.

Things that break

Linking the README to a draft URL means the stable link is the one that changes. Publishing before the DOI exists leaves the artifact unarchived. And an issue template without environment fields produces reports nobody can act on, which is worse than no template because it looks like a process.