Model

The developer's index into where 19-BM content lives. Design-phase.

19-BM is a documentation-and-descriptor scaffold today: it exists as the descriptor and docs below, not yet as registered events or integration scenarios. This page points to where each piece lives.

Kind	Where	Notes
Beamline descriptor	deployments/19-bm/beamline.yaml	the device walk; source of the generated Source page
Site descriptor	deployments/aps/site.yaml	the APS facility surface, shared with 2-BM; 19-BM is added there as a second beamline
Catalog Family	catalog/catalog.yaml	none added: 19-BM reuses the active families 2-BM established (Slit, Filter, Shutter, RotaryStage, LinearStage, Table, Camera, Scintillator, TimingController)
Catalog Assembly	catalog/catalog.yaml	the indirect detector reuses the cross-facility Microscope / Optics Assemblies (shared with 2-BM and TomoWISE)
Catalog Model	catalog/catalog.yaml	none bound: 19-BM hardware is not yet procured
Equipment Assets	not yet registered	the Inventory is the planned shape; no scenario registers 19-BM Assets yet
Trust / governance	not yet instantiated	see Governance

What is deliberately not here yet

• Integration scenarios. No test_19bm_*.py registers 19-BM Assets into the event store. Scenario code is where Assets become real, and hard-registering a design-phase, moving-target beamline would commit speculative structure. It lands when the design firms and the team approves.
• Vendor Models. No catalog Model is bound: the sample stages, the detector hardware, and the robotic changer are all procured after the FDR and are carried as open questions, not bindings.
• New catalog Families. 19-BM coins none of its own. The two passive families it pushed past the rule-of-three threshold (Window, with two more Be windows; Collimator, with two more Pb collimators) have since been promoted to catalog Families under the passive beam-path tier; 19-BM's windows and collimators now bind them.
• The autonomy build. The RunSupervisor enablement and the missing run-start capability that 19-BM's autonomous operation needs are real CORA work, not documentation; see Governance. They land as their own slices.
• The robotic sample changer. Deferred behind its separate safety review (ROBOT-1).
• Operations and experiment views. A runbook and live experiment view for an unbuilt beamline would be invention; see the note on the index.

The 2-BM Model page shows the by-kind index a fully-modelled deployment carries.