Number of actors the agent identified (e.g. customer, seller, administrator, guest).
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 resources the agent identified (e.g. sales, orders, channels). Surface this in the UI so the operator can sanity-check the scope before committing to a product plan.
Markdown body of wiki/sdk-map.md. Kept on the event so the UI can expand
it inline without a separate file fetch.
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 1 (SDK Study) of an AutoView run finishes.
The SDK Study phase reads every TypeScript file under
src/api/, extracts resources, actors, and end-to-end journeys, and writes the result towiki/sdk-map.md. Subsequent phases depend on this map.Author
Samchon