@autobe/agent 0.17.1 → 0.19.1

package/lib/orchestrate/prisma/structures/IAutoBePrismaReviewApplication.d.ts

@@ -0,0 +1,105 @@
+import { AutoBePrisma } from "@autobe/interface";
+export interface IAutoBePrismaReviewApplication {
+    /**
+     * Reviews and validates Prisma schema modifications to ensure compliance with
+     * database design best practices and business requirements.
+     *
+     * Performs comprehensive validation of proposed schema changes including
+     * normalization compliance, relationship integrity, performance optimization,
+     * and business logic alignment. The review process ensures all modifications
+     * maintain data consistency and follow enterprise-level database standards.
+     */
+    reviewSchemaFile(props: IAutoBePrismaReviewApplication.IProps): void;
+}
+export declare namespace IAutoBePrismaReviewApplication {
+    interface IProps {
+        /**
+         * Comprehensive review analysis of the proposed schema modifications.
+         *
+         * Contains the AI agent's detailed evaluation of the schema changes,
+         * including validation of normalization compliance, relationship integrity,
+         * index optimization, and business requirement alignment. The review
+         * identifies potential issues and confirms adherence to best practices.
+         *
+         * **Review Dimensions:**
+         *
+         * - **Normalization Validation**: Confirms 3NF compliance and proper data
+         *   structure
+         * - **Relationship Integrity**: Validates foreign key references and
+         *   cardinality
+         * - **Performance Optimization**: Reviews indexing strategy and query
+         *   patterns
+         * - **Business Logic Alignment**: Ensures schema supports all use cases
+         * - **Naming Conventions**: Verifies consistent naming patterns
+         * - **Data Type Consistency**: Confirms appropriate field types
+         * - **Temporal Field Handling**: Validates audit trail implementation
+         *
+         * **Example:**
+         *
+         *     "After reviewing the schema modifications:
+         *     1. All tables properly implement UUID primary keys
+         *     2. Foreign key relationships correctly reference existing models
+         *     3. Composite indexes optimize for common query patterns
+         *     4. Snapshot tables include proper temporal fields
+         *     5. Materialized views (mv_) contain appropriate denormalization
+         *     The schema follows all best practices and is ready for implementation."
+         */
+        review: string;
+        /**
+         * Strategic database design plan that guided the schema creation.
+         *
+         * Contains the original planning document that outlines the database
+         * architecture strategy, including table structures, relationships,
+         * normalization approach, and business requirement mapping. This plan
+         * serves as the blueprint for validating the implemented schema.
+         *
+         * **Planning Components:**
+         *
+         * - **Business Requirements**: Mapping of business needs to database
+         *   structures
+         * - **Table Design**: Entity definitions and attribute specifications
+         * - **Relationship Strategy**: Cardinality and referential integrity planning
+         * - **Normalization Approach**: Application of 1NF, 2NF, 3NF principles
+         * - **Performance Considerations**: Index strategy and query optimization
+         * - **Snapshot Architecture**: Temporal data handling and audit requirements
+         * - **Materialized Views**: Denormalization strategy for performance
+         *
+         * **Example:**
+         *
+         *     "Database Design Strategy:
+         *     Component: Sales Domain
+         *     Tables: shopping_sales, shopping_sale_snapshots, shopping_sale_units
+         *
+         *     Design Approach:
+         *     - Normalize product catalog to 3NF for data integrity
+         *     - Implement snapshot pattern for price history tracking
+         *     - Create composite indexes for product search queries
+         *     - Use materialized views for sales analytics dashboards"
+         */
+        plan: string;
+        /**
+         * Array of Prisma models that have been modified based on review feedback.
+         *
+         * Contains ONLY the models that required changes, not the entire schema.
+         * Each model represents a complete table definition with all fields,
+         * relationships, indexes, and documentation. These modifications will be
+         * applied to the models to produce the final implementation.
+         *
+         * **Model Requirements:**
+         *
+         * - **Complete Models**: Each entry must be a complete model definition
+         * - **Targeted Changes**: Only includes models that need modifications
+         * - **AST Compliance**: Follows AutoBePrisma.IModel interface structure
+         * - **Relationship Integrity**: All foreign keys reference valid models
+         * - **Index Optimization**: Strategic indexes without redundancy
+         * - **Documentation**: Comprehensive English descriptions
+         *
+         * **Notes:**
+         *
+         * - Models not included in this array remain unchanged from the models
+         * - The final schema merges these modifications with the original models
+         * - All modifications must resolve issues identified in the review
+         */
+        modifications: AutoBePrisma.IModel[];
+    }
+}

