Single Agent with Confirm Required
Multi-round approval workflow. Validates Confirm module integration.
Website Source Model
Actual page source: Website aggregate projection layer in MPLP_website/lib/content/flows.ts.
Upstream provenance: IDs, titles, and boundary classification come from tests/golden/flows/registry.ts; per-flow scenario detail is summarized from the upstream asset tests/golden/flows/flow-05-single-agent-confirm-required/README.md. The Docs page is a secondary reference at verified flow reference.
Goal
Validate that the runtime handles multi-round confirmation correctly.
Success Criteria
Plan transitions through approval states, Confirm records auditable.
Sequence
Execution Steps
Website summary of the scenario sequence represented by this flow.
Plan Creation
Plan requiring confirmation before execution.
Confirm Request
Confirmation request created with approver_role.
Approval/Rejection
Decision captured with timestamp and notes.
Conditional Execution
Plan proceeds only if approved.
Plan Creation
Plan requiring confirmation before execution.
Confirm Request
Confirmation request created with approver_role.
Approval/Rejection
Decision captured with timestamp and notes.
Conditional Execution
Plan proceeds only if approved.
Core Boundary
Core Flow Scope
This core flow aggregates the published boundary expectations 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 core flow should be treated as outside the published boundary expectations 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.
Core Published Boundary
FLOW-01~05 form the published v1.0 core boundary. Implementations are expected to satisfy this flow without violating the upstream constraints summarized above.
Failure to satisfy this core flow indicates that the published core-boundary expectations were not met.