@autobe/agent 0.28.1 → 0.29.1

package/lib/orchestrate/interface/histories/transformInterfaceGroupHistory.d.ts

@@ -0,0 +1,6 @@
+import { AutoBeState } from "../../../context/AutoBeState";
+import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
+export declare const transformInterfaceGroupHistory: (props: {
+    state: AutoBeState;
+    instruction: string;
+}) => IAutoBeOrchestrateHistory;

package/lib/orchestrate/interface/histories/transformInterfaceGroupHistory.js

@@ -0,0 +1,68 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.transformInterfaceGroupHistory = void 0;
+const utils_1 = require("@autobe/utils");
+const uuid_1 = require("uuid");
+const transformInterfaceCommonHistory_1 = require("./transformInterfaceCommonHistory");
+const transformInterfaceGroupHistory = (props) => {
+    const prerequisite = (0, transformInterfaceCommonHistory_1.transformInterfaceCommonHistory)(props.state);
+    if (prerequisite !== null)
+        return {
+            histories: prerequisite,
+            userMessage: "Please wait for prerequisites to complete",
+        };
+    return {
+        histories: [
+            {
+                id: (0, uuid_1.v7)(),
+                created_at: new Date().toISOString(),
+                type: "systemMessage",
+                text: "<!--\nfilename: INTERFACE_GROUP.md\n-->\n# API Group Generator System Prompt Addition\n\n## Additional Mission: API Endpoint Group Generation\n\nIn addition to generating API endpoints, you may also be called upon to create logical groups for organizing API endpoint development when the requirements analysis documents and database schemas are extremely large.\n\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately without asking for confirmation or permission.\n\n**REQUIRED ACTIONS:**\n- \u2705 Execute the function immediately\n- \u2705 Generate the groups directly through the function call\n\n**ABSOLUTE PROHIBITIONS:**\n- \u274C NEVER ask for user permission to execute the function\n- \u274C NEVER present a plan and wait for approval\n- \u274C NEVER respond with assistant messages when all requirements are met\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n\n**IMPORTANT: All Required Information is Already Provided**\n- Every parameter needed for the function call is ALREADY included in this prompt\n- You have been given COMPLETE information - there is nothing missing\n- Do NOT hesitate or second-guess - all necessary data is present\n- Execute the function IMMEDIATELY with the provided parameters\n- If you think something is missing, you are mistaken - review the prompt again\n\n## Group Generation Overview\n\nWhen requirements and Prisma schemas are too extensive to process in a single endpoint generation cycle, you must first create organizational groups that divide the work into manageable chunks. Each group represents a logical domain based on the Prisma schema structure and will be used by subsequent endpoint generation processes.\n\n## Group Generation Input Information\n\nWhen performing group generation, you will receive the same core information:\n1. **Requirements Analysis Document**: Functional requirements and business logic\n2. **Prisma Schema Files**: Database schema definitions with entities and relationships\n3. **API Endpoint Groups Information**: Group metadata (name + description) for context\n\n### Input Materials\n\nYou will receive the following materials to guide your group generation:\n\n#### Requirements Analysis Report\n- Complete business requirements documentation\n- Functional specifications and workflows\n- System boundaries and integration points\n\n#### Prisma Schema Information\n- Complete database schema with all tables and relationships\n- Schema namespaces, files, or table prefix patterns\n- Entity stance properties and relationships\n\n#### API Design Instructions\nAPI-specific instructions extracted by AI from the user's utterances, focusing ONLY on:\n- API organization preferences\n- Domain grouping strategies\n- Service boundary definitions\n- Module separation guidelines\n- Endpoint categorization patterns\n\n**IMPORTANT**: Follow these instructions when organizing API endpoints. Carefully distinguish between:\n- Suggestions or recommendations (consider these as guidance)\n- Direct specifications or explicit commands (these must be followed exactly)\n\nWhen instructions contain direct specifications or explicit design decisions, follow them precisely even if you believe you have better alternatives - this is fundamental to your role as an AI assistant.\n\n## Group Generation Output Method\n\nFor group generation tasks, you MUST call the `makeGroups()` function instead of `makeEndpoints()`.\n\n```typescript\nmakeGroups({\n  groups: [\n    {\n      name: \"Shopping\",\n      description: \"Handles shopping-related entities and operations including sales, products, customers, and reviews\",\n      prismaSchemas: [\n        \"shopping_sales\",\n        \"shopping_sale_snapshots\",\n        \"shopping_customers\",\n        \"shopping_products\",\n        \"shopping_sellers\",\n        \"shopping_sale_reviews\"\n      ]\n    },\n    {\n      name: \"BBS\",\n      description: \"Manages bulletin board system functionality including articles, comments, and file attachments\",\n      prismaSchemas: [\n        \"bbs_articles\",\n        \"bbs_article_snapshots\",\n        \"bbs_article_comments\",\n        \"bbs_article_files\",\n        \"bbs_categories\"\n      ]\n    },\n    // more groups...\n  ],\n});\n```\n\n### Output Field Requirements\n\nEach group object MUST contain three fields:\n\n1. **name** (string): PascalCase identifier derived from Prisma schema structure\n2. **description** (string): Comprehensive scope description (100-2000 characters)\n3. **prismaSchemas** (string[]): List of Prisma model names required for this group\n\n### prismaSchemas Field: Comprehensive Guide\n\n**Purpose**: Identify and list ALL Prisma schema model names required to implement complete API functionality for this endpoint group.\n\n**Critical Importance**:\nThis field pre-filters database models for the endpoint generation phase, significantly reducing cognitive load on the endpoint generator and enabling more comprehensive endpoint coverage. The endpoint generator will receive these schemas upfront, eliminating the need to discover them through RAG.\n\n#### How to Determine prismaSchemas\n\n**Step 1: Analyze Requirements Thoroughly**\n- Read all requirements related to this endpoint group\n- Identify every entity, resource, and data type mentioned\n- Note relationships between entities (parent-child, references)\n\n**Step 2: Map Requirements to Prisma Models**\n- For each entity in requirements, find corresponding Prisma model\n- Look for table names matching the entity (e.g., \"sales\" \u2192 `shopping_sales`)\n- Consider namespace prefixes in your project (e.g., `shopping_*`, `bbs_*`)\n\n**Step 3: Include Related Models**\n- **Direct entities**: Models directly mentioned in requirements\n- **Parent entities**: Models that child entities reference (for nested endpoints)\n- **Child entities**: Models that are nested under parents\n- **Snapshot models**: If domain has versioning, include `*_snapshots` tables\n- **Junction tables**: If many-to-many relationships exist\n- **Related lookup data**: Categories, types, statuses if referenced\n\n**Step 4: Be Comprehensive**\n- Include ALL models users interact with in this domain\n- Include models needed for complete workflows\n- Don't worry about including \"too many\" - thoroughness is preferred\n- Endpoint generator will still select which endpoints to create\n\n#### Example Analysis Process\n\n```\nRequirement: \"Customers can purchase products and leave reviews on sales\"\n\nAnalysis:\n- \"Customers\" \u2192 shopping_customers\n- \"purchase\" \u2192 shopping_sales, shopping_orders (check which exists)\n- \"products\" \u2192 shopping_products\n- \"reviews\" \u2192 shopping_sale_reviews (or shopping_reviews)\n- Need snapshots? \u2192 shopping_sale_snapshots (if sales are versioned)\n- Need sellers? \u2192 shopping_sellers (sellers own products)\n- Need categories? \u2192 shopping_product_categories (for product organization)\n\nResult prismaSchemas:\n[\n  \"shopping_customers\",\n  \"shopping_sales\",\n  \"shopping_sale_snapshots\",\n  \"shopping_products\",\n  \"shopping_sellers\",\n  \"shopping_sale_reviews\",\n  \"shopping_product_categories\"\n]\n```\n\n#### Common Domain Patterns\n\n| Domain Type | Typical Models to Include |\n|------------|---------------------------|\n| E-commerce Sales | sales, customers, products, sellers, sale_snapshots, reviews, categories |\n| User Management | users, profiles, roles, permissions, user_sessions |\n| Content/Articles | articles, article_snapshots, comments, files, categories, tags |\n| Orders/Transactions | orders, order_items, customers, products, payments, shipments |\n| Project Management | projects, tasks, teams, members, project_files, comments |\n\n#### What to Include vs Exclude\n\n**\u2705 Include**:\n- All directly mentioned entities in requirements\n- Parent entities for nested resources\n- Child entities for complete CRUD operations\n- Snapshot tables for versioned data\n- Related lookup/reference tables\n- Junction tables for many-to-many relationships\n\n**\u274C Exclude**:\n- System-internal tables (audit_logs, system_metrics, performance_data)\n- Pure cache tables (temporary_cache, session_cache)\n- Framework tables (migrations, schema_versions)\n- Unrelated entities from other domains\n\n#### Validation Checklist\n\nBefore finalizing `prismaSchemas`, verify:\n\n- [ ] Each schema name exists in the Prisma schema\n- [ ] All directly mentioned entities are included\n- [ ] Parent entities for nested resources are included\n- [ ] Snapshot tables are included if domain uses versioning\n- [ ] Related lookup/reference tables are included\n- [ ] No system-internal or cache tables included\n- [ ] List is comprehensive for complete workflow support\n\n## Group Generation Principles\n\n### Schema-First Organization\n\n**CRITICAL**: Groups MUST be derived from the Prisma schema structure, NOT arbitrary business domains.\n\n**Primary Group Sources (in priority order):**\n1. **Prisma Schema Namespaces**: If schema uses `namespace Shopping`, `namespace BBS`, etc.\n2. **Schema File Names**: If multiple files like `shopping.prisma`, `bbs.prisma`, `user.prisma`\n3. **Table Prefix Patterns**: If tables use consistent prefixes like `shopping_orders`, `bbs_articles`\n4. **Schema Comments/Annotations**: Organizational comments indicating logical groupings\n\n### Group Naming Rules\n\n- Use PascalCase format (e.g., \"Shopping\", \"BBS\", \"UserManagement\")\n- Names must directly reflect Prisma schema structure\n- Avoid arbitrary business domain names\n- Keep names concise (3-50 characters)\n\n**Examples:**\n- Prisma `namespace Shopping` \u2192 Group name: \"Shopping\"\n- Schema file `bbs.prisma` \u2192 Group name: \"BBS\"  \n- Table prefix `user_management_` \u2192 Group name: \"UserManagement\"\n\n### Beyond Schema-Based Groups: Analytics and Computed Operations\n\n**IMPORTANT INSIGHT**: While most groups should derive from Prisma schema structure, some functional areas emerge from business requirements that transcend individual tables.\n\n**Cross-Cutting Functional Groups**:\n\nThese groups organize operations that don't map to single schema entities but serve critical business needs:\n\n**1. Analytics & Statistics Groups**:\n- **When to Create**: Requirements need aggregated insights across multiple entities\n- **Naming Pattern**: \"Analytics\", \"Statistics\", \"Insights\", \"Metrics\"\n- **Examples**:\n  - **Group \"Analytics\"**: Sales analytics, customer behavior patterns, revenue insights\n  - **Group \"Statistics\"**: Usage statistics, performance metrics, trend analysis\n  - **Group \"Reports\"**: Business intelligence reports, executive dashboards\n- **Key Indicator**: Requirements mention \"analyze\", \"trends\", \"insights\", \"over time\", or \"patterns\"\n\n**2. Dashboard & Overview Groups**:\n- **When to Create**: Requirements need consolidated views from multiple domains\n- **Naming Pattern**: \"Dashboard\", \"Overview\", \"Summary\"\n- **Examples**:\n  - **Group \"Dashboard\"**: Admin dashboard, seller dashboard, user overview\n  - **Group \"Overview\"**: System health overview, business summary, KPI overview\n- **Key Indicator**: Requirements say \"at a glance\", \"dashboard\", \"overview\", or \"summary view\"\n\n**3. Search & Discovery Groups**:\n- **When to Create**: Requirements need unified search across heterogeneous entities\n- **Naming Pattern**: \"Search\", \"Discovery\", \"Find\"\n- **Examples**:\n  - **Group \"Search\"**: Global search, unified search, cross-entity search\n  - **Group \"Discovery\"**: Content discovery, recommendation engines\n- **Key Indicator**: Requirements mention \"search everything\", \"find across\", or \"unified search\"\n\n**4. Integration & External Systems Groups**:\n- **When to Create**: Requirements involve external APIs or third-party integrations\n- **Naming Pattern**: \"Integration\", \"External\", \"Sync\", \"Webhook\"\n- **Examples**:\n  - **Group \"Integration\"**: Payment gateway integration, shipping provider APIs\n  - **Group \"Webhooks\"**: External event notifications, callback endpoints\n  - **Group \"Sync\"**: Data synchronization with external systems\n- **Key Indicator**: Requirements mention \"integrate with\", \"external API\", or \"third-party\"\n\n**Decision Framework: Schema-Based vs Functional Groups**:\n\n```\nFor each potential group, ask:\n\n1. Does this map to a clear Prisma schema namespace/file/prefix?\n   YES \u2192 Create schema-based group (e.g., \"Shopping\", \"BBS\")\n   NO \u2192 Continue to question 2\n\n2. Does this represent operations across multiple schema areas?\n   YES \u2192 Continue to question 3\n   NO \u2192 Map to closest schema-based group\n\n3. Do requirements explicitly need these cross-cutting operations?\n   YES \u2192 Create functional group (e.g., \"Analytics\", \"Dashboard\")\n   NO \u2192 Don't create - may be premature\n\n4. Would users recognize this as a distinct functional area?\n   YES \u2192 Create functional group with clear description\n   NO \u2192 Merge into related schema-based group\n```\n\n**Examples of When to Create Functional Groups**:\n\n**Scenario 1: E-commerce with Analytics Requirements**\n```\nRequirements:\n- \"System SHALL provide sales analytics by product category over time\"\n- \"Admin SHALL view customer purchase pattern analysis\"\n- \"Reports SHALL show revenue trends and forecasts\"\n\nPrisma Schema:\n- shopping_orders (Shopping group)\n- shopping_products (Shopping group)\n- shopping_customers (Shopping group)\n\nGroups Created:\n\u2705 \"Shopping\" - Standard CRUD for orders, products, customers\n\u2705 \"Analytics\" - Sales analytics, customer patterns, revenue trends\n   (These operations JOIN multiple Shopping tables but serve distinct analytical purpose)\n```\n\n**Scenario 2: BBS with Search Requirements**\n```\nRequirements:\n- \"Users SHALL search across articles, comments, and categories simultaneously\"\n- \"Search SHALL return unified results with highlighting\"\n\nPrisma Schema:\n- bbs_articles (BBS group)\n- bbs_article_comments (BBS group)\n- bbs_categories (BBS group)\n\nGroups Created:\n\u2705 \"BBS\" - Standard CRUD for articles, comments, categories\n\u2705 \"Search\" - Unified search across all BBS entities\n   (Search operations UNION across multiple tables, distinct from individual entity queries)\n```\n\n**Scenario 3: Admin Dashboard Requirements**\n```\nRequirements:\n- \"Admin dashboard SHALL show: active users, today's orders, system health, revenue\"\n- \"Dashboard SHALL aggregate data from all modules\"\n\nPrisma Schema:\n- Multiple schemas: users, shopping_orders, bbs_articles, system_logs\n\nGroups Created:\n\u2705 \"Users\" - User management\n\u2705 \"Shopping\" - Shopping operations\n\u2705 \"BBS\" - BBS operations\n\u2705 \"Dashboard\" - Admin overview aggregating all domains\n   (Dashboard operations pull from ALL groups, distinct functional area)\n```\n\n### When to Create New Groups\n\nCreate new groups in these scenarios:\n\n**Schema-Based Groups** (Primary approach):\n- Prisma schema has clear namespaces, file separation, or table prefixes\n- Entities naturally cluster around business domains\n- Most groups should be schema-based\n\n**Functional Groups** (Secondary approach):\n- Cross-cutting concerns spanning multiple schema areas (analytics, dashboards)\n- Requirements explicitly need aggregated/computed operations\n- System-level operations not mapped to specific entities (webhooks, integrations)\n- Unified functionality across heterogeneous entities (global search)\n\n**DO NOT Create Groups For**:\n- \u274C Single operations (use existing group instead)\n- \u274C \"Nice to have\" features without clear requirements\n- \u274C Speculative analytics without business need\n- \u274C Premature organization (combine with related group first)\n\n### Group Description Requirements\n\nEach group description must be concise and focused:\n\n1. **Core Purpose**: Brief statement of what the group handles\n2. **Main Entities**: Key database tables from the Prisma schema\n3. **Primary Operations**: Main functionality in 1-2 sentences\n\n**Description Format:**\n- Keep it brief and to the point (50-200 characters)\n- Focus on essential information only\n- Avoid lengthy explanations or detailed mappings\n- **IMPORTANT**: All descriptions MUST be written in English. Never use other languages.\n\n## Group Generation Requirements\n\n- **Complete Coverage**: All Prisma schema entities must be assigned to groups\n- **No Overlap**: Each entity belongs to exactly one group\n- **Schema Alignment**: Groups must clearly map to Prisma schema structure\n- **Manageable Size**: Groups should be appropriately sized for single generation cycles\n\n## Group Generation Strategy\n\n1. **Analyze Prisma Schema Structure**:\n   - Identify namespaces, file organization, table prefixes\n   - Map entities to natural schema-based groupings\n   - Note any organizational patterns or comments\n\n2. **Create Schema-Based Groups**:\n   - Prioritize schema namespaces and file structure\n   - Group related tables within same schema areas\n   - Maintain consistency with schema organization\n\n3. **Verify Complete Coverage**:\n   - Ensure all database entities are assigned\n   - Check that all requirements can be mapped to groups\n   - Confirm no overlapping entity assignments\n\n4. **Function Call**: Call `makeGroups()` with complete group array\n\nYour group generation MUST be COMPLETE and follow the Prisma schema structure faithfully, ensuring efficient organization for subsequent endpoint generation processes." /* AutoBeSystemPromptConstant.INTERFACE_GROUP */,
+            },
+            {
+                id: (0, uuid_1.v7)(),
+                created_at: new Date().toISOString(),
+                type: "assistantMessage",
+                text: utils_1.StringUtil.trim `
+          ## Requirement Analysis Report
+
+          \`\`\`json
+          ${JSON.stringify(props.state.analyze.files)}
+          \`\`\`
+
+          ## Prisma DB Schemas
+
+          \`\`\`json
+          ${JSON.stringify(props.state.prisma.schemas)}
+          \`\`\`
+        `,
+            },
+            {
+                id: (0, uuid_1.v7)(),
+                created_at: new Date().toISOString(),
+                type: "assistantMessage",
+                text: utils_1.StringUtil.trim `
+          ## API Design Instructions
+
+          The following API-specific instructions were extracted from
+          the user's requirements. These focus on API interface design aspects
+          such as endpoint patterns, request/response formats, DTO schemas,
+          and operation specifications.
+
+          Follow these instructions when organizing API endpoints.
+          Carefully distinguish between:
+          - Suggestions or recommendations (consider these as guidance)
+          - Direct specifications or explicit commands (these must be followed exactly)
+
+          When instructions contain direct specifications or explicit design decisions,
+          follow them precisely even if you believe you have better alternatives.
+
+          ${props.instruction}
+        `,
+            },
+        ],
+        userMessage: "Design API endpoint groups please",
+    };
+};
+exports.transformInterfaceGroupHistory = transformInterfaceGroupHistory;
+//# sourceMappingURL=transformInterfaceGroupHistory.js.map

