@autobe/agent 0.17.1 → 0.19.1

package/lib/{orchestrate/prisma/orchestratePrismaSchemas.js → agent/src/orchestrate/prisma/orchestratePrismaReview.js}

@@ -45,148 +45,83 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.orchestratePrismaSchemas = orchestratePrismaSchemas;
+exports.orchestratePrismaReview = orchestratePrismaReview;
 const __typia_transform__isUniqueItems = __importStar(require("typia/lib/internal/_isUniqueItems.js"));
 const __typia_transform__validateReport = __importStar(require("typia/lib/internal/_validateReport.js"));
-const core_1 = require("@agentica/core");
 const typia_1 = __importDefault(require("typia"));
 const assertSchemaModel_1 = require("../../context/assertSchemaModel");
-const enforceToolCall_1 = require("../../utils/enforceToolCall");
-const forceRetry_1 = require("../../utils/forceRetry");
-const transformPrismaSchemaHistories_1 = require("./histories/transformPrismaSchemaHistories");
-function orchestratePrismaSchemas(ctx, components) {
+const transformPrismaReviewHistories_1 = require("./histories/transformPrismaReviewHistories");
+function orchestratePrismaReview(ctx, application, schemas, componentList) {
     return __awaiter(this, void 0, void 0, function* () {
-        const start = new Date();
-        const total = components
-            .map((c) => c.tables.length)
-            .reduce((x, y) => x + y, 0);
-        let completed = 0;
-        return yield Promise.all(components.map((comp) => __awaiter(this, void 0, void 0, function* () {
-            var _a, _b;
-            const targetComponent = comp;
-            const otherComponents = components.filter((y) => comp !== y);
-            const result = yield (0, forceRetry_1.forceRetry)(() => process(ctx, targetComponent, otherComponents));
-            const event = {
-                type: "prismaSchemas",
-                created_at: start.toISOString(),
-                thinking: result.thinking,
-                draft: result.draft,
-                review: result.review,
-                final: result.final,
-                file: {
-                    filename: comp.filename,
-                    namespace: comp.namespace,
-                    models: result.models,
-                },
-                completed: (completed += comp.tables.length),
-                total,
-                step: (_b = (_a = ctx.state().analyze) === null || _a === void 0 ? void 0 : _a.step) !== null && _b !== void 0 ? _b : 0,
-            };
-            ctx.dispatch(event);
-            return event;
-        })));
+        const progress = {
+            completed: 0,
+            total: componentList.length,
+        };
+        return (yield Promise.all(componentList.map((component) => __awaiter(this, void 0, void 0, function* () {
+            try {
+                return yield step(ctx, application, schemas, component, progress);
+            }
+            catch (_a) {
+                ++progress.completed;
+                return null;
+            }
+        })))).filter((v) => v !== null);
     });
 }
-function process(ctx, targetComponent, otherComponents) {
+function step(ctx, application, schemas, component, progress) {
     return __awaiter(this, void 0, void 0, function* () {
-        var _a;
+        var _a, _b, _c, _d;
+        const start = new Date();
         const pointer = {
             value: null,
         };
-        const agentica = new core_1.MicroAgentica({
-            model: ctx.model,
-            vendor: ctx.vendor,
-            config: Object.assign(Object.assign({}, ((_a = ctx.config) !== null && _a !== void 0 ? _a : {})), { executor: {
-                    describe: null,
-                } }),
-            histories: (0, transformPrismaSchemaHistories_1.transformPrismaSchemaHistories)(ctx.state().analyze.files, targetComponent, otherComponents),
-            controllers: [
-                createApplication(ctx, {
-                    targetComponent,
-                    otherComponents,
-                    build: (next) => {
-                        pointer.value = next;
-                    },
-                }),
-            ],
-        });
-        (0, enforceToolCall_1.enforceToolCall)(agentica);
-        yield agentica.conversate("Make prisma schema file please").finally(() => {
-            const tokenUsage = agentica.getTokenUsage().aggregate;
-            ctx.usage().record(tokenUsage, ["prisma"]);
+        const { tokenUsage } = yield ctx.conversate({
+            source: "prismaReview",
+            histories: (0, transformPrismaReviewHistories_1.transformPrismaReviewHistories)({
+                analysis: (_b = (_a = ctx
+                    .state()
+                    .analyze) === null || _a === void 0 ? void 0 : _a.files.map((file) => ({ [file.filename]: file.content })).reduce((acc, cur) => {
+                    return Object.assign(acc, cur);
+                }, {})) !== null && _b !== void 0 ? _b : {},
+                application,
+                schemas,
+                component,
+            }),
+            controller: createController(ctx, {
+                build: (next) => {
+                    pointer.value = next;
+                },
+            }),
+            enforceFunctionCall: true,
+            message: "Please review the Prisma schema file.",
         });
         if (pointer.value === null)
-            throw new Error("Unreachable code: Prisma Schema not generated");
-        return pointer.value;
+            throw new Error("Failed to review the Prisma schema.");
+        const event = {
+            type: "prismaReview",
+            created_at: start.toISOString(),
+            filename: component.filename,
+            review: pointer.value.review,
+            plan: pointer.value.plan,
+            modifications: pointer.value.modifications,
+            tokenUsage,
+            completed: ++progress.completed,
+            total: progress.total,
+            step: (_d = (_c = ctx.state().analyze) === null || _c === void 0 ? void 0 : _c.step) !== null && _d !== void 0 ? _d : 0,
+        };
+        ctx.dispatch(event);
+        return event;
     });
 }
-function createApplication(ctx, props) {
+function createController(ctx, props) {
     (0, assertSchemaModel_1.assertSchemaModel)(ctx.model);
     const application = collection[ctx.model];
-    // application.functions[0].validate = (
-    //   input: unknown,
-    // ): IValidation<IMakePrismaSchemaFileProps> => {
-    //   const result: IValidation<IMakePrismaSchemaFileProps> =
-    //     typia.validate<IMakePrismaSchemaFileProps>(input);
-    //   if (result.success === false) return result;
-    //   const everyModels: AutoBePrisma.IModel[] = result.data.models;
-    //   result.data.models = result.data.models.filter((m) =>
-    //     props.otherComponents.every((oc) => oc.tables.includes(m.name) === false),
-    //   );
-    //   const expected: string[] = props.targetComponent.tables;
-    //   const actual: string[] = result.data.models.map((m) => m.name);
-    //   const missed: string[] = expected.filter(
-    //     (x) => actual.includes(x) === false,
-    //   );
-    //   if (missed.length === 0) return result;
-    //   ctx.dispatch({
-    //     type: "prismaInsufficient",
-    //     created_at: new Date().toISOString(),
-    //     component: props.targetComponent,
-    //     actual: everyModels,
-    //     missed,
-    //     tablesToCreate: result.data.tablesToCreate,
-    //     validationReview: result.data.validationReview,
-    //     confirmedTables: result.data.confirmedTables,
-    //   });
-    //   return {
-    //     success: false,
-    //     data: result.data,
-    //     errors: [
-    //       {
-    //         path: "$input.file.models",
-    //         value: result.data.models,
-    //         expected: `Array<AutoBePrisma.IModel>`,
-    //         description: [
-    //           "You missed some tables from the current domain's component.",
-    //           "",
-    //           "Look at the following details to fix the schemas. Never forget to",
-    //           "compose the `missed` tables at the next function calling.",
-    //           "",
-    //           "- filename: current domain's filename",
-    //           "- namespace: current domain's namespace",
-    //           "- expected: expected tables in the current domain",
-    //           "- actual: actual tables you made",
-    //           "- missed: tables you have missed, and you have to compose again",
-    //           "",
-    //           JSON.stringify({
-    //             filename: props.targetComponent.filename,
-    //             namespace: props.targetComponent.namespace,
-    //             expected,
-    //             actual,
-    //             missed,
-    //           }),
-    //         ].join("\n"),
-    //       },
-    //     ],
-    //   };
-    // };
     return {
         protocol: "class",
-        name: "Prisma Generator",
+        name: "Prisma Schema Review",
         application,
         execute: {
-            makePrismaSchemaFile: (next) => {
+            reviewSchemaFile: (next) => {
                 props.build(next);
             },
         },
@@ -200,29 +135,21 @@ const claude = {
     },
     functions: [
         {
-            name: "makePrismaSchemaFile",
+            name: "reviewSchemaFile",
             parameters: {
-                description: " Properties containing the file\n\n------------------------------\n\nCurrent Type: {@link IAutoBePrismaSchemaApplication.IProps}",
+                description: "Current Type: {@link IAutoBePrismaReviewApplication.IProps}",
                 type: "object",
                 properties: {
-                    thinking: {
-                        description: "Step 1: Strategic database design analysis and planning.\n\nAI analyzes the target component and business requirements to formulate a\ncomprehensive database design strategy. This planning phase is crucial\nfor creating well-structured, normalized schemas that align with business\nobjectives. The AI must define table structures, relationships, indexing\nstrategies, and data integrity constraints before proceeding to schema\nimplementation.\n\n**Key Considerations:**\n\n- **Assignment Validation**: Extract targetComponent.tables as the complete\n  specification\n- **Table Count**: Must create exactly targetComponent.tables.length models\n- **Other Components**: Identify already-created tables for foreign key\n  references only\n- **Normalization**: Strict adherence to 1NF, 2NF, 3NF principles\n- **Snapshot Architecture**: Design for historical data preservation and\n  audit trails\n- **Junction Tables**: Plan M:N relationships with proper naming\n  ({table1}_{table2})\n- **Materialized Views**: Identify needs for mv_ prefixed denormalized\n  tables\n\nWorkflow: Component analysis \u2192 Strategic planning \u2192 Design rationale",
-                        type: "string"
-                    },
-                    draft: {
-                        description: "Step 2: Initial Prisma schema code implementation.\n\nAI generates the first working version of the Prisma schema based on the\nstrategic plan. This draft must be syntactically correct Prisma Schema\nLanguage (PSL) code that implements all planned tables, relationships,\nand constraints. The schema should follow Prisma conventions while\nincorporating enterprise patterns like snapshot tables and materialized\nviews.\n\n**Implementation Requirements:**\n\n- **Exact Table Names**: Use EXACT names from targetComponent.tables (NO\n  CHANGES)\n- **Valid PSL Syntax**: Proper model blocks, field definitions, and\n  directives\n- **Primary Keys**: Always UUID type with `@id` directive\n- **Foreign Keys**: UUID type following {target_model}_id naming pattern\n- **Data Types**: uuid, string, int, double, datetime, boolean, uri (no\n  pre-calculated fields)\n- **Relationships**: Proper `@relation` directives for 1:1, 1:N, M:N\n  patterns\n- **Descriptions**: Follow format with requirements mapping and business\n  purpose\n- **NO Prohibited Fields**: No totals, cached values, aggregates in regular\n  tables\n\nWorkflow: Strategic plan \u2192 PSL implementation \u2192 Functional schema code",
-                        type: "string"
-                    },
                     review: {
-                        description: "Step 3: Schema code review and quality assessment.\n\nAI performs a thorough review of the draft schema implementation,\nexamining multiple quality dimensions to ensure production readiness.\nThis review process identifies issues, suggests improvements, and\nvalidates compliance with best practices.\n\n**Review Dimensions:**\n\n**Syntax & Compilation:**\n\n- Prisma schema syntax errors and invalid directives\n- Model naming matches targetComponent.tables EXACTLY\n- Field type appropriateness (uuid for keys, no calculated fields)\n- Relationship definition correctness (`@relation` syntax)\n\n**Database Design Quality:**\n\n- **Normalization Compliance**:\n\n  - 1NF: Atomic values, no repeating groups\n  - 2NF: No partial dependencies on composite keys\n  - 3NF: No transitive dependencies\n- **Prohibited Fields Check**: No pre-calculated totals, cached values, or\n  aggregates in regular tables\n- **Snapshot Pattern**: Proper implementation for audit trails\n- **Junction Tables**: Correct naming ({table1}_{table2}) and structure\n\n**Index Strategy Validation:**\n\n- NO single foreign key indexes (Prisma auto-creates these)\n- Composite indexes for query patterns\n- Unique indexes for business constraints\n- GIN indexes for full-text search fields\n\n**Description Quality:**\n\n- Models include: requirement mapping, business purpose, relationships,\n  behaviors\n- Fields include: requirement aspect, business meaning, normalization\n  rationale\n\nWorkflow: Draft schema \u2192 Systematic analysis \u2192 Specific improvements",
+                        description: "Comprehensive review analysis of the proposed schema modifications.\n\nContains the AI agent's detailed evaluation of the schema changes,\nincluding validation of normalization compliance, relationship integrity,\nindex optimization, and business requirement alignment. The review\nidentifies potential issues and confirms adherence to best practices.\n\n**Review Dimensions:**\n\n- **Normalization Validation**: Confirms 3NF compliance and proper data\n  structure\n- **Relationship Integrity**: Validates foreign key references and\n  cardinality\n- **Performance Optimization**: Reviews indexing strategy and query\n  patterns\n- **Business Logic Alignment**: Ensures schema supports all use cases\n- **Naming Conventions**: Verifies consistent naming patterns\n- **Data Type Consistency**: Confirms appropriate field types\n- **Temporal Field Handling**: Validates audit trail implementation\n\n**Example:**\n\n    \"After reviewing the schema modifications:\n    1. All tables properly implement UUID primary keys\n    2. Foreign key relationships correctly reference existing models\n    3. Composite indexes optimize for common query patterns\n    4. Snapshot tables include proper temporal fields\n    5. Materialized views (mv_) contain appropriate denormalization\n    The schema follows all best practices and is ready for implementation.\"",
                         type: "string"
                     },
-                    final: {
-                        description: "Step 4: Final production-ready Prisma schema code.\n\nAI produces the final, polished version of the Prisma schema\nincorporating all review feedback. This code represents the completed\nschema implementation, ready for database migration and production\ndeployment. All identified issues must be resolved, and the schema must\nmeet enterprise-grade quality standards.\n\n**Final Schema Characteristics:**\n\n- **Complete Coverage**: All targetComponent.tables implemented with exact\n  names\n- **Zero Errors**: Valid PSL syntax, no compilation warnings\n- **Proper Relationships**: All foreign keys reference existing tables\n  correctly\n- **Optimized Indexes**: Strategic indexes without redundant foreign key\n  indexes\n- **Full Normalization**: Strict 3NF compliance, denormalization only in\n  mv_ tables\n- **Enterprise Documentation**: Complete descriptions with business context\n- **Audit Support**: Proper snapshot patterns and temporal fields\n  (created_at, updated_at, deleted_at)\n- **Type Safety**: Consistent use of UUID for all keys, appropriate field\n  types\n\nWorkflow: Review feedback \u2192 Schema refinement \u2192 Production-ready PSL code",
+                    plan: {
+                        description: "Strategic database design plan that guided the schema creation.\n\nContains the original planning document that outlines the database\narchitecture strategy, including table structures, relationships,\nnormalization approach, and business requirement mapping. This plan\nserves as the blueprint for validating the implemented schema.\n\n**Planning Components:**\n\n- **Business Requirements**: Mapping of business needs to database\n  structures\n- **Table Design**: Entity definitions and attribute specifications\n- **Relationship Strategy**: Cardinality and referential integrity planning\n- **Normalization Approach**: Application of 1NF, 2NF, 3NF principles\n- **Performance Considerations**: Index strategy and query optimization\n- **Snapshot Architecture**: Temporal data handling and audit requirements\n- **Materialized Views**: Denormalization strategy for performance\n\n**Example:**\n\n    \"Database Design Strategy:\n    Component: Sales Domain\n    Tables: shopping_sales, shopping_sale_snapshots, shopping_sale_units\n\n    Design Approach:\n    - Normalize product catalog to 3NF for data integrity\n    - Implement snapshot pattern for price history tracking\n    - Create composite indexes for product search queries\n    - Use materialized views for sales analytics dashboards\"",
                         type: "string"
                     },
-                    models: {
-                        description: "Step 5: Structured AST representation of the Prisma schema models.\n\nAI transforms the final Prisma schema code into a structured Abstract\nSyntax Tree (AST) representation using the AutoBePrisma.IModel interface.\nThis involves critical reinterpretation and reclassification of the final\ncode to conform to AST constraints.\n\n**CRITICAL: Reinterpretation & Post-Processing Required**\n\nThe AI-generated final code may not directly map to valid AST structures\ndue to:\n\n- Complex Prisma directives that need decomposition\n- Field attributes that require reclassification\n- Implicit relationships that need explicit AST representation\n- Schema-level constructs that must be distributed to models\n\n**Required Post-Processing Steps:**\n\n1. **Field Reclassification**: Separate fields into primary, foreign, and\n   plain categories\n2. **Relationship Extraction**: Convert `@relation` directives to IRelation\n   structures\n3. **Index Decomposition**: Parse `@@index`, `@@unique` into appropriate\n   index arrays\n4. **Type Normalization**: Map Prisma types to AST type enum values\n5. **Constraint Resolution**: Convert schema constraints to AST properties\n\n**AST Structure Requirements:**\n\n- **Model Array**: Each table from targetComponent.tables as IModel\n- **Primary Field**: Always UUID type with name \"id\"\n- **Foreign Fields**: Proper IRelation configurations for all relationships\n- **Plain Fields**: Business fields with correct types (no calculated\n  fields)\n- **Indexes**:\n\n  - UniqueIndexes: Business constraints and composite unique keys\n  - PlainIndexes: Query optimization (no single foreign key indexes)\n  - GinIndexes: Full-text search on string fields\n- **Material Flag**: true only for mv_ prefixed tables\n\n**Relationship Patterns in AST:**\n\n- 1:1: Foreign field with unique: true\n- 1:N: Foreign field with unique: false\n- M:N: Separate junction table model with composite indexes\n\nWorkflow: Final PSL code \u2192 Reinterpretation \u2192 AST transformation \u2192\nStructured models\n\nThis structured representation serves as the ultimate deliverable for\nprogrammatic schema generation and manipulation.",
+                    modifications: {
+                        description: "Array of Prisma models that have been modified based on review feedback.\n\nContains ONLY the models that required changes, not the entire schema.\nEach model represents a complete table definition with all fields,\nrelationships, indexes, and documentation. These modifications will be\napplied to the models to produce the final implementation.\n\n**Model Requirements:**\n\n- **Complete Models**: Each entry must be a complete model definition\n- **Targeted Changes**: Only includes models that need modifications\n- **AST Compliance**: Follows AutoBePrisma.IModel interface structure\n- **Relationship Integrity**: All foreign keys reference valid models\n- **Index Optimization**: Strategic indexes without redundancy\n- **Documentation**: Comprehensive English descriptions\n\n**Notes:**\n\n- Models not included in this array remain unchanged from the models\n- The final schema merges these modifications with the original models\n- All modifications must resolve issues identified in the review",
                         type: "array",
                         items: {
                             $ref: "#/$defs/AutoBePrisma.IModel"
@@ -230,11 +157,9 @@ const claude = {
                     }
                 },
                 required: [
-                    "thinking",
-                    "draft",
                     "review",
-                    "final",
-                    "models"
+                    "plan",
+                    "modifications"
                 ],
                 additionalProperties: false,
                 $defs: {
@@ -243,18 +168,32 @@ const claude = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "Name of the Prisma model (database table name).\n\nShould follow snake_case convention with domain prefix. Examples:\n\"shopping_customers\", \"shopping_sale_snapshots\", \"bbs_articles\"\nMaterialized views use \"mv_\" prefix: \"mv_shopping_sale_last_snapshots\"",
+                                description: "Name of the Prisma model (database table name).\n\nMUST use snake_case naming convention. Examples: \"shopping_customers\",\n\"shopping_sale_snapshots\", \"bbs_articles\" Materialized views use \"mv_\"\nprefix: \"mv_shopping_sale_last_snapshots\"",
                                 type: "string",
                                 pattern: "^[a-z][a-z0-9_]*$"
                             },
                             description: {
-                                description: "Detailed description explaining the business purpose and usage of the\nmodel.\n\nShould include:\n\n- Business context and purpose\n- Key relationships with other models\n- Important behavioral notes or constraints\n- References to related entities using \"{@\\link ModelName}\" syntax Example:\n  \"Customer information, but not a person but a **connection** basis...\"",
+                                description: "Detailed description explaining the business purpose and usage of the\nmodel.\n\nShould include:\n\n- Business context and purpose\n- Key relationships with other models\n- Important behavioral notes or constraints\n- References to related entities using \"{@\\link ModelName}\" syntax\n\n**IMPORTANT**: Description must be written in English. Example: \"Customer\ninformation, but not a person but a **connection** basis...\"",
                                 type: "string"
                             },
                             material: {
                                 description: "Indicates whether this model represents a materialized view for\nperformance optimization.\n\nMaterialized views are read-only computed tables that cache complex query\nresults. They're marked as \"@\\hidden\" in documentation and prefixed with\n\"mv_\" in naming. Examples: mv_shopping_sale_last_snapshots,\nmv_shopping_cart_commodity_prices",
                                 type: "boolean"
                             },
+                            stance: {
+                                description: "Specifies the architectural stance of this model within the database\nsystem.\n\nThis property defines how the table positions itself in relation to other\ntables and what role it plays in the overall data architecture,\nparticularly for API endpoint generation and business logic\norganization.\n\n## Values:\n\n### `\"primary\"` - Main Business Entity\n\nTables that represent core business concepts and serve as the primary\nsubjects of user operations. These tables typically warrant independent\nCRUD API endpoints since users directly interact with these entities.\n\n**Key principle**: If users need to independently create, search, filter,\nor manage entities regardless of their parent context, the table should\nbe primary stance.\n\n**API Requirements:**\n\n- Independent creation endpoints (POST /articles, POST /comments)\n- Search and filtering capabilities across all instances\n- Direct update and delete operations\n- List/pagination endpoints for browsing\n\n**Why `bbs_article_comments` is primary, not subsidiary:**\n\nAlthough comments belong to articles, they require independent\nmanagement:\n\n- **Search across articles**: \"Find all comments by user X across all\n  articles\"\n- **Moderation workflows**: \"List all pending comments for review\"\n- **User activity**: \"Show all comments made by this user\"\n- **Independent operations**: Users edit/delete their comments directly\n- **Notification systems**: \"Alert when any comment is posted\"\n\nIf comments were subsidiary, these operations would be impossible or\nrequire inefficient nested queries through parent articles.\n\n**Characteristics:**\n\n- Represents tangible business concepts that users manage\n- Serves as reference points for other tables\n- Requires comprehensive API operations (CREATE, READ, UPDATE, DELETE)\n- Forms the backbone of the application's business logic\n\n**Examples:**\n\n- `bbs_articles` - Forum posts that users create, edit, and manage\n- `bbs_article_comments` - User comments that require independent\n  management\n\n### `\"subsidiary\"` - Supporting/Dependent Entity\n\nTables that exist to support primary entities but are not independently\nmanaged by users. These tables are typically managed through their parent\nentities and may not need standalone API endpoints.\n\n**Characteristics:**\n\n- Depends on primary or snapshot entities for context\n- Often managed indirectly through parent entity operations\n- May have limited or no independent API operations\n- Provides supporting data or relationships\n\n**Examples:**\n\n- `bbs_article_snapshot_files` - Files attached to article snapshots\n- `bbs_article_snapshot_tags` - Tags associated with article snapshots\n- `bbs_article_comment_snapshot_files` - Files attached to comment\n  snapshots\n\n### `\"snapshot\"` - Historical/Versioning Entity\n\nTables that capture point-in-time states of primary entities for audit\ntrails, version control, or historical tracking. These tables record\nchanges but are rarely modified directly by users.\n\n**Characteristics:**\n\n- Captures historical states of primary entities\n- Typically append-only (rarely updated or deleted)\n- Referenced for audit trails and change tracking\n- Usually read-only from user perspective\n\n**Examples:**\n\n- `bbs_article_snapshots` - Historical states of articles\n- `bbs_article_comment_snapshots` - Comment modification history\n\n## API Generation Guidelines:\n\nThe stance property guides automatic API endpoint generation:\n\n- **`\"primary\"`** \u2192 Generate full CRUD endpoints based on business\n  requirements\n- **`\"subsidiary\"`** \u2192 Evaluate carefully; often managed through parent\n  entities\n- **`\"snapshot\"`** \u2192 Typically read-only endpoints for historical data\n  access",
+                                oneOf: [
+                                    {
+                                        "const": "primary"
+                                    },
+                                    {
+                                        "const": "subsidiary"
+                                    },
+                                    {
+                                        "const": "snapshot"
+                                    }
+                                ]
+                            },
                             primaryField: {
                                 description: "The primary key field of the model.\n\nIn all uploaded schemas, primary keys are always UUID type with \"@\\id\"\ndirective. Usually named \"id\" and marked with \"@\\db.Uuid\" for PostgreSQL\nmapping.",
                                 $ref: "#/$defs/AutoBePrisma.IPrimaryField"
@@ -299,6 +238,7 @@ const claude = {
                             "name",
                             "description",
                             "material",
+                            "stance",
                             "primaryField",
                             "foreignFields",
                             "plainFields",
@@ -312,7 +252,7 @@ const claude = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "Name of the primary key field.\n\nConsistently named \"id\" across all models in the uploaded schemas.\nRepresents the unique identifier for each record in the table.",
+                                description: "Name of the primary key field.\n\nMUST use snake_case naming convention. Consistently named \"id\" across all\nmodels in the uploaded schemas. Represents the unique identifier for each\nrecord in the table.",
                                 type: "string",
                                 pattern: "^[a-z][a-z0-9_]*$"
                             },
@@ -321,7 +261,7 @@ const claude = {
                                 "const": "uuid"
                             },
                             description: {
-                                description: "Description of the primary key field's purpose.\n\nStandard description is \"Primary Key.\" across all models. Serves as the\nunique identifier for the model instance.",
+                                description: "Description of the primary key field's purpose.\n\nStandard description is \"Primary Key.\" across all models. Serves as the\nunique identifier for the model instance.\n\n**IMPORTANT**: Description must be written in English.",
                                 type: "string"
                             }
                         },
@@ -336,7 +276,7 @@ const claude = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "Name of the foreign key field.\n\nFollows convention: \"{target_model_name_without_prefix}_id\" Examples:\n\"shopping_customer_id\", \"bbs_article_id\", \"attachment_file_id\" For\nself-references: \"parent_id\" (e.g., in hierarchical structures)",
+                                description: "Name of the foreign key field.\n\nMUST use snake_case naming convention. Follows convention:\n\"{target_model_name_without_prefix}_id\" Examples: \"shopping_customer_id\",\n\"bbs_article_id\", \"attachment_file_id\" For self-references: \"parent_id\"\n(e.g., in hierarchical structures)",
                                 type: "string",
                                 pattern: "^[a-z][a-z0-9_]*$"
                             },
@@ -345,7 +285,7 @@ const claude = {
                                 "const": "uuid"
                             },
                             description: {
-                                description: "Description explaining the purpose and target of this foreign key\nrelationship.\n\nShould reference the target model using format: \"Target model's {@\\link\nModelName.id}\" Examples: \"Belonged customer's {@\\link\nshopping_customers.id}\" May include additional context about the\nrelationship's business meaning.",
+                                description: "Description explaining the purpose and target of this foreign key\nrelationship.\n\nShould reference the target model using format: \"Target model's {@\\link\nModelName.id}\" Examples: \"Belonged customer's {@\\link\nshopping_customers.id}\" May include additional context about the\nrelationship's business meaning.\n\n**IMPORTANT**: Description must be written in English.",
                                 type: "string"
                             },
                             relation: {
@@ -377,7 +317,7 @@ const claude = {
                             name: {
                                 description: "Name of the relation property in the Prisma model.\n\nThis becomes the property name used to access the related model instance\nthrough the Prisma client. Should be descriptive and reflect the business\nrelationship being modeled.\n\nExamples:\n\n- \"customer\" for shopping_customer_id field\n- \"channel\" for shopping_channel_id field\n- \"parent\" for parent_id field in hierarchical structures\n- \"snapshot\" for versioning relationships\n- \"article\" for bbs_article_id field\n\nNaming convention: camelCase, descriptive of the relationship's business\nmeaning",
                                 type: "string",
-                                pattern: "^[a-zA-Z_][a-zA-Z0-9_]*$"
+                                pattern: "^[a-z][a-zA-Z0-9]*$"
                             },
                             targetModel: {
                                 description: "Name of the target model being referenced by this relation.\n\nMust exactly match an existing model name in the schema. This is used by\nPrisma to establish the foreign key constraint and generate the\nappropriate relation mapping.\n\nExamples:\n\n- \"shopping_customers\" for customer relationships\n- \"shopping_channels\" for channel relationships\n- \"bbs_articles\" for article relationships\n- \"attachment_files\" for file attachments\n\nThe target model should exist in the same schema or be accessible through\nthe Prisma schema configuration.",
@@ -394,7 +334,7 @@ const claude = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "Name of the field in the database table.\n\nShould use snake_case convention. Common patterns from uploaded schemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative",
+                                description: "Name of the field in the database table.\n\nMUST use snake_case naming convention. Common patterns from uploaded\nschemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative",
                                 type: "string",
                                 pattern: "^[a-z][a-z0-9_]*$"
                             },
@@ -425,7 +365,7 @@ const claude = {
                                 ]
                             },
                             description: {
-                                description: "Description explaining the business purpose and usage of this field.\n\nShould clearly explain:\n\n- What business concept this field represents\n- Valid values or constraints if applicable\n- How it relates to business processes\n- Any special behavioral notes Example: \"Amount of cash payment.\" or\n  \"Whether the unit is required or not.\"",
+                                description: "Description explaining the business purpose and usage of this field.\n\nShould clearly explain:\n\n- What business concept this field represents\n- Valid values or constraints if applicable\n- How it relates to business processes\n- Any special behavioral notes\n\n**IMPORTANT**: Description must be written in English. Example: \"Amount\nof cash payment.\" or \"Whether the unit is required or not.\"",
                                 type: "string"
                             },
                             nullable: {
@@ -496,46 +436,38 @@ const claude = {
                     }
                 }
             },
-            description: "Generates comprehensive Prisma schema files based on detailed requirements\nanalysis.\n\nCreates multiple organized schema files following enterprise patterns\nincluding proper domain separation, relationship modeling, snapshot\npatterns, inheritance, materialized views, and comprehensive documentation.\nThe generated schemas implement best practices for scalability,\nmaintainability, and data integrity.",
-            validate: (() => { const _io0 = input => "string" === typeof input.thinking && "string" === typeof input.draft && "string" === typeof input.review && "string" === typeof input.final && (Array.isArray(input.models) && input.models.every(elem => "object" === typeof elem && null !== elem && _io1(elem))); const _io1 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("object" === typeof input.primaryField && null !== input.primaryField && _io2(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every(elem => "object" === typeof elem && null !== elem && _io3(elem))) && (Array.isArray(input.plainFields) && input.plainFields.every(elem => "object" === typeof elem && null !== elem && _io5(elem))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every(elem => "object" === typeof elem && null !== elem && _io6(elem))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every(elem => "object" === typeof elem && null !== elem && _io7(elem))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every(elem => "object" === typeof elem && null !== elem && _io8(elem))); const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description; const _io3 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description && ("object" === typeof input.relation && null !== input.relation && _io4(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable; const _io4 = input => "string" === typeof input.name && RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) && "string" === typeof input.targetModel; const _io5 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && ("string" === input.type || "boolean" === input.type || "uuid" === input.type || "uri" === input.type || "int" === input.type || "double" === input.type || "datetime" === input.type) && "string" === typeof input.description && "boolean" === typeof input.nullable; const _io6 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)) && true === input.unique; const _io7 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)); const _io8 = input => "string" === typeof input.fieldName; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.thinking || _report(_exceptionable, {
-                    path: _path + ".thinking",
-                    expected: "string",
-                    value: input.thinking
-                }), "string" === typeof input.draft || _report(_exceptionable, {
-                    path: _path + ".draft",
-                    expected: "string",
-                    value: input.draft
-                }), "string" === typeof input.review || _report(_exceptionable, {
+            description: "Reviews and validates Prisma schema modifications to ensure compliance with\ndatabase design best practices and business requirements.\n\nPerforms comprehensive validation of proposed schema changes including\nnormalization compliance, relationship integrity, performance optimization,\nand business logic alignment. The review process ensures all modifications\nmaintain data consistency and follow enterprise-level database standards.",
+            validate: (() => { const _io0 = input => "string" === typeof input.review && "string" === typeof input.plan && (Array.isArray(input.modifications) && input.modifications.every(elem => "object" === typeof elem && null !== elem && _io1(elem))); const _io1 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("primary" === input.stance || "subsidiary" === input.stance || "snapshot" === input.stance) && ("object" === typeof input.primaryField && null !== input.primaryField && _io2(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every(elem => "object" === typeof elem && null !== elem && _io3(elem))) && (Array.isArray(input.plainFields) && input.plainFields.every(elem => "object" === typeof elem && null !== elem && _io5(elem))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every(elem => "object" === typeof elem && null !== elem && _io6(elem))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every(elem => "object" === typeof elem && null !== elem && _io7(elem))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every(elem => "object" === typeof elem && null !== elem && _io8(elem))); const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description; const _io3 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description && ("object" === typeof input.relation && null !== input.relation && _io4(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable; const _io4 = input => "string" === typeof input.name && RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name) && "string" === typeof input.targetModel; const _io5 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && ("string" === input.type || "boolean" === input.type || "uuid" === input.type || "uri" === input.type || "int" === input.type || "double" === input.type || "datetime" === input.type) && "string" === typeof input.description && "boolean" === typeof input.nullable; const _io6 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)) && true === input.unique; const _io7 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)); const _io8 = input => "string" === typeof input.fieldName; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.review || _report(_exceptionable, {
                     path: _path + ".review",
                     expected: "string",
                     value: input.review
-                }), "string" === typeof input.final || _report(_exceptionable, {
-                    path: _path + ".final",
+                }), "string" === typeof input.plan || _report(_exceptionable, {
+                    path: _path + ".plan",
                     expected: "string",
-                    value: input.final
-                }), (Array.isArray(input.models) || _report(_exceptionable, {
-                    path: _path + ".models",
+                    value: input.plan
+                }), (Array.isArray(input.modifications) || _report(_exceptionable, {
+                    path: _path + ".modifications",
                     expected: "Array<AutoBePrisma.IModel>",
-                    value: input.models
-                })) && input.models.map((elem, _index9) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".models[" + _index9 + "]",
+                    value: input.modifications
+                })) && input.modifications.map((elem, _index9) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".modifications[" + _index9 + "]",
                     expected: "AutoBePrisma.IModel",
                     value: elem
-                })) && _vo1(elem, _path + ".models[" + _index9 + "]", true && _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".models[" + _index9 + "]",
+                })) && _vo1(elem, _path + ".modifications[" + _index9 + "]", true && _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".modifications[" + _index9 + "]",
                     expected: "AutoBePrisma.IModel",
                     value: elem
                 })).every(flag => flag) || _report(_exceptionable, {
-                    path: _path + ".models",
+                    path: _path + ".modifications",
                     expected: "Array<AutoBePrisma.IModel>",
-                    value: input.models
+                    value: input.modifications
                 })].every(flag => flag); const _vo1 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "string & Pattern<\"^[a-z][a-z0-9_]*$\">",
+                    expected: "string & SnakePattern",
                     value: input.name
                 })) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "(string & Pattern<\"^[a-z][a-z0-9_]*$\">)",
+                    expected: "(string & SnakePattern)",
                     value: input.name
                 }), "string" === typeof input.description || _report(_exceptionable, {
                     path: _path + ".description",
@@ -545,6 +477,10 @@ const claude = {
                     path: _path + ".material",
                     expected: "boolean",
                     value: input.material
+                }), "primary" === input.stance || "subsidiary" === input.stance || "snapshot" === input.stance || _report(_exceptionable, {
+                    path: _path + ".stance",
+                    expected: "(\"primary\" | \"snapshot\" | \"subsidiary\")",
+                    value: input.stance
                 }), ("object" === typeof input.primaryField && null !== input.primaryField || _report(_exceptionable, {
                     path: _path + ".primaryField",
                     expected: "AutoBePrisma.IPrimaryField",
@@ -635,11 +571,11 @@ const claude = {
                     value: input.ginIndexes
                 })].every(flag => flag); const _vo2 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "string & Pattern<\"^[a-z][a-z0-9_]*$\">",
+                    expected: "string & SnakePattern",
                     value: input.name
                 })) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "(string & Pattern<\"^[a-z][a-z0-9_]*$\">)",
+                    expected: "(string & SnakePattern)",
                     value: input.name
                 }), "uuid" === input.type || _report(_exceptionable, {
                     path: _path + ".type",
@@ -651,11 +587,11 @@ const claude = {
                     value: input.description
                 })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "string & Pattern<\"^[a-z][a-z0-9_]*$\">",
+                    expected: "string & SnakePattern",
                     value: input.name
                 })) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "(string & Pattern<\"^[a-z][a-z0-9_]*$\">)",
