JWT-based authentication and authorization operations generated for each user role.
Contains role-specific authentication API operations including essential flows (join, login, validate, changePassword, refresh) plus additional operations based on Prisma schema capabilities like email verification and password reset. These operations are generated by analyzing the database schema to determine which authentication features are supported for each role.
ISO 8601 timestamp indicating when the API design process was completed.
Marks the exact moment when the Interface agent finished the complete transformation pipeline from AST construction through OpenAPI validation to NestJS code generation. This timestamp is crucial for tracking the development timeline and determining the currency of the API design relative to other development artifacts.
ISO 8601 timestamp indicating when this history record was created.
Marks the exact moment when this history entry was initiated or when the corresponding agent activity began. This timestamp is fundamental for maintaining chronological order, tracking development progress, and understanding the temporal relationships between different phases of the vibe coding process.
The constructed OpenAPI document containing the complete API specification.
Contains the validated AutoBeOpenApi.IDocument AST structure that defines all API endpoints, operations, schemas, and business logic. This document serves as the source of truth for API generation and ensures perfect alignment between database schemas and API interfaces.
The document includes comprehensive business logic integration, type safety bridges with Prisma schemas, and security pattern validation to ensure enterprise-grade API specifications.
Unique identifier for this history record.
A UUID that uniquely identifies this specific history entry within the system. This identifier enables precise referencing, cross-linking between related history records, and maintaining referential integrity across the development timeline and different agent activities.
Reason why the Interface agent was activated through function calling.
Explains the specific circumstances that triggered the AI chatbot to invoke the Interface agent via function calling. This could include reasons such as completing initial API design after database schema creation, updating API specifications due to requirement changes, or regenerating interfaces to reflect modified data models.
Iteration number of the requirements analysis report this API design was performed for.
Indicates which version of the requirements analysis this API design reflects. If this value is lower than AutoBeAnalyzeHistory.step, it means the API design has not yet been updated to reflect the latest requirements and may need to be regenerated.
A value of 0 indicates the initial API design, while higher values represent subsequent revisions based on updated requirements or database schema changes.
Type discriminator indicating the specific kind of history record.
Provides type-safe discrimination between different history record types such as "analyze", "prisma", "interface", "test", "realize", "userMessage", and "assistantMessage". This enables proper type narrowing and ensures that history records are processed according to their specific characteristics and requirements.
History record generated when the Interface agent completes RESTful API design based on the previous requirements analysis report and database design.
The Interface agent constructs data of type AutoBeOpenApi.IDocument through AI function calling, validates it, and stores it in the document property. This is then converted to a formal OpenAPI document, and NestJS API controllers, DTOs, and e2e test code are generated through the sophisticated multi-stage transformation pipeline.
The Interface agent operates on the same vibe coding principles as other agents, ensuring that API designs are syntactically perfect and semantically aligned with business requirements before any code generation occurs.
Author
Samchon