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 Domain Access (PGM‑DAC) AIM is the A‑User’s gateway to external domain knowledge. It resolves typed knowledge requests against the domain(s) authorised for the current session and returns structured knowledge that enriches perceptual interpretation and supports deliberation. Domain Access does not itself interpret scenes or deliberate.

Domain Access operates through a two‑fold interface, each side with distinct behaviour:

  • Control Interface — receives a DAC Directive from A‑User Control and returns a DAC Status. This interface is directive‑driven and non‑MCP. The DAC Directive carries a SessionID and authorises which domains may be accessed, the permitted scope and depth of access, and any A‑User Storage instructions (AUSRead/AUSWrite). It does not carry knowledge requests. A‑User Control governs all A‑User Storage access by Domain Access.
  • Service Interface (MCP) — resolves knowledge requests on demand, strictly within the bounds authorised by the prevailing DAC Directive. This interface serves two clients whose behaviour differs:
    • Context Enhancement issues a Domain Request (instantiated as Audio, Visual, or User Domain Access) seeking perceptual enrichment of the captured scene and of the User Entity State, and receives a Domain Response. Behaviour is descriptor‑level, modality‑scoped, and synchronous with enhancement.
    • Basic Knowledge issues a BKNToDAC message as part of the deliberation triggered by the PC Prompt, seeking topical and semantic domain knowledge, and receives a DACToBKN message. Behaviour is deliberation‑oriented and may be multi‑turn over the MCP session. Both directions are defined within the BKN-DAC Interaction schema.

Domain Access acts as the sole Domain Knowledge Provider. It is the only AIM responsible for resolving domain knowledge requests, from both Context Enhancement and Basic Knowledge, against the domains authorised for the current session.

The PGM‑DAC AIM:

Receives DAC Directive Instructions from A‑User Control specifying authorised domains, access scope and depth, session identification, and A‑User Storage access instructions.
Domain Request Request for domain‑specific knowledge from Context Enhancement (Audio, Visual, or User Domain Access).
BKNToDAC Request for domain‑specific knowledge from Basic Knowledge via MCP, issued during deliberation on the PC Prompt. Defined within the BKN-DAC Interaction schema.
Produces Domain Response Domain‑specific knowledge returned to Context Enhancement.
DACToBKN Domain‑specific knowledge returned to Basic Knowledge via MCP. Defined within the BKN-DAC Interaction schema.
DAC Status Status information describing the execution and outcome of DAC processing, including A‑User Storage operation outcomes, reported to A‑User Control.

2 Reference Model

Figure 1 depicts the Reference Model of the Domain Access (PGM‑DAC) AIM.

[Figure 1 image to be inserted]

Figure 1 – Reference Model of the Domain Access (PGM‑DAC) AIM

3 I/O Data

Table 1 specifies the Input and Output Data of the Domain Access (PGM‑DAC) AIM.

Table 1 – Input and Output Data of the Domain Access (PGM‑DAC) AIM

Input Description
DAC Directive Instructions from A‑User Control specifying authorised domains, access scope and depth, session identification, and A‑User Storage access instructions.
Domain Request Request for domain‑specific knowledge from Context Enhancement (Audio, Visual, or User Domain Access).
BKNToDAC Request for domain‑specific knowledge from Basic Knowledge via MCP, issued during deliberation on the PC Prompt. Defined within the BKN-DAC Interaction schema.
Output Description
Domain Response Domain‑specific knowledge returned to Context Enhancement.
DACToBKN Domain‑specific knowledge returned to Basic Knowledge via MCP. Defined within the BKN-DAC Interaction schema.
DAC Status Status information describing the execution and outcome of DAC processing, 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 Functions of SubAIMs

Figure 2 depicts the Reference Model of the Domain Access (PGM‑DAC) Composite AIM.

[Figure 2 image to be inserted]

Figure 2 – Reference Model of the Domain Access (PGM‑DAC) Composite AIM

4.2 Operation

The DAC operation includes the following SubAIMs:

  1. Domain Request Authorisation
    • Admits or rejects each incoming Domain Request and BKNToDAC message against the domains and scope authorised by the prevailing DAC Directive.
    • Forwards admitted requests to the appropriate client‑facing service.
  2. Perceptual Domain Service
    • Serves Context Enhancement: resolves admitted Domain Requests against the relevant domain knowledge source.
    • Produces Domain Responses at descriptor level, modality‑scoped (Audio, Visual, User).
  3. Deliberative Domain Service
    • Serves Basic Knowledge: resolves admitted BKNToDAC messages in support of deliberation on the PC Prompt.
    • Produces DACToBKN messages, supporting multi‑turn exchange over the MCP session.
  4. Domain Status Assembly
    • Consolidates per‑request access outcomes and A‑User Storage operation outcomes.
    • Generates the DAC Status reported to A‑User Control.

The reference model explicitly separates authorisation, perceptual (Context Enhancement) service, deliberative (Basic Knowledge) service, and status assembly, ensuring modularity, traceability, and reuse.

4.3 Functions of SubAIMs

Table 2 specifies the functions of the Domain Access (PGM‑DAC) SubAIMs.

Table 2 – Functions of the Domain Access (PGM‑DAC) SubAIMs

SubAIM Function
Domain Request Authorisation Validates each Domain Request and BKNToDAC message against the domains and scope authorised by the prevailing DAC Directive.
Perceptual Domain Service Resolves admitted Domain Requests for Context Enhancement and produces Domain Responses.
Deliberative Domain Service Resolves admitted BKNToDAC messages for Basic Knowledge and produces DACToBKN messages.
Domain Status Assembly Consolidates access outcomes into the DAC Status reported to A‑User Control.

4.4 I/O Data of SubAIMs

Table 3 gives the Input and Output Data of the Domain Access (PGM‑DAC) SubAIMs.

Table 3 – Input and Output Data of the Domain Access (PGM‑DAC) SubAIMs

SubAIM Input Output
Domain Request Authorisation DAC Directive
Domain Request
BKNToDAC		 Authorised Domain Request
Authorised BKNToDAC
Perceptual Domain Service Authorised Domain Request Domain Response
Perceptual Access Outcome
Deliberative Domain Service Authorised BKNToDAC DACToBKN
Deliberative Access Outcome
Domain Status Assembly Perceptual Access Outcome
Deliberative Access Outcome		 DAC Status

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 Domain Access (PGM‑DAC)

AIM1 AIM2 Name JSON
PGM‑DAC Domain Access X
PGM‑DRA Domain Request Authorisation X
PGM‑PDS Perceptual Domain Service X
PGM‑DDS Deliberative Domain Service X
PGM‑DSA Domain Status Assembly 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

Table 5 provides the Conformance Testing Method for the Domain Access (PGM‑DAC) 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 Domain Access (PGM‑DAC) AIM

Receives DAC Directive Shall validate against DAC Directive schema.
Domain Request Shall validate against Domain Request schema.
BKNToDAC Shall validate against BKN-DAC Interaction schema.
Produces Domain Response Shall validate against Domain Response schema.
DACToBKN Shall validate against BKN-DAC Interaction schema.
DAC Status Shall validate against DAC Status schema.

9 Performance Assessment

Not part of this specification.

Go to PGM-AUA V1.0 AI Modules