package/lib/orchestrate/prisma/structures/IAutoBePrismaSchemaApplication.d.ts

@@ -1,4 +1,5 @@
 import { AutoBePrisma } from "@autobe/interface";
+import { tags } from "typia";
 export interface IAutoBePrismaSchemaApplication {
     /**
      * Generates comprehensive Prisma schema files based on detailed requirements
@@ -17,7 +18,7 @@ export interface IAutoBePrismaSchemaApplication {
 export declare namespace IAutoBePrismaSchemaApplication {
     interface IProps {
         /**
-         * Step 1: Strategic database design analysis and planning.
+         * Strategic database design analysis and planning.
          *
          * AI analyzes the target component and business requirements to formulate a
          * comprehensive database design strategy. This planning phase is crucial
@@ -43,167 +44,56 @@ export declare namespace IAutoBePrismaSchemaApplication {
          *
          * Workflow: Component analysis → Strategic planning → Design rationale
          */
-        thinking: string;
+        plan: string;
         /**
-         * Step 2: Initial Prisma schema code implementation.
+         * Production-ready Prisma schema models generated based on the strategic
+         * plan.
          *
-         * AI generates the first working version of the Prisma schema based on the
-         * strategic plan. This draft must be syntactically correct Prisma Schema
-         * Language (PSL) code that implements all planned tables, relationships,
-         * and constraints. The schema should follow Prisma conventions while
-         * incorporating enterprise patterns like snapshot tables and materialized
-         * views.
+         * Contains a structured Abstract Syntax Tree (AST) representation of all
+         * database tables for the target component. Each model implements the
+         * planned table structure, relationships, indexes, and constraints using
+         * the AutoBePrisma.IModel interface. These models are designed to be
+         * production-ready from the initial generation, following all best
+         * practices and normalization principles.
          *
          * **Implementation Requirements:**
          *
-         * - **Exact Table Names**: Use EXACT names from targetComponent.tables (NO
-         *   CHANGES)
-         * - **Valid PSL Syntax**: Proper model blocks, field definitions, and
-         *   directives
-         * - **Primary Keys**: Always UUID type with `@id` directive
-         * - **Foreign Keys**: UUID type following {target_model}_id naming pattern
-         * - **Data Types**: uuid, string, int, double, datetime, boolean, uri (no
-         *   pre-calculated fields)
-         * - **Relationships**: Proper `@relation` directives for 1:1, 1:N, M:N
-         *   patterns
-         * - **Descriptions**: Follow format with requirements mapping and business
-         *   purpose
-         * - **NO Prohibited Fields**: No totals, cached values, aggregates in regular
-         *   tables
-         *
-         * Workflow: Strategic plan → PSL implementation → Functional schema code
-         */
-        draft: string;
-        /**
-         * Step 3: Schema code review and quality assessment.
-         *
-         * AI performs a thorough review of the draft schema implementation,
-         * examining multiple quality dimensions to ensure production readiness.
-         * This review process identifies issues, suggests improvements, and
-         * validates compliance with best practices.
-         *
-         * **Review Dimensions:**
-         *
-         * **Syntax & Compilation:**
-         *
-         * - Prisma schema syntax errors and invalid directives
-         * - Model naming matches targetComponent.tables EXACTLY
-         * - Field type appropriateness (uuid for keys, no calculated fields)
-         * - Relationship definition correctness (`@relation` syntax)
-         *
-         * **Database Design Quality:**
-         *
-         * - **Normalization Compliance**:
-         *
-         *   - 1NF: Atomic values, no repeating groups
-         *   - 2NF: No partial dependencies on composite keys
-         *   - 3NF: No transitive dependencies
-         * - **Prohibited Fields Check**: No pre-calculated totals, cached values, or
-         *   aggregates in regular tables
-         * - **Snapshot Pattern**: Proper implementation for audit trails
-         * - **Junction Tables**: Correct naming ({table1}_{table2}) and structure
-         *
-         * **Index Strategy Validation:**
-         *
-         * - NO single foreign key indexes (Prisma auto-creates these)
-         * - Composite indexes for query patterns
-         * - Unique indexes for business constraints
-         * - GIN indexes for full-text search fields
-         *
-         * **Description Quality:**
-         *
-         * - Models include: requirement mapping, business purpose, relationships,
-         *   behaviors
-         * - Fields include: requirement aspect, business meaning, normalization
-         *   rationale
-         *
-         * Workflow: Draft schema → Systematic analysis → Specific improvements
-         */
-        review: string;
-        /**
-         * Step 4: Final production-ready Prisma schema code.
-         *
-         * AI produces the final, polished version of the Prisma schema
-         * incorporating all review feedback. This code represents the completed
-         * schema implementation, ready for database migration and production
-         * deployment. All identified issues must be resolved, and the schema must
-         * meet enterprise-grade quality standards.
-         *
-         * **Final Schema Characteristics:**
-         *
-         * - **Complete Coverage**: All targetComponent.tables implemented with exact
-         *   names
-         * - **Zero Errors**: Valid PSL syntax, no compilation warnings
-         * - **Proper Relationships**: All foreign keys reference existing tables
-         *   correctly
-         * - **Optimized Indexes**: Strategic indexes without redundant foreign key
-         *   indexes
-         * - **Full Normalization**: Strict 3NF compliance, denormalization only in
-         *   mv_ tables
-         * - **Enterprise Documentation**: Complete descriptions with business context
-         * - **Audit Support**: Proper snapshot patterns and temporal fields
-         *   (created_at, updated_at, deleted_at)
-         * - **Type Safety**: Consistent use of UUID for all keys, appropriate field
-         *   types
-         *
-         * Workflow: Review feedback → Schema refinement → Production-ready PSL code
-         */
-        final: string;
-        /**
-         * Step 5: Structured AST representation of the Prisma schema models.
-         *
-         * AI transforms the final Prisma schema code into a structured Abstract
-         * Syntax Tree (AST) representation using the AutoBePrisma.IModel interface.
-         * This involves critical reinterpretation and reclassification of the final
-         * code to conform to AST constraints.
-         *
-         * **CRITICAL: Reinterpretation & Post-Processing Required**
-         *
-         * The AI-generated final code may not directly map to valid AST structures
-         * due to:
-         *
-         * - Complex Prisma directives that need decomposition
-         * - Field attributes that require reclassification
-         * - Implicit relationships that need explicit AST representation
-         * - Schema-level constructs that must be distributed to models
-         *
-         * **Required Post-Processing Steps:**
-         *
-         * 1. **Field Reclassification**: Separate fields into primary, foreign, and
-         *    plain categories
-         * 2. **Relationship Extraction**: Convert `@relation` directives to IRelation
-         *    structures
-         * 3. **Index Decomposition**: Parse `@@index`, `@@unique` into appropriate
-         *    index arrays
-         * 4. **Type Normalization**: Map Prisma types to AST type enum values
-         * 5. **Constraint Resolution**: Convert schema constraints to AST properties
-         *
-         * **AST Structure Requirements:**
-         *
-         * - **Model Array**: Each table from targetComponent.tables as IModel
-         * - **Primary Field**: Always UUID type with name "id"
-         * - **Foreign Fields**: Proper IRelation configurations for all relationships
-         * - **Plain Fields**: Business fields with correct types (no calculated
-         *   fields)
+         * - **Model Count**: Exactly matches targetComponent.tables.length (plus any
+         *   junction tables)
+         * - **Table Names**: EXACT names from targetComponent.tables - no
+         *   modifications allowed
+         * - **Primary Keys**: Always UUID type with field name "id"
+         * - **Foreign Keys**: Proper IRelation configurations for all relationships
+         * - **Business Fields**: Only raw data fields - no calculated or derived
+         *   values
+         * - **Data Types**: Limited to: uuid, string, int, double, datetime, boolean,
+         *   uri
+         * - **Relationships**: Correct patterns for 1:1, 1:N, and M:N relationships
          * - **Indexes**:
          *
          *   - UniqueIndexes: Business constraints and composite unique keys
-         *   - PlainIndexes: Query optimization (no single foreign key indexes)
-         *   - GinIndexes: Full-text search on string fields
-         * - **Material Flag**: true only for mv_ prefixed tables
-         *
-         * **Relationship Patterns in AST:**
-         *
-         * - 1:1: Foreign field with unique: true
-         * - 1:N: Foreign field with unique: false
-         * - M:N: Separate junction table model with composite indexes
-         *
-         * Workflow: Final PSL code → Reinterpretation → AST transformation →
-         * Structured models
+         *   - PlainIndexes: Multi-column query optimization (never single FK indexes)
+         *   - GinIndexes: Full-text search on appropriate string fields
+         * - **Materialized Views**: Tables prefixed with "mv_" have material flag set
+         *   to true
+         * - **Documentation**: Comprehensive English descriptions with business
+         *   context
+         *
+         * **Quality Standards:**
+         *
+         * - **Normalization**: Strict adherence to 3NF (Third Normal Form)
+         * - **No Denormalization**: Except in materialized views (mv_ tables)
+         * - **Referential Integrity**: All foreign keys reference valid existing
+         *   tables
+         * - **Temporal Fields**: Consistent created_at, updated_at, deleted_at
+         *   patterns
+         * - **Snapshot Support**: Proper historical data preservation where needed
+         * - **Performance Ready**: Optimized index strategy for expected query
+         *   patterns
          *
-         * This structured representation serves as the ultimate deliverable for
-         * programmatic schema generation and manipulation.
+         * The generated models will undergo review by a separate specialized agent
+         * to ensure compliance with all requirements and best practices.
          */
-        models: AutoBePrisma.IModel[];
+        models: AutoBePrisma.IModel[] & tags.MinItems<1>;
     }
 }

