_Draft (round 14): the text is being written; the sections may still grow._
A machine profile is the file the twin builds its machine from: one file per machine model, in JSON. It holds the machine's geometry and its axes, the drives and the ball screws, the spindle and its drive, the sensors and their wiring, the workholding, the cutting data for each material, the tool setter and the touch probe, the sounds, and what the controller is built with. The controller's settings come with it as a settings file.
The profile records where its values come from (its provenance): the design, a data sheet, a published source, an assumption, or a measurement.
The MC-1's profile is generated from the machine's parametric design: the same parameters that make its drawings and its bill of materials make its profile, so the twin and the machine's design cannot drift apart. The profile keeps checksums of the design files it was made from. A schema checks its form; the reference chapter Machine profile schema lists every key.
Each MC-1 is to be measured at commissioning and its twin set to the measurements (planned; the procedure and its tools are written and tested on the twin):
The measured values are recorded with the date, the tool that measured them and how; the profile is rebuilt with them, each marked as measured with the design's value kept in its history, and the controller settings they change are sent to the machine.
Studio can keep several machines of a model. Each keeps its own world between sessions (where it stands, its workpiece, its tools, its controller's memory) and its own window layout; the machine model's profile is the same for all of them until a machine is measured.
Every key of the profile, with its type, unit and the MC-1's value: Machine profile schema.