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 A‑User Storage (PGM‑AUS) AIM is the A‑User’s persistence and storage‑governance service. It holds the data that AIMs produce and consume within a session and, where retained, across sessions — including Interaction History, captured and enhanced scene descriptors, PC Prompts, resolved domain knowledge, AIM Statuses, and User materialisation assets such as the Avatar. A‑User Storage is more than a passive store: it authorises, scopes, keys, and retains the data it holds, and it enforces the storage policy set by A‑User Control.

A‑User Control governs all A‑User Storage access but is never in the data path; placing it on every read and write would make it a bottleneck. Instead, the AIMs that produce and consume data — Context Capture, Context Enhancement, Prompt Creation, Domain Access, and other AUS‑accessing AIMs — perform the physical operations against A‑User Storage, while A‑User Control governs in two complementary ways:

  • it instructs each producing AIM, through that AIM’s own Directive, what to persist and what it may read; and
  • it configures A‑User Storage itself, through the AUS Directive, with the session’s storage scopes, retention and lifecycle policy, and the authorisations A‑User Storage enforces on incoming operations.

A‑User Storage operates through a two‑fold interface, each side with distinct behaviour:

  • Control Interface — receives an AUS Directive from A‑User Control and returns an AUS Status. This interface is directive‑driven and non‑MCP. The AUS Directive carries a SessionID and establishes the storage scopes available (session and historical), the retention and lifecycle policy (open, close, archive session→historical, delete), and the read/write authorisations A‑User Storage enforces.
  • Storage Interface — receives an AUS Request from an AUS‑accessing AIM and returns an AUS Response. An AUS Request is a read or write operation carrying the requester’s identity, SessionID, and target scope. Session‑scope reads are served on request; historical‑scope reads are served only where authorised; writes are served as instructed to the requesting AIM. Every operation is recorded so that A‑User Control retains after‑the‑fact visibility through the AUS Status.

A‑User Storage acts as the sole persistence authority for the A‑User. It is the only AIM responsible for holding, scoping, keying, retaining, and serving the A‑User’s session and historical data.

The PGM‑AUS AIM:

Receives AUS Directive Instructions from A‑User Control establishing storage scopes, retention and lifecycle policy, session identification, and the read/write authorisations A‑User Storage enforces.
AUS Request A read or write operation from an AUS‑accessing AIM, carrying the requester’s identity, SessionID, target scope, and (for writes) the content to persist or (for reads) the selector of the content to retrieve.
Produces AUS Response The retrieved content for a read operation, or an acknowledgement and outcome for a write operation, returned to the requesting AIM.
AUS Status Status information describing storage state, per‑operation outcomes, scope and retention enforcement, integrity and capacity, and lifecycle outcomes, reported to A‑User Control.

2 Reference Model

Figure 1 depicts the Reference Model of the A‑User Storage (PGM‑AUS) AIM.

[Figure 1 image to be inserted]

Figure 1 – Reference Model of the A‑User Storage (PGM‑AUS) AIM

3 I/O Data

Table 1 specifies the Input and Output Data of the A‑User Storage (PGM‑AUS) AIM.

Table 1 – Input and Output Data of the A‑User Storage (PGM‑AUS) AIM

Input Description
AUS Directive Instructions from A‑User Control establishing storage scopes, retention and lifecycle policy, session identification, and the read/write authorisations A‑User Storage enforces.
AUS Request A read or write operation from an AUS‑accessing AIM, carrying the requester’s identity, SessionID, target scope, and content or selector.
Output Description
AUS Response The retrieved content for a read operation, or an acknowledgement and outcome for a write operation, returned to the requesting AIM.
AUS Status Status information describing storage state, per‑operation outcomes, scope and retention enforcement, integrity and capacity, and lifecycle outcomes, 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‑AUS. 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 A‑User Storage (PGM‑AUS) Composite AIM.

[Figure 2 image to be inserted]

Figure 2 – Reference Model of the A‑User Storage (PGM‑AUS) Composite AIM

4.2 Operation

The AUS operation includes the following SubAIMs:

  1. Access Authorisation
    • Validates each incoming AUS Request against the scopes and authorisations established by the prevailing AUS Directive.
    • Admits session‑scope reads, admits historical‑scope reads only where authorised, and admits writes as instructed to the requesting AIM.
  2. Retrieval Service
    • Executes admitted read operations against session or historical storage.
    • Returns the retrieved content as an AUS Response.
  3. Persistence Service
    • Executes admitted write operations, keying content by SessionID and scope and resolving concurrency.
    • Returns an acknowledgement and outcome as an AUS Response.
  4. Lifecycle & Retention Management
    • Opens and closes session storage, archives session data to historical scope, and enforces retention and deletion policy.
    • Maintains storage integrity and capacity.
  5. AUS Status Assembly
    • Consolidates per‑operation, enforcement, and lifecycle outcomes.
    • Generates the AUS Status reported to A‑User Control.

The reference model explicitly separates authorisation, retrieval, persistence, lifecycle and retention, and status assembly, ensuring modularity, traceability, and reuse.

4.3 Functions of SubAIMs

Table 2 specifies the functions of the A‑User Storage (PGM‑AUS) SubAIMs.

Table 2 – Functions of the A‑User Storage (PGM‑AUS) SubAIMs

SubAIM Function
Access Authorisation Validates each AUS Request against the scopes and authorisations established by the prevailing AUS Directive.
Retrieval Service Executes admitted read operations and returns the retrieved content.
Persistence Service Executes admitted write operations, keying by SessionID and scope, and returns an acknowledgement.
Lifecycle & Retention Management Manages session lifecycle, archival to historical scope, retention, deletion, and integrity.
AUS Status Assembly Consolidates operation, enforcement, and lifecycle outcomes into the AUS Status reported to A‑User Control.

4.4 I/O Data of SubAIMs

Table 3 gives the Input and Output Data of the A‑User Storage (PGM‑AUS) SubAIMs.

Table 3 – Input and Output Data of the A‑User Storage (PGM‑AUS) SubAIMs

SubAIM Input Output
Access Authorisation AUS Directive
AUS Request		 Authorised Read Operation
Authorised Write Operation
Retrieval Service Authorised Read Operation AUS Response
Retrieval Outcome
Persistence Service Authorised Write Operation AUS Response
Persistence Outcome
Lifecycle & Retention Management AUS Directive Lifecycle Outcome
AUS Status Assembly Retrieval Outcome
Persistence Outcome
Lifecycle Outcome		 AUS 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 A‑User Storage (PGM‑AUS)

AIM1 AIM2 Name JSON
PGM‑AUS A‑User Storage X
PGM‑AAU Access Authorisation X
PGM‑ARS Retrieval Service X
PGM‑APS Persistence Service X
PGM‑ALM Lifecycle & Retention Management X
PGM‑ASA AUS Status Assembly X

5 JSON Metadata

https://schemas.mpai.community/PGM1/V1.0/AIMs/AUserStorage.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 A‑User Storage (PGM‑AUS) 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 A‑User Storage (PGM‑AUS) AIM

Receives AUS Directive Shall validate against AUS Directive schema.
AUS Request Shall validate against AUS Request schema.
Produces AUS Response Shall validate against AUS Response schema.
AUS Status Shall validate against AUS Status schema.

9 Performance Assessment

Not part of this specification.

Go to PGM-AUA V1.0 AI Modules