package/lib/orchestrate/realize/histories/transformRealizeAuthorization.d.ts

@@ -0,0 +1,5 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { AutoBeAnalyzeRole } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../../context/AutoBeContext";
+export declare const transformRealizeAuthorizationHistories: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, role: AutoBeAnalyzeRole) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/realize/histories/transformRealizeAuthorizationCorrectHistories.d.ts

@@ -0,0 +1,5 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { AutoBeRealizeAuthorization, IAutoBeTypeScriptCompileResult } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../../context/AutoBeContext";
+export declare const transformRealizeAuthorizationCorrectHistories: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, auth: AutoBeRealizeAuthorization, templateFiles: Record<string, string>, diagnostics: IAutoBeTypeScriptCompileResult.IDiagnostic[]) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/realize/histories/transformRealizeCorrectHistories.d.ts

@@ -0,0 +1,14 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { AutoBeRealizeAuthorization, IAutoBeTypeScriptCompileResult } from "@autobe/interface";
+import { AutoBeState } from "../../../context/AutoBeState";
+import { IAutoBeTestScenarioArtifacts } from "../../test/structures/IAutoBeTestScenarioArtifacts";
+import { IAutoBeRealizeScenarioApplication } from "../structures/IAutoBeRealizeScenarioApplication";
+export declare function transformRealizeCorrectHistories(props: {
+    state: AutoBeState;
+    scenario: IAutoBeRealizeScenarioApplication.IProps;
+    artifacts: IAutoBeTestScenarioArtifacts;
+    authorization: AutoBeRealizeAuthorization | null;
+    totalAuthorizations: AutoBeRealizeAuthorization[];
+    code: string;
+    diagnostic: IAutoBeTypeScriptCompileResult.IDiagnostic;
+}): Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/realize/histories/transformRealizeWriteAuthorizationsHistories.d.ts