+                    expected: "(string & SnakePattern)",
                     value: input.name
                 }), "uuid" === input.type || _report(_exceptionable, {
                     path: _path + ".type",
@@ -681,13 +617,13 @@ const claude = {
                     path: _path + ".nullable",
                     expected: "boolean",
                     value: input.nullable
-                })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "string & Pattern<\"^[a-zA-Z_][a-zA-Z0-9_]*$\">",
+                    expected: "string & CamelPattern",
                     value: input.name
                 })) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "(string & Pattern<\"^[a-zA-Z_][a-zA-Z0-9_]*$\">)",
+                    expected: "(string & CamelPattern)",
                     value: input.name
                 }), "string" === typeof input.targetModel || _report(_exceptionable, {
                     path: _path + ".targetModel",
@@ -695,11 +631,11 @@ const claude = {
                     value: input.targetModel
                 })].every(flag => flag); const _vo5 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "string & Pattern<\"^[a-z][a-z0-9_]*$\">",
+                    expected: "string & SnakePattern",
                     value: input.name
                 })) || _report(_exceptionable, {
                     path: _path + ".name",
-                    expected: "(string & Pattern<\"^[a-z][a-z0-9_]*$\">)",
+                    expected: "(string & SnakePattern)",
                     value: input.name
                 }), "string" === input.type || "boolean" === input.type || "uuid" === input.type || "uri" === input.type || "int" === input.type || "double" === input.type || "datetime" === input.type || _report(_exceptionable, {
                     path: _path + ".type",
@@ -767,11 +703,11 @@ const claude = {
                     _report = __typia_transform__validateReport._validateReport(errors);
                     ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                         path: _path + "",
-                        expected: "IAutoBePrismaSchemaApplication.IProps",
+                        expected: "IAutoBePrismaReviewApplication.IProps",
                         value: input
                     })) && _vo0(input, _path + "", true) || _report(true, {
                         path: _path + "",
-                        expected: "IAutoBePrismaSchemaApplication.IProps",
+                        expected: "IAutoBePrismaReviewApplication.IProps",
                         value: input
                     }))(input, "$input", true);
                     const success = 0 === errors.length;
