Confirm Module
Handles Human-in-the-Loop (HITL) approvals, decision tracking, and learning signal capture.
Usage Boundary: This page provides an evaluative summary and a canonical schema excerpt for convenience. The authoritative, versioned specification remains on docs.mplp.io. MPGC does not issue certifications, badges, or endorsements; adoption and conformance are self-assessed by the adopting organization.
Definition
Protocol Role
The normative responsibility of this module.
The Confirm module defines when execution requires explicit approval.
It acts as a decision gate — declaring that a transition or action cannot proceed without confirmation.
Confirm does NOT make decisions; it triggers the need for one.
Architecture
Interaction Model
Dependencies and event emissions.
Triggers
- Plan: Step transitions MAY require confirmation.
- Collab: Participant changes MAY trigger confirmation.
Integration
- Role / Governance: Determines who can approve.
- Trace: All confirmation results MUST be recorded.
Compliance
Key Constraints
Essential requirements for this module.
- Execution MUST NOT proceed without required confirmation.
- Confirmation results MUST be traceable.
- Confirm MAY be mediated by human or system.
Specification
Canonical Schema
The normative JSON structure for this module.
{
"required": [
"meta",
"confirm_id",
"target_type",
"target_id",
"status",
"requested_by_role",
"requested_at"
],
"optional": [
"reason",
"decisions",
"trace",
"events",
"governance"
],
"targetTypes": [
"context",
"plan",
"trace",
"extension",
"other"
],
"decisionObject": {
"required": [
"decision_id",
"status",
"decided_by_role",
"decided_at"
],
"statusEnum": [
"approved",
"rejected",
"cancelled"
]
}
}Behavior
Lifecycle
Valid states and transitions.
Status Enum
Quick Links
Evaluation Path
Governance → Compliance → Golden Flows → Adoption Signals