Getting started

instr-core turns a requested measurement into a reviewable, constrained workflow:

1. Plan — resolve the instrument identity and build an operation plan from its Schema.
2. Validate — check capabilities, ranges, prerequisites, state, safety constraints, and dry-run output.
3. Explicit confirmation — show the exact proposed actions and risks to the operator.
4. Execute — only after confirmation, pass constrained actions to the local connection layer.

Integration surfaces

Applications can integrate through MCP or the Agent API. The Desktop environment presents local connection state and the confirmation UI. VISA / SCPI adapters sit closest to the instrument and must still enforce the validated plan.

Responsibility boundary

instr.cc publishes documentation, instrument keys, Schemas, and future machine-readable endpoints. It does not control physical hardware. Hardware access belongs to a user-controlled instr-core runtime, where identity, wiring, firmware, state, and command support can be checked locally.

Choose an instrument key

Use the same manufacturer/category/model instrument key everywhere:

keithley/dmm/dmm6500

That key identifies the human-readable Registry page and the future JSON, YAML, and API resources.