@autobe/agent 0.23.1 → 0.24.1

package/lib/orchestrate/realize/orchestrateRealizeWrite.js

@@ -98,16 +98,16 @@ function orchestrateRealizeWrite(ctx, props) {
         });
         if (pointer.value === null)
             throw new Error("Failed to write code.");
-        pointer.value.implementationCode = yield (0, replaceImportStatements_1.replaceImportStatements)(ctx, {
+        pointer.value.final = yield (0, replaceImportStatements_1.replaceImportStatements)(ctx, {
             operation: props.scenario.operation,
-            code: pointer.value.implementationCode,
+            code: pointer.value.final,
             decoratorType: (_a = props.authorization) === null || _a === void 0 ? void 0 : _a.payload.name,
         });
         const event = {
             type: "realizeWrite",
             id: (0, uuid_1.v7)(),
             location: props.scenario.location,
-            content: pointer.value.implementationCode,
+            content: pointer.value.final,
             tokenUsage,
             completed: ++props.progress.completed,
             total: props.progress.total,
@@ -142,61 +142,52 @@ const claude = {
         {
             name: "coding",
             parameters: {
-                description: " Properties containing the multi-phase implementation plan and code\n\n------------------------------\n\nDescription of the current {@link IAutoBeRealizeWriteApplication.IProps} type:\n\n> Properties for the Realize Write Application following Chain of Thinking (CoT).\n> \n> Each field represents a distinct phase in the reasoning and implementation process,\n> building upon the previous step to create a complete, error-free implementation.\n> This structured approach ensures clarity, debuggability, and systematic thinking.",
+                description: " Properties containing the multi-phase implementation plan and\ncode\n\n------------------------------\n\nDescription of the current {@link IAutoBeRealizeWriteApplication.IProps} type:\n\n> Properties for the Realize Write Application following Chain of Thinking\n> (CoT).\n> \n> Each field represents a distinct phase in the implementation process.\n> Detailed guidelines are in REALIZE_WRITE.md.",
                 type: "object",
                 properties: {
                     plan: {
-                        description: "Step 1 - Planning Phase (CoT: Initial Reasoning)\n\n\uD83E\uDDE0 Provider Function Implementation Plan\n\nThis field outlines the strategic plan for implementing the provider\nfunction according to the Realize Coder Agent specification. Before\nwriting the actual code, think through the logic and structure.\n\nThe plan follows a SCHEMA-FIRST APPROACH:\n\n\uD83D\uDCCB STEP 1 - PRISMA SCHEMA VERIFICATION:\n\nDO:\n\n- Examine the actual Prisma schema model definition\n- List EVERY field that exists in the model with exact types\n- Explicitly note fields that DO NOT exist\n- Verify database compatibility (PostgreSQL AND SQLite)\n\nDO NOT:\n\n- Assume common fields exist without verification\n- Use fields like deleted_at, created_by, updated_by, is_deleted, is_active\n  without checking\n- Use PostgreSQL-specific features like mode: \"insensitive\"\n\n\uD83D\uDCCB STEP 2 - FIELD INVENTORY:\n\n- List ONLY fields confirmed to exist in schema\n- Example: \"Verified fields in user model: id (String), email (String),\n  created_at (DateTime), updated_at (DateTime)\"\n- Example: \"Fields that DO NOT exist: deleted_at, is_active, created_by\"\n\n\uD83D\uDCCB STEP 3 - FIELD ACCESS STRATEGY:\n\n- Plan which verified fields will be used in select, update, create\n  operations\n- For complex operations with type errors, plan to use separate queries\n  instead of nested operations\n\n\uD83D\uDCCB STEP 4 - TYPE COMPATIBILITY:\n\n- Plan DateTime to ISO string conversions using toISOStringSafe()\n- Plan handling of nullable vs required fields\n\n\uD83D\uDCCB STEP 5 - IMPLEMENTATION APPROACH:\n\n- \uD83E\uDDE9 Required business entities (e.g., users, posts, logs) and their\n  relationships\n- \uD83D\uDEE0 Operations needed to fulfill the business scenario (e.g., fetch,\n  create, update) using ONLY verified fields\n- \uD83D\uDD04 Data dependencies between steps (e.g., use userId to fetch related\n  data)\n- \u2705 Validation points (based on business rules, not field presence)\n- \uD83D\uDEA7 Error and edge cases that must be handled explicitly (e.g., missing\n  records)\n- \uD83C\uDFD7 Structure: always a single `async function`, using only `parameters`\n  and `body`\n\n\u26A0\uFE0F Important Constraints:\n\n- Do NOT perform input validation \u2014 assume `parameters` and `body` are\n  already valid\n- Use `typia.random<T>()` with an explanatory comment if logic can't be\n  implemented\n- Never use `any` or make assumptions without sufficient context\n- Use only allowed imports \u2014 DTOs and Prisma types\n- Use `MyGlobal.prisma` for DB access and respect Prisma typing rules\n\n\u26A0\uFE0F TypeScript-specific considerations:\n\n- Do **not** use native `Date` objects directly; always convert all dates\n  using `toISOStringSafe()` and brand as `string &\n  tags.Format<'date-time'>`. This rule applies throughout all phases.\n- Prefer `satisfies` for DTO conformance instead of unsafe `as` casts\n- Avoid weak typing such as `any`, `as any`, or `satisfies any`\n- Use branded types (e.g., `tags.Format<'uuid'>`) and literal unions where\n  applicable\n\n\u2705 Example Structure:\n\n```ts\nexport async function doSomething(\n  user: { id: string & tags.Format<\"uuid\">; type: string },\n  parameters: IParams,\n  body: IBody\n): Promise<IReturn> {\n  const { id } = parameters;\n  const { name } = body;\n  const user = await MyGlobal.prisma.users.findFirst({ where: { id } });\n  if (!user) throw new Error(\"User not found\");\n  ...\n  return result;\n}\n```\n\n\uD83D\uDD0D Feasibility Analysis Requirement:\n\n- Before generating any code, the agent **must analyze** whether the\n  requested implementation is **feasible based on the given Prisma schema\n  and DTO types**.\n- If required fields or relationships are **missing or incompatible**, the\n  plan should explicitly state that the implementation is **not\n  possible** with the current schema/DTO, and no code should be generated\n  in later stages.\n- In such cases, only a detailed **comment in the `implementationCode`**\n  should be returned explaining why the logic cannot be implemented.\n\n\uD83D\uDD25 Error Handling Plan:\n\nIf an error is expected or encountered during implementation:\n\n- Clearly document the error message(s) and TypeScript error codes.\n- Analyze the root cause (e.g., type mismatch, missing field, nullability\n  issue).\n- Define concrete steps to resolve the issue, such as:\n\n  - Adjusting type declarations or using Prisma-generated input types.\n  - Using `?? undefined` to normalize nullable fields.\n  - Applying correct relation handling (e.g., `connect` instead of direct\n      foreign key assignment).\n  - Ensuring all date fields use `.toISOString()` and proper branding.\n- Include fallback or workaround plans if a direct fix is complex.\n- If no error is present, simply omit this section.\n\nThis plan ensures the function will:\n\n- Respect the global architecture and coding conventions\n- Be safe, predictable, and aligned with upstream logic",
+                        description: "Step 1 - Planning Phase (CoT: Initial Reasoning)\n\nStrategic plan following SCHEMA-FIRST APPROACH:\n\n1. Verify Prisma schema fields (list existing and non-existing)\n2. Plan field usage in operations\n3. Plan type conversions and nullable handling\n4. Define implementation approach with error handling\n\nSee REALIZE_WRITE.md for detailed requirements.",
                         type: "string"
                     },
-                    prisma_schemas: {
-                        description: "Step 2 - Schema Definition (CoT: Context Establishment)\n\nThe Prisma schema string that will be used to validate the implementation\nlogic in this file.\n\nYou must **explicitly specify only the relevant models and fields** from\nyour full schema that are used in this implementation. This ensures that\nyour logic is aligned with the expected database structure without\naccidentally introducing unrelated fields or models.\n\n\u26A0\uFE0F Important: The value of this field must be a valid Prisma schema\nstring containing only the models used in this code \u2014 not the entire\nschema.\n\nThis acts as a safeguard against:\n\n- Forgetting required fields used in this implementation\n- Including fields or models that are not actually used",
-                        type: "string"
-                    },
-                    draft_without_date_type: {
-                        description: "Step 3 - Initial Draft (CoT: First Implementation Attempt)\n\nDraft WITHOUT using native Date type.\n\nThis is the initial drafting phase where you outline the basic skeleton\nof the function.\n\nDO NOT: Use the native Date type.\n\n- The function signature must correctly include `user`, `parameters`, and\n  `body` arguments.\n- Design the main flow of business logic, such as DB fetches and early\n  returns based on conditions.\n- Mark any incomplete or missing parts clearly with placeholders (e.g.,\n  comments or temporary values).\n\nImport rules:\n\nDO NOT:\n\n- Add any new import statements manually\n- Write import statements directly (this causes compile errors)\n\nNote: All necessary imports are provided globally or by the system\nautomatically.\n\n\u2705 Requirements:\n\n- Avoid using the `any` type at all costs to ensure type safety.\n- NEVER declare variables with `: Date` type\n- ALWAYS use `string & tags.Format<'date-time'>` for date values\n- Use `toISOStringSafe(new Date())` for current timestamps\n- Maintain a single-function structure; avoid using classes.",
+                    prismaSchemas: {
+                        description: "Step 2 - Relevant Prisma schema models and fields",
                         type: "string"
                     },
                     review: {
-                        description: "Step 4 - Review and Refinement (CoT: Self-Reflection)\n\nA refined version of the draft with improved completeness.\n\n- Replace placeholder logic with real DTO-conformant operations.\n- Add error handling (`throw new Error(...)`) where necessary.\n- Begin resolving structural or type mismatches.\n\n\u2705 Requirements:\n\n- Use `satisfies` to ensure DTO conformity.\n- Avoid unsafe `as` casts unless only for branding or literal narrowing.\n- Use `toISOStringSafe()` for all date conversions (NOT `.toISOString()`).\n- Ensure all object keys strictly conform to the expected type definitions.\n- NEVER use `mode: \"insensitive\"` in string operations (breaks SQLite).",
+                        description: "Step 3 - Refined version with real operations",
                         type: "string"
                     },
-                    implementationCode: {
-                        description: "Step 5 - Complete Implementation (CoT: Final Synthesis)\n\nThe complete and fully correct TypeScript function implementation.\n\n- Passes strict type checking without errors.\n- Uses only safe branding or literal type assertions.\n- Converts all date values properly using `toISOStringSafe()`.\n- Follows DTO structures using `satisfies`.\n- Avoids any weak typing such as `any`, `as any`, or `satisfies any`.\n- Uses only allowed imports (e.g., from `../api/structures` and\n  `MyGlobal.prisma`).\n- NEVER creates intermediate variables for Prisma operations.\n- NEVER uses `mode: \"insensitive\"` (PostgreSQL-only, breaks SQLite).\n\n\u26A0\uFE0F Fallback Behavior:\n\n- If the `plan` phase explicitly determines that the requested logic is\n  **not feasible** due to mismatches or limitations in the provided\n  Prisma schema and DTO types:\n\n  - The implementation must still return a syntactically valid function.\n  - In such cases, return mock data using `typia.random<T>()` wrapped in the\n      correct structure, along with a comment explaining the limitation.\n\n  Example fallback:\n\n```ts\n  // \u26A0\uFE0F Cannot implement logic due to missing relation between A and B\n  export async function someFunction(...) {\n    return typia.random<IReturn>(); // mocked output\n  }\n```\n\n\u26A0\uFE0F Prohibited Practices:\n\n- Do NOT add or modify import statements manually. Imports are handled\n  automatically by the system.\n- Do NOT use `any`, `as any`, or `satisfies any` to bypass type checking.\n- Do NOT assign native `Date` objects directly; always convert them using\n  `toISOStringSafe()`.\n- Do NOT use unsafe type assertions except for safe branding or literal\n  narrowing.\n- Do NOT write code outside the single async function structure (e.g., no\n  classes or multiple functions).\n- Do NOT perform any input validation \u2014 assume all inputs are already\n  validated.\n- Do NOT use dynamic import expressions (`import()`); all imports must be\n  static.\n- Do NOT use Prisma-generated input types; always use types from\n  `../api/structures`.\n- Do NOT use `Object.prototype.hasOwnProperty.call()` for field checks.\n- Do NOT escape newlines or quotes in the implementation string (e.g., no\n  `\\\\n` or `\\\"`); use a properly formatted template literal with actual\n  line breaks instead.",
+                    final: {
+                        description: "Step 4 - Final implementation See REALIZE_WRITE.md for requirements",
                         type: "string"
                     }
                 },
                 required: [
                     "plan",
-                    "prisma_schemas",
-                    "draft_without_date_type",
+                    "prismaSchemas",
                     "review",
-                    "implementationCode"
+                    "final"
                 ],
                 additionalProperties: false,
                 $defs: {}
             },
-            description: "Generates provider function implementation through multi-phase development.\n\nThis method implements a systematic approach to generate NestJS provider\nfunctions that handle business logic for API operations. It follows a\nschema-first approach with multiple refinement phases to ensure type-safe,\nerror-free code generation.\n\nThe generation process includes:\n1. Strategic planning based on Prisma schema analysis\n2. Initial draft without Date type usage\n3. Review and refinement for completeness\n4. Compiler feedback integration if errors detected\n5. Final implementation with all validations and type safety",
-            validate: (() => { const _io0 = input => "string" === typeof input.plan && "string" === typeof input.prisma_schemas && "string" === typeof input.draft_without_date_type && "string" === typeof input.review && "string" === typeof input.implementationCode; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.plan || _report(_exceptionable, {
+            description: "Generates provider function implementation through multi-phase development.\n\nThis method implements a systematic approach to generate NestJS provider\nfunctions that handle business logic for API operations. It follows a\nschema-first approach with multiple refinement phases to ensure type-safe,\nerror-free code generation.\n\nThe generation process includes:\n\n1. Strategic planning based on Prisma schema analysis\n2. Schema definition for relevant models\n3. Review and refinement for completeness\n4. Final implementation with all validations and type safety",
+            validate: (() => { const _io0 = input => "string" === typeof input.plan && "string" === typeof input.prismaSchemas && "string" === typeof input.review && "string" === typeof input.final; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.plan || _report(_exceptionable, {
                     path: _path + ".plan",
                     expected: "string",
                     value: input.plan
-                }), "string" === typeof input.prisma_schemas || _report(_exceptionable, {
-                    path: _path + ".prisma_schemas",
-                    expected: "string",
-                    value: input.prisma_schemas
-                }), "string" === typeof input.draft_without_date_type || _report(_exceptionable, {
-                    path: _path + ".draft_without_date_type",
+                }), "string" === typeof input.prismaSchemas || _report(_exceptionable, {
+                    path: _path + ".prismaSchemas",
                     expected: "string",
-                    value: input.draft_without_date_type
+                    value: input.prismaSchemas
                 }), "string" === typeof input.review || _report(_exceptionable, {
                     path: _path + ".review",
                     expected: "string",
                     value: input.review
-                }), "string" === typeof input.implementationCode || _report(_exceptionable, {
-                    path: _path + ".implementationCode",
+                }), "string" === typeof input.final || _report(_exceptionable, {
+                    path: _path + ".final",
                     expected: "string",
-                    value: input.implementationCode
+                    value: input.final
                 })].every(flag => flag); const __is = input => "object" === typeof input && null !== input && _io0(input); let errors; let _report; return input => {
                 if (false === __is(input)) {
                     errors = [];
@@ -240,61 +231,52 @@ const collection = {
             {
                 name: "coding",
                 parameters: {
-                    description: " Properties containing the multi-phase implementation plan and code\n\n------------------------------\n\nDescription of the current {@link IAutoBeRealizeWriteApplication.IProps} type:\n\n> Properties for the Realize Write Application following Chain of Thinking (CoT).\n> \n> Each field represents a distinct phase in the reasoning and implementation process,\n> building upon the previous step to create a complete, error-free implementation.\n> This structured approach ensures clarity, debuggability, and systematic thinking.",
+                    description: " Properties containing the multi-phase implementation plan and\ncode\n\n------------------------------\n\nDescription of the current {@link IAutoBeRealizeWriteApplication.IProps} type:\n\n> Properties for the Realize Write Application following Chain of Thinking\n> (CoT).\n> \n> Each field represents a distinct phase in the implementation process.\n> Detailed guidelines are in REALIZE_WRITE.md.",
                     type: "object",
                     properties: {
                         plan: {
-                            description: "Step 1 - Planning Phase (CoT: Initial Reasoning)\n\n\uD83E\uDDE0 Provider Function Implementation Plan\n\nThis field outlines the strategic plan for implementing the provider\nfunction according to the Realize Coder Agent specification. Before\nwriting the actual code, think through the logic and structure.\n\nThe plan follows a SCHEMA-FIRST APPROACH:\n\n\uD83D\uDCCB STEP 1 - PRISMA SCHEMA VERIFICATION:\n\nDO:\n\n- Examine the actual Prisma schema model definition\n- List EVERY field that exists in the model with exact types\n- Explicitly note fields that DO NOT exist\n- Verify database compatibility (PostgreSQL AND SQLite)\n\nDO NOT:\n\n- Assume common fields exist without verification\n- Use fields like deleted_at, created_by, updated_by, is_deleted, is_active\n  without checking\n- Use PostgreSQL-specific features like mode: \"insensitive\"\n\n\uD83D\uDCCB STEP 2 - FIELD INVENTORY:\n\n- List ONLY fields confirmed to exist in schema\n- Example: \"Verified fields in user model: id (String), email (String),\n  created_at (DateTime), updated_at (DateTime)\"\n- Example: \"Fields that DO NOT exist: deleted_at, is_active, created_by\"\n\n\uD83D\uDCCB STEP 3 - FIELD ACCESS STRATEGY:\n\n- Plan which verified fields will be used in select, update, create\n  operations\n- For complex operations with type errors, plan to use separate queries\n  instead of nested operations\n\n\uD83D\uDCCB STEP 4 - TYPE COMPATIBILITY:\n\n- Plan DateTime to ISO string conversions using toISOStringSafe()\n- Plan handling of nullable vs required fields\n\n\uD83D\uDCCB STEP 5 - IMPLEMENTATION APPROACH:\n\n- \uD83E\uDDE9 Required business entities (e.g., users, posts, logs) and their\n  relationships\n- \uD83D\uDEE0 Operations needed to fulfill the business scenario (e.g., fetch,\n  create, update) using ONLY verified fields\n- \uD83D\uDD04 Data dependencies between steps (e.g., use userId to fetch related\n  data)\n- \u2705 Validation points (based on business rules, not field presence)\n- \uD83D\uDEA7 Error and edge cases that must be handled explicitly (e.g., missing\n  records)\n- \uD83C\uDFD7 Structure: always a single `async function`, using only `parameters`\n  and `body`\n\n\u26A0\uFE0F Important Constraints:\n\n- Do NOT perform input validation \u2014 assume `parameters` and `body` are\n  already valid\n- Use `typia.random<T>()` with an explanatory comment if logic can't be\n  implemented\n- Never use `any` or make assumptions without sufficient context\n- Use only allowed imports \u2014 DTOs and Prisma types\n- Use `MyGlobal.prisma` for DB access and respect Prisma typing rules\n\n\u26A0\uFE0F TypeScript-specific considerations:\n\n- Do **not** use native `Date` objects directly; always convert all dates\n  using `toISOStringSafe()` and brand as `string &\n  tags.Format<'date-time'>`. This rule applies throughout all phases.\n- Prefer `satisfies` for DTO conformance instead of unsafe `as` casts\n- Avoid weak typing such as `any`, `as any`, or `satisfies any`\n- Use branded types (e.g., `tags.Format<'uuid'>`) and literal unions where\n  applicable\n\n\u2705 Example Structure:\n\n```ts\nexport async function doSomething(\n  user: { id: string & tags.Format<\"uuid\">; type: string },\n  parameters: IParams,\n  body: IBody\n): Promise<IReturn> {\n  const { id } = parameters;\n  const { name } = body;\n  const user = await MyGlobal.prisma.users.findFirst({ where: { id } });\n  if (!user) throw new Error(\"User not found\");\n  ...\n  return result;\n}\n```\n\n\uD83D\uDD0D Feasibility Analysis Requirement:\n\n- Before generating any code, the agent **must analyze** whether the\n  requested implementation is **feasible based on the given Prisma schema\n  and DTO types**.\n- If required fields or relationships are **missing or incompatible**, the\n  plan should explicitly state that the implementation is **not\n  possible** with the current schema/DTO, and no code should be generated\n  in later stages.\n- In such cases, only a detailed **comment in the `implementationCode`**\n  should be returned explaining why the logic cannot be implemented.\n\n\uD83D\uDD25 Error Handling Plan:\n\nIf an error is expected or encountered during implementation:\n\n- Clearly document the error message(s) and TypeScript error codes.\n- Analyze the root cause (e.g., type mismatch, missing field, nullability\n  issue).\n- Define concrete steps to resolve the issue, such as:\n\n  - Adjusting type declarations or using Prisma-generated input types.\n  - Using `?? undefined` to normalize nullable fields.\n  - Applying correct relation handling (e.g., `connect` instead of direct\n      foreign key assignment).\n  - Ensuring all date fields use `.toISOString()` and proper branding.\n- Include fallback or workaround plans if a direct fix is complex.\n- If no error is present, simply omit this section.\n\nThis plan ensures the function will:\n\n- Respect the global architecture and coding conventions\n- Be safe, predictable, and aligned with upstream logic",
+                            description: "Step 1 - Planning Phase (CoT: Initial Reasoning)\n\nStrategic plan following SCHEMA-FIRST APPROACH:\n\n1. Verify Prisma schema fields (list existing and non-existing)\n2. Plan field usage in operations\n3. Plan type conversions and nullable handling\n4. Define implementation approach with error handling\n\nSee REALIZE_WRITE.md for detailed requirements.",
                             type: "string"
                         },
-                        prisma_schemas: {
-                            description: "Step 2 - Schema Definition (CoT: Context Establishment)\n\nThe Prisma schema string that will be used to validate the implementation\nlogic in this file.\n\nYou must **explicitly specify only the relevant models and fields** from\nyour full schema that are used in this implementation. This ensures that\nyour logic is aligned with the expected database structure without\naccidentally introducing unrelated fields or models.\n\n\u26A0\uFE0F Important: The value of this field must be a valid Prisma schema\nstring containing only the models used in this code \u2014 not the entire\nschema.\n\nThis acts as a safeguard against:\n\n- Forgetting required fields used in this implementation\n- Including fields or models that are not actually used",
-                            type: "string"
-                        },
-                        draft_without_date_type: {
-                            description: "Step 3 - Initial Draft (CoT: First Implementation Attempt)\n\nDraft WITHOUT using native Date type.\n\nThis is the initial drafting phase where you outline the basic skeleton\nof the function.\n\nDO NOT: Use the native Date type.\n\n- The function signature must correctly include `user`, `parameters`, and\n  `body` arguments.\n- Design the main flow of business logic, such as DB fetches and early\n  returns based on conditions.\n- Mark any incomplete or missing parts clearly with placeholders (e.g.,\n  comments or temporary values).\n\nImport rules:\n\nDO NOT:\n\n- Add any new import statements manually\n- Write import statements directly (this causes compile errors)\n\nNote: All necessary imports are provided globally or by the system\nautomatically.\n\n\u2705 Requirements:\n\n- Avoid using the `any` type at all costs to ensure type safety.\n- NEVER declare variables with `: Date` type\n- ALWAYS use `string & tags.Format<'date-time'>` for date values\n- Use `toISOStringSafe(new Date())` for current timestamps\n- Maintain a single-function structure; avoid using classes.",
+                        prismaSchemas: {
+                            description: "Step 2 - Relevant Prisma schema models and fields",
                             type: "string"
                         },
                         review: {
-                            description: "Step 4 - Review and Refinement (CoT: Self-Reflection)\n\nA refined version of the draft with improved completeness.\n\n- Replace placeholder logic with real DTO-conformant operations.\n- Add error handling (`throw new Error(...)`) where necessary.\n- Begin resolving structural or type mismatches.\n\n\u2705 Requirements:\n\n- Use `satisfies` to ensure DTO conformity.\n- Avoid unsafe `as` casts unless only for branding or literal narrowing.\n- Use `toISOStringSafe()` for all date conversions (NOT `.toISOString()`).\n- Ensure all object keys strictly conform to the expected type definitions.\n- NEVER use `mode: \"insensitive\"` in string operations (breaks SQLite).",
+                            description: "Step 3 - Refined version with real operations",
                             type: "string"
                         },
-                        implementationCode: {
-                            description: "Step 5 - Complete Implementation (CoT: Final Synthesis)\n\nThe complete and fully correct TypeScript function implementation.\n\n- Passes strict type checking without errors.\n- Uses only safe branding or literal type assertions.\n- Converts all date values properly using `toISOStringSafe()`.\n- Follows DTO structures using `satisfies`.\n- Avoids any weak typing such as `any`, `as any`, or `satisfies any`.\n- Uses only allowed imports (e.g., from `../api/structures` and\n  `MyGlobal.prisma`).\n- NEVER creates intermediate variables for Prisma operations.\n- NEVER uses `mode: \"insensitive\"` (PostgreSQL-only, breaks SQLite).\n\n\u26A0\uFE0F Fallback Behavior:\n\n- If the `plan` phase explicitly determines that the requested logic is\n  **not feasible** due to mismatches or limitations in the provided\n  Prisma schema and DTO types:\n\n  - The implementation must still return a syntactically valid function.\n  - In such cases, return mock data using `typia.random<T>()` wrapped in the\n      correct structure, along with a comment explaining the limitation.\n\n  Example fallback:\n\n```ts\n  // \u26A0\uFE0F Cannot implement logic due to missing relation between A and B\n  export async function someFunction(...) {\n    return typia.random<IReturn>(); // mocked output\n  }\n```\n\n\u26A0\uFE0F Prohibited Practices:\n\n- Do NOT add or modify import statements manually. Imports are handled\n  automatically by the system.\n- Do NOT use `any`, `as any`, or `satisfies any` to bypass type checking.\n- Do NOT assign native `Date` objects directly; always convert them using\n  `toISOStringSafe()`.\n- Do NOT use unsafe type assertions except for safe branding or literal\n  narrowing.\n- Do NOT write code outside the single async function structure (e.g., no\n  classes or multiple functions).\n- Do NOT perform any input validation \u2014 assume all inputs are already\n  validated.\n- Do NOT use dynamic import expressions (`import()`); all imports must be\n  static.\n- Do NOT use Prisma-generated input types; always use types from\n  `../api/structures`.\n- Do NOT use `Object.prototype.hasOwnProperty.call()` for field checks.\n- Do NOT escape newlines or quotes in the implementation string (e.g., no\n  `\\\\n` or `\\\"`); use a properly formatted template literal with actual\n  line breaks instead.",
+                        final: {
+                            description: "Step 4 - Final implementation See REALIZE_WRITE.md for requirements",
                             type: "string"
                         }
                     },
                     required: [
                         "plan",
-                        "prisma_schemas",
-                        "draft_without_date_type",
+                        "prismaSchemas",
                         "review",
-                        "implementationCode"
+                        "final"
                     ],
                     additionalProperties: false,
                     $defs: {}
                 },
-                description: "Generates provider function implementation through multi-phase development.\n\nThis method implements a systematic approach to generate NestJS provider\nfunctions that handle business logic for API operations. It follows a\nschema-first approach with multiple refinement phases to ensure type-safe,\nerror-free code generation.\n\nThe generation process includes:\n1. Strategic planning based on Prisma schema analysis\n2. Initial draft without Date type usage\n3. Review and refinement for completeness\n4. Compiler feedback integration if errors detected\n5. Final implementation with all validations and type safety",
-                validate: (() => { const _io0 = input => "string" === typeof input.plan && "string" === typeof input.prisma_schemas && "string" === typeof input.draft_without_date_type && "string" === typeof input.review && "string" === typeof input.implementationCode; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.plan || _report(_exceptionable, {
+                description: "Generates provider function implementation through multi-phase development.\n\nThis method implements a systematic approach to generate NestJS provider\nfunctions that handle business logic for API operations. It follows a\nschema-first approach with multiple refinement phases to ensure type-safe,\nerror-free code generation.\n\nThe generation process includes:\n\n1. Strategic planning based on Prisma schema analysis\n2. Schema definition for relevant models\n3. Review and refinement for completeness\n4. Final implementation with all validations and type safety",
+                validate: (() => { const _io0 = input => "string" === typeof input.plan && "string" === typeof input.prismaSchemas && "string" === typeof input.review && "string" === typeof input.final; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.plan || _report(_exceptionable, {
                         path: _path + ".plan",
                         expected: "string",
                         value: input.plan
-                    }), "string" === typeof input.prisma_schemas || _report(_exceptionable, {
-                        path: _path + ".prisma_schemas",
-                        expected: "string",
-                        value: input.prisma_schemas
-                    }), "string" === typeof input.draft_without_date_type || _report(_exceptionable, {
-                        path: _path + ".draft_without_date_type",
+                    }), "string" === typeof input.prismaSchemas || _report(_exceptionable, {
+                        path: _path + ".prismaSchemas",
                         expected: "string",
-                        value: input.draft_without_date_type
+                        value: input.prismaSchemas
                     }), "string" === typeof input.review || _report(_exceptionable, {
                         path: _path + ".review",
                         expected: "string",
                         value: input.review
-                    }), "string" === typeof input.implementationCode || _report(_exceptionable, {
-                        path: _path + ".implementationCode",
+                    }), "string" === typeof input.final || _report(_exceptionable, {
+                        path: _path + ".final",
                         expected: "string",
-                        value: input.implementationCode
+                        value: input.final
                     })].every(flag => flag); const __is = input => "object" === typeof input && null !== input && _io0(input); let errors; let _report; return input => {
                     if (false === __is(input)) {
                         errors = [];

package/lib/orchestrate/realize/orchestrateRealizeWrite.js.map

@@ -1 +1 @@
-{"version":3,"file":"orchestrateRealizeWrite.js","sourceRoot":"","sources":["../../../src/orchestrate/realize/orchestrateRealizeWrite.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAmBA,0DAuEC;;AArFD,yCAA2C;AAG3C,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,+FAA4F;AAG5F,mEAAgE;AAChE,6EAA0E;AAE1E,SAAsB,uBAAuB,CAC3C,GAAyB,EACzB,KAMC;;;QAED,MAAM,OAAO,GAA2D;YACtE,KAAK,EAAE,IAAI;SACZ,CAAC;QAEF,MAAM,GAAG,GAAG,MAAM,IAAA,uCAAkB,EAAC,GAAG,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS,CAAC,CAAC;QACpE,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;YAC1C,MAAM,EAAE,cAAc;YACtB,SAAS,EAAE,IAAA,+DAA8B,EAAC;gBACxC,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;gBAClB,QAAQ,EAAE,KAAK,CAAC,QAAQ;gBACxB,aAAa,EAAE,KAAK,CAAC,aAAa;gBAClC,mBAAmB,EAAE,KAAK,CAAC,mBAAmB;gBAC9C,GAAG;aACJ,CAAC;YACF,UAAU,EAAE,gBAAgB,CAAC;gBAC3B,KAAK,EAAE,GAAG,CAAC,KAAK;gBAChB,KAAK,EAAE,CAAC,IAAI,EAAE,EAAE;oBACd,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC;gBACvB,CAAC;aACF,CAAC;YACF,mBAAmB,EAAE,IAAI;YACzB,cAAc,EAAE,KAAK,CAAC,cAAc;YACpC,OAAO,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;KAgBvB;SACF,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;YAAE,MAAM,IAAI,KAAK,CAAC,uBAAuB,CAAC,CAAC;QAErE,OAAO,CAAC,KAAK,CAAC,kBAAkB,GAAG,MAAM,IAAA,iDAAuB,EAAC,GAAG,EAAE;YACpE,SAAS,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS;YACnC,IAAI,EAAE,OAAO,CAAC,KAAK,CAAC,kBAAkB;YACtC,aAAa,EAAE,MAAA,KAAK,CAAC,aAAa,0CAAE,OAAO,CAAC,IAAI;SACjD,CAAC,CAAC;QAEH,MAAM,KAAK,GAA4B;YACrC,IAAI,EAAE,cAAc;YACpB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,QAAQ,EAAE,KAAK,CAAC,QAAQ,CAAC,QAAQ;YACjC,OAAO,EAAE,OAAO,CAAC,KAAK,CAAC,kBAAkB;YACzC,UAAU;YACV,SAAS,EAAE,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS;YACrC,KAAK,EAAE,KAAK,CAAC,QAAQ,CAAC,KAAK;YAC3B,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;YACpC,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACrC,CAAC;QACF,GAAG,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;QACpB,OAAO,KAAK,CAAC;IACf,CAAC;CAAA;AAED,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAE/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IAEtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,YAAY;QAClB,WAAW;QACX,OAAO,EAAE;YACP,MAAM,EAAE,CAAC,IAAI,EAAE,EAAE;gBACf,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;YACpB,CAAC;SACuC;KAC3C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAGT,CAAC;AACJ,MAAM,UAAU,GAAG;IACjB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;KAAoE;IAC3E,MAAM;IACN,KAAK,EAAE,MAAM;IACb,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,MAAM;CACd,CAAC"}
+{"version":3,"file":"orchestrateRealizeWrite.js","sourceRoot":"","sources":["../../../src/orchestrate/realize/orchestrateRealizeWrite.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAmBA,0DAuEC;;AArFD,yCAA2C;AAG3C,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,+FAA4F;AAG5F,mEAAgE;AAChE,6EAA0E;AAE1E,SAAsB,uBAAuB,CAC3C,GAAyB,EACzB,KAMC;;;QAED,MAAM,OAAO,GAA2D;YACtE,KAAK,EAAE,IAAI;SACZ,CAAC;QAEF,MAAM,GAAG,GAAG,MAAM,IAAA,uCAAkB,EAAC,GAAG,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS,CAAC,CAAC;QACpE,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;YAC1C,MAAM,EAAE,cAAc;YACtB,SAAS,EAAE,IAAA,+DAA8B,EAAC;gBACxC,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;gBAClB,QAAQ,EAAE,KAAK,CAAC,QAAQ;gBACxB,aAAa,EAAE,KAAK,CAAC,aAAa;gBAClC,mBAAmB,EAAE,KAAK,CAAC,mBAAmB;gBAC9C,GAAG;aACJ,CAAC;YACF,UAAU,EAAE,gBAAgB,CAAC;gBAC3B,KAAK,EAAE,GAAG,CAAC,KAAK;gBAChB,KAAK,EAAE,CAAC,IAAI,EAAE,EAAE;oBACd,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC;gBACvB,CAAC;aACF,CAAC;YACF,mBAAmB,EAAE,IAAI;YACzB,cAAc,EAAE,KAAK,CAAC,cAAc;YACpC,OAAO,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;KAgBvB;SACF,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;YAAE,MAAM,IAAI,KAAK,CAAC,uBAAuB,CAAC,CAAC;QAErE,OAAO,CAAC,KAAK,CAAC,KAAK,GAAG,MAAM,IAAA,iDAAuB,EAAC,GAAG,EAAE;YACvD,SAAS,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS;YACnC,IAAI,EAAE,OAAO,CAAC,KAAK,CAAC,KAAK;YACzB,aAAa,EAAE,MAAA,KAAK,CAAC,aAAa,0CAAE,OAAO,CAAC,IAAI;SACjD,CAAC,CAAC;QAEH,MAAM,KAAK,GAA4B;YACrC,IAAI,EAAE,cAAc;YACpB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,QAAQ,EAAE,KAAK,CAAC,QAAQ,CAAC,QAAQ;YACjC,OAAO,EAAE,OAAO,CAAC,KAAK,CAAC,KAAK;YAC5B,UAAU;YACV,SAAS,EAAE,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS;YACrC,KAAK,EAAE,KAAK,CAAC,QAAQ,CAAC,KAAK;YAC3B,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;YACpC,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACrC,CAAC;QACF,GAAG,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;QACpB,OAAO,KAAK,CAAC;IACf,CAAC;CAAA;AAED,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAE/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IAEtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,YAAY;QAClB,WAAW;QACX,OAAO,EAAE;YACP,MAAM,EAAE,CAAC,IAAI,EAAE,EAAE;gBACf,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;YACpB,CAAC;SACuC;KAC3C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAGT,CAAC;AACJ,MAAM,UAAU,GAAG;IACjB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;KAAoE;IAC3E,MAAM;IACN,KAAK,EAAE,MAAM;IACb,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,MAAM;CACd,CAAC"}

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

@@ -21,19 +21,19 @@ export declare namespace IAutoBeRealizeCorrectApplication {
         revise: IRevise;
     }
     interface IRevise {
-        /** Step 1: Compilation error analysis and resolution strategy. */
+        /**
+         * Step 1: TypeScript compilation error analysis and resolution strategy.
+         * Analyzes TypeScript compiler diagnostics (error codes, messages) to understand
+         * type mismatches, missing properties, nullable conflicts, and other compilation issues.
+         */
         errorAnalysis?: string;
         /** Step 2: Provider function implementation plan. */
         plan?: string;
         /** Step 3: Relevant Prisma schema definitions. */
         prismaSchemas?: string;
-        /** Step 4: Initial draft without using native Date type. */
-        draftWithoutDateType?: string;
-        /** Step 5: Refined version with improved completeness. */
+        /** Step 4: Refined version with improved completeness. */
         review?: string;
-        /** Step 6: Corrected implementation after compiler feedback. */
-        withCompilerFeedback?: string;
-        /** Step 7: Final complete TypeScript function implementation. */
-        implementationCode: string;
+        /** Step 5: Final complete TypeScript function implementation. */
+        final: string;
     }
 }

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

@@ -8,288 +8,44 @@ export interface IAutoBeRealizeWriteApplication {
      * error-free code generation.
      *
      * The generation process includes:
+     *
      * 1. Strategic planning based on Prisma schema analysis
-     * 2. Initial draft without Date type usage
+     * 2. Schema definition for relevant models
      * 3. Review and refinement for completeness
-     * 4. Compiler feedback integration if errors detected
-     * 5. Final implementation with all validations and type safety
+     * 4. Final implementation with all validations and type safety
      *
-     * @param next Properties containing the multi-phase implementation plan and code
+     * @param next Properties containing the multi-phase implementation plan and
+     *   code
      */
     coding: (next: IAutoBeRealizeWriteApplication.IProps) => void;
 }
 export declare namespace IAutoBeRealizeWriteApplication {
     /**
-     * Properties for the Realize Write Application following Chain of Thinking (CoT).
+     * Properties for the Realize Write Application following Chain of Thinking
+     * (CoT).
      *
-     * Each field represents a distinct phase in the reasoning and implementation process,
-     * building upon the previous step to create a complete, error-free implementation.
-     * This structured approach ensures clarity, debuggability, and systematic thinking.
+     * Each field represents a distinct phase in the implementation process.
+     * Detailed guidelines are in REALIZE_WRITE.md.
      */
     interface IProps {
         /**
          * Step 1 - Planning Phase (CoT: Initial Reasoning)
          *
-         * 🧠 Provider Function Implementation Plan
-         *
-         * This field outlines the strategic plan for implementing the provider
-         * function according to the Realize Coder Agent specification. Before
-         * writing the actual code, think through the logic and structure.
-         *
-         * The plan follows a SCHEMA-FIRST APPROACH:
-         *
-         * 📋 STEP 1 - PRISMA SCHEMA VERIFICATION:
-         *
-         * DO:
-         *
-         * - Examine the actual Prisma schema model definition
-         * - List EVERY field that exists in the model with exact types
-         * - Explicitly note fields that DO NOT exist
-         * - Verify database compatibility (PostgreSQL AND SQLite)
-         *
-         * DO NOT:
-         *
-         * - Assume common fields exist without verification
-         * - Use fields like deleted_at, created_by, updated_by, is_deleted, is_active
-         *   without checking
-         * - Use PostgreSQL-specific features like mode: "insensitive"
-         *
-         * 📋 STEP 2 - FIELD INVENTORY:
-         *
-         * - List ONLY fields confirmed to exist in schema
-         * - Example: "Verified fields in user model: id (String), email (String),
-         *   created_at (DateTime), updated_at (DateTime)"
-         * - Example: "Fields that DO NOT exist: deleted_at, is_active, created_by"
-         *
-         * 📋 STEP 3 - FIELD ACCESS STRATEGY:
-         *
-         * - Plan which verified fields will be used in select, update, create
-         *   operations
-         * - For complex operations with type errors, plan to use separate queries
-         *   instead of nested operations
-         *
-         * 📋 STEP 4 - TYPE COMPATIBILITY:
-         *
-         * - Plan DateTime to ISO string conversions using toISOStringSafe()
-         * - Plan handling of nullable vs required fields
-         *
-         * 📋 STEP 5 - IMPLEMENTATION APPROACH:
-         *
-         * - 🧩 Required business entities (e.g., users, posts, logs) and their
-         *   relationships
-         * - 🛠 Operations needed to fulfill the business scenario (e.g., fetch,
-         *   create, update) using ONLY verified fields
-         * - 🔄 Data dependencies between steps (e.g., use userId to fetch related
-         *   data)
-         * - ✅ Validation points (based on business rules, not field presence)
-         * - 🚧 Error and edge cases that must be handled explicitly (e.g., missing
-         *   records)
-         * - 🏗 Structure: always a single `async function`, using only `parameters`
-         *   and `body`
+         * Strategic plan following SCHEMA-FIRST APPROACH:
          *
-         * ⚠️ Important Constraints:
+         * 1. Verify Prisma schema fields (list existing and non-existing)
+         * 2. Plan field usage in operations
+         * 3. Plan type conversions and nullable handling
+         * 4. Define implementation approach with error handling
          *
-         * - Do NOT perform input validation — assume `parameters` and `body` are
-         *   already valid
-         * - Use `typia.random<T>()` with an explanatory comment if logic can't be
-         *   implemented
-         * - Never use `any` or make assumptions without sufficient context
-         * - Use only allowed imports — DTOs and Prisma types
-         * - Use `MyGlobal.prisma` for DB access and respect Prisma typing rules
-         *
-         * ⚠️ TypeScript-specific considerations:
-         *
-         * - Do **not** use native `Date` objects directly; always convert all dates
-         *   using `toISOStringSafe()` and brand as `string &
-         *   tags.Format<'date-time'>`. This rule applies throughout all phases.
-         * - Prefer `satisfies` for DTO conformance instead of unsafe `as` casts
-         * - Avoid weak typing such as `any`, `as any`, or `satisfies any`
-         * - Use branded types (e.g., `tags.Format<'uuid'>`) and literal unions where
-         *   applicable
-         *
-         * ✅ Example Structure:
-         *
-         * ```ts
-         * export async function doSomething(
-         *   user: { id: string & tags.Format<"uuid">; type: string },
-         *   parameters: IParams,
-         *   body: IBody
-         * ): Promise<IReturn> {
-         *   const { id } = parameters;
-         *   const { name } = body;
-         *   const user = await MyGlobal.prisma.users.findFirst({ where: { id } });
-         *   if (!user) throw new Error("User not found");
-         *   ...
-         *   return result;
-         * }
-         * ```
-         *
-         * 🔍 Feasibility Analysis Requirement:
-         *
-         * - Before generating any code, the agent **must analyze** whether the
-         *   requested implementation is **feasible based on the given Prisma schema
-         *   and DTO types**.
-         * - If required fields or relationships are **missing or incompatible**, the
-         *   plan should explicitly state that the implementation is **not
-         *   possible** with the current schema/DTO, and no code should be generated
-         *   in later stages.
-         * - In such cases, only a detailed **comment in the `implementationCode`**
-         *   should be returned explaining why the logic cannot be implemented.
-         *
-         * 🔥 Error Handling Plan:
-         *
-         * If an error is expected or encountered during implementation:
-         *
-         * - Clearly document the error message(s) and TypeScript error codes.
-         * - Analyze the root cause (e.g., type mismatch, missing field, nullability
-         *   issue).
-         * - Define concrete steps to resolve the issue, such as:
-         *
-         *   - Adjusting type declarations or using Prisma-generated input types.
-         *   - Using `?? undefined` to normalize nullable fields.
-         *   - Applying correct relation handling (e.g., `connect` instead of direct
-         *       foreign key assignment).
-         *   - Ensuring all date fields use `.toISOString()` and proper branding.
-         * - Include fallback or workaround plans if a direct fix is complex.
-         * - If no error is present, simply omit this section.
-         *
-         * This plan ensures the function will:
-         *
-         * - Respect the global architecture and coding conventions
-         * - Be safe, predictable, and aligned with upstream logic
+         * See REALIZE_WRITE.md for detailed requirements.
          */
         plan: string;
-        /**
-         * Step 2 - Schema Definition (CoT: Context Establishment)
-         *
-         * The Prisma schema string that will be used to validate the implementation
-         * logic in this file.
-         *
-         * You must **explicitly specify only the relevant models and fields** from
-         * your full schema that are used in this implementation. This ensures that
-         * your logic is aligned with the expected database structure without
-         * accidentally introducing unrelated fields or models.
-         *
-         * ⚠️ Important: The value of this field must be a valid Prisma schema
-         * string containing only the models used in this code — not the entire
-         * schema.
-         *
-         * This acts as a safeguard against:
-         *
-         * - Forgetting required fields used in this implementation
-         * - Including fields or models that are not actually used
-         */
-        prisma_schemas: string;
-        /**
-         * Step 3 - Initial Draft (CoT: First Implementation Attempt)
-         *
-         * Draft WITHOUT using native Date type.
-         *
-         * This is the initial drafting phase where you outline the basic skeleton
-         * of the function.
-         *
-         * DO NOT: Use the native Date type.
-         *
-         * - The function signature must correctly include `user`, `parameters`, and
-         *   `body` arguments.
-         * - Design the main flow of business logic, such as DB fetches and early
-         *   returns based on conditions.
-         * - Mark any incomplete or missing parts clearly with placeholders (e.g.,
-         *   comments or temporary values).
-         *
-         * Import rules:
-         *
-         * DO NOT:
-         *
-         * - Add any new import statements manually
-         * - Write import statements directly (this causes compile errors)
-         *
-         * Note: All necessary imports are provided globally or by the system
-         * automatically.
-         *
-         * ✅ Requirements:
-         *
-         * - Avoid using the `any` type at all costs to ensure type safety.
-         * - NEVER declare variables with `: Date` type
-         * - ALWAYS use `string & tags.Format<'date-time'>` for date values
-         * - Use `toISOStringSafe(new Date())` for current timestamps
-         * - Maintain a single-function structure; avoid using classes.
-         */
-        draft_without_date_type: string;
-        /**
-         * Step 4 - Review and Refinement (CoT: Self-Reflection)
-         *
-         * A refined version of the draft with improved completeness.
-         *
-         * - Replace placeholder logic with real DTO-conformant operations.
-         * - Add error handling (`throw new Error(...)`) where necessary.
-         * - Begin resolving structural or type mismatches.
-         *
-         * ✅ Requirements:
-         *
-         * - Use `satisfies` to ensure DTO conformity.
-         * - Avoid unsafe `as` casts unless only for branding or literal narrowing.
-         * - Use `toISOStringSafe()` for all date conversions (NOT `.toISOString()`).
-         * - Ensure all object keys strictly conform to the expected type definitions.
-         * - NEVER use `mode: "insensitive"` in string operations (breaks SQLite).
-         */
+        /** Step 2 - Relevant Prisma schema models and fields */
+        prismaSchemas: string;
+        /** Step 3 - Refined version with real operations */
         review: string;
-        /**
-         * Step 5 - Complete Implementation (CoT: Final Synthesis)
-         *
-         * The complete and fully correct TypeScript function implementation.
-         *
-         * - Passes strict type checking without errors.
-         * - Uses only safe branding or literal type assertions.
-         * - Converts all date values properly using `toISOStringSafe()`.
-         * - Follows DTO structures using `satisfies`.
-         * - Avoids any weak typing such as `any`, `as any`, or `satisfies any`.
-         * - Uses only allowed imports (e.g., from `../api/structures` and
-         *   `MyGlobal.prisma`).
-         * - NEVER creates intermediate variables for Prisma operations.
-         * - NEVER uses `mode: "insensitive"` (PostgreSQL-only, breaks SQLite).
-         *
-         * ⚠️ Fallback Behavior:
-         *
-         * - If the `plan` phase explicitly determines that the requested logic is
-         *   **not feasible** due to mismatches or limitations in the provided
-         *   Prisma schema and DTO types:
-         *
-         *   - The implementation must still return a syntactically valid function.
-         *   - In such cases, return mock data using `typia.random<T>()` wrapped in the
-         *       correct structure, along with a comment explaining the limitation.
-         *
-         *   Example fallback:
-         *
-         * ```ts
-         *   // ⚠️ Cannot implement logic due to missing relation between A and B
-         *   export async function someFunction(...) {
-         *     return typia.random<IReturn>(); // mocked output
-         *   }
-         * ```
-         *
-         * ⚠️ Prohibited Practices:
-         *
-         * - Do NOT add or modify import statements manually. Imports are handled
-         *   automatically by the system.
-         * - Do NOT use `any`, `as any`, or `satisfies any` to bypass type checking.
-         * - Do NOT assign native `Date` objects directly; always convert them using
-         *   `toISOStringSafe()`.
-         * - Do NOT use unsafe type assertions except for safe branding or literal
-         *   narrowing.
-         * - Do NOT write code outside the single async function structure (e.g., no
-         *   classes or multiple functions).
-         * - Do NOT perform any input validation — assume all inputs are already
-         *   validated.
-         * - Do NOT use dynamic import expressions (`import()`); all imports must be
-         *   static.
-         * - Do NOT use Prisma-generated input types; always use types from
-         *   `../api/structures`.
-         * - Do NOT use `Object.prototype.hasOwnProperty.call()` for field checks.
-         * - Do NOT escape newlines or quotes in the implementation string (e.g., no
-         *   `\\n` or `\"`); use a properly formatted template literal with actual
-         *   line breaks instead.
-         */
-        implementationCode: string;
+        /** Step 4 - Final implementation See REALIZE_WRITE.md for requirements */
+        final: string;
     }
 }

package/lib/orchestrate/realize/utils/filterDiagnostics.d.ts

@@ -0,0 +1,13 @@
+import { IAutoBeRealizeFunctionFailure } from "../structures/IAutoBeRealizeFunctionFailure";
+/**
+ * Filter diagnostic failures to only include those matching the given
+ * locations.
+ *
+ * @param failures - Array of function failures with diagnostic information
+ * @param locations - Array of file locations to filter by
+ * @returns Filtered array of failures matching the specified locations
+ * @warning This function assumes f.function and f.function.location are always defined.
+ *          If f.function is undefined, this will throw a runtime error.
+ *          Consider using optional chaining: f.function?.location
+ */
+export declare function filterDiagnostics(failures: IAutoBeRealizeFunctionFailure[], locations: string[]): IAutoBeRealizeFunctionFailure[];

package/lib/orchestrate/realize/utils/filterDiagnostics.js

@@ -0,0 +1,20 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.filterDiagnostics = filterDiagnostics;
+/**
+ * Filter diagnostic failures to only include those matching the given
+ * locations.
+ *
+ * @param failures - Array of function failures with diagnostic information
+ * @param locations - Array of file locations to filter by
+ * @returns Filtered array of failures matching the specified locations
+ * @warning This function assumes f.function and f.function.location are always defined.
+ *          If f.function is undefined, this will throw a runtime error.
+ *          Consider using optional chaining: f.function?.location
+ */
+function filterDiagnostics(failures, locations) {
+    return failures
+        .filter((f) => f.function.location.startsWith("src/providers"))
+        .filter((f) => locations.includes(f.function.location));
+}
+//# sourceMappingURL=filterDiagnostics.js.map

package/lib/orchestrate/realize/utils/filterDiagnostics.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"filterDiagnostics.js","sourceRoot":"","sources":["../../../../src/orchestrate/realize/utils/filterDiagnostics.ts"],"names":[],"mappings":";;AAaA,8CAOC;AAlBD;;;;;;;;;;GAUG;AACH,SAAgB,iBAAiB,CAC/B,QAAyC,EACzC,SAAmB;IAEnB,OAAO,QAAQ;SACZ,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,CAAC,QAAQ,CAAC,UAAU,CAAC,eAAe,CAAC,CAAC;SAC9D,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,SAAS,CAAC,QAAQ,CAAC,CAAC,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC,CAAC;AAC5D,CAAC"}