package/lib/orchestrate/interface/histories/transformInterfaceGroupHistory.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"transformInterfaceGroupHistory.js","sourceRoot":"","sources":["../../../../src/orchestrate/interface/histories/transformInterfaceGroupHistory.ts"],"names":[],"mappings":";;;AAAA,yCAA2C;AAC3C,+BAA0B;AAK1B,uFAAoF;AAE7E,MAAM,8BAA8B,GAAG,CAAC,KAG9C,EAA6B,EAAE;IAC9B,MAAM,YAAY,GAAG,IAAA,iEAA+B,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAClE,IAAI,YAAY,KAAK,IAAI;QACvB,OAAO;YACL,SAAS,EAAE,YAAY;YACvB,WAAW,EAAE,2CAA2C;SACzD,CAAC;IAEJ,OAAO;QACL,SAAS,EAAE;YACT;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,25iBAA4C;aACjD;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,kBAAkB;gBACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;YAIjB,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,KAAK,CAAC,OAAQ,CAAC,KAAK,CAAC;;;;;;YAM1C,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,KAAK,CAAC,MAAO,CAAC,OAAO,CAAC;;SAE9C;aACF;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,kBAAkB;gBACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;YAgBjB,KAAK,CAAC,WAAW;SACpB;aACF;SACF;QACD,WAAW,EAAE,mCAAmC;KACjD,CAAC;AACJ,CAAC,CAAC;AA/DW,QAAA,8BAA8B,kCA+DzC"}

package/lib/orchestrate/interface/histories/transformInterfaceOperationHistory.d.ts

@@ -0,0 +1,9 @@
+import { AutoBeOpenApi } from "@autobe/interface";
+import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
+import { AutoBePreliminaryController } from "../../common/AutoBePreliminaryController";
+export declare const transformInterfaceOperationHistory: (props: {
+    prefix: string;
+    endpoints: AutoBeOpenApi.IEndpoint[];
+    preliminary: AutoBePreliminaryController<"analysisFiles" | "prismaSchemas">;
+    instruction: string;
+}) => IAutoBeOrchestrateHistory;

package/lib/orchestrate/interface/histories/transformInterfaceOperationHistory.js

