Single Agent – Large Plan
Volumetric validation with 20+ steps. Tests protocol handling of large execution plans.
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-02-single-agent-large-plan/README.md. The Docs page is a secondary reference at verified flow reference.
Goal
Validate that the runtime can execute a Plan with 20+ steps while maintaining invariants.
Success Criteria
All 20+ steps complete, Trace is generated, no performance degradation.
Sequence
Execution Steps
Website summary of the scenario sequence represented by this flow.
Large Context
Context framing batch processing scenario.
Multi-Step Plan
20-30 heterogeneous steps with dependencies.
Volumetric Execution
Steps processed with wildcard invariant validation.
Trace Verification
Events ordered correctly despite volume.
Large Context
Context framing batch processing scenario.
Multi-Step Plan
20-30 heterogeneous steps with dependencies.
Volumetric Execution
Steps processed with wildcard invariant validation.
Trace Verification
Events ordered correctly despite volume.
Core Boundary
Core Flow Scope
This core flow aggregates the published boundary expectations from the following MPLP modules.
Context Module
Context MUST remain stable across volumetric execution.
Plan Module
Large plans (20+ steps) MUST preserve dependency order and step integrity.
Trace Module
Trace events MUST be ordered correctly despite volume.
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 cannot handle 20+ steps without schema violations.
Step ordering is not preserved during execution.
Performance degrades unacceptably with large plans.
Trace event ordering becomes incorrect.
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.