PGM-AUA V1.0 AIMs - Basic Knowledge

Go to PGM-AUA V1.0 AI Modules

Function

Ref. Model

1. Function

The Basic Knowledge (PGM‑BKN) AIM is the deliberative core of the A‑User. It receives the PC Prompt, the BKN‑compatible representation of the A‑User’s understanding of the environment and the User produced by the Prompt Creation AIM, reasons about the PC Prompt and produces the Final Response, the deliberated content that the A-User will communicate and do – the text to be uttered, the Action Objects that carry the actions of the face and body that accompany it and, if A-User Control so requests, the Process Actions that carry it out. The Final Response is sent only to A-User Formation.

Unlike the perceptual AIMs, which form a feed‑forward chain, the Basic Knowledge AIM is a reasoner which proceeds by looping. Its information requirements are not known in advance: as it reasons, it discovers what it lacks and requests the missing information opportunistically from its partner Sub-AIMs. It does so through four MCP interaction interfaces, with the Prompt Creation (Context representation), Domain Access (domain knowledge), User State Refinement (the User’s state), and Personality Alignment (the personality‑aligned stance of the A-User) AIMs. Each interface is a single Data Type with two modes: the Request, sent by the Basic Knowledge AIM to the partner, and the Response, sent by the partner to the Basic Knowledge AIM. This traffic is data‑driven rather than scheduled, as appropriate for deliberation; it is internal to deliberation and need not be reported to the A‑User Control AIM.

As a reasoning AIM, Basic Knowledge is governed by the A‑User Control AIM: the A‑User Control AIM proposes and the AIM disposes. A AUC-BKN Request sets a goal and may carry a proposed correction with a Weight indicating its importance to the receiving Basic Knowledge AIM: Basic Knowledge makes its own conclusion. The AUC-BKN Response reports to the A‑User Control AIM only what a manager needs: the deliberation state, the headline conclusion, and any requirements that the Basic Knowledge AIM cannot satisfy through its partners. Routine partner traffic is not reported. Each reported unmet need carries the time at which deliberation began (the triggering of the Prompt Creation AIM’s prompt) so that the A‑User Control AIM, against its own clock, can judge how long the need has gone unmet. In a subsequent AUC-BKN Request, it instructs the Basic Knowledge AIM to abandon that line and conclude.

Process Actions and Action Objects. When the Actions property of the AUC-BKN Request is required or optional, Basic Knowledge produces, as parts of the Final Response, the Process Actions that carry the response out and the Action Objects with the actions of the face and body that accompany the text. It uses the Action context that Prompt Creation has placed in the PC Prompt (the repertoire, the vocabularies, the Rights, the Rules of the M-Instance, the affordances) and may ask Domain Access, through BKN-DAC, whether a Process Action that it is considering can be performed. The Process Actions conform with the grammar of MMM-TEC V2.2 and comply, as best Basic Knowledge can, with the Process Actions, the number of steps, the M-Locations, the Rights and the Wallet limit of the Request; the Action Objects are expressed in a vocabulary that the Request allows and that their Qualifier names. The Final Response, with the Process Actions and the Action Objects it contains, is sent only to A-User Formation: Basic Knowledge sends no part of the Final Response to A-User Control, and no validation stands between Basic Knowledge and A-User Formation. Basic Knowledge does not perform any Process Action. If a Process Action is refused or is not sent, A-User Control sends a further AUC-BKN Request with a Correction that conveys the refusal and its reason; Basic Knowledge decides its own conclusion and reports in the AUC-BKN Response how it treated the Correction. This specification does not specify how Basic Knowledge is prompted or how it generates the Process Actions and the Action Objects.

The Basic Knowledge AIM:

Operates on the PC Prompt produced by the Prompt Creation AIM, the AUC-BKN Request received from the A‑User Control AIM, and the responses received from its four MCP partners: BKN‑PRC Response from the Prompt Creation AIM; BKN‑DAC Response from the Domain Access AIM; BKN‑USR Response from the User State Refinement AIM; and BKN‑PAL Response from the Personality Alignment AIM.
Produces the Final Response which includes the Action Objects and the Process Actions and is sent only to the A‑User Formation AIM; the AUC-BKN Response reported to the A‑User Control AIM and the four MCP requests. These are: BKN‑PRC Request to the Prompt Creation; BKN‑DAC Request to the Domain Access; BKN‑USR Request to the User State Refinement; and BKN‑PAL Request to Personality Alignment AIMs.

A conforming Basic Knowledge implementation shall observe the following behavioural requirements:

