Governance¶
Who will act at P64, and the trust shape that will gate it. First cut.
Governance at P64 follows the same model as the rest of the fleet: people and autonomous agents are facility principals at the PETRA III Site, and on the beamline they surface through the actions they take. Their commands are gated by a trust shape (a Zone grouping the beamline's resources, a Conduit binding the surfaces that may issue commands, and Policies that say who may do what).
P64 is CORA's ninth PETRA III beamline: the DESY operator pool and the safety-review structure are carried pending on the PETRA III Site, shared across the facility's beamlines, until DESY staff confirm them (GOV-1). P64 is a reverse-engineered scaffold rather than a pilot, so the concrete Zone, Conduit, and Policy instances are deliberately not materialized; they land when the deployment approaches the point where CORA drives P64, following the 2-BM governance shape.
The safety tier is the other piece that is not yet settled. The OnlineXML carries beamline devices, not the personnel-safety interlock leaves, so the Enclosure permit signals and the interlock structure are carried pending and are not invented here (PSS-1). P64 shares its optics hutch with the applied-XAS sibling P65, so the optics-enclosure access state couples to the neighbouring beamline, part of the PSS-1 question.
The concrete Zone, Conduit, and Policy instances, and the operator pool, land when the deployment approaches the point where CORA drives P64, following the 2-BM governance shape.