(Tentative)

Definition Functional Requirements Syntax Semantics

Definition

UR-Prompt Plan (PGM-URP)

  1. Is produced by the User State Refinement (USR) AIM.
  2. Encapsulates a structured semantic scaffold integrating aligned user intent, referential context, expressive stance, and semantic constraints.
  3. Supports the formulation of a knowledge-oriented query that is linguistically and cognitively aligned with the User’s semantic posture and engagement state.

Functional Requirements

UR-Prompt Plan conveys the following main information elements:

Function Description
Aligned Intent Embedding Includes the semantically aligned user intent. Reflects adjustments made by USR based on User State, Personality Alignment, and contextual cues.
Referent Structuring Includes resolved entities with semantic roles and expressive framing. Supports referential clarity and stylistic coherence.
Expressive Alignment Includes tone, style, and pacing cues derived from Personality Alignment and User State. Supports expressive modulation of BKN responses.
Semantic Goal Framing Encodes the communicative goal of the prompt (e.g., affirm, elaborate, redirect). Supports BKN response shaping and semantic continuity.
Constraint Injection Includes semantic, emotional, or interaction constraints relevant to the query. Supports filtering or prioritisation in BKN response logic.
Traceability Includes origin metadata and timestamp for audit and replay.

Syntax

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

Semantics

Label Description
Header UR-Prompt Plan Header
├─ Standard-SRP The characters “PGP-URP-V”
├─ Version Major version – 1 or 2 characters
├─ Dot-separator The character “.” separating version components
└─ Subversion Minor version – 1 or 2 characters
URPromptPlanID Unique identifier for this UR-Prompt Plan instance
AlignedIntent Semantically aligned user intent
Referents Resolved entities with semantic roles and expressive cues
├─ ReferentID Identifier of the resolved entity
├─ ReferentType Type of entity: object, zone, concept, actor
└─ LinguisticCue Suggested phrasing (e.g., “to your left”, “nearby”)
ExpressiveFrame Modulation cues for tone, style, and pacing
├─ Tone Expressive stance: empathetic, assertive, playful, formal, neutral
├─ Style Linguistic style: concise, elaborate, technical, casual
└─ Pacing Delivery speed: slow, steady, fast
PromptGoal Communicative goal of the prompt
├─ GoalType Type of goal: affirm, elaborate, redirect, summarise
└─ TargetEntity Entity the prompt is centered on
Constraints Semantic or expressive constraints
├─ ConstraintType Type of constraint (e.g., emotional tone, relevance, priority)
└─ ConstraintValue Entity, concept, or expressive condition
Trace Provenance metadata
├─ Origin Module or subsystem that generated the prompt plan
└─ Timestamp Time of creation (conforming to Time.json)