@@ -0,0 +1,3 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { AutoBeOpenApi } from "@autobe/interface";
+export declare const transformRealizeWriteAuthorizationsHistories: (operation: AutoBeOpenApi.IOperation, payloads: Record<string, string>) => Array<IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/realize/histories/transformRealizeWriteHistories.d.ts

@@ -0,0 +1,14 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { AutoBeRealizeAuthorization } from "@autobe/interface";
+import { AutoBeState } from "../../../context/AutoBeState";
+import { IAutoBeTestScenarioArtifacts } from "../../test/structures/IAutoBeTestScenarioArtifacts";
+import { IAutoBeRealizeScenarioApplication } from "../structures/IAutoBeRealizeScenarioApplication";
+export declare const transformRealizeWriteHistories: (props: IProps) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;
+interface IProps {
+    state: AutoBeState;
+    scenario: IAutoBeRealizeScenarioApplication.IProps;
+    artifacts: IAutoBeTestScenarioArtifacts;
+    authorization: AutoBeRealizeAuthorization | null;
+    totalAuthorizations: AutoBeRealizeAuthorization[];
+}
+export {};

package/lib/orchestrate/realize/internal/compile.d.ts

@@ -0,0 +1,7 @@
+import { AutoBeRealizeAuthorization, AutoBeRealizeFunction, IAutoBeTypeScriptCompileResult } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../../context/AutoBeContext";
+export declare function compile<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, props: {
+    authorizations: AutoBeRealizeAuthorization[];
+    functions: AutoBeRealizeFunction[];
+}): Promise<IAutoBeTypeScriptCompileResult>;

