Function
Ref. Model
I/O Data
SubAIMs
JSON MData
Profiles
Ref. Software
Conformance
Performance
1 Functions
The A‑User Control (PGM‑AUC) AIM serves as the central coordinator for Action execution, AIM orchestration, and system traceability. It governs the lifecycle of the A‑User and orchestrates its interactions with the responsible human, the M‑Instance, and the Processes and Items with which the A‑User interacts.
A‑User Control sends Directive messages to AIMs to implement Instructions within the Rights the A‑User holds and the Rules applicable to the M‑Location, and tracks execution of Directives using Status messages received from A‑User AIMs.
The resulting control flow ensures that the A‑User operates predictably, transparently, and in alignment with human Commands, supporting lifecycle integrity and enabling trust through auditable orchestration.
2 Reference Model
Figure 1 gives the Reference Model of the A‑User Control (PGM‑AUC) AIM.
Figure 1 – Reference Model of the A‑User Control (PGM‑AUC) AIM
The A‑User Control AIM exercises its activity by implementing one of eight Instructions:
- Perception and Environment Capture (PEC): Configure perceptual subsystems to sense the responsible human in the Universe, the User in the M‑Instance, or the contents of the relevant M‑Location.
- Goal and Language Acquisition (GLA): Capture and segment multimodal expressions of the responsible human and/or the User. This corresponds to giving identity and spatial relationship to the objects in the scene and to understanding the User.
- Prompting and Knowledge Query (PKQ): Enable structured contextual representation and semantic grounding of perceptual and state information. The A‑User is now in a position to make sense of what it perceives and interprets.
- Goal and Intent Interpretation (GII): Based upon the results of the previous Instruction, trigger deliberative processing to determine the appropriate communicative behaviour of the A‑User. The A‑User Control is now able to decide the stance it should take.
- Policy, Rights, and Feasibility (PRF): Validate intended behaviour with respect to governance Rules, User Entity State constraints, human commands, and domain feasibility conditions. The A‑User Control knows that the A‑User actions must comply with a variety of constraints.
- Plan Construction and Execution (PCE): Orchestrate execution of the behaviour based on Statuses reported by the AIMs, including speech and actions. The A‑User Control is now able to execute the actions after taking constraints into account.
- Conflict Management and Escalation (CME): Detect unresolved inconsistencies or conflicts and escalate to the responsible human when required. Various impediments may be encountered and modifications to the action decided.
- Avatar Formation and Rendering (AFR): Enable synthesis and rendering of the speaking avatar. The A‑User’s Avatar is formed and can be rendered.
3 Input/Output Data
The A‑User Control (PGM‑AUC) AIM exchanges typed Directive and Status messages with each of the A‑User AIMs it orchestrates. Each AIM receives a typed Directive and returns a typed Status to A‑User Control.
Table 1 gives the Input and Output Data of the A‑User Control (PGM‑AUC) AIM.
Table 1 – Input and Output Data of the A‑User Control (PGM‑AUC) AIM
| Input | Description |
|---|---|
| Human Command | Command from the responsible human in the real world. |
| Process Action Response | From a Process that has received a Process Action Request. |
| CXC Status | Scene‑level context and User presence reported by Context Capture. |
| CXE Status | Spatial feasibility, occlusion, reachability flags reported by Context Enhancement. |
| PRC Status | Prompt readiness, alignment status, semantic goal framing reported by Prompt Creation. |
| BKN Status | Enriched response metadata and traceability reported by Basic Knowledge. |
| DAC Status | Execution feasibility and constraint validation reported by Domain Access. |
| USD Status | Current engagement, affective tone, override flags reported by User State Description. |
| PAL Status | Expressive alignment, persona framing, modulation constraints reported by Personality Alignment. |
| AUF Status | Avatar formation success, avatar state, expressive output status reported by A‑User Formation. |
| Output | Description |
| Action | Action performed by A‑User on the M‑Instance. |
| Process Action Request | Request made by A‑User to an M‑Instance Process. |
| CXC Directive | Instructions for perceptual acquisition sent to Context Capture. |
| CXE Directive | Context Enhancement‑related actions and sequences sent to Context Enhancement. |
| PRC Directive | Prompt generation or refinement instructions sent to Prompt Creation. |
| BKN Directive | Request for knowledge retrieval or response shaping sent to Basic Knowledge. |
| DAC Directive | Request for domain execution sent to Domain Access. |
| USD Directive | Request to modulate User State based on interaction feedback sent to User State Description. |
| PAL Directive | Request for expressive modulation or Personality reconfiguration sent to Personality Alignment. |
| AUF Directive | Request for avatar formation, spatial output, and expressive delivery sent to A‑User Formation. |
| Human Command Status | A‑User Control response to Human Command. |
4 SubAIMs
No SubAIMs.
5 JSON Metadata
https://schemas.mpai.community/PGM1/V1.0/data/AUserControl.json
6 Profiles
No Profiles.
