Product artifact roles¶
Execution trust policy and robot description are registered public roles.
Existing v1 roles retain their schemas; native scenario, runtime, observation
and result roles additionally admit explicit v2 versions in the same catalog. They use the usual offline
validate_document, validate_role, schema_path, schema_registry, and CLI
validate/describe interfaces; no separate CLI writer is required.
Execution trust policy¶
Role execution_trust_policy selects execution-trust-policy.v1. Its fields
match infrastructure’s policy/execution.rego,
config/authorization/trust-policy.example.json, and the trust_policy input in
test/policy/execution/valid.json:
Field |
Contract |
|---|---|
|
Common contract identifier. |
|
Integer from 1 through 1800, inclusive. |
|
|
|
|
|
The existing permit identity kinds: |
|
Common lowercase, unprefixed, 64-character SHA-256 of the target identity evidence bytes. |
|
Nonempty, unique subset of |
Unknown fields and exact duplicate principal/target entries are rejected.
Public validate_document, validate_role, and CLI validation also reject
repeated (role, identity) pairs with different issuers. Infrastructure selects
exactly one issuer by that pair; listing both old and new issuers during a
migration would prevent that principal from executing. This key uniqueness is
a semantic check: JSON Schema’s uniqueItems only detects whole-object duplicates.
The diagnostic is semantic.validation_failed at $.principals.
Multiple operators, approvers, and target records are allowed; distinct records
may authorize different identities or environments for a target. An identity may
appear once in each role, with the same or different issuers. Role/issuer
and target-kind/environment constraints reference the existing verification and
permit schemas, while shared identifiers and digests belong to common.v1.
The schema requires both roles; public validation ensures each role/identity pair
selects one issuer. Infrastructure’s authorization
step remains responsible for two distinct verified signers, current time,
permit lifetime, target and environment matching, and the observed runtime,
scenario, and subject digests. A valid policy alone authorizes no execution.
There is no policy self-digest, hardware scope, permit, or signature bundle in
this document. The permit/verification’s trust_policy_sha256 binds the whole
policy file’s exact bytes. Do not substitute a canonicalized JSON digest.
The infrastructure example is retained as a shape-compatibility fixture. Its repeated example target hash is not proof of a physical identity. The separate consumer example uses the actual SHA-256 of its checked-in synthetic identity evidence file. Deployment must replace example identities with reviewed, measured identities.
Robot description¶
Role robot_description selects robot-description.v1. It describes an authored
source artifact and a ready-to-load description, rather than embedding or
validating URDF/SDF contents. The
product root is the directory containing sim/ and ros/; a manifest normally
lives at sim/robot-description.json. All path fields are relative to that
product root, not to the manifest or description package.
Field |
Contract |
|---|---|
|
Common identifier, independent of robot hardware or product family. |
|
Exactly one of |
|
|
|
|
|
|
|
Positive finite total robot mass in kilograms. |
|
Three finite numbers |
|
|
|
|
Paths use forward-slash-separated ASCII letters, digits, underscores, hyphens,
and dots. Empty, absolute, drive-qualified, URI, dot/parent-segment, and
backslash paths are invalid. source.uri is an absolute URI, not a path or a
relative URI reference; file:, HTTPS, and other artifact URI schemes are
permitted. Validation never fetches a URI or reads a referenced file. Consumers
resolve paths within their chosen product root, enforce containment after
symlink resolution, and compare SHA-256 against unmodified file bytes.
The schema checks structure, scalar types, and finite geometry values. It does
not parse XML, execute CAD/Xacro, verify meshes, recompute mass/inertia, or
establish safe spawning. A failed or not_checked producer check remains a
valid record, not an approval to run. Consumer admission must establish its own
requirements. No extra semantic validator is needed for this artifact boundary.
The checked-in product example contains
a neutral 0.1 m cube, CAD source, a metre-scaled OBJ, and ready URDF/SDF manifests.
Tests check its file hashes, XML formats, package name, and URDF mass/inertia.
The source, package, and inertia_check subfields and pose representation
above make SPEC §2.5’s artifact interface concrete; there is no existing CAD
robot-manifest producer being silently reinterpreted.
Workload bindings¶
An optional workload.robot_description_sha256 in an acceptance scenario pins
the exact retained robot-description.json bytes. Each runtime manifest must
then report the same digest in workload.robot_description.sha256. Both none
and inference workloads may carry this optional binding. Existing documents
without it keep their behavior; a runtime may also report an unpinned description.
validate_robot_description_binding(scenario, runtime) compares schema-validated
documents and reports workload.robot_description_mismatch for a missing or
different runtime digest. Consumers can call it before starting observation.
Qualification additionally requires each reported description digest to resolve
to a retained other_evidence artifact. Register it with
--artifact other_evidence:robot-description.json=PATH. This preserves the
published qualification statement’s artifact-kind vocabulary. The file loader
hashes the original bytes, so changing whitespace changes the binding too.
The binding identifies the description manifest, not the URDF/SDF XML, CAD source,
or a reserialized JSON value. Validate the robot_description role separately
when admitting the manifest; the qualification raw-artifact boundary does not
parse its contents. Referenced XML and mesh files still require the product
admission checks above. Infrastructure spawning remains a later integration step.
Native acceptance documents¶
The canonical defaults for acceptance_scenario, runtime_manifest, acceptance_observation and acceptance_result remain v1. The same roles also support acceptance-scenario.v2, runtime-manifest.v2, acceptance-observation.v2 and acceptance-result.v2 through explicit version selection.
A native runtime manifest contains pre-run configuration and actually loaded bindings. Completed observations are a separate retained document. Native model bindings connect the declared model, runtime binding, actual bytes consumed by the producer and retained evidence; they do not mandate a robot-description format. Results preserve original run/source/evidence identities separately from assessment method, environment and time.
Profile-defined observation names have measured, not_applicable, unobserved or invalid states. Inapplicability preserves the declared reason. Required missing or invalid observations produce incomplete coverage; zero remains a valid measured value. A captured measurement window carries its clock and integer bounds. The assessment uses that same clock; UTC provenance is not a clock conversion.
The native archive example shows the bounded software/simulation path. Physical native qualification and independent archive re-evaluation are outside that path.