package/lib/orchestrate/realize/orchestrateRealizeCorrect.d.ts

@@ -0,0 +1,16 @@
+import { AutoBeRealizeAuthorization, AutoBeRealizeCorrectEvent, IAutoBeTypeScriptCompileResult } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../context/AutoBeContext";
+import { IAutoBeRealizeScenarioApplication } from "./structures/IAutoBeRealizeScenarioApplication";
+export declare function orchestrateRealizeCorrect<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, props: {
+    authorization: AutoBeRealizeAuthorization | null;
+    totalAuthorizations: AutoBeRealizeAuthorization[];
+    scenario: IAutoBeRealizeScenarioApplication.IProps;
+    code: string;
+    diagnostic: IAutoBeTypeScriptCompileResult.IDiagnostic;
+    progress: IProgress;
+}): Promise<AutoBeRealizeCorrectEvent>;
+export interface IProgress {
+    total: number;
+    completed: number;
+}

package/lib/orchestrate/realize/orchestrateRealizeScenario.d.ts

@@ -0,0 +1,91 @@
+import { AutoBeOpenApi, AutoBeRealizeAuthorization } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../context/AutoBeContext";
+import { IAutoBeRealizeScenarioApplication } from "./structures/IAutoBeRealizeScenarioApplication";
+export interface IAutoBeRealizeScenario {
+    /**
+     * The name of the function to be generated.
+     *
+     * Derived from the Swagger path and method. The function name must be written
+     * in snake_case. It serves as the entry point in both code generation and
+     * test code.
+     *
+     * Once the function is generated, the function name and file name will be the
+     * same. The generated file will be located at
+     * `src/providers/${function_name}.ts`.
+     */
+    functionName: string;
+    /**
+     * Definition of path and query parameters extracted from the OpenAPI spec.
+     *
+     * Includes input values passed via URL path or query string. Used for type
+     * definitions, validation, and function signature construction.
+     */
+    parameters: AutoBeOpenApi.IParameter[];
+    /**
+     * Schema definition for the request body input.
+     *
+     * Extracted from the requestBody section of Swagger. Represents the input
+     * data passed in the body (e.g., JSON). Used for generating function
+     * arguments or DTOs.
+     */
+    inputSchema: AutoBeOpenApi.IRequestBody | null;
+    /**
+     * Schema definition for the response body.
+     *
+     * Extracted from the responses section of Swagger. Used to define the return
+     * type and expected output in test code.
+     */
+    outputSchema: AutoBeOpenApi.IResponseBody | null;
+    /**
+     * Natural language description of the function’s purpose.
+     *
+     * Extracted from the summary or description field of Swagger. Used for code
+     * documentation, test scenario generation, and conveying function intent.
+     */
+    description: string;
+    /**
+     * HTTP method information.
+     *
+     * Extracted from the Swagger operation method. Used to define the request
+     * type during code and test generation.
+     */
+    method: "get" | "post" | "put" | "delete" | "patch";
+    /**
+     * List of scenario descriptions for test code generation.
+     *
+     * Each scenario describes the expected behavior of the function under certain
+     * conditions. Used as a basis for TDD-style automated test generation.
+     */
+    testScenarios: string[];
+    /**
+     * Optional decorator event for customizing code generation behavior.
+     *
+     * Provides additional metadata or instructions that can modify how the
+     * function implementation is generated. Can include custom annotations,
+     * middleware configurations, or special handling directives that affect the
+     * final code output.
+     */
+    decoratorEvent?: AutoBeRealizeAuthorization;
+}
+/**
+ * Generates a planning result that defines what kind of function should be
+ * created, based solely on the provided Swagger (OpenAPI) operation — without
+ * using an LLM.
+ *
+ * This function analyzes the structure of the OpenAPI operation (such as the
+ * path, method, parameters, request/response schema, and descriptions) to
+ * determine the appropriate function name, input/output types, and purpose of
+ * the function.
+ *
+ * The result of this function (`RealizePlannerOutput`) will be passed to the
+ * next step in the AutoBE pipeline, which is responsible for generating the
+ * actual implementation code.
+ *
+ * @author Kakasoo
+ * @param ctx - AutoBE context including model and configuration
+ * @param operation - A single OpenAPI operation object to analyze and plan
+ * @returns A planning object containing all structural information needed to
+ *   generate the function
+ */
+export declare const orchestrateRealizeScenario: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, operation: AutoBeOpenApi.IOperation, authorization?: AutoBeRealizeAuthorization) => IAutoBeRealizeScenarioApplication.IProps;

