I think the novel idea here is you jam some hardware together (whatever you like) that can do "physical real world" things with a well understood interface and then spin up Claude with access to it.

The way I'm thinking about it is, it's a _workflow_ innovation?

So you ask for data sheets for all the visible chips and get PDFs in an output directory with minimal user interaction except to flip the board, ask for a basic idea of connectivity, get a stitched high res surface image etc.... which of course are all currently possible, but you can do them potentially with very low effort. There doesn't have to be a _software stack_ ahead of time. You ask Claude to do the thing, it will figure out how to do it, write some code, pull in some OSS and make the thing happen. You can take this project's software or leave it.

You might say "tell me where you think the JTAG headers are" and it will come up with a workflow to do its best at that task (most likely with variable results...), but nonetheless this is not a thing you can ask of any commercial product I am aware of today. With probes, stuff can get interesting.

Of course experienced hardware & reverse engineers already can do all this stuff and have a plethora of workflows for it but I still think it's an interesting POC of a generalisable approach. You can take or leave this particular software stack. Also, the hardware barely matters, you can duct tape whatever to whatever.

feels like the author is hallucinating an instant solution to a problem with scope size of "research team and five years" class

From my understanding is you’d probe the board during different operations, process the results and deduct what signals are useful and traffic transmitting across the board (I.E private keys, what protocols are used, debug interfaces, firmware components, chip functions, etc).

I believe the standard production check is more like you check continuity between known nets, given that you're the manufacturer, you already know where they are exposed, and therefore you can perform those checks before adding any components. Post component checks are a lot more complicated because active components and passive components will modify the visible voltages and characteristics, often to the point where you won't have the same degree of physical insight.

I would assume once machines are set up that this is only really done if you're not confident of your manufacturing line for some reason (eg. maintenance, reconfiguration) or you are pushing limits somewhere, for example, particularly small vias or traces very close to the edge of the board.

To make this useful, you would want two flying probes because otherwise it's not going to be telling you much you don't already know.

Could an agent no develop a bespoke correction algorithm for the photos of the photo?

> someone is getting hired off a single github repo as CV

Isn't that a good thing?

Nowadays the former seems to be a requirement for the latter, so I'm inclined to agree with you

I think this is roughly solved. Tell the agent to do all of its calculations in python.