Go to PGM-AUA V1.0 AI Modules

Function
Ref. Model
I/O Data
SubAIMs
JSON MData
Profiles
Ref. Software
Conformance
Performance

1 Functions

The Personality Alignment (PGM‑PAL) AIM decides the stance the A‑User should adopt and produces the A‑User State that A‑User Formation renders. It is a reasoning AIM: knowing how the User feels and the context of the interaction, it judges what stance is appropriate for the A‑User, which is not the same as mirroring the User. If the User laughs, the A‑User laughing may be appropriate in a pub but improper in a church; Personality Alignment makes that judgement.

To make it, Personality Alignment needs two things only: the User’s internal state and the context. It receives the User State (an estimate of the User’s internal state) from User State Refinement as a one‑way input, sent autonomously whenever User State Refinement has reached a conclusion; Personality Alignment does not query for it. It obtains context as needed by consulting A‑User Storage, and may draw further context indirectly through its deliberation with Basic Knowledge. Personality Alignment is the sole producer of the A‑User State; User State Refinement reports only the User State and has no part in the A‑User State.

As a reasoning AIM, Personality Alignment is governed by A‑User Control under the principle that A‑User Control proposes and the AIM disposes. A PAL Directive sets a binding goal and may carry a proposed correction together with a Weight indicating how much importance Personality Alignment should give the proposal; Personality Alignment decides its own conclusion and reports, in the PAL Status, the stance it adopted and how it treated the proposal. Personality Alignment also participates in Basic Knowledge’s deliberation through the MCP exchange PALToBKN / BKNToPAL.

The PGM‑PAL AIM:

Receives PAL Directive Goal and, optionally, a weighted proposed correction from A‑User Control.
User State Estimate of the User’s internal state, sent one‑way by User State Refinement.
BKNToPAL Deliberation exchange from Basic Knowledge via MCP. Defined within the BKN-PAL Interaction schema.
Produces A‑User State The Entity State the A‑User should adopt, sent to A‑User Formation. Personality Alignment is its sole producer.
PAL Status Decision report to A‑User Control: the adopted stance and the treatment of any proposed correction.
PALToBKN Personality‑aligned contribution supplied to Basic Knowledge via MCP. Defined within the BKN-PAL Interaction schema.

Personality Alignment also consults A‑User Storage on an as‑needed basis to obtain context, performing its own reads under the access rights A‑User Control establishes and A‑User Storage enforces.

2 Reference Model

Figure 1 depicts the Reference Model of the Personality Alignment (PGM‑PAL) AIM.

[Figure 1 image to be inserted]

Figure 1 – Reference Model of the Personality Alignment (PGM‑PAL) AIM

3 I/O Data

Table 1 specifies the Input and Output Data of the Personality Alignment (PGM‑PAL) AIM.

Table 1 – Input and Output Data of the Personality Alignment (PGM‑PAL) AIM

Input Description
PAL Directive Goal and, optionally, a weighted proposed correction from A‑User Control.
User State Estimate of the User’s internal state, sent one‑way by User State Refinement.
BKNToPAL Deliberation exchange from Basic Knowledge via MCP. Defined within the BKN-PAL Interaction schema.
Output Description
A‑User State The Entity State the A‑User should adopt, sent to A‑User Formation.
PAL Status Decision report to A‑User Control: the adopted stance and the treatment of any proposed correction.
PALToBKN Personality‑aligned contribution supplied to Basic Knowledge via MCP. Defined within the BKN-PAL Interaction schema.

4 SubAIMs (informative)

This section is informative. The decomposition into SubAIMs described below illustrates one conformant architecture for producing the normative outputs of PGM‑PAL. Implementations may adopt alternative internal structures provided they satisfy the conformance requirements of Section 8.

4.1 Functions of SubAIMs

Figure 2 depicts the Reference Model of the Personality Alignment (PGM‑PAL) Composite AIM.

[Figure 2 image to be inserted]

Figure 2 – Reference Model of the Personality Alignment (PGM‑PAL) Composite AIM

4.2 Operation

The PAL operation includes the following SubAIMs:

  1. Context Resolver
    • Obtains the interaction context, consulting A‑User Storage as needed, and reconciles it with the User State so the stance decision is context‑aware.
  2. Stance Selector
    • Selects the personality stance appropriate to the User State and context, applying role and locale constraints.
  3. A‑User State Composer
    • Composes the A‑User State (the Entity State the A‑User should adopt) from the selected stance, incorporating any proposed correction according to its Weight.
  4. Deliberation Liaison
    • Conducts the MCP exchange with Basic Knowledge, supplying PALToBKN and incorporating BKNToPAL.

4.3 Functions of SubAIMs

Table 2 specifies the functions of the Personality Alignment (PGM‑PAL) SubAIMs.

Table 2 – Functions of the Personality Alignment (PGM‑PAL) SubAIMs

SubAIM Function
Context Resolver Obtains and reconciles the interaction context with the User State, consulting A‑User Storage as needed.
Stance Selector Selects the personality stance appropriate to the User State and context.
A‑User State Composer Composes the A‑User State, incorporating any proposed correction according to its Weight.
Deliberation Liaison Conducts the MCP exchange with Basic Knowledge.

4.4 I/O Data of SubAIMs

Table 3 gives the Input and Output Data of the Personality Alignment (PGM‑PAL) SubAIMs.

Table 3 – Input and Output Data of the Personality Alignment (PGM‑PAL) SubAIMs

SubAIM Input Output
Context Resolver User State
Context (from A‑User Storage)
Resolved Context
Stance Selector User State
Resolved Context
PAL Directive
Selected Stance
A‑User State Composer Selected Stance
PAL Directive (proposed correction, Weight)
A‑User State
Deliberation Liaison Selected Stance
BKNToPAL
PALToBKN

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.

Table 4 – AIMs and JSON Metadata of the Personality Alignment (PGM‑PAL)

AIM1 AIM2 Name JSON
PGM‑PAL Personality Alignment X
PGM‑CXR Context Resolver X
PGM‑STS Stance Selector X
PGM‑ASC A‑User State Composer X
PGM‑DLL Deliberation Liaison X

5 JSON Metadata

https://schemas.mpai.community/PGM1/V1.0/AIMs/PersonalityAlignment.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 Personality Alignment (PGM‑PAL) 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.

Table 5 – Conformance Testing Method for the Personality Alignment (PGM‑PAL) AIM

Receives PAL Directive Shall validate against PAL Directive schema.
User State Shall validate against User State schema.
BKNToPAL Shall validate against BKN-PAL Interaction schema.
Produces A‑User State Shall validate against A‑User State schema.
PAL Status Shall validate against PAL Status schema.
PALToBKN Shall validate against BKN-PAL Interaction schema.

9 Performance Assessment

Not part of this specification.

Go to PGM-AUA V1.0 AI Modules