Golden Flow: FLOW-05

Single Agent with Confirm Required

Multi-round approval workflow. Validates Confirm module integration.

Goal

Validate that the runtime handles multi-round confirmation correctly.

Success Criteria

Plan transitions through approval states, Confirm records auditable.

Sequence

Execution Steps

The normative sequence of operations for this flow.

1

Plan Creation

Plan requiring confirmation before execution.

2

Confirm Request

Confirmation request created with approver_role.

3

Approval/Rejection

Decision captured with timestamp and notes.

4

Conditional Execution

Plan proceeds only if approved.

Normative

Normative Scope

This flow normatively aggregates and enforces existing constraints from the following MPLP modules.

Confirm Module

Confirmation requests MUST block execution until resolved.

Plan Module

Plan status transitions MUST respect Confirm decisions.

Trace Module

All confirmation decisions MUST be recorded in trace.

Validation

Failure Conditions

Execution of this flow MUST be considered non-conformant if any of the following conditions occur.

Plan executes without required confirmation.

Confirmation decisions are not recorded.

Approval timestamps are not captured.

Rejected plans proceed to execution.

Protocol Conformance Requirement

Any MPLP-conformant runtime is expected to pass this flow without violating any of the normative constraints defined above.

Failure to satisfy this flow results in a non-conformant MPLP implementation.

Key Modules

ContextPlanConfirmTrace

Positioning Notice: This website provides discovery and positioning content only. For formal protocol definitions, see docs.mplp.io. Source of truth: GitHub Repository.