@@ -802,29 +738,21 @@ const collection = {
         },
         functions: [
             {
-                name: "makePrismaSchemaFile",
+                name: "reviewSchemaFile",
                 parameters: {
-                    description: " Properties containing the file\n\n------------------------------\n\nCurrent Type: {@link IAutoBePrismaSchemaApplication.IProps}",
+                    description: "Current Type: {@link IAutoBePrismaReviewApplication.IProps}",
                     type: "object",
                     properties: {
-                        thinking: {
-                            description: "Step 1: Strategic database design analysis and planning.\n\nAI analyzes the target component and business requirements to formulate a\ncomprehensive database design strategy. This planning phase is crucial\nfor creating well-structured, normalized schemas that align with business\nobjectives. The AI must define table structures, relationships, indexing\nstrategies, and data integrity constraints before proceeding to schema\nimplementation.\n\n**Key Considerations:**\n\n- **Assignment Validation**: Extract targetComponent.tables as the complete\n  specification\n- **Table Count**: Must create exactly targetComponent.tables.length models\n- **Other Components**: Identify already-created tables for foreign key\n  references only\n- **Normalization**: Strict adherence to 1NF, 2NF, 3NF principles\n- **Snapshot Architecture**: Design for historical data preservation and\n  audit trails\n- **Junction Tables**: Plan M:N relationships with proper naming\n  ({table1}_{table2})\n- **Materialized Views**: Identify needs for mv_ prefixed denormalized\n  tables\n\nWorkflow: Component analysis \u2192 Strategic planning \u2192 Design rationale",
-                            type: "string"
-                        },
-                        draft: {
-                            description: "Step 2: Initial Prisma schema code implementation.\n\nAI generates the first working version of the Prisma schema based on the\nstrategic plan. This draft must be syntactically correct Prisma Schema\nLanguage (PSL) code that implements all planned tables, relationships,\nand constraints. The schema should follow Prisma conventions while\nincorporating enterprise patterns like snapshot tables and materialized\nviews.\n\n**Implementation Requirements:**\n\n- **Exact Table Names**: Use EXACT names from targetComponent.tables (NO\n  CHANGES)\n- **Valid PSL Syntax**: Proper model blocks, field definitions, and\n  directives\n- **Primary Keys**: Always UUID type with `@id` directive\n- **Foreign Keys**: UUID type following {target_model}_id naming pattern\n- **Data Types**: uuid, string, int, double, datetime, boolean, uri (no\n  pre-calculated fields)\n- **Relationships**: Proper `@relation` directives for 1:1, 1:N, M:N\n  patterns\n- **Descriptions**: Follow format with requirements mapping and business\n  purpose\n- **NO Prohibited Fields**: No totals, cached values, aggregates in regular\n  tables\n\nWorkflow: Strategic plan \u2192 PSL implementation \u2192 Functional schema code",
-                            type: "string"
-                        },
                         review: {
-                            description: "Step 3: Schema code review and quality assessment.\n\nAI performs a thorough review of the draft schema implementation,\nexamining multiple quality dimensions to ensure production readiness.\nThis review process identifies issues, suggests improvements, and\nvalidates compliance with best practices.\n\n**Review Dimensions:**\n\n**Syntax & Compilation:**\n\n- Prisma schema syntax errors and invalid directives\n- Model naming matches targetComponent.tables EXACTLY\n- Field type appropriateness (uuid for keys, no calculated fields)\n- Relationship definition correctness (`@relation` syntax)\n\n**Database Design Quality:**\n\n- **Normalization Compliance**:\n\n  - 1NF: Atomic values, no repeating groups\n  - 2NF: No partial dependencies on composite keys\n  - 3NF: No transitive dependencies\n- **Prohibited Fields Check**: No pre-calculated totals, cached values, or\n  aggregates in regular tables\n- **Snapshot Pattern**: Proper implementation for audit trails\n- **Junction Tables**: Correct naming ({table1}_{table2}) and structure\n\n**Index Strategy Validation:**\n\n- NO single foreign key indexes (Prisma auto-creates these)\n- Composite indexes for query patterns\n- Unique indexes for business constraints\n- GIN indexes for full-text search fields\n\n**Description Quality:**\n\n- Models include: requirement mapping, business purpose, relationships,\n  behaviors\n- Fields include: requirement aspect, business meaning, normalization\n  rationale\n\nWorkflow: Draft schema \u2192 Systematic analysis \u2192 Specific improvements",
+                            description: "Comprehensive review analysis of the proposed schema modifications.\n\nContains the AI agent's detailed evaluation of the schema changes,\nincluding validation of normalization compliance, relationship integrity,\nindex optimization, and business requirement alignment. The review\nidentifies potential issues and confirms adherence to best practices.\n\n**Review Dimensions:**\n\n- **Normalization Validation**: Confirms 3NF compliance and proper data\n  structure\n- **Relationship Integrity**: Validates foreign key references and\n  cardinality\n- **Performance Optimization**: Reviews indexing strategy and query\n  patterns\n- **Business Logic Alignment**: Ensures schema supports all use cases\n- **Naming Conventions**: Verifies consistent naming patterns\n- **Data Type Consistency**: Confirms appropriate field types\n- **Temporal Field Handling**: Validates audit trail implementation\n\n**Example:**\n\n    \"After reviewing the schema modifications:\n    1. All tables properly implement UUID primary keys\n    2. Foreign key relationships correctly reference existing models\n    3. Composite indexes optimize for common query patterns\n    4. Snapshot tables include proper temporal fields\n    5. Materialized views (mv_) contain appropriate denormalization\n    The schema follows all best practices and is ready for implementation.\"",
                             type: "string"
                         },
-                        final: {
-                            description: "Step 4: Final production-ready Prisma schema code.\n\nAI produces the final, polished version of the Prisma schema\nincorporating all review feedback. This code represents the completed\nschema implementation, ready for database migration and production\ndeployment. All identified issues must be resolved, and the schema must\nmeet enterprise-grade quality standards.\n\n**Final Schema Characteristics:**\n\n- **Complete Coverage**: All targetComponent.tables implemented with exact\n  names\n- **Zero Errors**: Valid PSL syntax, no compilation warnings\n- **Proper Relationships**: All foreign keys reference existing tables\n  correctly\n- **Optimized Indexes**: Strategic indexes without redundant foreign key\n  indexes\n- **Full Normalization**: Strict 3NF compliance, denormalization only in\n  mv_ tables\n- **Enterprise Documentation**: Complete descriptions with business context\n- **Audit Support**: Proper snapshot patterns and temporal fields\n  (created_at, updated_at, deleted_at)\n- **Type Safety**: Consistent use of UUID for all keys, appropriate field\n  types\n\nWorkflow: Review feedback \u2192 Schema refinement \u2192 Production-ready PSL code",
+                        plan: {
+                            description: "Strategic database design plan that guided the schema creation.\n\nContains the original planning document that outlines the database\narchitecture strategy, including table structures, relationships,\nnormalization approach, and business requirement mapping. This plan\nserves as the blueprint for validating the implemented schema.\n\n**Planning Components:**\n\n- **Business Requirements**: Mapping of business needs to database\n  structures\n- **Table Design**: Entity definitions and attribute specifications\n- **Relationship Strategy**: Cardinality and referential integrity planning\n- **Normalization Approach**: Application of 1NF, 2NF, 3NF principles\n- **Performance Considerations**: Index strategy and query optimization\n- **Snapshot Architecture**: Temporal data handling and audit requirements\n- **Materialized Views**: Denormalization strategy for performance\n\n**Example:**\n\n    \"Database Design Strategy:\n    Component: Sales Domain\n    Tables: shopping_sales, shopping_sale_snapshots, shopping_sale_units\n\n    Design Approach:\n    - Normalize product catalog to 3NF for data integrity\n    - Implement snapshot pattern for price history tracking\n    - Create composite indexes for product search queries\n    - Use materialized views for sales analytics dashboards\"",
                             type: "string"
                         },
-                        models: {
-                            description: "Step 5: Structured AST representation of the Prisma schema models.\n\nAI transforms the final Prisma schema code into a structured Abstract\nSyntax Tree (AST) representation using the AutoBePrisma.IModel interface.\nThis involves critical reinterpretation and reclassification of the final\ncode to conform to AST constraints.\n\n**CRITICAL: Reinterpretation & Post-Processing Required**\n\nThe AI-generated final code may not directly map to valid AST structures\ndue to:\n\n- Complex Prisma directives that need decomposition\n- Field attributes that require reclassification\n- Implicit relationships that need explicit AST representation\n- Schema-level constructs that must be distributed to models\n\n**Required Post-Processing Steps:**\n\n1. **Field Reclassification**: Separate fields into primary, foreign, and\n   plain categories\n2. **Relationship Extraction**: Convert `@relation` directives to IRelation\n   structures\n3. **Index Decomposition**: Parse `@@index`, `@@unique` into appropriate\n   index arrays\n4. **Type Normalization**: Map Prisma types to AST type enum values\n5. **Constraint Resolution**: Convert schema constraints to AST properties\n\n**AST Structure Requirements:**\n\n- **Model Array**: Each table from targetComponent.tables as IModel\n- **Primary Field**: Always UUID type with name \"id\"\n- **Foreign Fields**: Proper IRelation configurations for all relationships\n- **Plain Fields**: Business fields with correct types (no calculated\n  fields)\n- **Indexes**:\n\n  - UniqueIndexes: Business constraints and composite unique keys\n  - PlainIndexes: Query optimization (no single foreign key indexes)\n  - GinIndexes: Full-text search on string fields\n- **Material Flag**: true only for mv_ prefixed tables\n\n**Relationship Patterns in AST:**\n\n- 1:1: Foreign field with unique: true\n- 1:N: Foreign field with unique: false\n- M:N: Separate junction table model with composite indexes\n\nWorkflow: Final PSL code \u2192 Reinterpretation \u2192 AST transformation \u2192\nStructured models\n\nThis structured representation serves as the ultimate deliverable for\nprogrammatic schema generation and manipulation.",
+                        modifications: {
+                            description: "Array of Prisma models that have been modified based on review feedback.\n\nContains ONLY the models that required changes, not the entire schema.\nEach model represents a complete table definition with all fields,\nrelationships, indexes, and documentation. These modifications will be\napplied to the models to produce the final implementation.\n\n**Model Requirements:**\n\n- **Complete Models**: Each entry must be a complete model definition\n- **Targeted Changes**: Only includes models that need modifications\n- **AST Compliance**: Follows AutoBePrisma.IModel interface structure\n- **Relationship Integrity**: All foreign keys reference valid models\n- **Index Optimization**: Strategic indexes without redundancy\n- **Documentation**: Comprehensive English descriptions\n\n**Notes:**\n\n- Models not included in this array remain unchanged from the models\n- The final schema merges these modifications with the original models\n- All modifications must resolve issues identified in the review",
                             type: "array",
                             items: {
                                 $ref: "#/$defs/AutoBePrisma.IModel"
@@ -832,11 +760,9 @@ const collection = {
                         }
                     },
                     required: [
-                        "thinking",
-                        "draft",
                         "review",
-                        "final",
-                        "models"
+                        "plan",
+                        "modifications"
                     ],
                     additionalProperties: false,
                     $defs: {
@@ -845,17 +771,26 @@ const collection = {
                             type: "object",
                             properties: {
                                 name: {
-                                    description: "Name of the Prisma model (database table name).\n\nShould follow snake_case convention with domain prefix. Examples:\n\"shopping_customers\", \"shopping_sale_snapshots\", \"bbs_articles\"\nMaterialized views use \"mv_\" prefix: \"mv_shopping_sale_last_snapshots\"\n\n\n@pattern ^[a-z][a-z0-9_]*$",
+                                    description: "Name of the Prisma model (database table name).\n\nMUST use snake_case naming convention. Examples: \"shopping_customers\",\n\"shopping_sale_snapshots\", \"bbs_articles\" Materialized views use \"mv_\"\nprefix: \"mv_shopping_sale_last_snapshots\"\n\n\n@pattern ^[a-z][a-z0-9_]*$",
                                     type: "string"
                                 },
                                 description: {
-                                    description: "Detailed description explaining the business purpose and usage of the\nmodel.\n\nShould include:\n\n- Business context and purpose\n- Key relationships with other models\n- Important behavioral notes or constraints\n- References to related entities using \"{@\\link ModelName}\" syntax Example:\n  \"Customer information, but not a person but a **connection** basis...\"",
+                                    description: "Detailed description explaining the business purpose and usage of the\nmodel.\n\nShould include:\n\n- Business context and purpose\n- Key relationships with other models\n- Important behavioral notes or constraints\n- References to related entities using \"{@\\link ModelName}\" syntax\n\n**IMPORTANT**: Description must be written in English. Example: \"Customer\ninformation, but not a person but a **connection** basis...\"",
                                     type: "string"
                                 },
                                 material: {
                                     description: "Indicates whether this model represents a materialized view for\nperformance optimization.\n\nMaterialized views are read-only computed tables that cache complex query\nresults. They're marked as \"@\\hidden\" in documentation and prefixed with\n\"mv_\" in naming. Examples: mv_shopping_sale_last_snapshots,\nmv_shopping_cart_commodity_prices",
                                     type: "boolean"
                                 },
+                                stance: {
+                                    description: "Specifies the architectural stance of this model within the database\nsystem.\n\nThis property defines how the table positions itself in relation to other\ntables and what role it plays in the overall data architecture,\nparticularly for API endpoint generation and business logic\norganization.\n\n## Values:\n\n### `\"primary\"` - Main Business Entity\n\nTables that represent core business concepts and serve as the primary\nsubjects of user operations. These tables typically warrant independent\nCRUD API endpoints since users directly interact with these entities.\n\n**Key principle**: If users need to independently create, search, filter,\nor manage entities regardless of their parent context, the table should\nbe primary stance.\n\n**API Requirements:**\n\n- Independent creation endpoints (POST /articles, POST /comments)\n- Search and filtering capabilities across all instances\n- Direct update and delete operations\n- List/pagination endpoints for browsing\n\n**Why `bbs_article_comments` is primary, not subsidiary:**\n\nAlthough comments belong to articles, they require independent\nmanagement:\n\n- **Search across articles**: \"Find all comments by user X across all\n  articles\"\n- **Moderation workflows**: \"List all pending comments for review\"\n- **User activity**: \"Show all comments made by this user\"\n- **Independent operations**: Users edit/delete their comments directly\n- **Notification systems**: \"Alert when any comment is posted\"\n\nIf comments were subsidiary, these operations would be impossible or\nrequire inefficient nested queries through parent articles.\n\n**Characteristics:**\n\n- Represents tangible business concepts that users manage\n- Serves as reference points for other tables\n- Requires comprehensive API operations (CREATE, READ, UPDATE, DELETE)\n- Forms the backbone of the application's business logic\n\n**Examples:**\n\n- `bbs_articles` - Forum posts that users create, edit, and manage\n- `bbs_article_comments` - User comments that require independent\n  management\n\n### `\"subsidiary\"` - Supporting/Dependent Entity\n\nTables that exist to support primary entities but are not independently\nmanaged by users. These tables are typically managed through their parent\nentities and may not need standalone API endpoints.\n\n**Characteristics:**\n\n- Depends on primary or snapshot entities for context\n- Often managed indirectly through parent entity operations\n- May have limited or no independent API operations\n- Provides supporting data or relationships\n\n**Examples:**\n\n- `bbs_article_snapshot_files` - Files attached to article snapshots\n- `bbs_article_snapshot_tags` - Tags associated with article snapshots\n- `bbs_article_comment_snapshot_files` - Files attached to comment\n  snapshots\n\n### `\"snapshot\"` - Historical/Versioning Entity\n\nTables that capture point-in-time states of primary entities for audit\ntrails, version control, or historical tracking. These tables record\nchanges but are rarely modified directly by users.\n\n**Characteristics:**\n\n- Captures historical states of primary entities\n- Typically append-only (rarely updated or deleted)\n- Referenced for audit trails and change tracking\n- Usually read-only from user perspective\n\n**Examples:**\n\n- `bbs_article_snapshots` - Historical states of articles\n- `bbs_article_comment_snapshots` - Comment modification history\n\n## API Generation Guidelines:\n\nThe stance property guides automatic API endpoint generation:\n\n- **`\"primary\"`** \u2192 Generate full CRUD endpoints based on business\n  requirements\n- **`\"subsidiary\"`** \u2192 Evaluate carefully; often managed through parent\n  entities\n- **`\"snapshot\"`** \u2192 Typically read-only endpoints for historical data\n  access",
+                                    type: "string",
+                                    "enum": [
+                                        "primary",
+                                        "subsidiary",
+                                        "snapshot"
+                                    ]
+                                },
                                 primaryField: {
                                     $ref: "#/$defs/AutoBePrisma.IPrimaryField"
                                 },
@@ -899,6 +834,7 @@ const collection = {
                                 "name",
                                 "description",
                                 "material",
+                                "stance",
                                 "primaryField",
                                 "foreignFields",
                                 "plainFields",
@@ -912,7 +848,7 @@ const collection = {
                             type: "object",
                             properties: {
                                 name: {
-                                    description: "Name of the primary key field.\n\nConsistently named \"id\" across all models in the uploaded schemas.\nRepresents the unique identifier for each record in the table.\n\n\n@pattern ^[a-z][a-z0-9_]*$",
+                                    description: "Name of the primary key field.\n\nMUST use snake_case naming convention. Consistently named \"id\" across all\nmodels in the uploaded schemas. Represents the unique identifier for each\nrecord in the table.\n\n\n@pattern ^[a-z][a-z0-9_]*$",
                                     type: "string"
                                 },
                                 type: {
@@ -923,7 +859,7 @@ const collection = {
                                     ]
                                 },
                                 description: {
-                                    description: "Description of the primary key field's purpose.\n\nStandard description is \"Primary Key.\" across all models. Serves as the\nunique identifier for the model instance.",
+                                    description: "Description of the primary key field's purpose.\n\nStandard description is \"Primary Key.\" across all models. Serves as the\nunique identifier for the model instance.\n\n**IMPORTANT**: Description must be written in English.",
                                     type: "string"
                                 }
                             },
@@ -938,7 +874,7 @@ const collection = {
                             type: "object",
                             properties: {
                                 name: {
-                                    description: "Name of the foreign key field.\n\nFollows convention: \"{target_model_name_without_prefix}_id\" Examples:\n\"shopping_customer_id\", \"bbs_article_id\", \"attachment_file_id\" For\nself-references: \"parent_id\" (e.g., in hierarchical structures)\n\n\n@pattern ^[a-z][a-z0-9_]*$",
+                                    description: "Name of the foreign key field.\n\nMUST use snake_case naming convention. Follows convention:\n\"{target_model_name_without_prefix}_id\" Examples: \"shopping_customer_id\",\n\"bbs_article_id\", \"attachment_file_id\" For self-references: \"parent_id\"\n(e.g., in hierarchical structures)\n\n\n@pattern ^[a-z][a-z0-9_]*$",
                                     type: "string"
                                 },
                                 type: {
@@ -949,7 +885,7 @@ const collection = {
                                     ]
                                 },
                                 description: {
-                                    description: "Description explaining the purpose and target of this foreign key\nrelationship.\n\nShould reference the target model using format: \"Target model's {@\\link\nModelName.id}\" Examples: \"Belonged customer's {@\\link\nshopping_customers.id}\" May include additional context about the\nrelationship's business meaning.",
+                                    description: "Description explaining the purpose and target of this foreign key\nrelationship.\n\nShould reference the target model using format: \"Target model's {@\\link\nModelName.id}\" Examples: \"Belonged customer's {@\\link\nshopping_customers.id}\" May include additional context about the\nrelationship's business meaning.\n\n**IMPORTANT**: Description must be written in English.",
                                     type: "string"
                                 },
                                 relation: {
@@ -978,7 +914,7 @@ const collection = {
                             type: "object",
                             properties: {
                                 name: {
-                                    description: "Name of the relation property in the Prisma model.\n\nThis becomes the property name used to access the related model instance\nthrough the Prisma client. Should be descriptive and reflect the business\nrelationship being modeled.\n\nExamples:\n\n- \"customer\" for shopping_customer_id field\n- \"channel\" for shopping_channel_id field\n- \"parent\" for parent_id field in hierarchical structures\n- \"snapshot\" for versioning relationships\n- \"article\" for bbs_article_id field\n\nNaming convention: camelCase, descriptive of the relationship's business\nmeaning\n\n\n@pattern ^[a-zA-Z_][a-zA-Z0-9_]*$",
+                                    description: "Name of the relation property in the Prisma model.\n\nThis becomes the property name used to access the related model instance\nthrough the Prisma client. Should be descriptive and reflect the business\nrelationship being modeled.\n\nExamples:\n\n- \"customer\" for shopping_customer_id field\n- \"channel\" for shopping_channel_id field\n- \"parent\" for parent_id field in hierarchical structures\n- \"snapshot\" for versioning relationships\n- \"article\" for bbs_article_id field\n\nNaming convention: camelCase, descriptive of the relationship's business\nmeaning\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$",
                                     type: "string"
                                 },
                                 targetModel: {
@@ -996,7 +932,7 @@ const collection = {
                             type: "object",
                             properties: {
                                 name: {
-                                    description: "Name of the field in the database table.\n\nShould use snake_case convention. Common patterns from uploaded schemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative\n\n\n@pattern ^[a-z][a-z0-9_]*$",
+                                    description: "Name of the field in the database table.\n\nMUST use snake_case naming convention. Common patterns from uploaded\nschemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative\n\n\n@pattern ^[a-z][a-z0-9_]*$",
                                     type: "string"
                                 },
                                 type: {
@@ -1013,7 +949,7 @@ const collection = {
                                     ]
                                 },
                                 description: {
-                                    description: "Description explaining the business purpose and usage of this field.\n\nShould clearly explain:\n\n- What business concept this field represents\n- Valid values or constraints if applicable\n- How it relates to business processes\n- Any special behavioral notes Example: \"Amount of cash payment.\" or\n  \"Whether the unit is required or not.\"",
+                                    description: "Description explaining the business purpose and usage of this field.\n\nShould clearly explain:\n\n- What business concept this field represents\n- Valid values or constraints if applicable\n- How it relates to business processes\n- Any special behavioral notes\n\n**IMPORTANT**: Description must be written in English. Example: \"Amount\nof cash payment.\" or \"Whether the unit is required or not.\"",
                                     type: "string"
                                 },
                                 nullable: {
@@ -1083,46 +1019,38 @@ const collection = {
                         }
                     }
                 },
-                description: "Generates comprehensive Prisma schema files based on detailed requirements\nanalysis.\n\nCreates multiple organized schema files following enterprise patterns\nincluding proper domain separation, relationship modeling, snapshot\npatterns, inheritance, materialized views, and comprehensive documentation.\nThe generated schemas implement best practices for scalability,\nmaintainability, and data integrity.",
-                validate: (() => { const _io0 = input => "string" === typeof input.thinking && "string" === typeof input.draft && "string" === typeof input.review && "string" === typeof input.final && (Array.isArray(input.models) && input.models.every(elem => "object" === typeof elem && null !== elem && _io1(elem))); const _io1 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("object" === typeof input.primaryField && null !== input.primaryField && _io2(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every(elem => "object" === typeof elem && null !== elem && _io3(elem))) && (Array.isArray(input.plainFields) && input.plainFields.every(elem => "object" === typeof elem && null !== elem && _io5(elem))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every(elem => "object" === typeof elem && null !== elem && _io6(elem))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every(elem => "object" === typeof elem && null !== elem && _io7(elem))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every(elem => "object" === typeof elem && null !== elem && _io8(elem))); const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description; const _io3 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description && ("object" === typeof input.relation && null !== input.relation && _io4(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable; const _io4 = input => "string" === typeof input.name && RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) && "string" === typeof input.targetModel; const _io5 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && ("string" === input.type || "boolean" === input.type || "uuid" === input.type || "uri" === input.type || "int" === input.type || "double" === input.type || "datetime" === input.type) && "string" === typeof input.description && "boolean" === typeof input.nullable; const _io6 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)) && true === input.unique; const _io7 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)); const _io8 = input => "string" === typeof input.fieldName; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.thinking || _report(_exceptionable, {
-                        path: _path + ".thinking",
-                        expected: "string",
-                        value: input.thinking
-                    }), "string" === typeof input.draft || _report(_exceptionable, {
-                        path: _path + ".draft",
-                        expected: "string",
-                        value: input.draft
-                    }), "string" === typeof input.review || _report(_exceptionable, {
+                description: "Reviews and validates Prisma schema modifications to ensure compliance with\ndatabase design best practices and business requirements.\n\nPerforms comprehensive validation of proposed schema changes including\nnormalization compliance, relationship integrity, performance optimization,\nand business logic alignment. The review process ensures all modifications\nmaintain data consistency and follow enterprise-level database standards.",
+                validate: (() => { const _io0 = input => "string" === typeof input.review && "string" === typeof input.plan && (Array.isArray(input.modifications) && input.modifications.every(elem => "object" === typeof elem && null !== elem && _io1(elem))); const _io1 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("primary" === input.stance || "subsidiary" === input.stance || "snapshot" === input.stance) && ("object" === typeof input.primaryField && null !== input.primaryField && _io2(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every(elem => "object" === typeof elem && null !== elem && _io3(elem))) && (Array.isArray(input.plainFields) && input.plainFields.every(elem => "object" === typeof elem && null !== elem && _io5(elem))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every(elem => "object" === typeof elem && null !== elem && _io6(elem))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every(elem => "object" === typeof elem && null !== elem && _io7(elem))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every(elem => "object" === typeof elem && null !== elem && _io8(elem))); const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description; const _io3 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description && ("object" === typeof input.relation && null !== input.relation && _io4(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable; const _io4 = input => "string" === typeof input.name && RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name) && "string" === typeof input.targetModel; const _io5 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && ("string" === input.type || "boolean" === input.type || "uuid" === input.type || "uri" === input.type || "int" === input.type || "double" === input.type || "datetime" === input.type) && "string" === typeof input.description && "boolean" === typeof input.nullable; const _io6 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)) && true === input.unique; const _io7 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)); const _io8 = input => "string" === typeof input.fieldName; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.review || _report(_exceptionable, {
                         path: _path + ".review",
                         expected: "string",
                         value: input.review
-                    }), "string" === typeof input.final || _report(_exceptionable, {
-                        path: _path + ".final",
+                    }), "string" === typeof input.plan || _report(_exceptionable, {
+                        path: _path + ".plan",
                         expected: "string",
-                        value: input.final
-                    }), (Array.isArray(input.models) || _report(_exceptionable, {
-                        path: _path + ".models",
+                        value: input.plan
+                    }), (Array.isArray(input.modifications) || _report(_exceptionable, {
+                        path: _path + ".modifications",
                         expected: "Array<AutoBePrisma.IModel>",
-                        value: input.models
-                    })) && input.models.map((elem, _index9) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                        path: _path + ".models[" + _index9 + "]",
+                        value: input.modifications
+                    })) && input.modifications.map((elem, _index9) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                        path: _path + ".modifications[" + _index9 + "]",
                         expected: "AutoBePrisma.IModel",
                         value: elem
-                    })) && _vo1(elem, _path + ".models[" + _index9 + "]", true && _exceptionable) || _report(_exceptionable, {
-                        path: _path + ".models[" + _index9 + "]",
+                    })) && _vo1(elem, _path + ".modifications[" + _index9 + "]", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".modifications[" + _index9 + "]",
                         expected: "AutoBePrisma.IModel",
                         value: elem
                     })).every(flag => flag) || _report(_exceptionable, {
-                        path: _path + ".models",
+                        path: _path + ".modifications",
                         expected: "Array<AutoBePrisma.IModel>",
-                        value: input.models
+                        value: input.modifications
                     })].every(flag => flag); const _vo1 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "string & Pattern<\"^[a-z][a-z0-9_]*$\">",
+                        expected: "string & SnakePattern",
                         value: input.name
                     })) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "(string & Pattern<\"^[a-z][a-z0-9_]*$\">)",
+                        expected: "(string & SnakePattern)",
                         value: input.name
                     }), "string" === typeof input.description || _report(_exceptionable, {
                         path: _path + ".description",
@@ -1132,6 +1060,10 @@ const collection = {
                         path: _path + ".material",
                         expected: "boolean",
                         value: input.material
+                    }), "primary" === input.stance || "subsidiary" === input.stance || "snapshot" === input.stance || _report(_exceptionable, {
+                        path: _path + ".stance",
+                        expected: "(\"primary\" | \"snapshot\" | \"subsidiary\")",
+                        value: input.stance
                     }), ("object" === typeof input.primaryField && null !== input.primaryField || _report(_exceptionable, {
                         path: _path + ".primaryField",
                         expected: "AutoBePrisma.IPrimaryField",
@@ -1222,11 +1154,11 @@ const collection = {
                         value: input.ginIndexes
                     })].every(flag => flag); const _vo2 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "string & Pattern<\"^[a-z][a-z0-9_]*$\">",
+                        expected: "string & SnakePattern",
                         value: input.name
                     })) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "(string & Pattern<\"^[a-z][a-z0-9_]*$\">)",
+                        expected: "(string & SnakePattern)",
                         value: input.name
                     }), "uuid" === input.type || _report(_exceptionable, {
                         path: _path + ".type",
@@ -1238,11 +1170,11 @@ const collection = {
                         value: input.description
                     })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "string & Pattern<\"^[a-z][a-z0-9_]*$\">",
+                        expected: "string & SnakePattern",
                         value: input.name
                     })) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "(string & Pattern<\"^[a-z][a-z0-9_]*$\">)",
+                        expected: "(string & SnakePattern)",
                         value: input.name
                     }), "uuid" === input.type || _report(_exceptionable, {
                         path: _path + ".type",
@@ -1268,13 +1200,13 @@ const collection = {
                         path: _path + ".nullable",
                         expected: "boolean",
                         value: input.nullable
-                    })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                    })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "string & Pattern<\"^[a-zA-Z_][a-zA-Z0-9_]*$\">",
+                        expected: "string & CamelPattern",
                         value: input.name
                     })) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "(string & Pattern<\"^[a-zA-Z_][a-zA-Z0-9_]*$\">)",
