1     Definition 2     Functional Requirements 3     Syntax
4     Semantics 5    Conformance Testing 6     Performance Assessment

Definition

A digital representation of the mental state of an Entity based on the Theory of Mind principle. It models beliefs, intentions, desires, and knowledge. An Entity State can be

  • Assigned (by a human or another Entity if the Entity is artificial).
  • Inferred (regardless of the human/artificial distinction, for both the inferrer and the inferee).

Entity is one of:

  • A Process rendered as a Virtual Human.
  • A Human or a rendered Digital Human.

Functional Requirements

Entity State shall support the following functional requirements:

  1. Dual Representation: Entity State shall represent both physical/functional and mental state attributes.
  2. Assignment and Inference: Entity State shall to be either explicitly assigned or inferred, supporting dynamic updates based on interaction context.
  3. Inference Capability: Entity State may be inferred dynamically based on interaction context, regardless of whether the inferrer or inferee is human or artificial.
  4. Entity Scope: Entity State may apply  to Humans, Digital Humans, and Virtual Humans (Processes), ensuring interoperability across real and synthetic Entoties.
  5. Predictive Reasoning: An Entity may use mental state attributes (beliefs, desires, intentions) to predict future actions and adapt interaction strategies.
  6. Confidence Management: Entity State shall support a confidence level for inferred mental states to guide decision-making under uncertainty.
  7. Temporal Consistency: Entity State shall be timestamped to enable temporal reasoning and historical analysis.

Syntax

https://schemas.mpai.community/MMC/V2.5/data/EntityState.json

Semantics

Label Description
Header Entity State Header.
– Standard‑EST The characters “MMC‑EST‑V” marking the Entity State data type family.
– Version Major version – 1 or 2 characters.
– Dot‑separator The character “.” separating version components.
– Subversion Minor version – 1 or 2 characters.
M-InstanceID ID or virtual instance.
EntityStateID Unique identifier for this Entity State instance.
EntityStateData SEt of Data included in Entity State.
SpatialAttitude Spatial attitude of Entity (position, orientation, media type).
TemporalCue Time-related signal (CueType, CueValue).
CognitiveState Internal mental disposition of the Entity (e.g., “attentive”, “comprehending”).
Emotion Emotional state resulting from interaction with context (e.g., “Angry”, “Sad”).
SocialAttitude Social positioning vis-à-vis context (e.g., “Respectful”, “Confrontational”).
Intentions Array of structured intents (symbolic goals or directives guiding behaviour).
Motivation Goal orientation or drive behind Entity behaviour.
Belief Array of structured beliefs, each with: Proposition (Subject, PredicateCategory, PredicateClass, Object, Domain), TruthValue, SourceType, ConfidenceScore, Trace.
Desire Goals the Entity wants to achieve, with optional priority.
Knowledge Verified facts known by the Entity, structured like Beliefs, with Certainty and optional link to CognitiveState categories influencing acquisition.
Engagement Level and mode of user engagement (e.g., “low”, “interactive”).
Focus Primary object or concept of attention (TargetType, TargetID).
Trace Provenance metadata (Originating AIM, Timestamp).
DescrMetadata Descriptive Metadata

5     Conformance Testing

A Data instance Conforms with MPAI-MMC Entity State (MMC-EST) if:

  1.  Its JSON Object validates against its JSON Schema.
  2. Any included  JSON Object validates against its JSON Schema.
  3. All Data in the JSON Object:
    1. Have the specified Data Types.
    2. Conform with the Qualifiers signaled in their JSON Schemas.

6     Performance Assessment