Function
Ref. Model
I/O Data
SubAIMs
JSON MData
Profiles
Ref. Software
Conformance
Performance
1 Functions
The User State Refinement (PGM‑USR) AIM improves the A‑User’s understanding of the evolving User State. It refines the baseline User State produced by Context Description into an authoritative, up‑to‑date User State (represented by an Entity State) that it passes to Personality Alignment. It refines the Engagement (level and mode) and the Entity State.
User State Refinement operates through one operative interface and one semantic interface:
- Operative Interface — receives an AUC-USR Request from A‑User Control and returns the AUC-USR Response. The Request specifies refinement goals, urgency, override conditions, and the A‑User Control mode (Overseer or Micromanager). The interface is non‑MCP.
- Semantic Interface (MCP) — exchanges the BKN‑USR Request and Response with Basic Knowledge, incorporating deliberation feedback and supplying the refined User State for the next deliberation cycle.
The AIM additionally reads and writes prior User State content through Interaction History (USR Interaction History Response and Request) with Private Storage. The refined User State, represented by an Entity State, is the main output of User State Refinement: it is passed to Personality Alignment and made available to A‑User Formation. The AUC-USR Response reports to A‑User Control the engagement, the override report and the provenance of the refinement.
PGM‑USR:
- Receives the AUC-USR Request from A‑User Control, the baseline User State produced by Context Description, the BKN‑USR Request (deliberation feedback) from Basic Knowledge, and the USR Interaction History Response (prior cadence and state) read from Private Storage.
- Refines the Engagement and the Entity State, and consolidates them with the baseline User State into the refined User State, resolving overrides and recording provenance.
- Produces the refined User State for Personality Alignment, the AUC-USR Response for A‑User Control, the BKN‑USR Response for Basic Knowledge, and the USR Interaction History Request that writes the refined User State and reads prior cadence and state.
2 Reference Model
Figure 1 depicts the Reference Model of the User State Refinement (PGM‑USR) AIM.
the 
Figure 1 – Reference Model of the User State Refinement (PGM‑USR) AIM
3 I/O Data
Table 1 specifies the Input and Output Data of the User State Refinement (PGM‑USR) AIM.
| Input | Description |
|---|---|
| AUC-USR Request | Instructions from the A‑User Control AIM specifying refinement goals, urgency, override conditions, and control mode. |
| User State | Baseline User State produced by the Context Description AIM, to be refined. |
| BKN‑USR Request | Deliberation feedback from the Basic Knowledge AIM via MCP. Defined within the BKN‑USR schema. |
| USR Interaction History Response | Prior User State content read from Private Storage (cadence history, prior state). |
| Output | Description |
| User State | The refined, authoritative User State, represented by an Entity State: Engagement, Entity State and provenance. Passed to the Personality Alignment AIM and made available to the A‑User Formation AIM . |
| AUC-USR Response | Report to A‑User Control: current engagement, override report and provenance of the refinement. |
| BKN‑USR Response | Refined User State supplied to the Basic Knowledge AIM via MCP for the next deliberation cycle. Defined within the BKN‑USR schema. |
| USR Interaction History Request | Request to Private Storage to write the refined User State and read prior cadence and state. |
4 SubAIMs (informative)
This section is informative. The decomposition into SubAIMs described below illustrates one conformant architecture for producing the normative outputs of PGM‑USR. Implementations may adopt alternative internal structures provided they satisfy the conformance requirements of Section 8.
4.1 Reference Model
Figure 2 depicts the Reference Model of the User State Refinement (PGM‑USR) Composite AIM.
Figure 2 – Reference Model of the User State Refinement (PGM‑USR) Composite AIM
4.2 Operation
The PGM-USR operation includes the following Sub-AIMs:
- Engagement Recalibration — computes engagement level and mode from the baseline User State, the cadence history (USR Interaction History Response) and the AUC-USR Request, and requests the cadence history from Private Storage.
- Entity State Refinement — refines the Entity State, incorporating the deliberation feedback received from the Basic Knowledge AIM (BKN‑USR Request). It is the only Sub-AIM that returns the BKN‑USR Response, carrying the Refined Entity State, to the Basic Knowledge AIM for the next deliberation cycle.
- User State Synthesis — consolidates the baseline User State, the Engagement metrics and the Refined Entity State into the authoritative refined User State and the AUC-USR Response, resolving overrides and recording provenance. It reads prior state through the USR Interaction History Response and issues the USR Interaction History Request that writes the refined User State.
4.3 Functions of Sub-AIMs
Table 2 specifies the functions of the User State Refinement (PGM‑USR) SubAIMs.
| SubAIM | Function |
|---|---|
| Engagement Recalibration | Computes engagement level and mode from the baseline User State, the cadence history, and the AUC-USR Request. |
| Entity State Refinement | Refines the Entity State, incorporating the deliberation feedback from the Basic Knowledge AIM (BKN‑USR Request) and returning the Refined Entity State (BKN‑USR Response) for the next cycle. |
| User State Synthesis | Consolidates the baseline User State, the Engagement metrics and the Refined Entity State into the authoritative refined User State and the AUC-USR Response, with override resolution and provenance; issues the Interaction History Request. |
4.4 I/O Data of SubAIMs
Table 3 gives the Input and Output Data of the User State Refinement (PGM‑USR) Sub-AIMs.
| SubAIM | Input | Output |
|---|---|---|
| Engagement Recalibration | AUC-USR Request User State USR Interaction History Response |
Engagement metrics USR Interaction History Request |
| Entity State Refinement | AUC-USR Request User State Engagement metrics BKN‑USR Request |
Refined Entity State BKN‑USR Response |
| User State Synthesis | AUC-USR Request User State Engagement metrics Refined Entity State USR Interaction History Response |
User State AUC-USR Response USR Interaction History Request |
4.5 AIMs and JSON Metadata
Table 4 provides the links to the AIM specifications and JSON schemas. AIM1 indicates the Composite AIM and AIM2 its SubAIMs.
| AIM1 | AIM2 | Name | JSON |
|---|---|---|---|
| PGM‑USR | User State Refinement | X | |
| PGM‑ENG | Engagement Recalibration | X | |
| PGM‑ESR | Entity State Refinement | X | |
| PGM‑USY | User State Synthesis | X |
5 JSON Metadata
https://schemas.mpai.community/PGM1/V1.0/AIMs/UserStateRefinement.json
6 Profiles
No Profiles.
7 Reference Software
Not part of this specification.
8 Conformance Testing
Table 5 provides the Conformance Testing Method for the User State Refinement (PGM‑USR) AIM. Conformance Testing of the individual SubAIMs is given by the individual AIM specifications.
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 AUC-USR Request schema. |
| User State | Shall validate against User State schema. | |
| BKN‑USR Request | Shall validate against the BKN‑USR schema, with Mode RQ. | |
| USR Interaction History Response | Shall validate against USR Interaction History schema. | |
| Produces | User State | Shall validate against User State schema. |
| AUC-USR Response | Shall validate against AUC-USR Response schema. | |
| BKN‑USR Response | Shall validate against the BKN‑USR schema, with Mode RS. | |
| USR Interaction History Request | Shall validate against USR Interaction History schema. |
9 Performance Assessment
Not part of this specification.
