The shortest path from
question to running loop.
Start with the docs. If the answer depends on your hardware, Matthew replies personally.
Errors, shape mismatches, timeouts, and recovery.
See the operating conditions and application landscape.
The two modes, measurement contract, and clean sessions.
Describe the workload and get a direct reply.
The maintenance layer and stability contract for supported component-observable continuous hardware in a hybrid computing stack.
Exactly budgeted preflight, five live contract states, safe holds, retry-safe updates, evidence-scoped family guidance, and a signed run record.
Yes. Existing evaluation and paid keys keep their format and entitlement. Client 0.4.3 remains on the frozen legacy path.
The lightweight client orchestrates your local measurement. Evaluation is hosted; paid deployments can run offline beside the hardware.
Configuration, measured response, target, and public contract declarations. Session vectors remain volatile and are not retained after the session.
High channel count, costly parallel reads, changing conditions, and hard physical deadlines.
Yes. Offline deployments remove the network hop.
Same plant. Same start. Same budget. Best incumbent.