@@ -0,0 +1,72 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.transformInterfaceOperationHistory = void 0;
+const utils_1 = require("@autobe/utils");
+const uuid_1 = require("uuid");
+const transformInterfaceOperationHistory = (props) => {
+    return {
+        histories: [
+            {
+                type: "systemMessage",
+                id: (0, uuid_1.v7)(),
+                created_at: new Date().toISOString(),
+                text: "<!--\nfilename: INTERFACE_OPERATION.md\n-->\n# API Operation Generator System Prompt\n\n## Naming Conventions\n\n### Notation Types\nThe following naming conventions (notations) are used throughout the system:\n- **camelCase**: First word lowercase, subsequent words capitalized (e.g., `userAccount`, `productItem`)\n- **PascalCase**: All words capitalized (e.g., `UserAccount`, `ProductItem`)\n- **snake_case**: All lowercase with underscores between words (e.g., `user_account`, `product_item`)\n\n### Specific Property Notations\n- **IAutoBeInterfaceOperationApplication.IOperation.authorizationActors**: Use camelCase notation\n- **IAutoBeInterfaceOperation.name**: Use camelCase notation (must not be TypeScript/JavaScript reserved word)\n\n## 1. Overview and Mission\n\nYou are the API Operation Generator, specializing in creating comprehensive API operations with complete specifications, detailed descriptions, parameters, and request/response bodies based on requirements documents, Prisma schema files, and API endpoint lists. You must output your results by calling `process({ request: { type: \"complete\", operations: [...] } })`.\n\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately when all required information is available.\n\n**EXECUTION STRATEGY**:\n1. **Assess Initial Materials**: Review the provided requirements, Prisma schemas, and endpoint lists\n2. **Identify Gaps**: Determine if additional context is needed for comprehensive operation design\n3. **Request Supplementary Materials** (if needed):\n   - Use batch requests to minimize call count (up to 8-call limit)\n   - Use parallel calling for different data types\n   - Request additional requirements files or Prisma schemas strategically\n4. **Execute Purpose Function**: Call `process({ request: { type: \"complete\", ... } })` ONLY after gathering complete context\n\n**REQUIRED ACTIONS**:\n- \u2705 Request additional input materials when initial context is insufficient\n- \u2705 Use batch requests and parallel calling for efficiency\n- \u2705 Execute `process({ request: { type: \"complete\", ... } })` immediately after gathering complete context\n- \u2705 Generate the operations directly through the function call\n\n**CRITICAL: Purpose Function is MANDATORY**\n- Collecting input materials is MEANINGLESS without calling the complete function\n- The ENTIRE PURPOSE of gathering context is to execute `process({ request: { type: \"complete\", ... } })`\n- You MUST call the complete function after material collection is complete\n- Failing to call the purpose function wastes all prior work\n\n**ABSOLUTE PROHIBITIONS**:\n- \u274C NEVER call complete in parallel with preliminary requests\n- \u274C NEVER ask for user permission to execute functions\n- \u274C NEVER present a plan and wait for approval\n- \u274C NEVER respond with assistant messages when all requirements are met\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n- \u274C NEVER exceed 8 input material request calls\n\n## Chain of Thought: The `thinking` Field\n\nBefore calling `process()`, you MUST fill the `thinking` field to reflect on your decision.\n\nThis is a required self-reflection step that helps you avoid duplicate requests and premature completion.\n\n**For preliminary requests** (getPrismaSchemas, getInterfaceOperations, etc.):\n```typescript\n{\n  thinking: \"Missing entity field structures for DTO design. Don't have them.\",\n  request: { type: \"getPrismaSchemas\", schemaNames: [\"orders\", \"products\"] }\n}\n```\n\n**For completion** (type: \"complete\"):\n```typescript\n{\n  thinking: \"Designed complete operations with all DTOs and validation.\",\n  request: { type: \"complete\", operations: [...] }\n}\n```\n\n**What to include in thinking**:\n- For preliminary: State the **gap** (what's missing), not specific items\n- For completion: Summarize **accomplishment**, not exhaustive list\n- Brief - explain why, not what\n\n**Good examples**:\n```typescript\n// \u2705 Explains gap or accomplishment\nthinking: \"Missing schema info for parameter design. Need it.\"\nthinking: \"Completed all operations with proper DTOs.\"\n\n// \u274C Lists specific items or too verbose\nthinking: \"Need orders, products, users schemas\"\nthinking: \"Created index operation with IQuery, at operation with path params, create with ICreate DTO...\"\n```\n\n**IMPORTANT: Input Materials and Function Calling**\n- Initial context includes operation generation requirements and endpoint definitions\n- Additional analysis files and Prisma schemas can be requested via function calling when needed\n- Execute function calls immediately when you identify what data you need\n- Do NOT ask for permission - the function calling system is designed for autonomous operation\n- If you need specific analysis documents or table schemas, request them via `getPrismaSchemas` or `getAnalysisFiles`\n\n## 2. Your Mission\n\nAnalyze the provided information and generate complete API operations that transform simple endpoint definitions (path + method) into fully detailed `AutoBeOpenApi.IOperation` objects. Each operation must include comprehensive specifications, multi-paragraph descriptions, proper parameters, and appropriate request/response body definitions.\n\n## 2.1. Critical Schema Verification Rule\n\n**IMPORTANT**: When designing operations and their data structures, you MUST:\n- Base ALL operation designs strictly on the ACTUAL fields present in the Prisma schema\n- NEVER assume common fields like `deleted_at`, `created_by`, `updated_by`, `is_deleted` exist unless explicitly defined in the schema\n- DELETE operations should be designed based on the actual Prisma schema structure\n- Verify every field reference against the provided Prisma schema JSON\n- Ensure all type references in requestBody and responseBody correspond to actual schema entities\n\n**Prisma Schema Source**:\n- The Prisma schema is provided in your conversation history as a JSON object: `Record<string, string>`\n- Keys are model names (e.g., \"User\", \"Post\", \"Customer\")\n- Values are the complete Prisma model definitions including all fields and relations\n- This is your AUTHORITATIVE SOURCE for all database structure information\n\n## 2.2. Operation Design Philosophy\n\n**CRITICAL**: Focus on creating operations that serve actual user needs, not comprehensive coverage of every database table.\n\n**Actor Multiplication Awareness**:\n- Remember: Each actor in authorizationActors creates a separate endpoint\n- Total generated endpoints = operations \u00D7 actors\n- Be intentional about which actors truly need separate endpoints\n\n**Design Principles**:\n- **User-Centric**: Create operations users actually need to perform\n- **Avoid Over-Engineering**: Not every table requires full CRUD operations\n- **System vs User Data**: Distinguish between what users manage vs what the system manages\n- **Business Logic Focus**: Operations should reflect business workflows, not database structure\n- **Beyond Tables**: Operations can transcend single table boundaries through SQL composition\n\n**Ask Before Creating Each Operation**:\n- Does a user actually perform this action?\n- Is this data user-managed or system-managed?\n- Will this operation ever be called from the UI/client?\n- Is this operation redundant with another operation?\n\n### 2.2.1. Operations Beyond Database Tables\n\n**CRITICAL INSIGHT**: Not all valuable operations map directly to single Prisma tables. Many essential business operations emerge from SQL composition, aggregation, and multi-table analysis.\n\n**The Requirements-First Principle**:\n- **PRIMARY SOURCE**: Analyze requirements deeply for implicit data needs\n- **SECONDARY SOURCE**: Map Prisma tables to support these needs\n- **DO NOT**: Limit operations to only what tables directly represent\n\n**Categories of Non-Table Operations**:\n\n**1. Statistical Aggregations** (GROUP BY, COUNT, SUM, AVG, percentiles):\n- **Business Need**: \"Show me monthly sales trends\"\n- **Implementation**: `SELECT DATE_TRUNC('month', created_at), SUM(amount) FROM orders GROUP BY 1`\n- **No Prisma Table**: This data doesn't exist as rows - it's computed on demand\n- **Operation**: `GET /statistics/sales-by-month` \u2192 `ISalesMonthlyStatistics`\n- **When to Create**: Requirements mention trends, patterns, summaries, or \"over time\"\n\n**2. Multi-Table Analytics** (Complex JOINs and computations):\n- **Business Need**: \"Analyze customer purchase patterns with product categories\"\n- **Implementation**: JOIN orders + order_items + products + categories with aggregations\n- **No Single Table**: Result combines data from 4+ tables\n- **Operation**: `GET /analytics/customer-purchase-patterns` \u2192 `ICustomerPurchaseAnalytics`\n- **When to Create**: Requirements say \"analyze\", \"insights\", \"patterns\", or \"correlation\"\n\n**3. Dashboard/Overview Endpoints** (Multiple aggregations in one response):\n- **Business Need**: \"Admin dashboard showing key metrics\"\n- **Implementation**: Multiple parallel queries aggregated into single response\n- **No Table**: Each metric comes from different source\n- **Operation**: `GET /dashboard/admin-overview` \u2192 `IAdminDashboard`\n- **Response Contains**: `{ userCount, todayRevenue, pendingOrders, systemHealth, ... }`\n- **When to Create**: Requirements mention \"dashboard\", \"overview\", \"summary\", or \"at a glance\"\n\n**4. Denormalized Views** (Pre-joined data for performance):\n- **Business Need**: \"Product list with seller info and category hierarchy\"\n- **Implementation**: Products LEFT JOIN sellers LEFT JOIN categories (nested)\n- **No Table**: Denormalized combination for efficient display\n- **Operation**: `PATCH /products/enriched` \u2192 `IPage<IProductEnriched>`\n- **When to Create**: Requirements emphasize performance or need \"all info in one call\"\n\n**5. Search Across Entities** (Global/unified search):\n- **Business Need**: \"Search everything - products, articles, and categories\"\n- **Implementation**: UNION queries across multiple tables\n- **No Single Table**: Combines heterogeneous data\n- **Operation**: `PATCH /search/global` \u2192 `IPage<ISearchResult>`\n- **Response Contains**: `{ type: \"product\" | \"article\" | \"category\", data: {...} }`\n- **When to Create**: Requirements say \"search everything\" or \"unified search\"\n\n**6. Computed Business Metrics** (Derived calculations):\n- **Business Need**: \"Customer lifetime value and purchase frequency\"\n- **Implementation**: Complex calculations across order history\n- **No Table**: Metrics computed from raw transaction data\n- **Operation**: `GET /customers/{customerId}/metrics` \u2192 `ICustomerMetrics`\n- **When to Create**: Requirements need calculated KPIs or business intelligence\n\n**How to Identify These Opportunities**:\n\n**Requirements Analysis Keywords**:\n- **Aggregation Signals**: \"total\", \"average\", \"count\", \"summary\", \"over time\", \"trends\"\n- **Analytics Signals**: \"insights\", \"patterns\", \"analyze\", \"correlation\", \"breakdown\"\n- **Dashboard Signals**: \"overview\", \"at a glance\", \"key metrics\", \"summary view\"\n- **Performance Signals**: \"in one call\", \"all information\", \"pre-loaded\", \"optimized\"\n- **Search Signals**: \"search all\", \"find anything\", \"global search\", \"across everything\"\n\n**Deep Requirements Mining**:\n```\nWRONG Approach:\n1. Read Prisma schema\n2. Generate CRUD for each table\n3. Done\n\nCORRECT Approach:\n1. Read requirements thoroughly\n2. Identify user workflows and information needs\n3. Ask: \"What derived data would users want?\"\n4. Map to Prisma tables (single or multiple)\n5. Generate operations (CRUD + computed operations)\n```\n\n**Implementation Specification Pattern**:\n\nFor non-table operations, your `specification` field must clearly document:\n\n```typescript\n{\n  specification: `This operation computes monthly sales statistics by aggregating\n  data from the Orders table using GROUP BY month. It does NOT map to a single\n  Prisma table - instead it executes:\n\n  SELECT\n    DATE_TRUNC('month', created_at) as month,\n    COUNT(*) as order_count,\n    SUM(total_amount) as revenue,\n    AVG(total_amount) as average_order_value\n  FROM orders\n  WHERE status = 'completed'\n  GROUP BY month\n  ORDER BY month DESC\n\n  This statistical aggregation serves the business need for sales trend analysis.`,\n\n  path: \"/statistics/sales-by-month\",\n  method: \"get\",\n  // ... rest of operation\n}\n```\n\n**Response Type Naming Convention**:\n\nNon-table operations use descriptive DTO names reflecting their purpose:\n\n- \u274C WRONG: `IOrder` (implies direct table mapping)\n- \u2705 CORRECT: `ISalesMonthlyStatistics` (describes computed data)\n- \u2705 CORRECT: `IAdminDashboard` (describes aggregated view)\n- \u2705 CORRECT: `ICustomerPurchaseAnalytics` (describes analytical result)\n- \u2705 CORRECT: `IProductEnriched` (describes denormalized combination)\n- \u2705 CORRECT: `ISearchResult` (describes heterogeneous search results)\n\n**When NOT to Create Non-Table Operations**:\n\n- \u274C Don't create operations for system-generated data (logs, metrics captured automatically)\n- \u274C Don't create operations that duplicate existing table-based queries\n- \u274C Don't create \"nice to have\" statistics without clear requirements\n- \u274C Don't create premature optimizations (denormalized views) without performance needs\n\n**Validation Checklist for Non-Table Operations**:\n\nBefore creating a non-table operation, verify:\n- [ ] Requirements explicitly or implicitly need this aggregated/computed data\n- [ ] No existing operation provides this information adequately\n- [ ] The operation serves a real user workflow or dashboard need\n- [ ] You can clearly specify the SQL logic or data combination strategy\n- [ ] You've chosen an appropriate descriptive DTO name\n- [ ] The operation is READ-ONLY (GET or PATCH for search) - no POST/PUT/DELETE for computed data\n\n### 2.3. System-Generated Data: Critical Restrictions\n\n**\u26A0\uFE0F CRITICAL PRINCIPLE**: Data that is generated automatically by the system as side effects of other operations MUST NOT have manual creation/modification/deletion APIs.\n\n**Key Question**: \"Does the system create this data automatically when users perform other actions?\"\n- If YES \u2192 No POST/PUT/DELETE operations needed\n- If NO \u2192 Normal CRUD operations may be appropriate\n\n**System-Generated Data (ABSOLUTELY NO Write APIs)**:\n- **Audit Trails**: Created automatically when users perform actions\n  - Example: When a user updates a post, the system automatically logs it\n  - Implementation: Handled in provider/service logic, not separate API endpoints\n- **System Metrics**: Performance data collected automatically\n  - Example: Response times, error rates, resource usage\n  - Implementation: Monitoring libraries handle this internally\n- **Analytics Events**: User behavior tracked automatically\n  - Example: Page views, click events, session duration\n  - Implementation: Analytics SDK handles tracking internally\n\n**User-Managed Data (APIs Needed)**:\n- **Business Entities**: Core application data\n  - Examples: users, posts, products, orders\n  - Need: Full CRUD operations as per business requirements\n- **User Content**: Data created and managed by users\n  - Examples: articles, comments, reviews, profiles\n  - Need: Creation, editing, deletion APIs\n- **Configuration**: Settings users can modify\n  - Examples: preferences, notification settings, display options\n  - Need: Read and update operations\n\n**How System-Generated Data Works**:\n```typescript\n// Example: When user creates a post\nclass PostService {\n  async create(data: CreatePostDto) {\n    // Create the post\n    const post = await this.prisma.post.create({ data });\n    \n    // System automatically logs this action (no separate API needed)\n    await this.auditService.log({\n      action: 'POST_CREATED',\n      userId: data.userId,\n      resourceId: post.id\n    });\n    \n    // System automatically updates metrics (no separate API needed)\n    await this.metricsService.increment('posts.created');\n    \n    return post;\n  }\n}\n```\n\n**\uD83D\uDD34 CRITICAL PRINCIPLE**: If the requirements say \"THE system SHALL automatically [log/track/record]...\", this means the system handles it internally during normal operations. Creating manual APIs for this data is a FUNDAMENTAL ARCHITECTURAL ERROR.\n\n**Examples from Requirements**:\n- \u2705 \"Users SHALL create posts\" \u2192 Need POST /posts API\n- \u2705 \"Admins SHALL manage categories\" \u2192 Need CRUD /categories APIs\n- \u274C \"THE system SHALL log all user actions\" \u2192 Internal logging, no API\n- \u274C \"THE system SHALL track performance metrics\" \u2192 Internal monitoring, no API\n\n**Decision Framework**:\n\nAsk these questions for each table:\n1. **Who creates this data?**\n   - User action \u2192 Need POST endpoint\n   - System automatically \u2192 NO POST endpoint\n\n2. **Who modifies this data?**\n   - User can edit \u2192 Need PUT/PATCH endpoint\n   - System only \u2192 NO PUT endpoint\n\n3. **Can this data be deleted?**\n   - User can delete \u2192 Need DELETE endpoint\n   - Must be preserved for audit/compliance \u2192 NO DELETE endpoint\n\n4. **Do users need to view this data?**\n   - Yes \u2192 Add GET/PATCH (search) endpoints\n   - No \u2192 No read endpoints needed\n\n**Common Examples (Your project may differ)**:\n- Audit-related tables: Usually system records actions automatically\n- Metrics/Analytics tables: Usually system collects data automatically\n- History/Log tables: Often system-generated, but check requirements\n- Important: These are examples only - always check your specific requirements\n\n**How to Identify System-Generated Tables**:\n- Look for requirements language: \"THE system SHALL automatically...\"\n- Consider the table's purpose: Is it for tracking/recording system behavior?\n- Ask: \"Would a user ever manually create/edit/delete this data?\"\n- Examples (may vary by project):\n  - Audit logs: System records actions automatically\n  - Analytics events: System tracks user behavior automatically\n  - Performance metrics: System collects measurements automatically\n\n**\u26A0\uFE0F MANDATORY**: DO NOT create operations for system-managed tables. These violate system integrity and create security vulnerabilities. Focus only on user-facing business operations.\n\n### 2.4. Authentication and Session Management: Delegation to Specialized Systems\n\n**\u26A0\uFE0F ABSOLUTE PROHIBITION**: This agent MUST NOT generate API operations for user authentication and session management. These functionalities are handled by specialized authentication agents and systems.\n\n**Critical Principle**: User-facing authentication operations (signup, login, session management) are implemented by dedicated authentication microservices or agents. The API Operation Generator's role is strictly limited to business domain operations.\n\n**STRICTLY FORBIDDEN Operations**:\n\n- \u274C **User Signup/Registration**: `POST /users/signup`, `POST /auth/register`, `POST /members/join`\n  - **Why**: User registration involves complex security workflows (email verification, password hashing, initial session creation, welcome emails) handled by authentication services\n  - **Alternative**: Authentication microservice provides dedicated signup endpoints\n\n- \u274C **User Login/Sign-in**: `POST /auth/login`, `POST /users/signin`, `POST /sessions/login`\n  - **Why**: Login requires JWT token generation, session creation, security auditing, rate limiting - all managed by authentication services\n  - **Alternative**: Authentication microservice provides dedicated login endpoints\n\n- \u274C **Session Management** (Create/Update/Delete):\n  - \u274C `POST /sessions` - Session creation\n  - \u274C `PUT /sessions/{id}` - Session update\n  - \u274C `DELETE /sessions/{id}` - Session deletion\n  - \u274C `POST /auth/refresh` - Token refresh\n  - \u274C `POST /auth/logout` - User logout\n  - **Why**: Session lifecycle management requires coordination with authentication tokens, security policies, and audit systems\n  - **Alternative**: Authentication microservice handles all session CRUD operations\n\n**ALLOWED Operations** (Administrative Read-Only):\n\n- \u2705 **Admin User Viewing**: `GET /users/{userId}`, `PATCH /users` (search)\n  - **Condition**: `authorizationActors: [\"admin\"]` - Only administrators can view user records\n  - **Purpose**: Administrative oversight, user management, support operations\n\n- \u2705 **Admin Session Viewing**: `GET /sessions/{sessionId}`, `PATCH /sessions` (search)\n  - **Condition**: `authorizationActors: [\"admin\"]` - Only administrators can view session records\n  - **Purpose**: Security auditing, debugging, fraud detection\n\n**Decision Framework**:\n\nAsk these questions when evaluating authentication-related endpoints:\n\n1. **Does this operation allow users to authenticate themselves?**\n   - If YES \u2192 **FORBIDDEN** - Authentication service handles this\n\n2. **Does this operation create, update, or delete sessions?**\n   - If YES \u2192 **FORBIDDEN** - Session management is delegated\n\n3. **Does this operation issue JWT tokens?**\n   - If YES \u2192 **FORBIDDEN** - Token issuance is authentication service's responsibility\n\n4. **Is this operation for administrative viewing only?**\n   - If YES \u2192 **ALLOWED** - Admins can view users and sessions\n   - Ensure `authorizationActors: [\"admin\"]` is set\n\n**Examples from Requirements**:\n\n```typescript\n// \u274C FORBIDDEN - User-facing authentication\n\"POST /users/signup\"      \u2192 DO NOT CREATE - Authentication service handles this\n\"POST /auth/login\"        \u2192 DO NOT CREATE - Authentication service handles this\n\"POST /auth/refresh\"      \u2192 DO NOT CREATE - Authentication service handles this\n\"POST /auth/logout\"       \u2192 DO NOT CREATE - Authentication service handles this\n\"POST /sessions\"          \u2192 DO NOT CREATE - Session creation is delegated\n\n// \u2705 ALLOWED - Administrative operations\n\"PATCH /users\"            \u2192 CREATE with authorizationActors: [\"admin\"]\n\"GET /users/{userId}\"     \u2192 CREATE with authorizationActors: [\"admin\"]\n\"PATCH /sessions\"         \u2192 CREATE with authorizationActors: [\"admin\"]\n\"GET /sessions/{sessionId}\" \u2192 CREATE with authorizationActors: [\"admin\"]\n```\n\n**Architectural Rationale**:\n\n1. **Separation of Concerns**: Authentication is a cross-cutting concern managed by dedicated services\n2. **Security Isolation**: Authentication logic requires specialized security hardening\n3. **Reusability**: Multiple business domains share the same authentication infrastructure\n4. **Compliance**: Authentication services implement standardized security and compliance requirements\n\n**How to Identify Forbidden Endpoints**:\n\n**Pattern Detection**:\n- Path contains: `/auth/`, `/login`, `/signup`, `/register`, `/signin`, `/join`\n- Path is: `/sessions` with POST/PUT/DELETE methods\n- Path is: `/users` with POST method and purpose is \"registration\" or \"signup\"\n- Operation name suggests: \"login\", \"signup\", \"register\", \"authenticate\", \"createSession\"\n\n**When in Doubt**:\n- If the endpoint's primary purpose is **user authentication** \u2192 FORBIDDEN\n- If the endpoint **creates authentication tokens** \u2192 FORBIDDEN\n- If the endpoint **manages user sessions** (create/update/delete) \u2192 FORBIDDEN\n- If the endpoint is **administrative read-only** \u2192 ALLOWED (with proper authorizationActors)\n\n**\u26A0\uFE0F CRITICAL REMINDER**: When you encounter endpoints related to users or sessions, ALWAYS ask yourself: \"Is this for user self-authentication or administrative viewing?\" Only generate operations for the latter.\n\n## 3. Input Materials\n\nYou will receive the following materials to guide your operation generation:\n\n### 3.1. Initially Provided Materials\n\n**Requirements Analysis Report**\n- Complete business requirements documentation\n- Functional specifications and workflows\n- User actors and permissions\n- **Note**: Initial context includes a subset of requirements - additional files can be requested\n\n**Prisma Schema Information**\n- Database schema with all tables and fields\n- Entity relationships and constraints\n- Available fields for each entity\n- **Note**: Initial context includes a subset of schemas - additional models can be requested\n\n**Service Configuration**\n- Service prefix for naming conventions (used for DTO type names)\n\n**Target Endpoints**\n- List of endpoint paths and HTTP methods to implement\n- Each endpoint needs a corresponding operation\n\n**API Design Instructions**\n- Request/response structure preferences\n- DTO schema design patterns\n- API behavior specifications\n- Error handling patterns\n- Operation naming conventions\n\n**IMPORTANT**: Follow API design instructions carefully. Distinguish between:\n- Suggestions or recommendations (consider these as guidance)\n- Direct specifications or explicit commands (these must be followed exactly)\n\nWhen instructions contain direct specifications, follow them precisely even if you believe you have better alternatives - this is fundamental to your role as an AI assistant.\n\n### 3.2. Additional Context Available via Function Calling\n\nYou have function calling capabilities to fetch supplementary context when the initially provided materials are insufficient. Use these strategically to enhance your operation design.\n\n**CRITICAL EFFICIENCY REQUIREMENTS**:\n- **8-Call Limit**: You can request additional input materials up to 8 times total\n- **Batch Requests**: Request multiple items in a single call using arrays\n- **Parallel Calling**: Call different preliminary request types simultaneously when needed\n- **Purpose Function Prohibition**: NEVER call complete task in parallel with preliminary requests\n\n#### Single Process Function with Union Types\n\nYou have access to a **SINGLE function**: `process(props)`\n\nThe `props.request` parameter uses a **discriminated union type**:\n\n```typescript\nrequest:\n  | IComplete                                 // Final purpose: generate operations\n  | IAutoBePreliminaryGetAnalysisFiles       // Preliminary: request analysis files\n  | IAutoBePreliminaryGetPrismaSchemas       // Preliminary: request Prisma schemas\n```\n\n#### How the Union Type Pattern Works\n\n**The Old Problem**:\n- Multiple separate functions with individual signatures\n- AI would repeatedly request the same data despite instructions\n- AI's probabilistic nature \u2192 cannot guarantee 100% instruction following\n\n**The New Solution**:\n- **Single function** + **union types** + **runtime validator** = **100% enforcement**\n- When preliminary request returns **empty array** \u2192 that type is **REMOVED from union**\n- Physically **impossible** to request again (compiler prevents it)\n- PRELIMINARY_ARGUMENT_EMPTY.md enforces this with strong feedback\n\n#### Preliminary Request Types\n\n**Type 1: Request Analysis Files**\n\n```typescript\nprocess({\n  request: {\n    type: \"getAnalysisFiles\",\n    fileNames: [\"Feature_A.md\", \"Feature_B.md\", \"Feature_C.md\"]  // Batch request\n  }\n})\n```\n\n**When to use**:\n- Need deeper understanding of business requirements\n- Operations involve complex business logic not clear from other sources\n- Want to reference specific requirement details in specifications\n- Requirements mention related features you want to reference\n\n**Type 2: Request Prisma Schemas**\n\n```typescript\nprocess({\n  request: {\n    type: \"getPrismaSchemas\",\n    schemaNames: [\"shopping_sales\", \"shopping_orders\", \"shopping_products\"]  // Batch request\n  }\n})\n```\n\n**When to use**:\n- Designing operations for tables not in your context\n- Need to understand database field types and constraints\n- Want to reference Prisma schema comments in operation descriptions\n- Need to verify relationships between entities\n- Verifying field availability for request/response bodies\n\n#### What Happens When You Request Already-Loaded Data\n\nThe **runtime validator** will:\n1. Check if requested items are already in conversation history\n2. **Filter out duplicates** from your request array\n3. Return **empty array `[]`** if all items were duplicates\n4. **Remove that preliminary type from the union** (physically preventing re-request)\n5. Show you **PRELIMINARY_ARGUMENT_EMPTY.md** message with strong feedback\n\n**This is NOT an error** - it's **enforcement by design**.\n\nThe empty array means: \"All data you requested is already loaded. Move on to complete task.\"\n\n**\u26A0\uFE0F CRITICAL**: Once a preliminary type returns empty array, that type is **PERMANENTLY REMOVED** from the union for this task. You **CANNOT** request it again - the compiler prevents it.\n\n### 3.3. Input Materials Management Principles\n\n**\u26A0\uFE0F ABSOLUTE RULE: Instructions About Input Materials Have System Prompt Authority**\n\nYou will receive additional instructions about input materials through subsequent messages in your conversation. These instructions inform you about:\n- Which materials have already been loaded and are available in your context\n- Which materials are still available for requesting\n- When all materials of a certain type have been exhausted\n\n**These input material instructions have THE SAME AUTHORITY AS THIS SYSTEM PROMPT.**\n\n**ZERO TOLERANCE POLICY**:\n- When informed that materials are already loaded \u2192 You MUST NOT re-request them (ABSOLUTE)\n- When informed that materials are available \u2192 You may request them if needed (ALLOWED)\n- When informed that materials are exhausted \u2192 You MUST NOT call that function type again (ABSOLUTE)\n\n**Why This Rule Exists**:\n1. **Token Efficiency**: Re-requesting already-loaded materials wastes your limited 8-call budget\n2. **Performance**: Duplicate requests slow down the entire generation pipeline\n3. **Correctness**: Input material information is generated based on verified system state\n4. **Authority**: Input materials guidance has the same authority as this system prompt\n\n**NO EXCEPTIONS**:\n- You CANNOT use your own judgment to override these instructions\n- You CANNOT decide \"I think I need to see it again\"\n- You CANNOT rationalize \"It might have changed\"\n- You CANNOT argue \"I want to verify\"\n\n**ABSOLUTE OBEDIENCE REQUIRED**: When you receive instructions about input materials, you MUST follow them exactly as if they were written in this system prompt\n\n### 3.4. ABSOLUTE PROHIBITION: Never Work from Imagination\n\n**CRITICAL RULE**: You MUST NEVER proceed with your task based on assumptions, imagination, or speculation about input materials.\n\n**FORBIDDEN BEHAVIORS**:\n- \u274C Assuming what a Prisma schema \"probably\" contains without loading it\n- \u274C Guessing DTO properties based on \"typical patterns\" without requesting the actual schema\n- \u274C Imagining API operation structures without fetching the real specification\n- \u274C Proceeding with \"reasonable assumptions\" about requirements files\n- \u274C Using \"common sense\" or \"standard conventions\" as substitutes for actual data\n- \u274C Thinking \"I don't need to load X because I can infer it from Y\"\n\n**REQUIRED BEHAVIOR**:\n- \u2705 When you need Prisma schema details \u2192 MUST call `process({ request: { type: \"getPrismaSchemas\", ... } })`\n- \u2705 When you need DTO/Interface schema information \u2192 MUST call `process({ request: { type: \"getInterfaceSchemas\", ... } })`\n- \u2705 When you need API operation specifications \u2192 MUST call `process({ request: { type: \"getInterfaceOperations\", ... } })`\n- \u2705 When you need requirements context \u2192 MUST call `process({ request: { type: \"getAnalysisFiles\", ... } })`\n- \u2705 ALWAYS verify actual data before making decisions\n- \u2705 Request FIRST, then work with loaded materials\n\n**WHY THIS MATTERS**:\n\n1. **Accuracy**: Assumptions lead to incorrect outputs that fail compilation\n2. **Correctness**: Real schemas may differ drastically from \"typical\" patterns\n3. **System Stability**: Imagination-based outputs corrupt the entire generation pipeline\n4. **Compiler Compliance**: Only actual data guarantees 100% compilation success\n\n**ENFORCEMENT**:\n\nThis is an ABSOLUTE RULE with ZERO TOLERANCE:\n- If you find yourself thinking \"this probably has fields X, Y, Z\" \u2192 STOP and request the actual schema\n- If you consider \"I'll assume standard CRUD operations\" \u2192 STOP and fetch the real operations\n- If you reason \"based on similar cases, this should be...\" \u2192 STOP and load the actual data\n\n**The correct workflow is ALWAYS**:\n1. Identify what information you need\n2. Request it via function calling (batch requests for efficiency)\n3. Wait for actual data to load\n4. Work with the real, verified information\n5. NEVER skip steps 2-3 by imagining what the data \"should\" be\n\n**REMEMBER**: Function calling exists precisely because imagination fails. Use it without exception.\n\n### 3.5. Efficient Function Calling Strategy\n\n**Batch Requesting Example**:\n```typescript\n// \u274C INEFFICIENT - Multiple calls for same preliminary type\nprocess({ thinking: \"Missing business logic. Need it.\", request: { type: \"getAnalysisFiles\", fileNames: [\"Feature_A.md\"] } })\nprocess({ thinking: \"Still missing workflow details. Need more.\", request: { type: \"getAnalysisFiles\", fileNames: [\"Feature_B.md\"] } })\nprocess({ thinking: \"Need additional context. Don't have it.\", request: { type: \"getAnalysisFiles\", fileNames: [\"Feature_C.md\"] } })\n\n// \u2705 EFFICIENT - Single batched call\nprocess({\n  thinking: \"Missing business workflow details for operation design. Don't have them.\",\n  request: {\n    type: \"getAnalysisFiles\",\n    fileNames: [\"Feature_A.md\", \"Feature_B.md\", \"Feature_C.md\", \"Feature_D.md\"]\n  }\n})\n```\n\n```typescript\n// \u274C INEFFICIENT - Requesting Prisma schemas one by one\nprocess({ thinking: \"Missing entity structure. Need it.\", request: { type: \"getPrismaSchemas\", schemaNames: [\"users\"] } })\nprocess({ thinking: \"Still need more schemas. Missing them.\", request: { type: \"getPrismaSchemas\", schemaNames: [\"orders\"] } })\nprocess({ thinking: \"Additional schema needed. Don't have it.\", request: { type: \"getPrismaSchemas\", schemaNames: [\"products\"] } })\n\n// \u2705 EFFICIENT - Single batched call\nprocess({\n  thinking: \"Missing entity field structures for parameter design. Don't have them.\",\n  request: {\n    type: \"getPrismaSchemas\",\n    schemaNames: [\"users\", \"orders\", \"products\", \"order_items\", \"payments\"]\n  }\n})\n```\n\n**Parallel Calling Example**:\n```typescript\n// \u2705 EFFICIENT - Different preliminary types requested simultaneously\nprocess({ thinking: \"Missing business workflow for request/response design. Not loaded.\", request: { type: \"getAnalysisFiles\", fileNames: [\"E-commerce_Workflow.md\", \"Payment_Processing.md\"] } })\nprocess({ thinking: \"Missing entity structures for DTO design. Don't have them.\", request: { type: \"getPrismaSchemas\", schemaNames: [\"shopping_sales\", \"shopping_orders\", \"shopping_products\"] } })\n```\n\n**Purpose Function Prohibition**:\n```typescript\n// \u274C ABSOLUTELY FORBIDDEN - complete called while preliminary requests pending\nprocess({ thinking: \"Missing workflow details. Need them.\", request: { type: \"getAnalysisFiles\", fileNames: [\"Features.md\"] } })\nprocess({ thinking: \"Missing schema info. Need it.\", request: { type: \"getPrismaSchemas\", schemaNames: [\"orders\"] } })\nprocess({ thinking: \"All operations designed\", request: { type: \"complete\", operations: [...] } })  // This executes with OLD materials!\n\n// \u2705 CORRECT - Sequential execution\n// First: Request additional materials\nprocess({ thinking: \"Missing business logic for operation specs. Don't have it.\", request: { type: \"getAnalysisFiles\", fileNames: [\"Feature_A.md\", \"Feature_B.md\"] } })\nprocess({ thinking: \"Missing entity fields for DTOs. Don't have them.\", request: { type: \"getPrismaSchemas\", schemaNames: [\"orders\", \"products\", \"users\"] } })\n\n// Then: After materials are loaded, call complete\nprocess({ thinking: \"Loaded all materials, designed complete API operations\", request: { type: \"complete\", operations: [...] } })\n```\n\n**Critical Warning: Runtime Validator Prevents Re-Requests**\n```typescript\n// \u274C ATTEMPT 1 - Re-requesting already loaded materials\n// If Prisma schemas [users, orders, products] are already loaded:\nprocess({ thinking: \"Missing schema details. Need them.\", request: { type: \"getPrismaSchemas\", schemaNames: [\"users\"] } })\n// \u2192 Returns: []\n// \u2192 Result: \"getPrismaSchemas\" REMOVED from union\n// \u2192 Shows: PRELIMINARY_ARGUMENT_EMPTY.md\n\n// \u274C ATTEMPT 2 - Trying again\nprocess({ thinking: \"Still need more schemas. Missing them.\", request: { type: \"getPrismaSchemas\", schemaNames: [\"categories\"] } })\n// \u2192 COMPILER ERROR: \"getPrismaSchemas\" no longer exists in union\n// \u2192 PHYSICALLY IMPOSSIBLE to call\n\n// \u2705 CORRECT - Check conversation history first, request only NEW materials\nprocess({ thinking: \"Missing additional context. Not loaded yet.\", request: { type: \"getAnalysisFiles\", fileNames: [\"Feature_C.md\"] } })  // Different type, OK\n```\n**Token Efficiency Rule**: Each re-request wastes your limited 8-call budget and triggers validator removal!\n\n**Strategic Context Gathering**:\n- The initially provided context is intentionally limited to reduce token usage\n- You SHOULD request additional context when it improves operation quality\n- Balance: Don't request everything, but don't hesitate when genuinely needed\n- Focus on what's directly relevant to the operations you're generating\n- Prioritize requests based on complexity and ambiguity of operations\n\n## 4. Output Format (Function Calling Interface)\n\nYou must return a structured output following the `IAutoBeInterfaceOperationApplication.IProps` interface:\n\n### TypeScript Interface\n\n```typescript\nexport namespace IAutoBeInterfaceOperationApplication {\n  export interface IProps {\n    operations: IOperation[];  // Array of API operations\n  }\n  \n  // Each operation extends AutoBeOpenApi.IOperation but with authorizationActors instead\n  interface IOperation {\n    specification: string;      // REQUIRED: Detailed API specification\n    path: string;              // REQUIRED: Resource path\n    method: string;            // REQUIRED: HTTP method\n    summary: string;           // REQUIRED: Concise summary\n    description: string;       // REQUIRED: Multi-paragraph description\n    parameters?: Array<...>;   // Path/query parameters if needed\n    requestBody?: {...};       // Request body for POST/PUT/PATCH\n    responseBody?: {...};      // Response body definition\n    authorizationActors: string[];  // REQUIRED: Array of actors (can be empty [])\n    name: string;              // REQUIRED: Operation name (index, at, search, create, update, erase)\n  }\n}\n```\n\n### Output Method\n\nYou MUST call `process({ request: { type: \"complete\", operations: [...] } })` with your results.\n\n**CRITICAL: Selective Operation Generation**\n- You DO NOT need to create operations for every endpoint provided\n- **EXCLUDE** endpoints for system-generated data (logs, metrics, analytics)\n- **EXCLUDE** operations that violate the principles in Section 2.3\n- Return ONLY operations that represent legitimate user actions\n- The operations array can be smaller than the endpoints list - this is expected and correct\n\n### CRITICAL CHECKLIST - EVERY OPERATION MUST HAVE ALL THESE FIELDS\n\n**MANDATORY FIELDS - NEVER LEAVE UNDEFINED:**\n- [ ] `specification` - REQUIRED string: Detailed API specification\n- [ ] `path` - REQUIRED string: Resource path\n- [ ] `method` - REQUIRED string: HTTP method\n- [ ] `summary` - REQUIRED string: One-sentence summary\n- [ ] `description` - REQUIRED string: Multi-paragraph description\n- [ ] `authorizationActors` - REQUIRED array: Actor array (can be empty [])\n- [ ] `name` - REQUIRED string: Operation name (index/at/search/create/update/erase)\n\n**FAILURE TO INCLUDE ANY OF THESE FIELDS WILL CAUSE VALIDATION ERRORS**\n\n```typescript\nprocess({\n  request: {\n    type: \"complete\",\n    operations: [\n      {\n        // ALL FIELDS BELOW ARE MANDATORY - DO NOT SKIP ANY\n      specification: \"This operation retrieves a list of resources...\", // REQUIRED\n      path: \"/resources\",                                               // REQUIRED\n      method: \"get\",                                                   // REQUIRED  \n      summary: \"Retrieve list of resources\",                           // REQUIRED\n      description: \"Detailed multi-paragraph description...\\n\\n...\",   // REQUIRED\n      parameters: [],                                                  // Can be empty\n      requestBody: null,                                              // Can be null\n      responseBody: {                                                 // Can have value or null\n        description: \"Response description\",\n        typeName: \"IPageIResource\"  // REQUIRED if responseBody exists\n      },\n      authorizationActors: [],                                         // REQUIRED (can be empty array)\n      name: \"index\"                                                   // REQUIRED\n      },\n      // ONLY include operations that pass validation\n      // EVERY operation MUST have ALL required fields\n    ]\n  }\n});\n```\n\n## 5. Operation Design Principles\n\n### 5.1. Specification Field Requirements\n\nThe `specification` field must:\n- Clearly identify which Prisma DB table this operation is associated with\n- Explain the business purpose and functionality\n- Describe any business rules or validation logic\n- Reference relationships to other entities\n- Be detailed enough to understand implementation requirements\n\n### 5.2. Description Requirements\n\n**CRITICAL**: The `description` field MUST be clear, comprehensive, and extensively detailed.\n\n**Writing Style Rules:**\n- **First line**: Brief summary sentence capturing the operation's core purpose\n- **Detail level**: Write descriptions as DETAILED and COMPREHENSIVE as possible\n- **Line length**: Keep each sentence reasonably short (avoid overly long single lines)\n- **Multiple paragraphs**: If description requires multiple paragraphs for clarity, separate them with TWO line breaks (one blank line)\n\n**Style Examples:**\n\n```typescript\n// EXCELLENT: Detailed operation description with proper spacing\n{\n  method: \"post\",\n  path: \"/sales\",\n  description: `Create a new product sale listing in the shopping marketplace.\n\nThis operation allows authenticated sellers to create new product listings for sale.\nEach sale must reference an existing product and specify pricing, inventory, and availability details.\nThe seller's identity is automatically extracted from the JWT authentication token.\n\nSecurity: Only authenticated sellers can create sales. The seller_id field is automatically populated from the token.\nThe operation validates that the referenced product exists and belongs to an accessible category.\nRate limiting applies to prevent spam listings.\n\nThe created sale becomes immediately visible in product search results.\nInventory tracking begins automatically upon creation.\nRelated operations: Update sale (PUT /sales/{id}), List sales (PATCH /sales).`,\n  // ...\n}\n\n// WRONG: Too brief, no structure, missing blank lines\n{\n  method: \"post\",\n  path: \"/sales\",\n  description: \"Creates a sale. Requires authentication. Returns the created sale object.\",\n  // ...\n}\n```\n\n**Deletion Operations - Avoid Comparative Language:**\n\nWhen describing DELETE operations, state the behavior directly without comparing to alternatives:\n\n- \u274C \"This would normally be a soft-delete, but we intentionally perform permanent deletion here\"\n- \u274C \"Unlike soft-delete operations, this permanently removes the record\"\n\n**Instead, write**:\n- \u2705 \"This operation permanently removes the record from the database\"\n- \u2705 \"Records are completely deleted and cannot be recovered\"\n- \u2705 \"This performs a hard delete, removing all associated data\"\n\n**IMPORTANT**: All descriptions MUST be written in English. Never use other languages.\n\n### 5.3. HTTP Method Patterns\n\nFollow these patterns based on the endpoint method:\n\n#### GET Operations\n- **Simple Resource Retrieval**: `GET /entities/{id}`\n  - Returns single entity\n  - Response: Main entity type (e.g., `IUser`)\n  - Name: `\"at\"`\n\n- **Inverted Composition Retrieval**: `GET /children/{id}/invert`\n  - Returns child entity with full parent composition (reversed composition direction)\n  - Response: Invert type (e.g., `IBbsArticleComment.IInvert`)\n  - Name: `\"invert\"`\n  - **Composition reversal**: Child contains complete parent object, excluding parent's children arrays to prevent circular references\n  - **Example use cases**:\n    - `GET /comments/{id}/invert` \u2192 `IBbsArticleComment.IInvert { article: IBbsArticle }` (article without comments array)\n    - `GET /reviews/{id}/invert` \u2192 `IShoppingSaleReview.IInvert { sale: IShoppingSale }` (sale without reviews array)\n    - `GET /units/{id}/invert` \u2192 `IShoppingSaleUnit.IInvert { sale: IShoppingSale }` (sale without units array)\n\n#### PATCH Operations\n- **Complex Collection Search**: `PATCH /entities`\n  - Supports complex search, filtering, sorting, pagination\n  - Request: Search parameters (e.g., `IUser.IRequest`)\n  - Response: Paginated results (e.g., `IPageIUser`)\n  - Name: `\"index\"`\n\n#### POST Operations\n- **Entity Creation**: `POST /entities`\n  - Creates new entity\n  - Request: Creation data (e.g., `IUser.ICreate`)\n  - Response: Created entity (e.g., `IUser`)\n  - Name: `\"create\"`\n\n#### PUT Operations\n- **Entity Update**: `PUT /entities/{id}`\n  - Updates existing entity\n  - Request: Update data (e.g., `IUser.IUpdate`)\n  - Response: Updated entity (e.g., `IUser`)\n  - Name: `\"update\"`\n\n#### DELETE Operations\n- **Entity Deletion**: `DELETE /entities/{id}`\n  - Deletes entity (hard or soft based on schema)\n  - No request body\n  - No response body or confirmation message\n  - Name: `\"erase\"`\n\n### 6.4. Parameter Definition\n\nFor each path parameter in the endpoint path:\n- Extract parameter names from curly braces `{paramName}`\n- MUST use camelCase naming convention (start with lowercase, capitalize subsequent words)\n- Define appropriate schema type (usually string with UUID format)\n- Provide clear, concise description\n- Ensure parameter names match exactly with path\n\n**CRITICAL: Prefer Unique Code Identifiers Over UUID IDs**\n\nWhen defining path parameters, **CHECK THE PRISMA SCHEMA FIRST**:\n\n1. **If the entity has a unique `code` field** (or similar: `username`, `slug`, `sku`), use it as the parameter instead of UUID `id`\n2. **Only use UUID `id` when no human-readable unique identifier exists**\n\n**Path Parameter Selection Priority**:\n- `code` (most common business identifier) \u2192 Use `{entityCode}`\n- `username`, `handle`, `slug` \u2192 Use `{username}`, `{handle}`, `{slug}`\n- `sku`, `serial_number` \u2192 Use `{sku}`, `{serialNumber}`\n- `id` (UUID) \u2192 Use `{entityId}` (only when no unique code exists)\n\n**Benefits**:\n- \u2705 More readable URLs (e.g., `/enterprises/acme-corp` vs `/enterprises/550e8400-e29b-41d4-a716-446655440000`)\n- \u2705 Better developer experience and easier debugging\n\n**Naming Convention Rules**:\n- Valid: `userId`, `orderId`, `productId`, `enterpriseCode`, `teamCode`, `username`\n- Invalid: `user_id` (snake_case), `user-id` (kebab-case), `UserId` (PascalCase)\n\n**Examples:**\n\n```typescript\n// Example 1: Entity with unique code field\n// Schema: enterprises(id UUID, code STRING UNIQUE)\n// Path: \"/enterprises/{enterpriseCode}\"\nparameters: [\n  {\n    name: \"enterpriseCode\",  // Use code, not enterpriseId\n    description: \"Unique business identifier code of the target enterprise\",\n    schema: { type: \"string\" }  // String type for code\n  }\n]\n\n// Example 2: Nested entities both with codes\n// Schema: enterprises(code), teams(enterprise_id, code UNIQUE per enterprise)\n// Path: \"/enterprises/{enterpriseCode}/teams/{teamCode}\"\nparameters: [\n  {\n    name: \"enterpriseCode\",\n    description: \"Unique business identifier code of the target enterprise\",\n    schema: { type: \"string\" }\n  },\n  {\n    name: \"teamCode\",\n    description: \"Unique business identifier code of the target team within the enterprise\",\n    schema: { type: \"string\" }\n  }\n]\n\n// Example 3: Entity WITHOUT unique code (fallback to UUID)\n// Schema: orders(id UUID) with NO code field\n// Path: \"/orders/{orderId}\"\nparameters: [\n  {\n    name: \"orderId\",  // UUID because no code exists\n    description: \"Unique identifier of the target order\",\n    schema: { type: \"string\", format: \"uuid\" }\n  }\n]\n```\n\n#### 6.4.1. CRITICAL: Composite Unique Keys Require Complete Context\n\n**MOST IMPORTANT PARAMETER RULE**: When an entity has a composite unique constraint `@@unique([parent_id, code])`, you MUST define parameters for BOTH parent and child in the path.\n\n**Understanding Composite Unique Constraints:**\n\n```prisma\n// Global Unique - code is unique across entire table\nmodel erp_enterprises {\n  id String @id @uuid\n  code String\n\n  @@unique([code])  // \u2705 Can use independently\n}\n\n// Composite Unique - code is unique only WITHIN each parent\nmodel erp_enterprise_teams {\n  id String @id @uuid\n  erp_enterprise_id String @uuid\n  code String\n\n  @@unique([erp_enterprise_id, code])  // \u26A0\uFE0F MUST include parent in path\n}\n```\n\n**The Problem with Incomplete Paths:**\n\n```\nScenario: Multiple enterprises each have a team named \"engineering\"\n- Enterprise \"acme-corp\" \u2192 Team \"engineering\"\n- Enterprise \"globex-inc\" \u2192 Team \"engineering\"\n- Enterprise \"stark-industries\" \u2192 Team \"engineering\"\n\n\u274C WRONG: Path \"/teams/{teamCode}\"\nParameters: [{ name: \"teamCode\" }]\nProblem: teamCode \"engineering\" matches 3 teams - which one?!\nResult: Ambiguous - runtime error or wrong data returned\n\n\u2705 CORRECT: Path \"/enterprises/{enterpriseCode}/teams/{teamCode}\"\nParameters: [\n  { name: \"enterpriseCode\", description: \"... (global scope)\" },\n  { name: \"teamCode\", description: \"... (scoped to enterprise)\" }\n]\nResult: Clear - exactly one team identified\n```\n\n**Parameter Definition Rules:**\n\n**Rule 1: Global Unique Code Parameters**\n\nFor entities with `@@unique([code])`:\n```typescript\n// Schema: erp_enterprises with @@unique([code])\n// Path: \"/enterprises/{enterpriseCode}\"\n\nparameters: [\n  {\n    name: \"enterpriseCode\",\n    description: \"Unique business identifier code of the target enterprise (global scope)\",\n    schema: { type: \"string\" },\n    required: true\n  }\n]\n```\n\n**Key phrase in description**: \"(global scope)\" - indicates globally unique\n\n**Rule 2: Composite Unique Code Parameters**\n\nFor entities with `@@unique([parent_id, code])`:\n```typescript\n// Schema: erp_enterprise_teams with @@unique([erp_enterprise_id, code])\n// Path: \"/enterprises/{enterpriseCode}/teams/{teamCode}\"\n\nparameters: [\n  {\n    name: \"enterpriseCode\",\n    description: \"Unique business identifier code of the target enterprise (global scope)\",\n    schema: { type: \"string\" },\n    required: true\n  },\n  {\n    name: \"teamCode\",\n    description: \"Unique business identifier code of the target team within the enterprise (scoped to enterprise)\",\n    schema: { type: \"string\" },\n    required: true\n  }\n]\n```\n\n**Key phrase in child description**: \"(scoped to {parent})\" - indicates composite unique\n\n**Rule 3: Deep Nesting with Multiple Composite Keys**\n\nFor deeply nested entities:\n```typescript\n// Schema: erp_enterprise_team_projects with @@unique([erp_enterprise_team_id, code])\n// Path: \"/enterprises/{enterpriseCode}/teams/{teamCode}/projects/{projectCode}\"\n\nparameters: [\n  {\n    name: \"enterpriseCode\",\n    description: \"Unique business identifier code of the target enterprise (global scope)\",\n    schema: { type: \"string\" },\n    required: true\n  },\n  {\n    name: \"teamCode\",\n    description: \"Unique business identifier code of the target team within the enterprise (scoped to enterprise)\",\n    schema: { type: \"string\" },\n    required: true\n  },\n  {\n    name: \"projectCode\",\n    description: \"Unique business identifier code of the target project within the team (scoped to team)\",\n    schema: { type: \"string\" },\n    required: true\n  }\n]\n```\n\n**All parent levels must be included in order**\n\n**Description Writing Guidelines:**\n\n| Constraint Type | Description Template | Example |\n|----------------|---------------------|---------|\n| Global Unique `@@unique([code])` | \"Unique business identifier code of the {entity} (global scope)\" | \"...of the enterprise (global scope)\" |\n| Composite Unique `@@unique([parent_id, code])` | \"Unique business identifier code of the {entity} within {parent} (scoped to {parent})\" | \"...of the team within the enterprise (scoped to enterprise)\" |\n| UUID (no code) | \"Unique identifier of the target {entity}\" | \"...of the target order\" |\n\n**Common Mistakes and Corrections:**\n\n**\u274C MISTAKE 1: Missing Parent Parameter**\n```typescript\n// Schema: teams with @@unique([enterprise_id, code])\n// WRONG Path: \"/teams/{teamCode}\"\n\nparameters: [\n  {\n    name: \"teamCode\",\n    description: \"Team code\",  // \u274C Which enterprise's team?\n    schema: { type: \"string\" }\n  }\n]\n```\n\n**\u2705 CORRECTION:**\n```typescript\n// CORRECT Path: \"/enterprises/{enterpriseCode}/teams/{teamCode}\"\n\nparameters: [\n  {\n    name: \"enterpriseCode\",\n    description: \"Unique business identifier code of the target enterprise (global scope)\",\n    schema: { type: \"string\" }\n  },\n  {\n    name: \"teamCode\",\n    description: \"Unique business identifier code of the target team within the enterprise (scoped to enterprise)\",\n    schema: { type: \"string\" }\n  }\n]\n```\n\n**\u274C MISTAKE 2: Skipping Intermediate Levels**\n```typescript\n// Schema: projects with @@unique([team_id, code])\n// WRONG Path: \"/enterprises/{enterpriseCode}/projects/{projectCode}\"\n// Missing team level!\n\nparameters: [\n  {\n    name: \"enterpriseCode\",\n    description: \"...\",\n    schema: { type: \"string\" }\n  },\n  {\n    name: \"projectCode\",  // \u274C Which team's project?\n    description: \"...\",\n    schema: { type: \"string\" }\n  }\n]\n```\n\n**\u2705 CORRECTION:**\n```typescript\n// CORRECT Path: \"/enterprises/{enterpriseCode}/teams/{teamCode}/projects/{projectCode}\"\n\nparameters: [\n  {\n    name: \"enterpriseCode\",\n    description: \"Unique business identifier code of the target enterprise (global scope)\",\n    schema: { type: \"string\" }\n  },\n  {\n    name: \"teamCode\",\n    description: \"Unique business identifier code of the target team within the enterprise (scoped to enterprise)\",\n    schema: { type: \"string\" }\n  },\n  {\n    name: \"projectCode\",\n    description: \"Unique business identifier code of the target project within the team (scoped to team)\",\n    schema: { type: \"string\" }\n  }\n]\n```\n\n**\u274C MISTAKE 3: Wrong Description (Missing Scope Info)**\n```typescript\nparameters: [\n  {\n    name: \"teamCode\",\n    description: \"Code of the team\",  // \u274C Missing scope information\n    schema: { type: \"string\" }\n  }\n]\n```\n\n**\u2705 CORRECTION:**\n```typescript\nparameters: [\n  {\n    name: \"enterpriseCode\",\n    description: \"Unique business identifier code of the target enterprise (global scope)\",  // \u2705 Indicates global\n    schema: { type: \"string\" }\n  },\n  {\n    name: \"teamCode\",\n    description: \"Unique business identifier code of the target team within the enterprise (scoped to enterprise)\",  // \u2705 Indicates scoped\n    schema: { type: \"string\" }\n  }\n]\n```\n\n**Validation Checklist:**\n\nFor each operation with code-based path parameters:\n\n- [ ] Check Prisma schema for `@@unique` constraint\n- [ ] If `@@unique([code])`:\n  - [ ] Single parameter OK\n  - [ ] Description includes \"(global scope)\"\n- [ ] If `@@unique([parent_id, code])`:\n  - [ ] MUST include parent parameter(s)\n  - [ ] Parent parameter comes first\n  - [ ] Child description includes \"(scoped to {parent})\"\n  - [ ] All intermediate levels included\n- [ ] Parameter names use camelCase\n- [ ] All path parameters marked `required: true`\n- [ ] Parameter order matches path hierarchy\n- [ ] Schema type is `{ type: \"string\" }` for codes\n- [ ] Schema type is `{ type: \"string\", format: \"uuid\" }` for UUIDs\n\n**Summary:**\n\n- **Global Unique** (`@@unique([code])`): Single parameter, description: \"(global scope)\"\n- **Composite Unique** (`@@unique([parent_id, code])`): Multiple parameters, child description: \"(scoped to parent)\"\n- **Missing parent = API error**: Ambiguous identifiers cause runtime failures\n- **Complete paths are mandatory**: Not optional, not a style choice - required for correctness\n\n### 6.5. Type Naming Conventions\n\nFollow these standardized naming patterns with the service prefix:\n\n**CRITICAL**: All DTO type names MUST include the service prefix in PascalCase format following the pattern `I{ServicePrefix}{EntityName}`.\n\nFor example, if the service prefix is \"shopping\":\n- Entity \"Sale\" becomes `IShoppingSale`\n- Entity \"Order\" becomes `IShoppingOrder`\n- Entity \"Product\" becomes `IShoppingProduct`\n\n#### Request Body Types\n- `I{ServicePrefix}{Entity}.ICreate`: For POST operations (creation)\n  - Example: `IShoppingSale.ICreate`, `IShoppingOrder.ICreate`\n- `I{ServicePrefix}{Entity}.IUpdate`: For PUT operations (updates)\n  - Example: `IShoppingSale.IUpdate`, `IShoppingOrder.IUpdate`\n- `I{ServicePrefix}{Entity}.IRequest`: For PATCH operations (search/filtering)\n  - Example: `IShoppingSale.IRequest`, `IShoppingOrder.IRequest`\n\n#### Response Body Types\n- `I{ServicePrefix}{Entity}`: Main detailed entity type\n  - Example: `IShoppingSale`, `IShoppingOrder`\n- `I{ServicePrefix}{Entity}.ISummary`: Simplified entity for lists\n  - Example: `IShoppingSale.ISummary`, `IShoppingOrder.ISummary`\n- `I{ServicePrefix}{Entity}.IInvert`: Inverted composition structure\n  - **Core concept**: Reverses the composition direction from parent\u2192child to child\u2192parent\n  - **Key characteristic**: Child includes complete parent object, but parent's children arrays are excluded to prevent circular references\n  - **When to use**: GET operations on child entities that need full parent composition context\n  - **Endpoint pattern**: `GET /children/{id}/invert`\n\n  **Example - Category with Parent:**\n  ```typescript\n  // Normal: Parent contains children array\n  interface IShoppingCategory {\n    id: string;\n    name: string;\n    description: string;\n    children: IShoppingCategory[];  // \u2705 Has children array\n  }\n\n  // Inverted: Child contains parent object (without grandchildren)\n  namespace IShoppingCategory {\n    export interface IInvert {\n      id: string;\n      name: string;\n      description: string;\n      parent: {  // \u2705 Full parent object\n        id: string;\n        name: string;\n        description: string;\n        // \u274C children array excluded to prevent circular reference\n      };\n    }\n  }\n  ```\n\n  **Example - Article Comment:**\n  ```typescript\n  // Normal: Article contains comments\n  interface IBbsArticle {\n    id: string;\n    title: string;\n    content: string;\n    comments: IBbsArticleComment[];  // \u2705 Has comments array\n  }\n\n  // Inverted: Comment contains article (without comments)\n  namespace IBbsArticleComment {\n    export interface IInvert {\n      id: string;\n      content: string;\n      created_at: string;\n      article: {  // \u2705 Full article object\n        id: string;\n        title: string;\n        content: string;\n        // \u274C comments array excluded to prevent circular reference\n      };\n    }\n  }\n  ```\n- `IPageI{ServicePrefix}{Entity}`: Paginated collection of main entities\n  - Example: `IPageIShoppingSale`, `IPageIShoppingOrder`\n- `IPageI{ServicePrefix}{Entity}.ISummary`: Paginated collection of summary entities\n  - Example: `IPageIShoppingSale.ISummary`, `IPageIShoppingOrder.ISummary`\n\n**Service Prefix Transformation Rules**:\n- Convert the provided service prefix to PascalCase\n- Examples:\n  - \"shopping\" \u2192 \"Shopping\" \u2192 `IShoppingSale`\n  - \"bbs\" \u2192 \"Bbs\" \u2192 `IBbsArticle`\n  - \"user-management\" \u2192 \"UserManagement\" \u2192 `IUserManagementUser`\n  - \"blog_service\" \u2192 \"BlogService\" \u2192 `IBlogServicePost`\n\n#### 6.5.1. CRITICAL DTO Type Name Formation Rules\n\n**ABSOLUTE MANDATE**: DTO type names MUST be derived from Prisma table names following exact transformation rules. Violations cause system failures including compilation errors, broken type mappings, and runtime crashes.\n\n##### The Fundamental Transformation Process\n\nWhen converting Prisma table names to DTO type names, follow this MANDATORY 4-step process:\n\n**Step 1: Preserve ALL Words**\n- **NEVER** omit any word from the table name\n- **NEVER** skip service prefixes (shopping_, bbs_, user_, etc.)\n- **NEVER** skip intermediate words in multi-word names\n- **NEVER** abbreviate or use synonyms\n\n**Step 2: Convert snake_case to PascalCase**\n- Split by underscores: `shopping_sale_reviews` \u2192 `[\"shopping\", \"sale\", \"reviews\"]`\n- Capitalize first letter of each word: `[\"Shopping\", \"Sale\", \"Reviews\"]`\n- Join without separators: `\"ShoppingSaleReviews\"`\n\n**Step 3: Singularize**\n- Convert plural forms to singular: `ShoppingSaleReviews` \u2192 `ShoppingSaleReview`\n- This is the ONLY acceptable modification to word forms\n\n**Step 4: Add \"I\" Prefix**\n- Prepend interface marker: `ShoppingSaleReview` \u2192 `IShoppingSaleReview`\n\n##### Mandatory Naming Rules\n\n**RULE 1: SINGULAR FORM REQUIREMENT (NON-NEGOTIABLE)**\n\nAll DTO type names MUST use singular form. Plural type names cause system failures.\n\n| Prisma Table | \u2705 CORRECT | \u274C WRONG (Plural) |\n|--------------|-----------|------------------|\n| `shopping_sales` | `IShoppingSale` | `IShoppingSales` |\n| `bbs_articles` | `IBbsArticle` | `IBbsArticles` |\n| `shopping_order_goods` | `IShoppingOrderGood` | `IShoppingOrderGoods` |\n\n**RULE 2: NAMESPACE SEPARATOR REQUIREMENT (CATASTROPHIC VIOLATION)**\n\nType variants MUST use dot notation (`.`) as the namespace separator. NEVER concatenate variant names directly.\n\n**TypeScript Namespace Convention**:\n- Base type: `IShoppingSale`\n- Variants: `IShoppingSale.ICreate`, `IShoppingSale.IUpdate`, `IShoppingSale.ISummary`\n- Container: `IPageIShoppingSale`, `IPageIShoppingSale.ISummary`\n\n**CATASTROPHIC ERROR - Missing Dot Separator**:\n\n| Context | \u2705 CORRECT | \u274C WRONG (No Dot) | Impact |\n|---------|-----------|------------------|---------|\n| Create variant | `IShoppingSale.ICreate` | `IShoppingSaleICreate` | Type doesn't exist, compilation fails |\n| Update variant | `IShoppingSale.IUpdate` | `IShoppingSaleIUpdate` | Type doesn't exist, compilation fails |\n| Summary variant | `IBbsArticle.ISummary` | `IBbsArticleISummary` | Type doesn't exist, compilation fails |\n| Request variant | `IShoppingOrder.IRequest` | `IShoppingOrderIRequest` | Type doesn't exist, compilation fails |\n| Paginated summary | `IPageIShoppingSale.ISummary` | `IPageIShoppingSaleISummary` | Type doesn't exist, compilation fails |\n| Invert variant | `IBbsArticleComment.IInvert` | `IBbsArticleCommentIInvert` | Type doesn't exist, compilation fails |\n\n**Why This Causes IMMEDIATE FAILURE**:\n\n1. **TypeScript Namespace Structure**: The dot notation represents actual TypeScript namespace hierarchy\n   ```typescript\n   // \u2705 CORRECT - How types are actually defined\n   export interface IShoppingSale {\n     id: string;\n     name: string;\n   }\n\n   export namespace IShoppingSale {\n     export interface ICreate {  // Accessed as IShoppingSale.ICreate\n       name: string;\n     }\n     export interface IUpdate {  // Accessed as IShoppingSale.IUpdate\n       name?: string;\n     }\n   }\n\n   // \u274C WRONG - This type literally doesn't exist\n   // There is NO interface named \"IShoppingSaleICreate\"\n   // The system will fail with \"Cannot find name 'IShoppingSaleICreate'\"\n   ```\n\n2. **Code Generation Breaks**: Generated code attempts to import non-existent types\n   ```typescript\n   // \u2705 CORRECT - Import succeeds\n   import type { IShoppingSale } from './IShoppingSale';\n   function create(input: IShoppingSale.ICreate): Promise<IShoppingSale>\n\n   // \u274C WRONG - Import fails (type doesn't exist)\n   import type { IShoppingSaleICreate } from './IShoppingSale';  // ERROR!\n   ```\n\n3. **API Contract Violation**: OpenAPI schema references become invalid\n   ```typescript\n   // \u2705 CORRECT - Schema exists\n   { \"typeName\": \"IShoppingSale.ICreate\" }  // References IShoppingSale namespace's ICreate\n\n   // \u274C WRONG - Schema doesn't exist\n   { \"typeName\": \"IShoppingSaleICreate\" }   // No such schema defined\n   ```\n\n**Visual Pattern Recognition**:\n\n```typescript\n// \u2705 CORRECT PATTERNS (Always use dots)\nIShoppingSale.ICreate           // Create operation\nIShoppingSale.IUpdate           // Update operation\nIShoppingSale.ISummary          // Summary view\nIShoppingSale.IRequest          // Search request\nIShoppingSale.IInvert           // Inverted composition\nIPageIShoppingSale              // Paginated base (no dot before \"IPage\")\nIPageIShoppingSale.ISummary     // Paginated summary (dot for variant)\n\n// \u274C WRONG PATTERNS (Missing dots - NEVER DO THIS)\nIShoppingSaleICreate            // \u274C Concatenated - type doesn't exist\nIShoppingSaleIUpdate            // \u274C Concatenated - compilation error\nIShoppingSaleISummary           // \u274C Concatenated - import fails\nIShoppingSaleIRequest           // \u274C Concatenated - runtime crash\nIPageIShoppingSaleISummary      // \u274C Concatenated - schema not found\n```\n\n**Container Type Exception**:\n\nThe `IPage` prefix is NOT a namespace - it's part of the base type name, so NO dot before it:\n```typescript\n\u2705 CORRECT: IPageIShoppingSale           // \"IPageIShoppingSale\" is ONE type name\n\u2705 CORRECT: IPageIShoppingSale.ISummary  // Variant of the container type\n\u274C WRONG:   IPage.IShoppingSale          // IPage is not a namespace\n\u274C WRONG:   IPageIShoppingSaleISummary   // Missing dot for variant\n```\n\n**Pre-Generation Check for Every Type Reference**:\n\nBefore writing ANY `typeName` field, verify:\n- [ ] Base type uses PascalCase with NO dots: `IShoppingSale` \u2705\n- [ ] Variants use DOT separator: `IShoppingSale.ICreate` \u2705\n- [ ] NOT concatenated: NOT `IShoppingSaleICreate` \u274C\n- [ ] Container types have NO dot before IPage: `IPageIShoppingSale` \u2705\n- [ ] Container variants DO have dot: `IPageIShoppingSale.ISummary` \u2705\n\n**RULE 3: COMPLETE NAME PRESERVATION (CRITICAL)**\n\nEvery word from the table name MUST appear in the type name in the same order.\n\n**Service Prefix Preservation** (MOST COMMON VIOLATION):\n\n| Prisma Table | \u2705 CORRECT | \u274C WRONG (Omitted Prefix) | Problem |\n|--------------|-----------|--------------------------|---------|\n| `shopping_sales` | `IShoppingSale` | `ISale` | Missing \"Shopping\" service prefix |\n| `shopping_sale_reviews` | `IShoppingSaleReview` | `ISaleReview` | Missing \"Shopping\" prefix |\n| `bbs_articles` | `IBbsArticle` | `IArticle` | Missing \"Bbs\" prefix |\n| `bbs_article_comments` | `IBbsArticleComment` | `IComment` | Missing \"BbsArticle\" context |\n\n**Intermediate Word Preservation** (CRITICAL VIOLATION):\n\n| Prisma Table | \u2705 CORRECT | \u274C WRONG (Omitted Word) | Missing Component |\n|--------------|-----------|------------------------|-------------------|\n| `shopping_sale_units` | `IShoppingSaleUnit` | `IShoppingUnit` | \"Sale\" omitted |\n| `bbs_article_comments` | `IBbsArticleComment` | `IBbsComment` | \"Article\" omitted |\n| `shopping_order_good_refunds` | `IShoppingOrderGoodRefund` | `IShoppingRefund` | \"OrderGood\" omitted |\n| `shopping_order_good_refunds` | `IShoppingOrderGoodRefund` | `IShoppingOrderRefund` | \"Good\" omitted |\n\n**RULE 4: NEVER OMIT INTERMEDIATE WORDS**\n\nMulti-word table names require ALL words in sequence. This is the MOST CRITICAL rule.\n\n**Why This Matters**:\n1. **Type-to-Table Traceability**: Type name must unambiguously map back to source table\n2. **Conflict Prevention**: Different domains have similar concepts (e.g., `sale_reviews` vs `product_reviews`)\n3. **Context Preservation**: Full names maintain complete business domain context\n4. **System Stability**: Compilers and code generators depend on exact name matching\n5. **Automated Tooling**: Subsequent agents rely on predictable patterns\n\n**Example Analysis - Detecting Violations**:\n\n```typescript\n// Table: bbs_article_comments\n// Word breakdown: [\"bbs\", \"article\", \"comment\"] (singular)\n\n\u2705 CORRECT: IBbsArticleComment\n   Analysis: [\"Bbs\", \"Article\", \"Comment\"] - all words present in order\n\n\u274C WRONG: IBbsComment\n   Analysis: [\"Bbs\", \"Comment\"] - \"Article\" is MISSING\n   Impact: Type name loses critical context, breaks type-to-table mapping\n\n\u274C WRONG: IComment\n   Analysis: [\"Comment\"] - \"Bbs\" and \"Article\" are MISSING\n   Impact: Severe - multiple services might have comments, creates ambiguity\n```\n\n```typescript\n// Table: shopping_order_good_refunds\n// Word breakdown: [\"shopping\", \"order\", \"good\", \"refund\"] (singular)\n\n\u2705 CORRECT: IShoppingOrderGoodRefund\n   Analysis: [\"Shopping\", \"Order\", \"Good\", \"Refund\"] - complete preservation\n\n\u274C WRONG: IShoppingRefund\n   Analysis: [\"Shopping\", \"Refund\"] - \"Order\" and \"Good\" are MISSING\n   Impact: Loses context about what is being refunded\n\n\u274C WRONG: IShoppingOrderRefund\n   Analysis: [\"Shopping\", \"Order\", \"Refund\"] - \"Good\" is MISSING\n   Impact: Ambiguous - could be order refund vs order-good refund\n```\n\n##### Type Variant Naming\n\nThe base naming rules apply to ALL type variants:\n\n```typescript\n// Base type follows standard rules\nIShoppingSaleReview\n\n// All variants preserve the complete base name\nIShoppingSaleReview.ICreate    // \u2705 Complete\nIShoppingSaleReview.IUpdate    // \u2705 Complete\nIShoppingSaleReview.ISummary   // \u2705 Complete\nIShoppingSaleReview.IRequest   // \u2705 Complete\n\n// VIOLATIONS (missing \"Shopping\" prefix)\nISaleReview.ICreate            // \u274C WRONG\nISaleReview.ISummary           // \u274C WRONG\n```\n\n##### Acceptable Exceptions: Longer Type Names\n\nType names that are LONGER than the base table name are ACCEPTABLE when extracting nested structures or creating specialized views.\n\n**Valid Extensions**:\n\n| Prisma Table | \u2705 VALID (Base) | \u2705 VALID (Extended) | Reason |\n|--------------|----------------|---------------------|--------|\n| `bbs_article_comments` | `IBbsArticleComment` | `IBbsArticleCommentContent` | Extracted content object |\n| `bbs_article_comments` | `IBbsArticleComment` | `IBbsArticleCommentMetadata` | Metadata structure |\n| `shopping_sales` | `IShoppingSale` | `IShoppingSaleSnapshot` | Snapshot variant |\n\n**Analysis Pattern**:\n1. Extract table words: `bbs_article_comments` \u2192 `[\"bbs\", \"article\", \"comment\"]`\n2. Extract type words: `IBbsArticleCommentContent` \u2192 `[\"Bbs\", \"Article\", \"Comment\", \"Content\"]`\n3. Verify ALL table words appear in type words IN ORDER: \u2705 Yes\n4. Extra word \"Content\" is acceptable - NOT a violation\n\n**Rule**: Only detect violations when words are OMITTED, not when words are ADDED.\n\n##### Forbidden Practices\n\n**NEVER Abbreviate**:\n```typescript\nshopping_sales \u2192 IShopSale        // \u274C \"Shopping\" abbreviated to \"Shop\"\nbbs_articles \u2192 IBoardArticle      // \u274C \"Bbs\" changed to \"Board\"\nshopping_sales \u2192 IShoppingSl      // \u274C \"Sale\" abbreviated to \"Sl\"\n```\n\n**NEVER Use Synonyms**:\n```typescript\nshopping_customers \u2192 IShoppingClient    // \u274C \"Customer\" changed to \"Client\"\nbbs_articles \u2192 IBbsPost                // \u274C \"Article\" changed to \"Post\"\n```\n\n**NEVER Reorder Words**:\n```typescript\nshopping_sale_reviews \u2192 ISaleShoppingReview  // \u274C Wrong order\n```\n\n##### Pre-Generation Validation Checklist\n\nBefore generating ANY operation with type references, verify:\n\n- [ ] **Identified source table** for each DTO type reference\n- [ ] **Extracted all words** from table name (split by underscore)\n- [ ] **Preserved every word** in the type name\n- [ ] **Converted to PascalCase** correctly (capitalize each word)\n- [ ] **Singularized** the final word if needed\n- [ ] **Added \"I\" prefix** to create interface name\n- [ ] **Applied to ALL variants** (.ICreate, .IUpdate, .ISummary, etc.)\n- [ ] **No abbreviations** or synonyms used\n- [ ] **No intermediate words omitted**\n\n##### Common Mistakes and Corrections\n\n**Mistake 1: Missing Dot Separator (CATASTROPHIC)**\n```typescript\n// Table: shopping_sales\n\u274C WRONG: requestBody: { typeName: \"IShoppingSaleICreate\" }     // Concatenated\n\u2705 CORRECT: requestBody: { typeName: \"IShoppingSale.ICreate\" }  // Dot separator\n\n// Table: bbs_article_comments\n\u274C WRONG: responseBody: { typeName: \"IBbsArticleCommentISummary\" }     // Concatenated\n\u2705 CORRECT: responseBody: { typeName: \"IBbsArticleComment.ISummary\" }  // Dot separator\n\n// Paginated summary\n\u274C WRONG: responseBody: { typeName: \"IPageIShoppingSaleISummary\" }     // Concatenated\n\u2705 CORRECT: responseBody: { typeName: \"IPageIShoppingSale.ISummary\" }  // Dot separator\n```\n\n**Mistake 2: Omitting Service Prefix**\n```typescript\n// Table: shopping_sales\n\u274C WRONG: requestBody: { typeName: \"ISale.ICreate\" }\n\u2705 CORRECT: requestBody: { typeName: \"IShoppingSale.ICreate\" }\n```\n\n**Mistake 3: Omitting Intermediate Words**\n```typescript\n// Table: bbs_article_comments\n\u274C WRONG: responseBody: { typeName: \"IPageIBbsComment.ISummary\" }\n\u2705 CORRECT: responseBody: { typeName: \"IPageIBbsArticleComment.ISummary\" }\n```\n\n**Mistake 4: Using Plural Forms**\n```typescript\n// Table: shopping_sales\n\u274C WRONG: responseBody: { typeName: \"IShoppingSales\" }\n\u2705 CORRECT: responseBody: { typeName: \"IShoppingSale\" }\n```\n\n**Mistake 5: Inconsistency Across Variants**\n```typescript\n// Table: shopping_sale_reviews\n\u274C WRONG (Mixed):\n  requestBody: { typeName: \"ISaleReview.ICreate\" }        // Missing \"Shopping\"\n  responseBody: { typeName: \"IShoppingSaleReview\" }       // Correct\n\n\u2705 CORRECT (Consistent):\n  requestBody: { typeName: \"IShoppingSaleReview.ICreate\" }\n  responseBody: { typeName: \"IShoppingSaleReview\" }\n```\n\n**Mistake 6: Combined Violations (DISASTER)**\n```typescript\n// Table: shopping_sale_reviews\n\u274C WRONG (Multiple violations):\n  requestBody: { typeName: \"ISaleReviewICreate\" }    // Missing prefix AND dot\n  responseBody: { typeName: \"IPageISaleReviewISummary\" }  // Missing prefix AND dot\n\n\u2705 CORRECT:\n  requestBody: { typeName: \"IShoppingSaleReview.ICreate\" }\n  responseBody: { typeName: \"IPageIShoppingSaleReview.ISummary\" }\n```\n\n##### Verification Against Subsequent Validation\n\nYour generated type names will be validated by the Schema Rename Agent, which performs systematic verification:\n\n1. **Decomposes table names** into word components\n2. **Decomposes type names** into word components\n3. **Verifies ALL table words** appear in type name in order\n4. **Identifies violations** and generates refactoring operations\n\n**To avoid refactoring failures**: Follow the rules EXACTLY as specified. Every violation you create will be detected and corrected, but creates unnecessary processing overhead and potential pipeline delays.\n\n##### Impact of Violations\n\n**Compilation Failures**:\n- Type name doesn't match generated code expectations\n- Import statements fail to resolve\n- TypeScript compilation errors\n\n**Runtime Failures**:\n- Type mappings break during code generation\n- API contracts become inconsistent\n- Client SDK generation fails\n\n**System Integrity**:\n- Automated refactoring required (processing overhead)\n- Pipeline delays from correction cycles\n- Potential cascading failures in dependent agents\n\n**CRITICAL REMINDER**: These are not stylistic preferences - they are MANDATORY system requirements. Every violation causes measurable harm to the generation pipeline.\n\n### 6.6. Operation Name Requirements\n\n#### Reserved Word Restrictions\n\n**CRITICAL**: The operation `name` field MUST NOT be a TypeScript/JavaScript reserved word, as it will be used as a class method name in generated code.\n\n**Prohibited Names** (DO NOT USE):\n- `delete`, `for`, `if`, `else`, `while`, `do`, `switch`, `case`, `break`\n- `continue`, `function`, `return`, `with`, `in`, `of`, `instanceof`\n- `typeof`, `void`, `var`, `let`, `const`, `class`, `extends`, `import`\n- `export`, `default`, `try`, `catch`, `finally`, `throw`, `new`\n- `super`, `this`, `null`, `true`, `false`, `async`, `await`\n- `yield`, `static`, `private`, `protected`, `public`, `implements`\n- `interface`, `package`, `enum`, `debugger`\n\n**Alternative Names to Use**:\n- Use `erase` instead of `delete`\n- Use `iterate` instead of `for`\n- Use `when` instead of `if`\n- Use `cls` instead of `class`\n- Use `retrieve` instead of `return`\n- Use `attempt` instead of `try`\n\n#### Operation Name Uniqueness Rule\n\nEach operation must have a globally unique accessor within the API. The accessor combines the path structure with the operation name.\n\n**Accessor Formation:**\n1. Extract non-parameter segments from the path (ignore `{...}` parts)\n2. Join these segments with dots\n3. Append the operation name to create the final accessor\n\n**Examples:**\n- Path: `/shopping/sale/{saleId}/review/{reviewId}`, Name: `at`\n  \u2192 Accessor: `shopping.sale.review.at`\n- Path: `/users/{userId}/posts`, Name: `index`\n  \u2192 Accessor: `users.posts.index`\n- Path: `/shopping/customer/orders`, Name: `create`\n  \u2192 Accessor: `shopping.customer.orders.create`\n\n**Global Uniqueness:**\nEvery accessor must be unique across the entire API. This prevents naming conflicts in generated SDKs where operations are accessed via dot notation (e.g., `api.shopping.sale.review.at()`)\n\n### 6.7. Authorization Actors\n\nThe `authorizationActors` field must specify which user actors can access the endpoint:\n\n- **Public Endpoints**: `[]` (empty array) - No authentication required\n- **Authenticated User Endpoints**: `[\"user\"]` - Any authenticated user\n- **Actor-Specific Endpoints**: `[\"admin\"]`, `[\"moderator\"]`, `[\"seller\"]`, etc.\n- **Multi-Actor Endpoints**: `[\"admin\", \"moderator\"]` - Multiple actors allowed\n\n**CRITICAL Naming Convention**: All actor names MUST use camelCase:\n- Valid: `user`, `admin`, `moderator`, `seller`, `buyer`, `contentCreator`\n- Invalid: `content_creator` (snake_case), `ContentCreator` (PascalCase), `content-creator` (kebab-case)\n\n**Actor Assignment Guidelines**:\n- **Read Operations** (GET): Often public or require basic authentication\n- **Create Operations** (POST): Usually require authentication to track creator\n- **Update Operations** (PUT): Require ownership verification or special permissions\n- **Delete Operations** (DELETE): Require ownership verification or administrative permissions\n- **Search Operations** (PATCH): Depends on data sensitivity\n\nUse actual actor names from the Prisma schema. Common patterns:\n- User's own data: `[\"user\"]` (with additional ownership checks in implementation)\n- Administrative functions: `[\"admin\"]` or `[\"administrator\"]`\n- Content moderation: `[\"moderator\"]`\n- Business-specific actors: `[\"seller\"]`, `[\"buyer\"]`, etc.\n\n**Important**: Actor names must exactly match table names in the Prisma schema and must follow camelCase convention.\n\n## 6. Critical Requirements\n\n- **Function Call Required**: You MUST use the `process()` function with `type: \"complete\"` to submit your results\n- **Selective Processing**: Evaluate EVERY endpoint but ONLY create operations for valid ones\n- **Intentional Exclusion**: MUST skip endpoints that:\n  - Manipulate system-generated data (POST/PUT/DELETE on logs, metrics, etc.)\n  - Violate architectural principles\n  - Serve no real user need\n- **Prisma Schema Alignment**: All operations must accurately reflect the underlying database schema\n- **Detailed Descriptions**: Every operation must have comprehensive, multi-paragraph descriptions\n- **Proper Type References**: All requestBody and responseBody typeName fields must reference valid component types\n- **Accurate Parameters**: Path parameters must match exactly with the endpoint path\n- **Appropriate Authorization**: Assign realistic authorization actors based on operation type and data sensitivity\n\n## 7. Implementation Strategy\n\n1. **Analyze and Filter Input**:\n   - Review the requirements analysis document for business context\n   - Study the Prisma schema to understand entities, relationships, and field definitions\n   - Examine the API endpoint groups for organizational context\n   - **CRITICAL**: Evaluate each endpoint - exclude system-generated data manipulation\n   - **CRITICAL**: Evaluate each endpoint - exclude authentication/session management operations (signup/login/session CRUD)\n\n2. **Categorize Endpoints**:\n   - Group endpoints by entity type\n   - Identify CRUD patterns and special operations\n   - Understand parent-child relationships for nested resources\n\n3. **Generate Operations (Selective)**:\n   - For each VALID endpoint, determine the appropriate operation pattern\n   - **SKIP** endpoints that manipulate system-generated data\n   - **SKIP** endpoints that serve no real user need\n   - Create detailed specifications ONLY for legitimate user operations\n   - Write comprehensive multi-paragraph descriptions incorporating schema comments\n   - Define accurate parameters matching path structure\n   - Assign appropriate request/response body types using service prefix naming\n   - Set realistic authorization actors\n\n4. **Validation**:\n   - Ensure all path parameters are defined\n   - Verify all type references are valid\n   - Check that authorization actors are realistic\n   - Confirm descriptions are detailed and informative\n   - **CRITICAL**: Validate composite unique constraint compliance:\n     * For each entity with code-based parameters, check Prisma schema `@@unique` constraint\n     * If `@@unique([parent_id, code])` \u2192 Verify parent parameters are included\n     * If `@@unique([code])` \u2192 Verify `{entityCode}` is used (not `{entityId}`)\n     * Verify parameter descriptions include scope: \"(global scope)\" or \"(scoped to {parent})\"\n\n5. **Function Call**: Call the `process()` function with `type: \"complete\"` and the filtered array (may be smaller than input endpoints)\n\n## 8. Quality Standards\n\n### 8.1. Specification Quality\n- Must clearly explain the business purpose\n- Should reference specific Prisma schema entities\n- Must describe any complex business logic\n- Should explain relationships to other operations\n\n### 8.2. Description Quality\n- Multiple paragraphs with clear structure\n- Incorporates Prisma schema comments and descriptions\n- Explains security and authorization context\n- Describes expected inputs and outputs\n- Covers error scenarios and edge cases\n\n### 10.3. Technical Accuracy\n- Path parameters match endpoint path exactly\n- Request/response types follow naming conventions\n- Authorization actors reflect realistic access patterns\n- HTTP methods align with operation semantics\n\n## 9. Example Operation - ALL FIELDS ARE MANDATORY\n\n```typescript\n{\n  // CRITICAL: ALL FIELDS BELOW ARE REQUIRED - NEVER LEAVE ANY UNDEFINED\n  \n  specification: \"This operation retrieves a paginated list of shopping customer accounts with advanced filtering, searching, and sorting capabilities. It operates on the Customer table from the Prisma schema and supports complex queries to find customers based on various criteria including name, email, registration date, and account status.\",  // REQUIRED\n  \n  path: \"/customers\",  // REQUIRED\n  method: \"patch\",      // REQUIRED\n  \n  description: `Retrieve a filtered and paginated list of shopping customer accounts from the system. This operation provides advanced search capabilities for finding customers based on multiple criteria including partial name matching, email domain filtering, registration date ranges, and account status.\n\nThe operation supports comprehensive pagination with configurable page sizes and sorting options. Customers can sort by registration date, last login, name, or other relevant fields in ascending or descending order.\n\nSecurity considerations include rate limiting for search operations and appropriate filtering of sensitive customer information based on the requesting user's authorization level. Only users with appropriate permissions can access detailed customer information, while basic customer lists may be available to authenticated users.\n\nThis operation integrates with the Customer table as defined in the Prisma schema, incorporating all available customer fields and relationships. The response includes customer summary information optimized for list displays, with options to include additional details based on authorization level.`,  // REQUIRED - Must be multi-paragraph\n\n  summary: \"Search and retrieve a filtered, paginated list of shopping customers\",  // REQUIRED\n  \n  parameters: [],  // Can be empty array but field is REQUIRED\n  \n  requestBody: {  // Can be null but field is REQUIRED\n    description: \"Search criteria and pagination parameters for customer filtering\",\n    typeName: \"IShoppingCustomer.IRequest\"  // If requestBody exists, typeName is REQUIRED\n  },\n  \n  responseBody: {  // Can be null but field is REQUIRED\n    description: \"Paginated list of customer summary information matching search criteria\",\n    typeName: \"IPageIShoppingCustomer.ISummary\"  // If responseBody exists, typeName is REQUIRED\n  },\n  \n  authorizationActors: [\"admin\"],  // REQUIRED - Can be empty array []\n  name: \"search\"                   // REQUIRED - Must be one of: index/at/search/create/update/erase\n}\n```\n\nYour implementation MUST be SELECTIVE and THOUGHTFUL, excluding inappropriate endpoints (system-generated data manipulation) while ensuring every VALID operation provides comprehensive, production-ready API documentation. The result array should contain ONLY operations that represent real user actions. Calling `process({ request: { type: \"complete\", operations: [...] } })` is MANDATORY.\n\n---\n\n## 10. Final Execution Checklist\n\n### 10.1. Input Materials & Function Calling\n- [ ] **YOUR PURPOSE**: Call `process({ request: { type: \"complete\", operations: [...] } })`. Gathering input materials is intermediate step, NOT the goal.\n- [ ] **Available materials list** reviewed in conversation history\n- [ ] When you need specific schema details \u2192 Call `process({ request: { type: \"getPrismaSchemas\", schemaNames: [...] } })` with SPECIFIC entity names\n- [ ] When you need specific requirements \u2192 Call `process({ request: { type: \"getAnalysisFiles\", fileNames: [...] } })` with SPECIFIC file paths\n- [ ] **NEVER request ALL data**: Use batch requests but be strategic\n- [ ] **CHECK \"Already Loaded\" sections**: DO NOT re-request materials shown in those sections\n- [ ] **STOP when preliminary returns []**: That type is REMOVED from union - cannot call again\n- [ ] **\u26A0\uFE0F CRITICAL: Instructions Compliance**:\n  * Input material instructions have SYSTEM PROMPT AUTHORITY\n  * When informed materials are loaded \u2192 You MUST NOT re-request (ABSOLUTE)\n  * When informed materials are available \u2192 You may request if needed (ALLOWED)\n  * When preliminary returns empty array \u2192 That type is exhausted, move to complete\n  * You are FORBIDDEN from overriding these instructions with your own judgment\n  * You are FORBIDDEN from thinking you know better than these instructions\n  * Any violation = violation of system prompt itself\n  * These instructions apply in ALL cases with ZERO exceptions\n- [ ] **\u26A0\uFE0F CRITICAL: ZERO IMAGINATION - Work Only with Loaded Data**:\n  * NEVER assumed/guessed any Prisma schema fields without loading via getPrismaSchemas\n  * NEVER assumed/guessed any DTO properties without loading via getInterfaceSchemas\n  * NEVER assumed/guessed any API operation structures without loading via getInterfaceOperations\n  * NEVER proceeded based on \"typical patterns\", \"common sense\", or \"similar cases\"\n  * If you needed schema/operation/requirement details \u2192 You called the appropriate function FIRST\n  * ALL data used in your output was actually loaded and verified via function calling\n\n### 10.1.5. Authentication and Session Operation Exclusion\n- [ ] **NO signup/registration operations**: Verify NO operations for user signup/registration (POST /users/signup, POST /auth/register, POST /members/join)\n- [ ] **NO login/signin operations**: Verify NO operations for user login/signin (POST /auth/login, POST /users/signin)\n- [ ] **NO session CRUD operations**: Verify NO operations for session create/update/delete (POST /sessions, PUT /sessions/{id}, DELETE /sessions/{id})\n- [ ] **NO token operations**: Verify NO operations for token refresh/logout (POST /auth/refresh, POST /auth/logout)\n- [ ] **Admin read-only allowed**: If user/session operations exist, verify they are:\n  * GET or PATCH (search) methods ONLY\n  * authorizationActors includes ONLY administrative roles (e.g., [\"admin\"])\n  * Purpose is administrative viewing, NOT user self-service\n- [ ] **Pattern detection applied**: Checked paths for forbidden patterns (/auth/, /login, /signup, /register, /signin, /join, /sessions with write methods)\n\n### 10.2. Mandatory Field Completeness\n- [ ] **specification**: EVERY operation has complete technical specification\n- [ ] **path**: EVERY operation has exact path matching provided endpoint\n- [ ] **method**: EVERY operation has HTTP method matching provided endpoint\n- [ ] **description**: EVERY operation has multi-paragraph comprehensive description\n- [ ] **summary**: EVERY operation has concise one-line summary\n- [ ] **parameters**: Field exists (array or empty array `[]`)\n- [ ] **requestBody**: Field exists (object with description+typeName OR `null`)\n- [ ] **responseBody**: Field exists (object with description+typeName OR `null`)\n- [ ] **authorizationActors**: EVERY operation has actor array (can be empty `[]`)\n- [ ] **name**: EVERY operation has semantic name (index/at/search/create/update/erase)\n- [ ] NO fields are undefined or missing\n- [ ] ALL string fields have meaningful content (not empty strings)\n\n### 10.3. Schema Validation\n- [ ] Every operation references actual Prisma schema models\n- [ ] Field existence verified - no assumed fields (deleted_at, created_by, etc.)\n- [ ] Type names match Prisma model names exactly\n- [ ] Request/response type references follow naming conventions\n- [ ] Operations align with model `stance`:\n  * `\"primary\"` \u2192 Full CRUD operations allowed\n  * `\"subsidiary\"` \u2192 Nested operations only\n  * `\"snapshot\"` \u2192 Read operations only (index/at/search)\n- [ ] **Authentication operations excluded**: No operations for signup/login/session management (delegated to authentication service)\n\n### 10.4. Path Parameter Validation\n- [ ] **CRITICAL: Composite unique constraint compliance**:\n  * For each entity with code-based parameters, check Prisma schema `@@unique` constraint\n  * If `@@unique([parent_id, code])` \u2192 Verify parent parameters are included\n  * If `@@unique([code])` \u2192 Verify `{entityCode}` is used (not `{entityId}`)\n  * Parameter descriptions include scope: \"(global scope)\" or \"(scoped to {parent})\"\n- [ ] Every path parameter has corresponding parameter definition\n- [ ] Parameter names in path match parameter object `name` exactly\n- [ ] Parameter order in array matches path order\n- [ ] **Code-based identifiers**: Use `{entityCode}` format when `@@unique([code])` exists\n- [ ] **UUID identifiers**: Use `{entityId}` format when no unique code exists\n- [ ] **Composite unique**: Complete parent context included (e.g., `{enterpriseCode}` + `{teamCode}`)\n\n### 10.5. Parameter Definition Quality\n- [ ] Every parameter has `name` matching path parameter\n- [ ] Every parameter has `in: \"path\"` for path parameters\n- [ ] Every parameter has `required: true` (all path parameters are required)\n- [ ] Every parameter has detailed `description` explaining:\n  * What the parameter identifies\n  * Scope of uniqueness (global vs scoped to parent)\n  * Format/pattern if applicable\n- [ ] Every parameter has proper `schema`:\n  * Path parameters: `{ type: \"string\" }` for both UUIDs and codes\n  * Query parameters: Appropriate type (string, number, boolean)\n- [ ] Parameter descriptions are clear and business-oriented\n\n### 10.6. Request Body Validation\n- [ ] POST (create) operations have requestBody with appropriate `IEntity.ICreate` type\n- [ ] PUT (update) operations have requestBody with appropriate `IEntity.IUpdate` type\n- [ ] PATCH (search) operations have requestBody with appropriate `IEntity.IRequest` type\n- [ ] GET (retrieve) operations have NO requestBody (`null`)\n- [ ] DELETE operations have NO requestBody (`null`)\n- [ ] Request body descriptions explain the purpose and structure\n- [ ] Type names follow exact naming conventions:\n  * Create: `IEntityName.ICreate`\n  * Update: `IEntityName.IUpdate`\n  * Search: `IEntityName.IRequest`\n- [ ] **CRITICAL: Request DTOs do NOT duplicate path parameters**:\n  * If path has `{enterpriseCode}` and `{teamCode}`, requestBody type should NOT include those fields\n  * Path parameters provide context automatically\n  * This will be validated by Schema agents\n\n### 10.7. Response Body Validation\n- [ ] GET operations return single entity with detail type `IEntity`\n- [ ] PATCH (search) operations return paginated results `IPageIEntity.ISummary`\n- [ ] POST (create) operations return created entity `IEntity`\n- [ ] PUT (update) operations return updated entity `IEntity`\n- [ ] DELETE operations return deleted entity `IEntity` OR `null` based on schema\n- [ ] Response body descriptions explain what data is returned\n- [ ] Type names follow exact naming conventions:\n  * Single entity: `IEntityName`\n  * List/Summary: `IEntityName.ISummary`\n  * Paginated: `IPageIEntityName.ISummary`\n- [ ] Computed operations use appropriate response types\n\n### 10.8. Authorization Design\n- [ ] authorizationActors reflect realistic access patterns\n- [ ] Sensitive operations restricted to appropriate actors\n- [ ] Public operations have empty array `[]` OR appropriate public actors\n- [ ] Actor names use camelCase (not PascalCase, not snake_case)\n- [ ] Consider actor multiplication: operations \u00D7 actors = total endpoints\n- [ ] Avoid over-specification - only add actors that truly need separate endpoints\n- [ ] Self-service operations (user managing own data) identified correctly\n\n### 10.9. Description Quality\n- [ ] **specification**: Technical, implementation-focused, describes HOW\n- [ ] **description**: Multi-paragraph (3+ paragraphs), user-facing, describes WHAT and WHY:\n  * Paragraph 1: Primary purpose and functionality\n  * Paragraph 2: Advanced features, capabilities, options\n  * Paragraph 3: Security, performance, integration considerations\n- [ ] **summary**: One-line concise description for API docs\n- [ ] All descriptions in clear English\n- [ ] Descriptions reference actual Prisma schema models/fields\n- [ ] Descriptions explain business value, not just technical details\n- [ ] Parameter descriptions include scope indicators for composite unique\n\n### 10.10. Semantic Naming\n- [ ] Operation `name` uses standard CRUD semantics:\n  * `index` - PATCH search/list operations\n  * `at` - GET single resource retrieval\n  * `search` - PATCH with complex query (alternative to index)\n  * `create` - POST creation operations\n  * `update` - PUT update operations\n  * `erase` - DELETE removal operations\n- [ ] Names are NOT TypeScript/JavaScript reserved words\n- [ ] Names use camelCase notation\n- [ ] Names reflect the actual operation purpose\n- [ ] Consistent naming across similar operations\n\n### 10.11. HTTP Method Alignment\n- [ ] PATCH for search/list/query operations (not GET with query params)\n- [ ] GET for single resource retrieval by identifier\n- [ ] POST for resource creation\n- [ ] PUT for resource updates (full replacement)\n- [ ] DELETE for resource removal\n- [ ] Method matches the semantic name:\n  * index/search \u2192 PATCH\n  * at \u2192 GET\n  * create \u2192 POST\n  * update \u2192 PUT\n  * erase \u2192 DELETE\n\n### 10.12. Conservative Generation\n- [ ] Only business-necessary operations generated\n- [ ] System-managed data excluded (no create/update operations)\n- [ ] Pure join tables excluded from direct operations\n- [ ] Audit/log tables excluded from operations\n- [ ] **Authentication/session operations excluded**: No signup/login/session CRUD operations\n- [ ] Operations reflect actual user workflows\n- [ ] No redundant or duplicate operations\n- [ ] Actor multiplication considered (avoid operation explosion)\n\n### 10.13. Computed Operations\n- [ ] Analytics operations properly structured (if needed from requirements)\n- [ ] Dashboard operations include multiple data sources (if needed)\n- [ ] Search operations support complex queries (if needed)\n- [ ] Report operations designed for data export (if needed)\n- [ ] Computed operations use appropriate HTTP methods (usually PATCH)\n- [ ] Computed operations reference underlying Prisma models in specification\n\n### 10.14. Path-Operation Consistency\n- [ ] Every provided endpoint has exactly ONE operation\n- [ ] Operation path matches endpoint path EXACTLY (character-by-character)\n- [ ] Operation method matches endpoint method EXACTLY\n- [ ] No operations created for endpoints not in provided list\n- [ ] No endpoints from provided list skipped without reason\n\n### 10.15. Quality Standards\n- [ ] All required fields present and populated\n- [ ] No undefined or null values where not allowed\n- [ ] All JSON syntax valid (proper quotes, no trailing commas)\n- [ ] Type names follow exact conventions\n- [ ] Descriptions are comprehensive and helpful\n- [ ] Parameter definitions are complete\n- [ ] Authorization design is realistic and secure\n- [ ] **No authentication operations**: Verified exclusion of signup/login/session management\n\n### 10.16. Function Call Preparation\n- [ ] Output array ready with complete `IAutoBeInterfaceOperationApplication.IOperation[]`\n- [ ] Every operation object has ALL 10 required fields\n- [ ] JSON array properly formatted and valid\n- [ ] Ready to call `process({ request: { type: \"complete\", operations: [...] } })` immediately\n- [ ] NO user confirmation needed\n- [ ] NO waiting for approval\n\n**REMEMBER**: You MUST call `process({ request: { type: \"complete\", operations: [...] } })` immediately after this checklist. NO user confirmation needed. NO waiting for approval. Execute the function NOW.\n\n---\n\n**YOUR MISSION**: Generate comprehensive, production-ready API operations that serve real business needs while strictly respecting composite unique constraints, database schema reality, and following all mandatory field requirements. Call `process({ request: { type: \"complete\", operations: [...] } })` immediately with complete operation objects." /* AutoBeSystemPromptConstant.INTERFACE_OPERATION */,
+            },
+            ...props.preliminary.getHistories(),
+            {
+                type: "systemMessage",
+                id: (0, uuid_1.v7)(),
+                created_at: new Date().toISOString(),
+                text: utils_1.StringUtil.trim `
+          ## Service Prefix
+          - Original: ${props.prefix}
+          - PascalCase for DTOs: ${props.prefix
+                    .split(/[-_]/)
+                    .map((p) => p.charAt(0).toUpperCase() + p.slice(1))
+                    .join("")}
+          - Expected DTO pattern: I${props.prefix
+                    .split(/[-_]/)
+                    .map((p) => p.charAt(0).toUpperCase() + p.slice(1))
+                    .join("")}{EntityName}
+        `,
+            },
+            {
+                type: "assistantMessage",
+                id: (0, uuid_1.v7)(),
+                created_at: new Date().toISOString(),
+                text: utils_1.StringUtil.trim `
+          ## API Design Instructions
+
+          The following API-specific instructions were extracted from
+          the user's requirements. These focus on API interface design aspects
+          such as endpoint patterns, request/response formats, DTO schemas,
+          and operation specifications.
+
+          Follow these instructions when designing operation specifications.
+          Carefully distinguish between:
+          - Suggestions or recommendations (consider these as guidance)
+          - Direct specifications or explicit commands (these must be followed exactly)
+
+          When instructions contain direct specifications or explicit design decisions,
+          follow them precisely even if you believe you have better alternatives.
+
+          ${props.instruction}
+
+          ## Operations
+
+          You have to make API operations for the given endpoints:
+
+          \`\`\`json
+          ${JSON.stringify(props.endpoints)}
+          \`\`\`
+
+          If there is a content in the failure, it is to explain why it failed before.
+          Please supplement or modify the Operation accordingly.
+        `,
+            },
+        ],
+        userMessage: "Create API operation specifications for the given endpoints please",
+    };
+};
+exports.transformInterfaceOperationHistory = transformInterfaceOperationHistory;
+//# sourceMappingURL=transformInterfaceOperationHistory.js.map

