| Function | Ref. Model | I/O Data | SubAIMs | JSON MData | Profiles | Ref. Software | Conformance | Performance |
1. Function
The Entity State Refinement (PGM‑ESR) AIM is a Sub-AIM of User State Refinement (PGM‑USR). It refines the Entity State of the User, incorporating the deliberation feedback received from the Basic Knowledge AIM.
PGM‑ESR:
- Receives the AUC-USR Request, the baseline User State, the Engagement Metrics and the BKN‑USR Request (deliberation feedback) from Basic Knowledge via MCP.
- Refines the Entity State of the User into the Refined Entity State.
- Returns the Refined Entity State to the Basic Knowledge AIM in the BKN‑USR Response, for the next deliberation cycle.
PGM‑ESR is the only Sub-AIM of User State Refinement (PGM‑USR) that exchanges the BKN‑USR Request and Response with the Basic Knowledge AIM.
2. Reference Model
Figure 1 depicts the Reference Model of the Entity State Refinement (PGM‑ESR) AIM.
Figure 1 – The Entity State Refinement (PGM‑ESR) AIM
3. Input/Output Data
Table 1 specifies the Input and Output Data of the Entity State Refinement (PGM‑ESR) AIM.
Table 1 – I/O Data of the Entity State Refinement (PGM‑ESR) AIM
| Input | Description |
|---|---|
| AUC-USR Request | Instructions from A‑User Control specifying refinement goals, urgency, override conditions, and control mode. |
| User State | Baseline User State produced by the Context Description AIM, to be refined. |
| Engagement Metrics | Engagement level and mode of the User. |
| BKN‑USR Request | Deliberation feedback from Basic Knowledge via MCP. |
| Output | Description |
| Refined Entity State | The refined Entity State of the User. |
| BKN‑USR Response | Response to a BKN‑USR Request: the Refined Entity State supplied to Basic Knowledge via MCP for the next deliberation cycle. |
4. Sub-AIMs
No Sub-AIMs.
5. JSON Metadata
https://schemas.mpai.community/PGM1/V1.0/AIMs/EntityStateRefinement.json
6. Profiles
No Profiles.
7. Reference Software
Not part of this specification.
8. Conformance Testing
Table 2 provides the Conformance Testing Method for the Entity State Refinement (PGM‑ESR) AIM.
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, if present, and conform with the Qualifier, if present.
| Receives | AUC-USR Request | Shall validate against the AUC-USR Request schema. |
| User State | Shall validate against the User State schema. | |
| Engagement Metrics | Shall validate against the Engagement Metrics schema. | |
| BKN‑USR Request | Shall validate against the BKN‑USR schema, with Mode RQ. | |
| Produces | Refined Entity State | Shall validate against the Refined Entity State schema. |
| BKN‑USR Response | Shall validate against the BKN‑USR schema, with Mode RS. |
9. Performance Assessment
Not part of this specification.
