| Function | Ref. Model | I/O Data | SubAIMs | JSON MData | Profiles | Ref. Software | Conformance | Performance |
1. Function
The Domain Access (PGM‑DAC) AIM provides authoritative domain‑level semantics to two distinct classes of consumers within the A‑User Architecture: Context Capture, which requires situational, single‑shot semantic grounding during perceptual processing; and the deliberative AIMs (Basic Knowledge, Prompt Creation, User State Refinement, and Personality Alignment), which require goal‑directed, multi‑turn semantic support during reasoning.
These two uses are logically distinct. Capture‑level domain access is situational and not goal‑directed. Reasoning‑level domain access is goal‑directed and deliberative. Domain Access serves both without performing perception or reasoning itself.
Domain Access:
- Operates on DAC Directive instructions from A‑User Control, Domain Requests from Context Capture via the Directed Semantic Query Interface, and BKN‑DAC Requests from Basic Knowledge via the Dialogic Semantic Interface (MCP). Domain Requests from Context Capture and BKN‑DAC Requests from Basic Knowledge are resolved against external domain knowledge sources accessible to Domain Access through MCP‑compatible interfaces.
- Produces Domain Responses to Context Capture at descriptor level, scoped to the modality of the request (Audio, Visual, or User), BKN‑DAC Responses to Basic Knowledge supporting multi‑turn deliberative exchange, and the DAC Status reported to A‑User Control.
2. Reference Model
Figure 1 depicts the Reference Model of the Domain Access (PGM‑DAC) AIM.
Figure 1 – Reference Model of the Domain Access (PGM‑DAC) AIM
A conforming Domain Access implementation SHALL observe the following behavioural requirements:
- SHALL expose a Directed Semantic Query Interface for operational, single‑shot Domain Requests from Context Capture. This interface is stateless; no session continuity is preserved across successive requests.
- SHALL expose a Dialogic Semantic Interface implemented using the Model Context Protocol (MCP) for multi‑turn Domain Requests from Basic Knowledge. This interface is session‑oriented; semantic commitments MAY be preserved across successive exchanges within the same session.
- SHALL resolve Domain Requests and BKN‑DAC Requests against external domain knowledge sources. External domain knowledge sources SHALL expose an MCP‑compatible interface. For the current version of this specification, the M‑Instance is the sole provider of domain knowledge services accessible by Domain Access.
- SHALL return Domain Responses scoped to the modality of the request (Audio, Visual, or User) when responding to Context Capture.
- SHALL NOT modify perceptual or user descriptors produced by other AI Modules.
- SHALL NOT maintain perception state or user state beyond that required for MCP session continuity.
- If a requested external domain knowledge source is unavailable or returns an error, Domain Access SHALL report the failure in DAC Status identifying the requested service, the request that triggered the failure, and whether the failure is transient or permanent, so that A‑User Control can determine the appropriate course of action.
3. Input/Output Data
Table 1 specifies the Input and Output Data of the Domain Access (PGM‑DAC) AIM.
Table 1 – Input/Output Data of the Domain Access (PGM‑DAC) AIM
| Input | Description |
| DAC Directive | Instructions from A‑User Control specifying the operational scope, access rights, and session constraints for domain knowledge retrieval. |
| Domain Request | Single‑shot semantic grounding request from Context Capture via the Directed Semantic Query Interface. |
| BKN‑DAC Request | Multi‑turn domain knowledge request from Basic Knowledge via the Dialogic Semantic Interface (MCP). |
| Output | Description |
| Domain Response | Structured domain knowledge returned to Context Capture at descriptor level, scoped to the modality of the request (Audio, Visual, or User). |
| BKN‑DAC Response | Domain knowledge response to Basic Knowledge supporting multi‑turn deliberative exchange via the Dialogic Semantic Interface (MCP). |
| DAC Status | Status information describing the execution and outcome of DAC processing, including any external service access failures, reported to A‑User Control. |
4. SubAIMs (Informative)
This section is informative. The decomposition into SubAIMs described below illustrates one conformant architecture for producing the normative outputs of PGM‑DAC. 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 Domain Access (PGM‑DAC) Composite AIM.
Figure 2 – Reference Model of the Domain Access (PGM‑DAC) Composite AIM
4.2 Operation
The Domain Access operation receives Domain Requests from Context Capture and BKN‑DAC Requests from Basic Knowledge, resolves them against external domain knowledge sources, and assembles the responses together with the execution status.
The Perceptual Domain Service SubAIM serves Context Capture. It receives Domain Requests via the Directed Semantic Query Interface, resolves them against the relevant external domain knowledge source via MCP, and returns Domain Responses scoped to the modality of the request. Each request is stateless and self‑contained.
The Deliberative Domain Service SubAIM serves Basic Knowledge. It receives BKN‑DAC Requests via the Dialogic Semantic Interface (MCP), maintains session continuity across successive exchanges, resolves requests against the relevant external domain knowledge source, and returns BKN‑DAC Responses supporting multi‑turn deliberative reasoning.
The Domain Status Assembly SubAIM consolidates per‑request access outcomes from both SubAIMs, including any external service access failures, and generates the DAC Status reported to A‑User Control.
4.3 Functions of SubAIMs
Table 2 specifies the functions of the SubAIMs of the Domain Access (PGM‑DAC) Composite AIM.
Table 2 – Functions of the SubAIMs of the Domain Access (PGM‑DAC) Composite AIM
| Name | Function |
| Perceptual Domain | Serves Context Capture via the Directed Query Interface. Resolves single‑shot Domain Requests against external domain knowledge sources and returns modality‑scoped Domain Responses. |
| Deliberative Domain | Serves Basic Knowledge via the Dialogic Semantic Interface (MCP). Resolves BKN‑DAC Requests against external domain knowledge sources and returns BKN‑DAC Responses supporting multi‑turn deliberative reasoning. |
4.4 Input/Output Data of SubAIMs
Table 3 lists the Input and Output Data of the SubAIMs of the Domain Access (PGM‑DAC) Composite AIM.
Table 3 – Input/Output Data of the SubAIMs of the Domain Access (PGM‑DAC) Composite AIM
| Name | Input Data | Output Data |
| Perceptual Domain Service | Domain Request DAC Directive |
Domain Response DAC Status |
| Deliberative Domain Service | BKN‑DAC Request DAC Directive |
BKN‑DAC Response DAC Status |
4.5 AIMs and JSON Metadata
Table 4 gives the Domain Access (AIM1) and its SubAIMs (AIM2).
Table 4 – Domain Access (AIM1) and its SubAIMs (AIM2)
| AIM1 | AIM2 | Name | JSON |
| PGM‑DAC | Domain Access | X | |
| PGM‑PDS | Perceptual Domain Service | X | |
| PGM‑DDS | Deliberative Domain Service | X |
5. JSON Metadata
https://schemas.mpai.community/PGM1/V1.0/AIMs/DomainAccess.json
6. Profiles
No Profiles.
7. Reference Software
Not part of this specification.
8. Conformance Testing
A DAC implementation conforms with Domain Access (PGM‑DAC) if it satisfies the conformance requirements of Table 5.
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 Domain Access (PGM‑DAC) AIM
| Receives | DAC Directive | Shall validate against DAC Directive schema. |
| Domain Request | Shall validate against Domain Request schema. | |
| BKN‑DAC Request | Shall validate against BKN‑DAC Interaction schema. | |
| Produces | Domain Response | Shall validate against Domain Response schema. |
| BKN‑DAC Response | Shall validate against BKN‑DAC Interaction schema. | |
| DAC Status | Shall validate against DAC Status schema. |
9. Performance Assessment
Not part of this specification.
