Go to PGM-AUA V1.0 Data Types

Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment

Definition

Human Command (PGM-HCM): The Data Type with which the human responsible for the A-User influences its behaviour, state or decision-making, and with which A-User Control reports the outcome. It has two modes, told apart by Mode: Request (RQ), the Human Command, an authenticated instruction, structured or expressed with audio, speech, text or visual media, that may trigger the execution of an action, override logic, escalation or the reconfiguration of an AIM; and Response (RS), the Human Command Status, produced by A-User Control after processing a Human Command, that reports the outcome (accepted, rejected, escalated or ignored), the lifecycle transition, the AIMs affected and the override report. A Response carries the identifier of the Request it answers. The Request reaches A-User Control from the User Agent of the A-User Module through the Controller; the Response goes back the same way.

Functional Requirements

  1. Header: The Data shall have Header “PGM-HCM-V1.0” and Mode equal to RQ for a Request and to RS for a Response; the properties that belong to the other mode shall not be present.
  2. Identification: The Data shall carry the identifiers of the M‑Instance, of the U‑Environment and of the session, and a unique identifier and a time (HumanCommandID, HumanCommandTime).
  3. Correlation: A Response shall carry the identifier (RequestID) of the Request that it answers.
  4. Request: A Request (the Human Command) shall state the CommandType and may carry the TargetScope, the CommandIntent, the Content (the command expressed with audio, speech, text or visual media), the AuthenticationToken, the UrgencyLevel and the Trace of its issuer.
  5. Response: A Response (the Human Command Status) shall state the ExecutionResult, shall be produced for every Request when A-User Control has decided the outcome (not when the Goal has been reached) and may carry the LifecycleTransition, the AIMs affected (AIMImpact) and the OverrideReport; it carries the identifier of the Request it answers.
  6. Metadata: The Data shall include DataXMData and may include DescrMetadata.

Syntax

https://schemas.mpai.community/PGM1/V1.0/data/HumanCommand.json

Semantics

Table 1 gives the properties common to the two modes, Table 2 those of the Request and Table 3 those of the Response.

Table 1 – Properties common to the Request and the Response of Human Command

Label Description
Header Header of the Data Type, with the version. (required)
Mode RQ for a Request, RS for a Response. One of: RQ, RS. (required)
MInstance Identifier of the M-Instance. (required)
UEnvironment Identifier of the U-Environment. (required)
SessionID Identifier of the A-User session. (required)
HumanCommandID Identifier of this Request or Response. (required)
HumanCommandTime Time at which the Data was produced. (required)
DataXMData Data Exchange Metadata of MPAI-PTF: provenance, authorisation, security and confidence of the Data.
DescrMetadata Descriptive metadata (plain text, at most 2048 characters).

Table 2 – Properties of the Request (Mode RQ)

Label Description
CommandType The nature of the human intervention. One of: override, confirm, escalate, pause, resume, terminate, instruct. instruct: the human gives the A-User a Goal, expressed in the Content (for example, “go and open the doors”).
TargetScope The AIM, process or behaviour to which the command applies.
– TargetAIM Name of the AIM addressed.
– TargetAction Specific action or behaviour influenced.
– TargetEntityID Entity involved in the command.
CommandIntent The semantic purpose or goal of the command, if already known to the sender. A command in free speech carries it in the Content and may leave this property absent.
Content The command as expressed by the human with one or more media, captured by the Units of the User Agent and passed through the Controller. The same objects reach Context Description. At least one of the following shall be present.
– AudioObject Audio of the human, as captured by the Units of the User Agent (Basic Audio Object, OSD), when the User Agent has not recognised it as speech.
– SpeechObject Speech of the human (Basic Speech Object, OSD), when the User Agent has recognised that the audio it captured is speech.
– TextObject Text typed or otherwise provided by the human (Basic Text Object, OSD).
– VisualObject Visual expression of the human, e.g., a gesture (Basic Visual Object, OSD).
AuthenticationToken Token or credential that validates the source and the authority of the command.
UrgencyLevel Priority or time sensitivity. One of: low, normal, high, critical.
Trace Provenance of the command, for auditability.
– IssuerID Identifier of the human or system that issues the command.
– Timestamp Timestamp.

Table 3 – Properties of the Response (Mode RS)

Label Description
RequestID ID of the Request this Response answers.
ExecutionResult Outcome of the processing of the command, produced when A-User Control has decided it. One of: accepted, rejected, escalated, ignored.
LifecycleTransition Lifecycle change triggered by the command. One of: none, paused, resumed, terminated.
AIMImpact AIMs activated, suspended or reconfigured by the command.
– Activated Activated.
– Suspended Suspended.
– Reconfigured Reconfigured.
OverrideReport Whether override logic was applied and of which type.
– OverrideApplied Override Applied.
– OverrideType Override Type.

Conformance Testing

Data conforms with Human Command if it validates against the schema of Section 3 and, if the Mode is RQ, contains the properties required for a Request and none of those of a Response, and vice versa. If a schema contains references to other schemas, conformance of data for the primary schema implies that any data referencing a secondary schema shall also validate against the relevant schema.

Performance Assessment

Not part of this specification.

Go to PGM-AUA V1.0 Data Types