Timestamp when the event was created.
ISO 8601 formatted date-time string indicating when this event was emitted by the system. This timestamp is crucial for event ordering, performance analysis, and debugging the agent workflow execution timeline.
Format: "YYYY-MM-DDTHH:mm:ss.sssZ" (e.g., "2024-01-15T14:30:45.123Z")
A unique identifier for the event.
Number of SDK endpoints the plan intentionally leaves out.
Number of pages the plan defines.
Markdown body of wiki/product-plan.md. Surfaced verbatim so the operator
can review every page in the UI gate without leaving the conversation.
Step counter — matches autoViewStart.step.
Unique identifier for the event type.
A literal string that discriminates between different event types in the AutoBE system. This field enables TypeScript's discriminated union feature, allowing type-safe event handling through switch statements or conditional checks.
Examples: "analyzeWrite", "databaseSchema", "interfaceOperation", "testScenario"
Event fired when phase 2 (Product Plan) of an AutoView run finishes.
The Product Plan phase reads
sdk-mapplus the optional design theme and produces an information architecture: which pages exist, what each page does, which SDK endpoints it composes, and which endpoints are intentionally omitted.This phase has a human gate immediately after — the UI shows the plan and waits for the operator to confirm before scaffold/render run.
Author
Samchon