Single Agent – Happy Path
The baseline single-agent workflow. Agent receives context, generates a minimal 2-step plan, executes, and produces trace.
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-01-single-agent-plan/README.md. The Docs page is a secondary reference at verified flow reference.
Goal
Validate that the runtime can accept a Context with an Intent and produce a valid Plan.
Success Criteria
Plan is schema-valid and logically addresses the Intent.
Sequence
Execution Steps
Website summary of the scenario sequence represented by this flow.
Context Creation
Context established with domain and environment.
Plan Generation
2-step plan created with deterministic UUIDs.
Task Execution
Steps executed in dependency order.
Trace Recording
All state transitions recorded.
Verification
Output validated against expected fixtures.
Context Creation
Context established with domain and environment.
Plan Generation
2-step plan created with deterministic UUIDs.
Task Execution
Steps executed in dependency order.
Trace Recording
All state transitions recorded.
Verification
Output validated against expected fixtures.
Core Boundary
Core Flow Scope
This core flow aggregates the published boundary expectations from the following MPLP modules.
Context Module
A valid Context MUST exist and be referenced prior to plan generation.
Plan Module
The generated Plan MUST be schema-valid, dependency-consistent, and logically derived from the Intent.
Trace Module
All transitions and outcomes during this flow MUST be traceable and auditable.
Validation
Failure Conditions
Execution of this core flow should be treated as outside the published boundary expectations if any of the following conditions occur.
A valid Context is missing, invalid, or not referenced.
The generated Plan violates schema or dependency constraints.
The Plan does not logically address the originating Intent.
The execution result cannot be verified against the Intent through Trace records.
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.