Diffable circuit snippets
<KernelDiff> showing G1 vs. G3 side-by-side. Same kernel, different post-processing — proves the structural point without prose.
Results · real Selene shots
kernel_diff_shipped<KernelDiff baseline=G1 candidate=G3> renders on /nadarasa/g3 with a 50-line client-side LCS. The two kernel snippets are ~90% identical — the structural point the card claims, rendered without prose.
Why this matters
Every JSON already carries `kernel_snippet`. G1 and G3 use the same Guppy kernel shape; the experimental difference is entirely in the host post-processor. A side-by-side syntax-highlighted diff makes this obvious in two seconds.
What the repo already has
`kernel_snippet` fields in all nadarasa_g*.json files.
What's missing
A `<KernelDiff baseline=g1 candidate=g3 />` React component using a minimal diff algorithm; drop it on /nadarasa/g3.
Smallest experiment
Build it or kill itQubits
n/a — pure frontend.
Ancilla pattern
n/a
Shots
n/a
Predicted outcome
Diff highlights zero lines in the kernel; the difference is entirely in the host_post_process field (which we'll add to the JSON schema as part of the json-ir-schema card).
Refutation criterion
If the kernel diff is non-empty, the 'same kernel, different post-processor' claim is wrong and the G3 page text needs updating.
Kernel sketch
Untested — sketch only// React component. Use diff-match-patch or a 50-line LCS implementation; render in a monospace grid with green/red gutters.
Host pipeline
n/a — UI only.
Related
Files in this repo
- · src/lib/lcs-diff.ts
- · src/components/selene/KernelDiff.tsx
- · src/routes/nadarasa.g3.tsx
- · src/data/demos/nadarasa_g1.json
- · src/data/demos/nadarasa_g3.json