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

Definition

The digital representation of a mental state expressing what an Entity wants to bring about in the world per the Theory of Mind where desires are motivational constructs representing preferred outcomes guiding the formation of intentions.

Desire are a component of BDI  – Belief (what the Entity considers true)–Desire–Intent (what the Entity plans to do) reflecting what the Entity values, forming the basis for autonomous decision-making and adaptive behaviour.

Functional Requirements

  1. Semantic Representation: Desires represent goal-oriented mental states that the Entity wants to achieve supporting attributes:
    • Proposition: Logical representation of the desired goal (Subject, PredicateCategory, PredicateClass, Object, Domain).
    • Priority: Indicates importance (integer 1–10).
    • Certainty: Confidence in relevance or strength of the desire (0.0–1.0).
  2. Contextualisation and Alignment: Desires must integrate with other Entity State components:
    • Belief: Validates feasibility of Desires.
    • Motivation: Reinforces or weakens pursuit of Desires.
    • Intent: Translates Desire into actionable plans.
  3. Traceability: Desire includes a Trace object supporting provenance for reasoning and accountability with:
    • Origin: AIM that inferred or updated the desire.
    • Timestamp: Time of creation or update.
  4. Confidence Scoring: Desire includes a Certainty score for reasoning under uncertainty to enable fallback strategies when confidence is low or conflicting desires exist.
  5. Uniqueness and Referencing: Desire holds a globally unique DesireID for runtime referencing, logging, and chaining with related intents or actions.
  6. Dynamic Update Capability: Desires support revision based on new evidence, interaction, or reasoning outcomes to allow marking Desires as deprecated or fulfilled when conditions change.

Syntax

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

Semantics

Label Description
Header Schema header with version tag.
Standard‑EDS The characters “MMC‑EDS‑V” marking the Desires data type family.
Version Major version – 1 or 2 characters.
Dot‑separator The character “.” separating version components.
Subversion Minor version – 1 or 2 characters.
DesireID Unique identifier for this desire set instance.
DesireData Set of data representing the goal the Entity wants to achieve.
DesireID Unique identifier for desire instance.
Proposition Representation of desired goal as a logical statement (Subject, PredicateCategory, PredicateClass, Object, Domain, TemporalContext, SpatialContext).
Priority Priority level of the desire (integer 1–10).
Certainty Confidence in relevance or strength of the desire (0.0–1.0).
Trace Provenance metadata for the desire.
– Origin AIM or Entity that generated or updated the desire.
– Timestamp Time the desire was created or updated.
DescrMetadata Descriptive metadata for documentation or indexing.

5     Conformance Testing

A Data instance Conforms with PGM-AUA Desire (PGM-EDS) 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