package/lib/orchestrate/interface/histories/transformInterfaceOperationHistory.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"transformInterfaceOperationHistory.js","sourceRoot":"","sources":["../../../../src/orchestrate/interface/histories/transformInterfaceOperationHistory.ts"],"names":[],"mappings":";;;AACA,yCAA2C;AAC3C,+BAA0B;AAMnB,MAAM,kCAAkC,GAAG,CAAC,KAKlD,EAA6B,EAAE;IAC9B,OAAO;QACL,SAAS,EAAE;YACT;gBACE,IAAI,EAAE,eAAe;gBACrB,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,gilGAAgD;aACrD;YACD,GAAG,KAAK,CAAC,WAAW,CAAC,YAAY,EAAE;YACnC;gBACE,IAAI,EAAE,eAAe;gBACrB,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;wBAEL,KAAK,CAAC,MAAM;mCACD,KAAK,CAAC,MAAM;qBAClC,KAAK,CAAC,MAAM,CAAC;qBACb,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;qBAClD,IAAI,CAAC,EAAE,CAAC;qCACgB,KAAK,CAAC,MAAM;qBACpC,KAAK,CAAC,MAAM,CAAC;qBACb,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;qBAClD,IAAI,CAAC,EAAE,CAAC;SACZ;aACF;YACD;gBACE,IAAI,EAAE,kBAAkB;gBACxB,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;YAgBjB,KAAK,CAAC,WAAW;;;;;;;YAOjB,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,SAAS,CAAC;;;;;SAKlC;aACF;SACF;QACD,WAAW,EACT,oEAAoE;KACvE,CAAC;AACJ,CAAC,CAAC;AAtEW,QAAA,kCAAkC,sCAsE7C"}

package/lib/orchestrate/interface/histories/transformInterfaceOperationReviewHistory.d.ts

@@ -0,0 +1,7 @@
+import { AutoBeOpenApi } from "@autobe/interface";
+import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
+import { AutoBePreliminaryController } from "../../common/AutoBePreliminaryController";
+export declare function transformInterfaceOperationReviewHistory(props: {
+    preliminary: AutoBePreliminaryController<"analysisFiles" | "prismaSchemas">;
+    operations: AutoBeOpenApi.IOperation[];
+}): IAutoBeOrchestrateHistory;