Analysis of the actor's authentication requirements and schema context.
Documents the agent's understanding of the actor type (guest/member/admin), what authentication fields exist in the database schema, what additional authentication features are supported by the schema, and what operations are appropriate for this actor kind.
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.
Array of API operations being defined for the endpoints.
Contains the detailed AutoBeOpenApi.IOperation specifications that define the business logic, parameters, responses, and behavior for each API function. Each operation includes comprehensive documentation, request/response schemas, error handling specifications, and security requirements that transform basic endpoints into complete API contracts.
The operations ensure that every API function has clear behavioral definitions, proper validation rules, and comprehensive documentation that enables accurate implementation and reliable client integration throughout the application ecosystem.
Rationale for the authorization operation design decisions.
Explains why specific operations were included or excluded, how the actor kind influenced the essential operations selection (e.g., why guests don't have login), what schema fields enabled additional operations, and why certain authentication patterns were chosen.
Iteration number of the requirements analysis this operation definition was performed for.
Indicates which version of the requirements analysis this operation design reflects. This step number ensures that the API operations are aligned with the current requirements and helps track the evolution of API functionality as business requirements change.
The step value enables proper synchronization between operation definitions and the underlying requirements, ensuring that the API behavior remains relevant to the current project scope and business objectives.
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"
Event emitted during the API authorization and security design phase.
This event is triggered when the Interface Agent is defining authorization and security configurations for API operations. It represents the process of establishing access control, authentication requirements, and security policies for each API endpoint, ensuring that the generated backend application implements proper security measures.
The authorization phase transforms basic API endpoints into secure, production-ready operations by adding authentication schemes, authorization rules, and security headers. This critical step ensures that sensitive business operations are properly protected and that the API adheres to security best practices and compliance requirements.
By extending multiple base interfaces, this event provides comprehensive tracking capabilities including progress monitoring for batch operation processing and token usage analytics for cost optimization.
Author
Michael