package/lib/orchestrate/realize/orchestrateRealizeWrite.d.ts

@@ -0,0 +1,14 @@
+import { AutoBeRealizeAuthorization, AutoBeRealizeWriteEvent } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../context/AutoBeContext";
+import { IAutoBeRealizeScenarioApplication } from "./structures/IAutoBeRealizeScenarioApplication";
+export declare function orchestrateRealizeWrite<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, props: {
+    totalAuthorizations: AutoBeRealizeAuthorization[];
+    authorization: AutoBeRealizeAuthorization | null;
+    scenario: IAutoBeRealizeScenarioApplication.IProps;
+    progress: IProgress;
+}): Promise<AutoBeRealizeWriteEvent>;
+export interface IProgress {
+    total: number;
+    completed: number;
+}

package/lib/orchestrate/realize/structures/IAutoBeRealizeAuthorizationApplication.d.ts

@@ -1,3 +1,4 @@
+import { CamelPattern, PascalPattern } from "@autobe/interface";
 export interface IAutoBeRealizeAuthorizationApplication {
     createDecorator: (next: IAutoBeRealizeAuthorizationApplication.IProps) => void;
 }
@@ -32,8 +33,10 @@ export declare namespace IAutoBeRealizeAuthorizationApplication {
          * format (e.g., adminAuthorize, userAuthorize). This function will be
          * called by the decorator to verify JWT tokens and return authenticated
          * user information for the specified role.
+         *
+         * DO: Use camelCase naming convention.
          */
-        name: string;
+        name: string & CamelPattern;
         /**
          * Complete TypeScript code for the authentication Provider function. Must
          * include: JWT token verification using jwtAuthorize function, role type
@@ -51,8 +54,10 @@ export declare namespace IAutoBeRealizeAuthorizationApplication {
          * decorator in Controller methods to automatically authenticate and
          * authorize users for the specific role, injecting the authenticated user
          * payload as a method parameter.
+         *
+         * DO: Use PascalCase naming convention.
          */
-        name: string;
+        name: string & PascalPattern;
         /**
          * Complete TypeScript code for the authentication Decorator implementation.
          * Must include: SwaggerCustomizer integration to add bearer token security
@@ -69,8 +74,10 @@ export declare namespace IAutoBeRealizeAuthorizationApplication {
          * (e.g., AdminPayload, UserPayload). This type defines the structure of the
          * authenticated user data that will be injected into Controller methods
          * when using the decorator.
+         *
+         * DO: Use PascalCase naming convention.
          */
-        name: string;
+        name: string & PascalPattern;
         /**
          * Complete TypeScript code for the Payload type interface in {Role}Payload
          * format (e.g., AdminPayload, UserPayload). Must include: id field with

package/lib/orchestrate/realize/structures/IAutoBeRealizeCorrectApplication.d.ts

@@ -0,0 +1,79 @@
+import { IAutoBeRealizeWriteApplication } from "./IAutoBeRealizeWriteApplication";
+export interface IAutoBeRealizeCorrectApplication {
+    review: (props: IAutoBeRealizeCorrectApplication.IProps) => void;
+}
+export declare namespace IAutoBeRealizeCorrectApplication {
+    interface IProps extends IAutoBeRealizeWriteApplication.IProps {
+        /**
+         * Compilation Error Analysis and Resolution Strategy
+         *
+         * This field contains a detailed analysis of TypeScript compilation errors
+         * that occurred during the previous compilation attempt, along with
+         * specific strategies to resolve each error.
+         *
+         * The analysis MUST include:
+         *
+         * 📊 ERROR BREAKDOWN:
+         *
+         * - List of all TypeScript error codes encountered (e.g., TS2339, TS2345)
+         * - Exact error messages and the lines/files where they occurred
+         * - Categorization of errors by type (type mismatch, missing property, etc.)
+         *
+         * 🔍 ROOT CAUSE ANALYSIS:
+         *
+         * - Why each error occurred (e.g., incorrect type assumptions, missing
+         *   fields)
+         * - Relationship between errors (e.g., cascading errors from a single issue)
+         * - Common patterns identified across multiple errors
+         *
+         * 🛠 RESOLUTION STRATEGY:
+         *
+         * - Specific fixes for each error type
+         * - Priority order for addressing errors (fix critical errors first)
+         * - Alternative approaches if the direct fix is not possible
+         *
+         * 📝 SCHEMA VERIFICATION:
+         *
+         * - Re-verification of Prisma schema fields actually available
+         * - Identification of assumed fields that don't exist
+         * - Correct field types and relationships
+         *
+         * ⚠️ COMMON ERROR PATTERNS TO CHECK:
+         *
+         * - Using non-existent fields (e.g., deleted_at, created_by)
+         * - Type mismatches in Prisma operations
+         * - Incorrect date handling (using Date instead of string)
+         * - Missing required fields in create/update operations
+         * - Incorrect relation handling in nested operations
+         *
+         * 🎯 CORRECTION APPROACH:
+         *
+         * - Remove references to non-existent fields
+         * - Fix type conversions (especially dates with toISOStringSafe())
+         * - Simplify complex nested operations into separate queries
+         * - Add missing required fields
+         * - Use correct Prisma input types
+         *
+         * Example structure:
+         *
+         *     Errors Found:
+         *     1. TS2339: Property 'deleted_at' does not exist on type 'User'
+         *        - Cause: Field assumed but not in schema
+         *        - Fix: Remove all deleted_at references
+         *
+         *     2. TS2345: Type 'Date' is not assignable to type 'string'
+         *        - Cause: Direct Date assignment without conversion
+         *        - Fix: Use toISOStringSafe() for all date values
+         *
+         *     Resolution Plan:
+         *     1. First, remove all non-existent field references
+         *     2. Then, fix all date type conversions
+         *     3. Finally, adjust Prisma query structures
+         *
+         * This analysis ensures the review process addresses all compilation errors
+         * systematically and produces error-free code in the corrected
+         * implementation.
+         */
+        errorAnalysis: string;
+    }
+}