<-Conformance Go to ToC Examples ->

1 General

The MPAI-AIF Reference Software implements MPAI-AIF V3.0: a Controller, the Controller API, Communication, Storage, the MPAI Store, Zero Trust over MPAI-PTF, a User Agent that interprets Workflows, and AIMs of several MPAI Standards. The Reference Software of MPAI-MAS – the Thalia Service and its clients – is built on it.

The software is written in C# for .NET 10. The Controller and the Service run on Windows and Linux; the browser client runs in any current browser; the desktop clients run on Windows.

2 Components

Table 1 – Components of the Reference Software

Component What it contains
AIF The Controller – Module loader, life cycle, the executor for the exchange and continuous execution, status and degradation, time base and Trace -, the Controller API, Communication (Channels and transports), Storage (Private and Shared, under rules, the record of the boundary), the AIM Metadata reader and checker, the MPAI Store, the AIM host, Trust and the root of trust.
AIMs The Middleware: Implementations of AIMs of MPAI-MMC, MPAI-PAF, MPAI-OSD, MPAI-CAE and MPAI-CAV, with their AIM Instance Metadata.
UserAgent The User Agent: the Workflow reader and interpreter, the Physical Layer, the Controller API client, local and over MPAI-MAS, and the desktop and browser clients.
MAS MPAI-MAS: the MAS API Service, its Service Controller Instances and the Store service.
Apps Applications: each a Module and a Workflow.
schemas The JSON Schemas of the Data Types and of the Metadata the software uses.
Test The automated tests.

3 What is implemented

Table 2 – Implementation of MPAI-AIF V3.0

Chapter Implemented
User Agent Workflow interpretation; the Physical Layer on the desktop and in the browser, acquiring by Qualifier; the Controller API client, local and over MPAI-MAS; record and playback; sessions.
AI Modules Basic and Composite AIMs to any depth; Ports by Data Type and Port Number; placement of Sub-AIMs on AIM hosts; reports and status.
Controller One Controller, one Module; start, pause, resume and stop at every depth; OnDegraded and RestartLimit; trust authority over MPAI-PTF.
Communication Channels with the Controller, InProcess and Remote transports; Port behaviour; payloads by reference within a Controller, inlined at its boundary; one time base.
Storage Private Storage of an AIM and of a Module, Shared Storage, rules with a central control, the record of the boundary.
Metadata AIM Metadata and AIM Instance Metadata read, validated, and checked for the instance-of relation.
Execution The exchange and continuous execution on one executor; Period, Deadline and MaxAge.
MPAI Store Submission, versions, findings, fingerprints and verification of Implementations and models.
Zero Trust Identities and credentials of AIM Instances; code and models verified before they run; trust between a Controller and an AIM host; attestation over a simulated root of trust; the Trace.

Not yet implemented are, among others: the PointToPoint, Bus and External transports; Grants per Channel end; a Deployment Controller; a Controller managing Controllers; authenticated submission to the MPAI Store; a hardware root of trust.

4 Verification

The Reference Software is verified by automated tests, among them:

  • every AIM Instance Metadata loaded, validated and checked against its AIM Metadata;
  • Modules run by exchange and continuously, with loops, degradation and restarts;
  • Sub-AIMs run on an AIM host on another process, under the one Controller;
  • Storage under rules, the record of a boundary and its playback;
  • Implementations and models verified against the MPAI Store, and a Module refused when they differ;
  • the Applications of MPAI-MAS run end to end, by several clients at once.

5 Access to the code

Please send an email to the MPAI Secretariat to access the code.

<-Conformance Go to ToC Examples ->