HSIMC · UN Six-Language White Paper · P6 / W0-017

Appendix C - Common Capability Contract

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.

C.Field - contract_id

Stable identifier for the function contract or profile.

C.Field - function

Human-readable action/result, e.g. locate_marks.

C.Field - input_schema

Versioned input objects, units, allowed ranges and required files.

C.Field - output_schema

Versioned result, quality fields, units, evidence references and error states.

C.Field - resource_target

HSIMC Resource or target class; actual physical instance is bound separately.

C.Field - execution_mode

simulation / physical_reference / physical_delivered / operational.

C.Field - conditions

Environment, tooling, calibration, material and prerequisite conditions.

C.Field - authority_required

Minimum Authority required to discover, read, reserve, configure, execute, stop, accept or administer.

C.Field - effect_identity

Digest or identifier that locks the intended physical effect independently of short-lived credentials.

C.Field - operation_id

Stable identity used for retry/read-back of a physical-effect request.

C.Field - freshness_requirement

Maximum acceptable age for observations used to authorize or plan the action.

C.Field - resource_locking

Reservation, lease, busy/conflict behavior and release rule.

C.Field - safety_boundary

Conditions that must remain local/deterministic and cannot be delegated to a remote model.

C.Field - acceptance

Measurement, tolerances, evidence and human/organizational acceptance step.

C.Field - recovery

Stop, unknown-result, interrupted-network and restart behavior.

C.Field - version

Contract, adapter, algorithm, hardware/BOM, calibration and deployment version references.

C.Field - cost_time

Expected and actual time, material, energy and monetary cost fields.

C.Field - rights

Contribution, reuse, attribution, confidentiality and withdrawal constraints.

C.1 Example - 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.

C.2 Retry and effect rule

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.