Skip to content

Blog

Write Once, Run at Another Beamline: content-addressing for portable experiments

Here is a promise the recipe ladder made, and a question it left open. A Method, the portable rung of the ladder, is meant to describe a technique without naming any one facility's hardware, so that in principle a tomography technique perfected at one beamline could run at another. The question is what "in principle" is hiding. Hand a recipe from one facility to another and it will only run if both places agree on what its words mean: that "Hexapod" refers to the same kind of device, that "the microscope" refers to the same cluster of parts, that a "Positioner" is the same contract. And they have to agree without calling anyone, because in a federation of independent facilities there is no central authority to call. This is the same problem Git solved for source code, and CORA borrows the same answer.

What a Beamline Is Made Of: kinds, instances, and an inventory that stays honest

A photograph of a beamline looks like a fixed instrument. The reality is a population in slow motion. A detector is swapped for a better one. A stage is sent out for repair and a loaner takes its place. A mirror is recoated, a lens is recalibrated, a whole microscope is rebuilt around a new camera. Over a few years almost every part may change while everyone keeps calling it the same beamline. That is the old puzzle of the ship whose planks are replaced one by one: what makes it still the same thing? A system that means to record what a beamline did, for years, has to answer that puzzle first, because it cannot describe the work until it can faithfully name the equipment the work ran on.

The Right to Be Forgotten: erasing a person from a log that cannot be edited

An earlier post argued that CORA can be trusted for one reason above all: it was built never to overwrite anything. Every change of state is an immutable event, appended to a log the application is not even permitted to edit. That is the whole point. So here is the uncomfortable question it raises. A person has a legal right to ask that their personal data be erased, named in European law as the right to erasure, or the right to be forgotten, in Article 17 of the GDPR. How does a system whose defining property is that it cannot forget honor a request to forget someone?

The Recipe Ladder: from a portable technique to what actually happens at the beamline

Michael Polanyi observed that "we know more than we can tell." At a beamline this is not a philosophical aside but the daily operating reality. An operator carries years of practice that never fits in the written standard operating procedure, and software that models only the written procedure tends to fail the moment it meets the realities of daily operation. CORA's response is a structure we call the recipe ladder: four steps that give this tacit, unwritten knowledge somewhere to live, so that a technique described once can run at more than one facility, and a single experiment can record precisely where reality departed from the plan.

How CORA Remembers: an append-only log and no silent decisions

A record you can edit is not really a record. Overwrite a stored value and its past is gone: what it used to say, and why it changed, are simply unrecoverable. Yet those are exactly the things a beamline needs back, long after the fact. Which recipe did this run follow? Who approved the energy? Why was the center of rotation set there? CORA can answer questions like these for the same reason it can be trusted at all: it was built never to overwrite anything in the first place.

Agents as Principals: one identity for humans and AI

Two of the operators at the 2-BM beamline are not people. One of them reads a finished scan and records whether it completed cleanly, ran degraded, or aborted on a fault. The other watches for terminal run events and proposes a caution for a human to review. Both are software, and both raise the question every team adopting AI is now asking: how do you let an automated actor do real work without giving it a special, weaker, or unaccountable identity of its own? CORA's answer is that there is no special path. An agent is a principal, recorded, authorized, and audited exactly as a person is.