(Tentative)
| Definition | Functional Requirements | Syntax | Semantics |
Definition
Human Command Status (PGM-HCS)
- Is produced by A-User Control (PGM-AUC) after processing a Human Command.
- Represents the outcome of the command execution, including acceptance, rejection, escalation, and resulting lifecycle or AIM changes.
- Includes execution result, affected targets, override report, and trace metadata.
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 behavior 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/HumanCommandStatus.json
Semantics
| Label | Description |
|---|---|
| Header | Human Command Status Header |
| – Standard-HCS | The characters “PGM-HCS-V” indicating schema family and type |
| – Version | Major and minor version components |
| StatusID | Unique identifier for this Human Command Status instance |
| ExecutionResult | Outcome of command processing (accepted, rejected, escalated, ignored) |
| LifecycleTransition | Lifecycle change triggered by the command (none, paused, resumed, terminated) |
| AIMImpact | Resulting changes to AIMs |
| – Activated | AIMs activated by the command |
| – Suspended | AIMs suspended by the command |
| – Reconfigured | AIMs reconfigured by the command |
| OverrideReport | Whether override logic was applied |
| – OverrideApplied | Boolean flag indicating override usage |
| – OverrideType | Type of override applied |
| Trace | Provenance metadata for Human Command Status |
| – CommandID | Reference to the originating Human Command |
| – Timestamp | Time of status emission |
