(Tentative)

Definition Functional Requirements Syntax Semantics

Definition

SubAIMs To AIMs is the compact message format through which a SubAIM (HGV, GIR, PFS, GPO, CDE) issues a
Directive to a target AIM and receives a Status in return. The schema reuses the Common Interface Envelope for Envelope, Trace, and Accuracy, identifies AIMs with AIF v3.0 AIMInstance, timestamps via OSD v1.5, references MMC v2.5 Intent when goal semantics are required, and integrates governance with single Items Rights and Rule from MMM‑TEC v2.2.

Functional Requirements

  • Role — Distinguish Directive vs Status via Payload.Role, with role‑based required fields.
  • Addressing — Use full AIMInstance.json for TargetAIM (and for Trace.From/To at envelope level).
  • Envelope/Time — Include identifiers and timestamps using OSD v1.5 time data types.
  • Correlation — Keep Envelope.CorrelationId stable across a Directive and all its Status messages.
  • SubAIM tokens — Indicate issuing SubAIM via 3‑char tokens: HGV, GIR, PFS, GPO, CDE.
  • Policy — Allow Policy context referencing single MMM‑TEC Items Rights / Rule (required for PFS Directives).
  • Intent — When goal semantics are required, allow MMC v2.5 Intent inside GoalContext.
  • Parameters/SchemaRef — Allow AIM‑specific Parameters; optionally constrain via SchemaRef (micro‑schema) without changing message names.
  • Status taxonomy — Use {Received, Queued, InProgress, Paused, Completed, Failed, Rejected, Cancelled}; optionally include Progress, Summary, Result, Errors.
  • Accuracy — Carry Accuracy (confidence, method/calibration); recommended for Status.
  • Operation specialisation — Constrain Operation by FromSubAIM:
    HGV → HumanGoalIntake|Validation; GIR → GoalNormalisation|IntentResolution; PFS → PolicyScreening|FeasibilityAssessment; GPO → PlanIntegration|OrchestrationHandoff; CDE → ConflictDetection|Escalation.

Syntax

https://schemas.mpai.community/PGM1/V1.0/data/SubAIMsToAIMs.json

Semantics

Label Description
Header SubAIMs To AIMs Header
– Standard-SubAIMsToAIMs The characters “PGM-STA-V” indicating schema family and type
– Version Major version – 1 or 2 characters
– Dot-separator The character “.” separating version components
– Subversion Minor version – 1 or 2 characters
Envelope Transport/control metadata: MessageId, CorrelationId, MessageType, Timestamp, Version. Reused from CIE.
Trace From/To/Timestamp and optional lineage chain. From/To MUST be full AIMInstance.json objects.
Accuracy Confidence [0..1] and optional method/calibration; recommended for Status; optional for Directive.
Payload.Role Discriminator of payload shape: Directive or Status. Drives conditional required fields.
Payload.DirectiveId Identifier of the directive lifecycle. Required in both Directive and Status. Bind Statuses to the Directive via the same CorrelationId.
Payload.DirectiveName Stable directive name for the target AIM (retains any prefix words placed before “Directive”).
Payload.FromSubAIM Issuing SubAIM token (HGV, GIR, PFS, GPO, CDE). SubAIMs are AIMs; tokens are 3‑char.
Payload.TargetAIM Target AIM instance as full AIMInstance.json (AIF v3.0).
Payload.Operation Behavioural op constrained by SubAIM: HGV → HumanGoalIntake|Validation; GIR → GoalNormalisation|IntentResolution; PFS → PolicyScreening|FeasibilityAssessment; GPO → PlanIntegration|OrchestrationHandoff; CDE → ConflictDetection|Escalation.
Payload.GoalContext Goal identification and semantics (GoalId, Description), optionally MMC Intent when applicable.
Payload.PlanContext Plan identifier and step taxonomy. Step may be a short code or a structured object (code,name,phase,subaim,details).
Payload.Policy Policy constraints. Rights and Rule are single MMM‑TEC Items (each item can encode the applicable set). Required for PFS directives.
Payload.Constraints Operational constraints (TimeoutMs, MaxCost, RiskTolerance). AIM SHOULD honour or return Status.State=”Rejected” with Errors.
Payload.Priority Scheduling hint: Low|Normal|High|Critical.
Payload.Parameters AIM‑specific parameters; optionally constrained by Payload.SchemaRef (micro‑schema).
Payload.SchemaRef URI of a micro‑schema specialising Parameters/Result; optional.
Payload.State Status taxonomy: Received, Queued, InProgress, Paused, Completed, Failed, Rejected, Cancelled.
Payload.Progress Fractional progress [0..1] for streaming/long‑running operations.
Payload.Summary Short human‑readable status string (logs/ops UI).
Payload.Result AIM‑specific result object; optionally constrained via SchemaRef.
Payload.Errors Error list {Code, Message, Severity} with Severity ∈ Info|Warning|Error|Critical.
Payload.Next Advisory hint for next actor/step (e.g., suggested handoff target token).