(Tentative)

Definition Functional Requirements Syntax Semantics

Definition

Human Command (PGM-HCM)

  • Is issued by the human responsible for the A-User to influence the behaviour, state, or decision-making of the A-User.
  • Represents a structured, authenticated instruction that may trigger action execution, override logic, escalation, or AIM reconfiguration.
  • Includes command type, target scope, intent metadata, and traceable authentication.

Functional Requirements

Function Description
Command Type Specifies the nature of the human intervention (e.g., override, confirm, escalate).
Target Scope Identifies the AIM, process, or behaviour being addressed.
Command Intent Describes the semantic purpose or goal of the command.
Authentication Token Validates the source and authority of the command.
Urgency Level Indicates priority or time sensitivity.
Trace Metadata Provides provenance for auditability and control lineage.

Syntax

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

Semantics

Label Description
Header Human Command Header
– Standard-HCM The characters “PGM-HCM-V” indicating schema family and type
– Version Major version – 1 or 2 characters
– Dot-separator The character “.” separating version components
– Subversion Minor version – 1 or 2 characters
CommandID Unique identifier for this Human Command instance
CommandType Nature of the command (override, confirm, escalate, pause, resume, terminate)
TargetScope Target AIM, process, or behavior
– TargetAIM Name of the AIM being addressed
– TargetAction Specific action or behavior being influenced
– TargetEntityID Entity involved in the command
CommandIntent Semantic purpose or goal of the command
AuthenticationToken Token or credential validating the command source
UrgencyLevel Priority or time sensitivity (low, normal, high, critical)
Trace Provenance metadata for Human Command
– IssuerID Identifier of the human or system issuing the command
– Timestamp Time of command issuance
DescrMetadata Descriptive Metadata