(Tentative)

Function Reference Model Input/Output Data
SubAIMs JSON Metadata Profiles

Function

The Domain Access AIM (PGM-DAC) receives contextual inputs from perceptual, cognitive, and expressive AIMs – Prompt Creation, Spatial Reasoning, User State Refinement, and Personality Alignment. Its primary function is to interpret, structure, and route this information to access domain-specific knowledge, services, or capabilities.

Internally, PGM-DAC may perform the following operations:

  • Context Interpretation: Parses incoming semantic context to identify relevant domain triggers, constraints, and access parameters.
  • Domain Mapping: Matches contextual cues to domain-specific modules, APIs, or knowledge graphs, selecting appropriate access pathways.
  • Query Structuring: Constructs formalised domain queries or action requests based on inferred goals, User State, and interaction history.
  • Access Execution: Dispatches structured requests to internal or external domain resources, applying governance and permission constraints.
  • Response Normalisation: Transforms domain responses into semantically aligned outputs suitable for downstream AIMs.
  • Output Construction: Produces a DA Execution Status for A-User Control and structured domain content for Basic Knowledge or Prompt Creation.

The resulting outputs enable A-User Control, Basic Knowledge, and Prompt Creation to operate with full access to domain-specific information, supporting goal-driven orchestration, semantic traceability, and context-sensitive interaction.

Reference Model

Figure 8 gives the Reference Model of Domain Access (PGM-DAC) AIM.

 

Figure 8 – The Reference Model of Domain Access AIM

Domain Access may be structured to performs the following functions:

# Function Details
1 Parse BKN Output Extract key-value pairs from BKN’s structured text.
2 Ingest Spatial Output Load structured spatial data: occlusion, reachability, referents, zones.
3 Cross-Validate Items Confirm that Source Item and Target Zone from BKN match SPR referents.
4 Verify Constraints Compare BKN’s Reachable, Occluded flags with SPR maps.
5 Check Zone Classification Use SPR zone tags to validate interaction feasibility.
6 Check Scene Consistency Ensure SceneID from BKN matches SPR’s current scene
7 Lookup Behaviour Registry Match Intent to available executable behaviour.
8 Evaluate Execution Feasibility Use SPR constraints to approve or block behaviour.
9 Fallback or Adjust If SPR contradicts BKN (e.g. entity not reachable), trigger fallback or rephrasing.
10 Emit Execution Payload Construct final behaviour object with validated parameters.
11 Log Trace Metadata Store provenance from both BKN and SPR streams.

Input/Output Data

Table 17 gives Input and Output Data of Domain Access (PGM-DAC).

Table 17 – Input and Output Data of Domain Access (PGM-DAC)

Input Description
Audio Spatial Output A Data Type providing spatial relationships, referent resolutions, and interaction constraints to Domain Access (DA) to support reasoning about physical feasibility, visibility, and referential clarity within a visual scene.
Visual Spatial Output A Data Type providing localised, annotated and salience-ranked Audio Objects to Domain Access (DAC) and encapsulates spatial, temporal, and semantic interpretations of audio-emitting Items.
Initial Response Basic Knowledge’s response to PC-Prompt.
DA Action Directive Request for domain execution from PGM-AUC.
Output Description
Audio Spatial Directive A Data Type providing referential cues, User intent, and contextual constraints to guide interpretation of audio scenes to enable Audio Spatial Reasoning (ASR) to resolve ambiguous entities, assess auditory relevance, and generate expressive primitives aligned with the A-User’s interaction goals.
Visual Spatial Directive A Data Type including referential cues, User Intent, and contextual constraints that guide the interpretation of spatial scenes and enable Spatial Reasoning to resolve ambiguous entities, evaluate spatial feasibility, and generate primitives aligned with the User’s cognitive and interaction goals.
Personality Context Guide A Data Type including validated User Intent, contextual constraints, and referent semantics to inform the Personality Alignment (PA) of the behavioural framing, domain-specific context, and semantic scaffolding necessary to adapt A-User responses to the User State.
DA-Prompt Prompt produced by Domain Access.
DA Action Status Action feasibility and constraint validation reports to PGM-AUC.

SubAIMs

No SubAIMs.

JSON Metadata

https://schemas.mpai.community/PGM1/V1.0/AIMs/DomainAccess.json

Profiles

No Profiles.