| Function | Ref. Model | I/O Data | SubAIMs | JSON MData | Profiles | Ref. Software | Conformance | Performance |
1. Function
The Prompt Token Analysis (PGM‑PTA) AIM derives the Meaning, expressed as Text Descriptors (TXD), from the Context Descriptors produced by Context Description. The Context Descriptors carry the Text Object, if any.
PGM‑PTA:
- Receives the Context Descriptors, the AUC-PRC Request from A‑User Control and the PRC Interaction History Response resulting from queries made to Private Storage.
- Parses the Text Object carried by the Context Descriptors and produces the Meaning, establishing what was said and how it was structured.
- Queries Private Storage via a PRC Interaction History Request when past interaction context may inform tokenisation and entity recognition.
- Reports the outcome of its processing with an AUC-PRC Response.
PGM‑PTA does not infer intent, resolve referents, or produce goal or expressive configurations. Interpretation is left to the downstream Sub-AIMs of Prompt Creation.
2. Reference Model
Figure 1 depicts the Reference Model of the Prompt Token Analysis (PGM‑PTA) AIM.
Figure 1 – The Prompt Token Analysis (PGM‑PTA) AIM
3. Input/Output Data
Table 1 specifies the Input and Output Data of the Prompt Token Analysis (PGM‑PTA) AIM.
Table 1 – I/O Data of the Prompt Token Analysis (PGM‑PTA) AIM
| Input | Description |
|---|---|
| Context Descriptors | Structured descriptors of the current interaction context produced by Context Description, providing domain and situational framing for tokenisation and entity recognition. |
| AUC-PRC Request | Request from A‑User Control specifying scope, depth, and policy constraints for prompt construction. |
| PRC Interaction History Response | Interaction History response from Private Storage providing relevant past interaction context to inform tokenisation and named entity recognition. |
| Output | Description |
| Text Descriptors | The Meaning, expressed as Text Descriptors (TXD), resulting from linguistic analysis of the Text Object carried by the Context Descriptors. |
| AUC-PRC Response | Response reporting the processing outcome of the AIM. |
| PRC Interaction History Request | Request for Interaction History issued to Private Storage. |
4. Sub-AIMs
No Sub-AIMs.
5. JSON Metadata
https://schemas.mpai.community/PGM1/V1.0/AIMs/PromptTokenAnalysis.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 Prompt Token Analysis (PGM‑PTA) 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 | Context Descriptors | Shall validate against the Context Descriptors schema. |
| AUC-PRC Request | Shall validate against the AUC-PRC Request schema. | |
| PRC Interaction History Response | Shall validate against the PRC Interaction History schema. | |
| Produces | Text Descriptors | Shall validate against the Text Descriptors schema. |
| AUC-PRC Response | Shall validate against the AUC-PRC Response schema. | |
| PRC Interaction History Request | Shall validate against the PRC Interaction History schema. |
9. Performance Assessment
Not part of this specification.
