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.
Detailed reason why these schemas need redesign.
Explains what implementation issues the current schema design causes, as reported by the realize agent.
Iteration number of the requirements analysis.
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"
DTO type names that are being redesigned.
These are schema names from components.schemas that were identified as
problematic for implementation by the realize agent.
Event fired when the Realize agent triggers backward propagation to redesign DTO schemas in the Interface phase.
When the realize agent discovers that DTO schemas are inadequately designed for proper API implementation, it triggers backward propagation to have the interface schema refine process redesign the affected schemas. This event captures that occurrence for monitoring and debugging purposes.
After this event is dispatched, the standard
interfaceSchemaRefineevents will follow as the schemas are actually refined. This event serves as the trigger notification.Author
Samchon