+                        expected: "(string & CamelPattern)",
                         value: input.name
                     }), "string" === typeof input.targetModel || _report(_exceptionable, {
                         path: _path + ".targetModel",
@@ -1282,11 +1214,11 @@ const collection = {
                         value: input.targetModel
                     })].every(flag => flag); const _vo5 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "string & Pattern<\"^[a-z][a-z0-9_]*$\">",
+                        expected: "string & SnakePattern",
                         value: input.name
                     })) || _report(_exceptionable, {
                         path: _path + ".name",
-                        expected: "(string & Pattern<\"^[a-z][a-z0-9_]*$\">)",
+                        expected: "(string & SnakePattern)",
                         value: input.name
                     }), "string" === input.type || "boolean" === input.type || "uuid" === input.type || "uri" === input.type || "int" === input.type || "double" === input.type || "datetime" === input.type || _report(_exceptionable, {
                         path: _path + ".type",
@@ -1354,11 +1286,11 @@ const collection = {
                         _report = __typia_transform__validateReport._validateReport(errors);
                         ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                             path: _path + "",
-                            expected: "IAutoBePrismaSchemaApplication.IProps",
+                            expected: "IAutoBePrismaReviewApplication.IProps",
                             value: input
                         })) && _vo0(input, _path + "", true) || _report(true, {
                             path: _path + "",
-                            expected: "IAutoBePrismaSchemaApplication.IProps",
+                            expected: "IAutoBePrismaReviewApplication.IProps",
                             value: input
                         }))(input, "$input", true);
                         const success = 0 === errors.length;
@@ -1384,4 +1316,4 @@ const collection = {
     deepseek: claude,
     "3.1": claude,
 };
-//# sourceMappingURL=orchestratePrismaSchemas.js.map
+//# sourceMappingURL=orchestratePrismaReview.js.map