Shall pursue the goal stated in the AUC-BKN Request.
May give a proposed correction carried in the AUC-BKN Request a weight proportional to the Weight value provided. The Basic Knowledge AIM decides its own conclusion.
Shall abandon the referenced unmet need and conclude with available information when the AUC-BKN Request carries a relevant abandon instruction.
Shall produce a Final Response when deliberation reaches a conclusion, whether by success, by forced abandonment, or by exhaustion of all partner interactions without resolution. However, no Final Response shall be produced during ongoing deliberation.
Shall emit AUC-BKN Response when deliberation concludes; when an unmet need persists and cannot be satisfied through partners; or when instructed by AUC-BKN Request to abandon a line of deliberation.
May expose partner interaction content in AUC-BKN Response. Routine partner traffic is internal to deliberation and shall not be reported to the A‑User Control AIM.
Shall not acquire information through any channel other than the four normative MCP partner interfaces.
Shall produce Process Actions only when the Actions property of the AUC-BKN Request is required or optional, and shall limit them to the Process Actions, the number of steps, the M-Locations, the Rights and the Wallet limit that it indicates.
Shall express the Process Actions in the syntax of MMM-TEC V2.2 and shall not perform any of them, and shall express the Action Objects in a vocabulary that the Actions property allows.
May use BKN-DAC Requests to verify the feasibility of a Process Action it is considering.
Shall send the whole of the Final Response to A-User Formation and no part of it to A-User Control.

2. Reference Model

Figure 1 depicts the Reference Model of the Basic Knowledge (PGM‑BKN) AIM.

Figure 1 – Reference Model of the Basic Knowledge (PGM‑BKN) AIM

3. Input/Output Data

Table 1 specifies the Input and Output Data of the Basic Knowledge (PGM‑BKN) AIM. Each of the four MCP interface Data Types has two modes: the Request, which is an output of Basic Knowledge, and the Response, which is an input.

Table 1 – Input/Output Data of the Basic Knowledge (PGM‑BKN) AIM

Input	Description
AUC-BKN Request	Goal and, optionally, a weighted proposed correction, an instruction to abandon a referenced unmet need, and the Actions property that asks for Process Actions and sets their limits and names the vocabularies of the Action Objects. The Request is sent by the A-User Control AIM.
PC Prompt	The BKN‑compatible representation of the A‑User’s understanding, from the Prompt Creation AIM.
BKN‑PRC Response	Response of the Prompt Creation AIM to a BKN‑PRC Request: a more complete or different representation of the Context’s understanding, supplied via MCP.
BKN‑DAC Response	Response of the Domain Access AIM to a BKN‑DAC Request: the requested domain knowledge, supplied via MCP.
BKN‑USR Response	Response of the User State Refinement AIM to a BKN‑USR Request: the refined User State, supplied via MCP.
BKN‑PAL Response	Response of the Personality Alignment AIM to a BKN‑PAL Request: the personality‑aligned stance, supplied via MCP.
Output	Description
Final Response	The deliberated content: the text to be uttered, the Action Objects that carry the actions of the face and body that accompany it and, when A-User Control has asked for them, the Process Actions, in the syntax of MMM-TEC V2.2, that carry the response out. It is sent only to A-User Formation.
AUC-BKN Response	Decision report to the A-User Control AIM: deliberation state, headline conclusion, what was produced and how the Request was met, and unmet needs that could not be satisfied through partners.
BKN‑PRC Request	Request from the Basic Knowledge AIM to the Prompt Creation AIM for a more complete or different representation of the A‑User’s understanding, sent via MCP.
BKN‑DAC Request	Request from the Basic Knowledge AIM to the Domain Access AIM for domain knowledge, sent via MCP.
BKN‑USR Request	Request from the Basic Knowledge AIM to the User State Refinement AIM for the User’s state, sent via MCP.
BKN‑PAL Request	Request from the Basic Knowledge AIM to the Personality Alignment AIM for the personality‑aligned stance, sent via MCP.

4. SubAIMs

No SubAIMs.

5. JSON Metadata

https://schemas.mpai.community/PGM1/V1.0/AIMs/BasicKnowledge.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 Basic Knowledge (PGM‑BKN) 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.

Table 2 – Conformance Testing Method for the Basic Knowledge (PGM‑BKN) AIM

Receives	AUC-BKN Request	Shall validate against the AUC-BKN schema, with Mode RQ.
	PC Prompt	Shall validate against PC Prompt schema.
	BKN‑PRC Response	Shall validate against the BKN‑PRC schema, with Mode RS.
	BKN‑DAC Response	Shall validate against the BKN‑DAC schema, with Mode RS.
	BKN‑USR Response	Shall validate against the BKN‑USR schema, with Mode RS.
	BKN‑PAL Response	Shall validate against the BKN‑PAL schema, with Mode RS.
Produces	Final Response	Shall validate against the Final Response schema; its Process Actions shall validate against the Process Actions schema of MMM-TEC V2.2 and conform with its grammar.
	AUC-BKN Response	Shall validate against the AUC-BKN schema, with Mode RS.
	BKN‑PRC Request	Shall validate against the BKN‑PRC schema, with Mode RQ.
	BKN‑DAC Request	Shall validate against the BKN‑DAC schema, with Mode RQ.
	BKN‑USR Request	Shall validate against the BKN‑USR schema, with Mode RQ.
	BKN‑PAL Request	Shall validate against the BKN‑PAL schema, with Mode RQ.

9. Performance Assessment