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
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.
Function calling trial statistics for the operation.
Records the complete trial history of function calling attempts, tracking total executions, successful completions, consent requests, validation failures, and invalid JSON responses. These metrics reveal the reliability and quality of AI agent autonomous operation with tool usage.
Trial statistics are critical for identifying operations where agents struggle with tool interfaces, generate invalid outputs, or require multiple correction attempts through self-healing spiral loops. High failure rates indicate opportunities for system prompt optimization or tool interface improvements.
Observation of the current type and its documentation.
Describes what was observed about the type: the current definition, JSDoc content, database hints, and naming patterns. This is the first step in the Chain-of-Thought reasoning process.
The original schema definition before refinement.
Contains the potentially degenerate schema (typically a primitive like
string, number, boolean, or integer) that is being evaluated.
This preserves the original state for comparison and audit purposes.
Reasoning about whether the type is degenerate.
Analyzes the observations and explains the logical reasoning for the decision. This is the second step in the Chain-of-Thought process.
The refined object schema that replaces the degenerate primitive.
Contains the proper object schema definition that accurately represents
the data structure described in the documentation. The refined schema
is always an object type (including Record<K,V> patterns via
additionalProperties).
If null, the agent determined that the original type was intentional
and correct (e.g., type IUserId = string is a valid semantic alias).
Current iteration number of the schema refinement process.
Indicates which pass of refinement is being performed, helping track the iterative improvement process.
Detailed token usage metrics for the operation.
Contains comprehensive token consumption data including total usage, input token breakdown with cache hit rates, and output token categorization by generation type (reasoning, predictions). This component-level tracking enables precise cost analysis and identification of operations that benefit most from prompt caching or require optimization.
Token usage directly translates to operational costs, making this metric essential for understanding the financial implications of different operation types and guiding resource allocation decisions.
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", "databaseSchema", "interfaceOperation", "testScenario"
Type name of the schema being analyzed for refinement.
The name of the DTO type alias that may be incorrectly defined as a primitive and potentially needs refinement into a proper structured schema.
Final verdict on whether to refine the type.
States the conclusion clearly: whether this is a degenerate type needing refinement or a valid primitive alias. This is the final step in the Chain-of-Thought process.
Event emitted when a degenerate primitive type alias is analyzed and potentially refined into a proper structured schema.
This event is dispatched during the Interface phase when the Schema Refine agent analyzes type aliases that may have been incorrectly simplified to primitive types (
string,number,boolean,integer) when they should be complex structures like objects or records.The agent uses Chain-of-Thought reasoning (observation → reasoning → verdict) to systematically evaluate each type before making a refinement decision.
Common violations detected:
numberstringAuthor
Samchon