A Common Capability Contract is the shared boundary that lets different teams work before final hardware is available. It describes the function, not an unlimited permission to use a Resource.
contract_idStable identifier for the function contract or profile.
functionHuman-readable action/result, e.g. locate_marks.
input_schemaVersioned input objects, units, allowed ranges and required files.
output_schemaVersioned result, quality fields, units, evidence references and error states.
resource_targetHSIMC Resource or target class; actual physical instance is bound separately.
execution_modesimulation / physical_reference / physical_delivered / operational.
conditionsEnvironment, tooling, calibration, material and prerequisite conditions.
authority_requiredMinimum Authority required to discover, read, reserve, configure, execute, stop, accept or administer.
effect_identityDigest or identifier that locks the intended physical effect independently of short-lived credentials.
operation_idStable identity used for retry/read-back of a physical-effect request.
freshness_requirementMaximum acceptable age for observations used to authorize or plan the action.
resource_lockingReservation, lease, busy/conflict behavior and release rule.
safety_boundaryConditions that must remain local/deterministic and cannot be delegated to a remote model.
acceptanceMeasurement, tolerances, evidence and human/organizational acceptance step.
recoveryStop, unknown-result, interrupted-network and restart behavior.
versionContract, adapter, algorithm, hardware/BOM, calibration and deployment version references.
cost_timeExpected and actual time, material, energy and monetary cost fields.
rightsContribution, reuse, attribution, confidentiality and withdrawal constraints.
locate_marks{
"contract_id": "hsimc.locate_marks.v0",
"function": "locate_marks",
"input": {"image_ref": "sha256:...", "marker_profile": "marker-profile-v3", "calibration_ref": null},
"target": {"resource_id": null, "mode": "simulation"},
"authority": {"subject": "bound-at-runtime", "scope": ["read_input", "run_observation"]},
"output": {"coordinate_space": "pixels", "marks": [], "quality": {}, "evidence_refs": []},
"limits": ["No millimetre conversion without calibration evidence", "Observation only; no machine motion or laser action"]
}The same contract can run against fixed images, a cloud simulator, a remote reference camera, or a delivered device. Each target still requires its own adapter and evidence.
A retry should reuse the original operation_id when the
requested physical effect is the same. If the outcome is unknown, query
the original operation before creating a new effect. New credentials or
a refreshed token do not by themselves create a new physical Work.