Number of items completed.
Tracks how many items have been successfully processed so far in the current operation. This value increments as each item is completed, providing real-time progress indication.
The ratio of completed to total gives the completion percentage:
progress = (completed / total) * 100
Corrected content of the implementation file.
Contains the finalized TypeScript code that was previously incorrect but has now been updated to compile and align with project requirements. This code bridges the gap between the flawed implementation and a working production-quality version.
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.
Name of the implementation file that has been corrected and finalized.
Specifies the filename of the TypeScript implementation file that was corrected. This may represent service classes, business logic modules, DAOs, or integration handlers that initially failed validation and have now been successfully revised.
Iteration number of the requirements analysis this corrected file corresponds to.
Ensures that the correction reflects the latest understanding of the business requirements and that code remains synchronized with current objectives.
Detailed token usage metrics for the current operation.
Contains comprehensive token consumption data including total usage, input token breakdown with cache statistics, and output token categorization by generation type. This component-level tracking enables precise analysis of resource utilization for specific agent operations such as schema generation, test writing, or code implementation.
The token usage data helps identify optimization opportunities, monitor operational costs, and ensure efficient use of AI resources throughout the automated backend development process.
Total number of items to process.
Represents the complete count of operations, files, endpoints, or other entities that need to be processed in the current workflow step. This value is typically determined at the beginning of an operation and remains constant throughout the process.
Used together with the completed field to calculate progress percentage
and estimate time to completion.
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", "prismaSchemas", "interfaceOperations", "testScenarios"
Event fired when the Realize agent corrects and finalizes a faulty implementation file during the code generation process.
This event is triggered after the AI detects issues such as compilation errors or logic flaws in an implementation file and successfully applies corrections. The corrected implementation is then finalized and emitted as part of the application’s development process.
Unlike the initial write event, this correction event reflects the AI's self-improving feedback loop — demonstrating how it revisits and enhances previously written code to meet quality standards and business requirements.
Author
Samchon