Function
Ref. Model
I/O Data
SubAIMs
JSON MData
Profiles
Ref. Software
Conformance
Performance
1 Functions
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 Prompt Creation, reasons over it, and produces the Final Response, the deliberated content the A‑User will communicate.
Unlike the perceptual AIMs, which form a feed‑forward chain, Basic Knowledge is a reasoner and reasons by looping. Its information needs are not known in advance: as it reasons it discovers what it lacks and requests it, opportunistically, from its partners. It does so through four MCP interaction interfaces, with Prompt Creation (more or different representation), Domain Access (domain knowledge), User State Refinement (the User’s state), and Personality Alignment (the personality‑aligned stance). Each interface is a single interaction Data Type carrying both directions, BKNToX and XToBKN. This traffic is data‑driven rather than scheduled, which is the proper shape for deliberation; it is internal to the deliberation and is not reported to A‑User Control.
As a reasoning AIM, Basic Knowledge is governed by A‑User Control under the principle that A‑User Control proposes and the AIM disposes. A BKN Directive sets a binding goal and may carry a proposed correction with a Weight indicating how much importance Basic Knowledge should give it; Basic Knowledge decides its own conclusion. The BKN Status reports to A‑User Control only what a manager needs: the deliberation state, the headline conclusion, and any need Basic Knowledge 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 Prompt Creation’s prompt) so that A‑User Control, against its own clock, can judge how long the need has gone unmet and, in a subsequent BKN Directive, instruct Basic Knowledge to abandon that line and conclude with what it has.
The PGM‑BKN AIM:
| Receives | BKN Directive | Goal and, optionally, a weighted proposed correction or an instruction to abandon a referenced unmet need, from A‑User Control. |
| PC‑Prompt | The BKN‑compatible representation of the A‑User’s understanding, from Prompt Creation. | |
| Exchanges | BKN-PRC | BKN-PRC Request/ BKN-PRC Response exchange with Prompt Creation (MCP). |
| BKN-DAC | BKN-DAC Request/ BKN-DACResponse exchange with Domain Access (MCP). | |
| BKN-USR | BKN-USR Request/ BKN-USR Response exchange with User State Refinement (MCP). | |
| BKN-PAL | BKN-PAL Request/ BKN-PAL Response exchange with Personality Alignment (MCP). | |
| Produces | Final Response | The deliberated content, a Text Object, sent to A‑User Formation to be rendered and to A‑User Control for information. |
| BKN Status | Decision report to A‑User Control: deliberation state, headline conclusion, and unmet needs that could not be satisfied through partners. |
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 I/O Data
Table 1 specifies the Input and Output Data of the Basic Knowledge (PGM‑BKN) AIM. The four MCP interaction Data Types each carry both directions (BKNToX and XToBKN) and so appear once.
| Input | Description |
|---|---|
| BKN Directive | Goal and, optionally, a weighted proposed correction or an instruction to abandon a referenced unmet need, from A‑User Control. |
| PC‑Prompt | The BKN‑compatible representation of the A‑User’s understanding, from Prompt Creation. |
| BKN-PRC Response | PRCToBKN exchange with Prompt Creation via MCP. |
| BKN-DAC Response | DACToBKN exchange with Domain Access via MCP. |
| BKN-USR Response | USRToBKN exchange with User State Refinement via MCP. |
| BKN-PAL Response | PALToBKN exchange with Personality Alignment via MCP. |
| Output | Description |
| BKN Status | Decision report to A‑User Control: deliberation state, headline conclusion, and unmet needs that could not be satisfied through partners. |
| Final Response | The deliberated content, a Text Object, sent to A‑User Formation to be rendered and to A‑User Control for information. |
| BKN-PRC Request | BKNToPRC exchange with Prompt Creation via MCP. |
| BKN-DAC Request | BKNToDAC exchange with Domain Access via MCP. |
| BKN-USR Request | BKNToUSR exchange with User State Refinement via MCP. |
| BKN-PAL Request | BKNToPAL exchange with Personality Alignment 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.
| Receives | BKN Directive | Shall validate against BKN Directive schema. |
| PC‑Prompt | Shall validate against PC-Prompt schema. | |
| BKN-PRC Response | Shall validate against BKN-PRC Interaction schema. | |
| BKN-DAC Response | Shall validate against BKN-DAC Interaction schema. | |
| BKN-USR Response | Shall validate against BKN-USR Interaction schema. | |
| BKN-PAL Response | Shall validate against BKN-PAL Interaction schema. | |
| Produces | Final Response | Shall validate against Text Object schema. |
| BKN Status | Shall validate against BKN Status schema. | |
| BKN-PRC Request | Shall validate against BKN-PRC Interaction schema. | |
| BKN-DAC Request | Shall validate against BKN-DAC Interaction schema. | |
| BKN-USR Request | Shall validate against BKN-USR Interaction schema. | |
| BKN-PAL Request | Shall validate against BKN-PAL Interaction schema. | |
9 Performance Assessment
Not part of this specification.
