@tailor-platform/erp-kit 0.5.0 → 0.6.0

package/src/modules/manufacturing/docs/commands/CompleteWorkOrder.md

@@ -0,0 +1,66 @@
+# CompleteWorkOrder
+
+## Overview
+
+CompleteWorkOrder finishes an operation after final execution evidence is recorded. The command may trigger manual-issue reconciliation, backflush issue intent, and intermediate or finished receipt handoff to inventory.
+
+## Business Rules
+
+- Target work order must exist and be in `IN_PROGRESS`.
+- The work order must have started before completion.
+- Completion transaction must report positive completed quantity or valid zero-quantity completion under an explicit bypass policy.
+- Backflush consumption must not duplicate quantities already issued manually.
+- Required receipt-handoff payload fields must be present when output receipt is required.
+- `finishedGoodLotReference` is required whenever the receipted item is lot-tracked.
+- `serialReferences` are required whenever the receipted item is serial-tracked.
+- Completing the work order updates parent production-order progress.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive complete request] --> B{Work order exists and is IN_PROGRESS?}
+    B -->|No| C[Return WORK_ORDER_NOT_COMPLETABLE]
+    B -->|Yes| D[Validate completion quantities]
+    D --> E{Backflush required?}
+    E -->|Yes| F[Emit material issue intent]
+    E -->|No| G[Skip issue intent]
+    F --> H{Receipt handoff required?}
+    G --> H
+    H -->|Yes| I[Validate lot and serial receipt requirements]
+    I --> J[Emit ManufacturingReceiptHandoff]
+    H -->|No| K[Skip receipt handoff]
+    J --> L[Set status to COMPLETE]
+    K --> L
+    L --> M[Roll up parent progress]
+    M --> N[Return completed work order]
+```
+
+## External Dependencies
+
+- [ProductionOrder](../models/ProductionOrder.md) - Completion rolls up into parent order progress and completion gating.
+
+## Error Scenarios
+
+- **WORK_ORDER_NOT_FOUND**: Target work order does not exist.
+- **WORK_ORDER_NOT_COMPLETABLE**: Work order is not in `IN_PROGRESS`.
+- **WORK_ORDER_NOT_STARTED**: No actual start evidence exists.
+- **INVALID_COMPLETION_QUANTITY**: Completion quantity is invalid for the transaction.
+- **DUPLICATE_BACKFLUSH_RISK**: Requested backflush would duplicate manual issue quantity.
+- **RECEIPT_HANDOFF_REQUIRED**: Required receipt-handoff data is incomplete.
+- **LOT_REFERENCE_REQUIRED**: `finishedGoodLotReference` is required for a lot-tracked receipted item.
+- **SERIAL_REFERENCE_REQUIRED**: `serialReferences` are required for a serial-tracked receipted item.
+
+## Test Cases
+
+- completes an in-progress work order with final quantity reporting
+- returns error when the work order does not exist
+- returns error when the work order is not in progress
+- returns error when the work order was never started
+- returns error when completion quantity is invalid
+- returns error when backflush would duplicate manual issue
+- emits receipt handoff when output receipt is required
+- returns error when receipt is required but receipt data is missing
+- returns error when a lot-tracked receipt omits finishedGoodLotReference
+- returns error when a serial-tracked receipt omits serialReferences
+- rolls up completion to the parent order

package/src/modules/manufacturing/docs/commands/CreateBillOfMaterial.md

@@ -0,0 +1,54 @@
+# CreateBillOfMaterial
+
+## Overview
+
+CreateBillOfMaterial creates a draft BOM version for one manufactured parent item at company or site scope. The command establishes the initial `bomType`, effectivity window, default-selection intent, and component-line payload that later activation validates.
+
+## Business Rules
+
+- Parent item is required and must be an active manufactured item.
+- Company scope is required; site scope is optional.
+- `bomType` must be `MANUFACTURE`, `PHANTOM`, or `KIT`.
+- At least one component line is required.
+- Each component line requires positive quantity and a compatible unit of measure.
+- Inactive items cannot be added as components.
+- Initial version identity must be unique within the same parent item and scope.
+- New BOMs are created in `DRAFT`.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive create request] --> B[Validate parent item and scope]
+    B --> C[Validate bomType and lines]
+    C --> D{Version identity unique?}
+    D -->|No| E[Return BOM_VERSION_CONFLICT]
+    D -->|Yes| F[Create draft BOM and lines]
+    F --> G[Return draft BOM]
+```
+
+## External Dependencies
+
+- [Item](../../../item-management/docs/models/Item.md) - Parent and component references must resolve to valid items.
+
+## Error Scenarios
+
+- **PARENT_ITEM_NOT_FOUND**: Referenced parent item does not exist.
+- **PARENT_ITEM_NOT_MANUFACTURED**: Parent item is not eligible for manufacturing BOM ownership.
+- **INVALID_BOM_TYPE**: `bomType` is not one of the supported values.
+- **COMPONENT_LINE_REQUIRED**: No component lines were provided.
+- **INVALID_COMPONENT_QUANTITY**: A component quantity is zero or negative.
+- **COMPONENT_ITEM_INACTIVE**: A new component references an inactive item.
+- **BOM_VERSION_CONFLICT**: The proposed version or effectivity identity already exists in the same scope.
+
+## Test Cases
+
+- creates a draft BOM for an active manufactured item
+- returns error when the parent item does not exist
+- returns error when the parent item is not manufacturable
+- returns error when `bomType` is invalid
+- returns error when no component lines are provided
+- returns error when a component quantity is not positive
+- returns error when a component item is inactive
+- returns error when a component item exists but is inactive
+- returns error when the version identity already exists in scope

package/src/modules/manufacturing/docs/commands/CreateProductionOrder.md

@@ -0,0 +1,49 @@
+# CreateProductionOrder
+
+## Overview
+
+CreateProductionOrder creates a draft manufacturing request with produced item, quantity, site, and planned dates. It records planner intent without yet freezing BOM, routing, work orders, or cost assumptions.
+
+## Business Rules
+
+- Produced item, company, site, and planned quantity are required.
+- Planned quantity must be greater than zero.
+- Produced item must be an active manufacturable item.
+- Referenced company and site must exist and belong to the same scope.
+- Optional BOM or routing references must belong to the same company and site context.
+- New production orders are created in `DRAFT`.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive create request] --> B[Validate item, quantity, and scope]
+    B --> C[Validate optional BOM and routing references]
+    C --> D[Create draft production order]
+    D --> E[Return draft order]
+```
+
+## External Dependencies
+
+- [Item](../../../item-management/docs/models/Item.md) - Produced item must be valid and manufacturable.
+- [Company](../../../organization/docs/models/Company.md) - Order company scope must be valid.
+- [Site](../../../organization/docs/models/Site.md) - Execution site must be valid for the company scope.
+
+## Error Scenarios
+
+- **PRODUCTION_ITEM_NOT_FOUND**: Produced item does not exist.
+- **PRODUCTION_ITEM_NOT_MANUFACTURABLE**: Produced item cannot be built through manufacturing.
+- **INVALID_PLANNED_QUANTITY**: Planned quantity is zero or negative.
+- **INVALID_SITE_SCOPE**: Company and site scope are missing or inconsistent.
+- **CROSS_SCOPE_MASTER_REFERENCE**: BOM or routing reference belongs to another company or site.
+
+## Test Cases
+
+- creates a draft production order for a manufacturable item
+- returns error when the produced item does not exist
+- returns error when the produced item is not manufacturable
+- returns error when planned quantity is not positive
+- returns error when site scope is inconsistent with company
+- returns error when site does not exist
+- returns error when an optional BOM reference is outside scope
+- returns error when an optional routing reference is outside scope

package/src/modules/manufacturing/docs/commands/CreateRouting.md

@@ -0,0 +1,50 @@
+# CreateRouting
+
+## Overview
+
+CreateRouting creates a draft process definition for one manufactured item or scope. The command stores ordered operation payload, standard times, instructions, and work-center assignments that later activation validates.
+
+## Business Rules
+
+- Target manufactured item and company scope are required.
+- At least one operation is required.
+- Operation sequence numbers must be unique within the routing.
+- Standard setup and run times must be zero or greater.
+- Every operation must reference a valid work center in the same company scope.
+- New routings are created in `DRAFT`.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive create request] --> B[Validate parent item and scope]
+    B --> C[Validate operation payload]
+    C --> D{Sequence unique?}
+    D -->|No| E[Return DUPLICATE_OPERATION_SEQUENCE]
+    D -->|Yes| F[Create draft routing and operations]
+    F --> G[Return draft routing]
+```
+
+## External Dependencies
+
+- [Item](../../../item-management/docs/models/Item.md) - The routing targets one manufactured parent item.
+- [WorkCenter](../models/WorkCenter.md) - Each operation must reference a valid work center.
+
+## Error Scenarios
+
+- **ROUTING_ITEM_NOT_FOUND**: Referenced parent item does not exist.
+- **OPERATION_REQUIRED**: No routing operations were provided.
+- **DUPLICATE_OPERATION_SEQUENCE**: Two operations use the same sequence number.
+- **INVALID_STANDARD_TIME**: Setup or run time is negative.
+- **WORK_CENTER_NOT_FOUND**: A referenced work center does not exist.
+- **CROSS_COMPANY_WORK_CENTER**: A work center belongs to a different company scope.
+
+## Test Cases
+
+- creates a draft routing with ordered operations
+- returns error when no operations are provided
+- returns error when two operations share the same sequence
+- returns error when a standard time is negative
+- returns error when a referenced work center does not exist
+- returns error when a work center is outside the routing company
+- returns error when parent item does not exist

package/src/modules/manufacturing/docs/commands/CreateWorkCenter.md

@@ -0,0 +1,51 @@
+# CreateWorkCenter
+
+## Overview
+
+CreateWorkCenter creates a draft work center with scope, capacity assumptions, labor or machine rate context, and optional overhead-absorption policy. The work center remains non-executable until explicitly activated.
+
+## Business Rules
+
+- Company scope and unique work-center code are required.
+- Site scope is required when the company model uses site-level work centers.
+- Capacity must be positive.
+- Labor and machine rates must be zero or greater.
+- Overhead method, when provided, must be supported by the manufacturing-cost policy.
+- New work centers are created in `DRAFT`.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive create request] --> B[Validate scope and code]
+    B --> C[Validate capacity and rates]
+    C --> D{Code unique in scope?}
+    D -->|No| E[Return DUPLICATE_WORK_CENTER_CODE]
+    D -->|Yes| F[Create draft work center]
+    F --> G[Return draft work center]
+```
+
+## External Dependencies
+
+- [Company](../../../organization/docs/models/Company.md) - Work center scope must belong to a valid company.
+- [Site](../../../organization/docs/models/Site.md) - Site-scoped work centers must reference a valid organization site.
+
+## Error Scenarios
+
+- **INVALID_SCOPE**: Required company or site scope is missing.
+- **DUPLICATE_WORK_CENTER_CODE**: Another work center already uses the same code in scope.
+- **INVALID_CAPACITY**: Capacity is zero or negative.
+- **INVALID_RATE**: Labor or machine rate is negative.
+- **INVALID_OVERHEAD_METHOD**: Overhead method is not supported.
+- **OVERHEAD_CURRENCY_REQUIRED**: Fixed-amount overhead requires a currency.
+
+## Test Cases
+
+- creates a draft work center with positive capacity
+- returns error when scope is missing
+- returns error when the code already exists in scope
+- returns error when capacity is not positive
+- returns error when a rate is negative
+- returns error when overhead method is invalid
+- returns error when fixed-amount overhead omits currency
+- creates a draft work center without siteId when not required

package/src/modules/manufacturing/docs/commands/DeactivateBillOfMaterial.md

@@ -0,0 +1,45 @@
+# DeactivateBillOfMaterial
+
+## Overview
+
+DeactivateBillOfMaterial removes an active BOM version from future selection. The command preserves audit history and any released production-order snapshots that already depend on the version.
+
+## Business Rules
+
+- Target BOM must exist.
+- Only `ACTIVE` BOM versions can be deactivated.
+- Deactivation prevents future production-order release from selecting the version.
+- Existing production-order snapshots remain valid after deactivation.
+- Deactivation may be blocked when policy requires a replacement active version first.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive deactivate request] --> B{BOM exists?}
+    B -->|No| C[Return BOM_NOT_FOUND]
+    B -->|Yes| D{Status is ACTIVE?}
+    D -->|No| E[Return BOM_NOT_DEACTIVATABLE]
+    D -->|Yes| F{Replacement policy satisfied?}
+    F -->|No| G[Return REPLACEMENT_REQUIRED]
+    F -->|Yes| H[Set status to INACTIVE]
+    H --> I[Return inactive BOM]
+```
+
+## External Dependencies
+
+- None
+
+## Error Scenarios
+
+- **BOM_NOT_FOUND**: Target BOM does not exist.
+- **BOM_NOT_DEACTIVATABLE**: The BOM is not in `ACTIVE`.
+- **REPLACEMENT_REQUIRED**: Policy requires another selectable BOM before deactivation.
+
+## Test Cases
+
+- deactivates an active BOM
+- returns error when the BOM does not exist
+- returns error when the BOM is not active
+- returns error when replacement policy blocks deactivation
+- preserves released production-order snapshots after deactivation

package/src/modules/manufacturing/docs/commands/DeactivateRouting.md

@@ -0,0 +1,45 @@
+# DeactivateRouting
+
+## Overview
+
+DeactivateRouting removes an active routing from future production-order selection. Released production orders keep their frozen operation plan even after the routing is deactivated.
+
+## Business Rules
+
+- Target routing must exist.
+- Only `ACTIVE` routings can be deactivated.
+- Deactivation blocks future selection for release.
+- Existing production-order and work-order snapshots remain valid.
+- Deactivation may be blocked when future scheduling policy requires a replacement routing first.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive deactivate request] --> B{Routing exists?}
+    B -->|No| C[Return ROUTING_NOT_FOUND]
+    B -->|Yes| D{Status is ACTIVE?}
+    D -->|No| E[Return ROUTING_NOT_DEACTIVATABLE]
+    D -->|Yes| F{Replacement policy satisfied?}
+    F -->|No| G[Return REPLACEMENT_REQUIRED]
+    F -->|Yes| H[Set status to INACTIVE]
+    H --> I[Return inactive routing]
+```
+
+## External Dependencies
+
+- None
+
+## Error Scenarios
+
+- **ROUTING_NOT_FOUND**: Target routing does not exist.
+- **ROUTING_NOT_DEACTIVATABLE**: The routing is not in `ACTIVE`.
+- **REPLACEMENT_REQUIRED**: Policy requires another selectable routing before deactivation.
+
+## Test Cases
+
+- deactivates an active routing
+- returns error when the routing does not exist
+- returns error when the routing is not active
+- returns error when replacement policy blocks deactivation
+- preserves released operation snapshots after deactivation

package/src/modules/manufacturing/docs/commands/DeactivateWorkCenter.md

@@ -0,0 +1,45 @@
+# DeactivateWorkCenter
+
+## Overview
+
+DeactivateWorkCenter removes a work center from future routing and release selection. The command preserves historical work-order and cost records while blocking new execution use.
+
+## Business Rules
+
+- Target work center must exist.
+- Only `ACTIVE` work centers can be deactivated.
+- Deactivation may be blocked when future active routings or open released work still require the work center.
+- Historical work orders and cost baselines remain intact after deactivation.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive deactivate request] --> B{Work center exists?}
+    B -->|No| C[Return WORK_CENTER_NOT_FOUND]
+    B -->|Yes| D{Status is ACTIVE?}
+    D -->|No| E[Return WORK_CENTER_NOT_DEACTIVATABLE]
+    D -->|Yes| F{Open dependency check passes?}
+    F -->|No| G[Return WORK_CENTER_IN_USE]
+    F -->|Yes| H[Set status to INACTIVE]
+    H --> I[Return inactive work center]
+```
+
+## External Dependencies
+
+- [Routing](../models/Routing.md) - Future active routings may block deactivation.
+
+## Error Scenarios
+
+- **WORK_CENTER_NOT_FOUND**: Target work center does not exist.
+- **WORK_CENTER_NOT_DEACTIVATABLE**: The work center is not in `ACTIVE`.
+- **WORK_CENTER_IN_USE**: Future routings or open released work still require the work center.
+
+## Test Cases
+
+- deactivates an active work center with no blocking dependencies
+- returns error when the work center does not exist
+- returns error when the work center is not active
+- returns error when open routing or released-work dependencies block deactivation
+- returns error when open work orders block deactivation
+- preserves historical work-order and cost data after deactivation

package/src/modules/manufacturing/docs/commands/PauseWorkOrder.md

@@ -0,0 +1,44 @@
+# PauseWorkOrder
+
+## Overview
+
+PauseWorkOrder temporarily halts an in-progress operation and records the reason for the interruption. The command preserves accumulated execution history so the work order can later resume.
+
+## Business Rules
+
+- Target work order must exist.
+- Work order must be in `IN_PROGRESS`.
+- Pause reason is required.
+- Pausing preserves previously reported quantity, scrap, and time.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive pause request] --> B{Work order exists?}
+    B -->|No| C[Return WORK_ORDER_NOT_FOUND]
+    B -->|Yes| D{Status is IN_PROGRESS?}
+    D -->|No| E[Return WORK_ORDER_NOT_PAUSABLE]
+    D -->|Yes| F{Pause reason provided?}
+    F -->|No| G[Return PAUSE_REASON_REQUIRED]
+    F -->|Yes| H[Record pause event and set PAUSED]
+    H --> I[Return paused work order]
+```
+
+## External Dependencies
+
+- None
+
+## Error Scenarios
+
+- **WORK_ORDER_NOT_FOUND**: Target work order does not exist.
+- **WORK_ORDER_NOT_PAUSABLE**: Work order is not in `IN_PROGRESS`.
+- **PAUSE_REASON_REQUIRED**: No pause reason was provided.
+
+## Test Cases
+
+- pauses an in-progress work order
+- returns error when the work order does not exist
+- returns error when the work order is not in progress
+- returns error when no pause reason is provided
+- preserves prior execution quantities and time after pause

package/src/modules/manufacturing/docs/commands/RecordInventoryIssueOutcome.md

@@ -0,0 +1,59 @@
+# RecordInventoryIssueOutcome
+
+## Overview
+
+RecordInventoryIssueOutcome applies one inventory-owned valuation outcome to the manufacturing cost summary for a production order. It is the only valid path for actual material cost to enter manufacturing.
+
+## Business Rules
+
+- Referenced production order and cost summary must exist.
+- Cost summary must be in `COLLECTING`.
+- Inventory outcome payload must include `productionOrderReference`, `inventoryIssueReference`, `itemReference`, `issuedQuantity`, `unitOfMeasure`, `actualUnitCost`, `actualExtendedCost`, `currency`, `valuationMethod`, `postingDate`, and `siteReference`.
+- Inventory issue outcome must already be final-valued by inventory.
+- The event must not be double-applied to the same summary.
+- Actual material cost is recorded using the payload values rather than manufacturing-side recalculation.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive inventory issue outcome] --> B[Resolve production order and cost summary]
+    B --> C[Validate required payload fields]
+    C --> D{Summary collecting?}
+    D -->|No| E[Return COST_SUMMARY_NOT_COLLECTING]
+    D -->|Yes| F{Inventory valuation final?}
+    F -->|No| G[Return ISSUE_OUTCOME_NOT_FINAL]
+    F -->|Yes| H{Already applied?}
+    H -->|Yes| I[Return DUPLICATE_ISSUE_OUTCOME]
+    H -->|No| J[Apply actual material cost to summary]
+    J --> K[Return updated summary]
+```
+
+## External Dependencies
+
+- [ManufacturingCostSummary](../models/ManufacturingCostSummary.md) - Actual material issue outcomes accumulate on the linked summary.
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Referenced production order does not exist.
+- **COST_SUMMARY_NOT_FOUND**: Linked cost summary does not exist.
+- **COST_SUMMARY_NOT_COLLECTING**: Summary is not in `COLLECTING`.
+- **MISSING_INVENTORY_ISSUE_REFERENCE**: `inventoryIssueReference` was not provided in the outcome payload.
+- **MISSING_ACTUAL_UNIT_COST**: `actualUnitCost` was not provided in the outcome payload.
+- **MISSING_ACTUAL_EXTENDED_COST**: `actualExtendedCost` was not provided in the outcome payload.
+- **MISSING_POSTING_DATE**: `postingDate` was not provided in the outcome payload.
+- **ISSUE_OUTCOME_NOT_FINAL**: Inventory valuation is not yet final.
+- **DUPLICATE_ISSUE_OUTCOME**: The same inventory issue outcome was already applied.
+
+## Test Cases
+
+- applies a final-valued inventory issue outcome to a collecting summary
+- returns error when the production order does not exist
+- returns error when the linked cost summary does not exist
+- returns error when the summary is not collecting
+- returns error when `inventoryIssueReference` is missing from the outcome payload
+- returns error when `actualUnitCost` is missing from the outcome payload
+- returns error when `actualExtendedCost` is missing from the outcome payload
+- returns error when `postingDate` is missing from the outcome payload
+- returns error when the inventory issue outcome is not yet final
+- returns error when the same issue outcome is applied twice

package/src/modules/manufacturing/docs/commands/RecordManufacturingCostSettlementAcknowledgment.md

@@ -0,0 +1,49 @@
+# RecordManufacturingCostSettlementAcknowledgment
+
+## Overview
+
+RecordManufacturingCostSettlementAcknowledgment persists the downstream accounting acknowledgment that a reviewed manufacturing cost handoff has been consumed by settlement processing. It is the only path that moves a reviewed summary to `SETTLED`.
+
+## Business Rules
+
+- Target cost summary must exist and be in `VARIANCE_REVIEWED`.
+- Acknowledgment payload must match the reviewed summary's production order, summary reference, and settlement currency.
+- Downstream accounting owns the acknowledgment payload; manufacturing may record it but must not fabricate it.
+- An acknowledgment that is rejected, reversed, or superseded by downstream accounting must not settle the summary and requires a valid replacement acknowledgment before settlement can proceed.
+- Successful recording sets the summary status to `SETTLED`.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive settlement acknowledgment] --> B{Summary exists and is reviewed?}
+    B -->|No| C[Return COST_SUMMARY_NOT_SETTLABLE]
+    B -->|Yes| D[Validate payload identity and currency]
+    D --> E{Payload valid?}
+    E -->|No| F[Return ACKNOWLEDGMENT_MISMATCH]
+    E -->|Yes| G{Downstream accepted and not superseded?}
+    G -->|No| H[Return ACKNOWLEDGMENT_REJECTED_OR_SUPERSEDED]
+    G -->|Yes| I[Persist acknowledgment and set SETTLED]
+    I --> J[Return settled summary]
+```
+
+## External Dependencies
+
+- None
+
+## Error Scenarios
+
+- **COST_SUMMARY_NOT_FOUND**: Target cost summary does not exist.
+- **COST_SUMMARY_NOT_SETTLABLE**: Summary is not in `VARIANCE_REVIEWED`.
+- **ACKNOWLEDGMENT_MISMATCH**: Order, summary reference, or currency does not match the reviewed handoff.
+- **ACKNOWLEDGMENT_REJECTED_OR_SUPERSEDED**: Downstream accounting rejected, reversed, or superseded the reviewed handoff, so the summary must remain in `VARIANCE_REVIEWED`.
+- **ACKNOWLEDGMENT_SOURCE_INVALID**: Payload was not produced by the downstream settlement process.
+
+## Test Cases
+
+- records a valid downstream settlement acknowledgment and settles the summary
+- returns error when the summary does not exist
+- returns error when the summary is not variance reviewed
+- returns error when the payload does not match the reviewed handoff
+- returns error when downstream accounting rejects, reverses, or supersedes the reviewed handoff
+- returns error when the acknowledgment source is invalid

package/src/modules/manufacturing/docs/commands/ReleaseProductionOrder.md

@@ -0,0 +1,57 @@
+# ReleaseProductionOrder
+
+## Overview
+
+ReleaseProductionOrder turns a draft plan into executable work by resolving active BOM and routing content, freezing snapshots, creating work orders and material requirements, and opening manufacturing cost collection.
+
+## Business Rules
+
+- Target order must exist and be in `DRAFT`.
+- An active BOM and active routing must be explicitly selected or resolvable by default.
+- BOM and routing must belong to the same company as the order, and any site-scoped master must match the order site exactly.
+- Planned material unit cost for every required component must be resolved from inventory-owned valuation data at release time.
+- Release snapshots BOM lines, routing operations, work-center rates, overhead policy, and planned material valuation.
+- Release creates work orders, material requirements, and one manufacturing cost summary in `COLLECTING`.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive release request] --> B{Order exists and is DRAFT?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_RELEASABLE]
+    B -->|Yes| D[Resolve active BOM and routing]
+    D --> E[Validate company and site scope of resolved masters]
+    E --> F[Query inventory valuation for planned material cost]
+    F --> G[Snapshot BOM, routing, and cost baseline]
+    G --> H[Create work orders and material requirements]
+    H --> I[Set order status to RELEASED]
+    I --> J[Return released order]
+```
+
+## External Dependencies
+
+- [BillOfMaterial](../models/BillOfMaterial.md) - One active BOM version must be selected or resolved.
+- [Routing](../models/Routing.md) - One active routing revision must be selected or resolved.
+- [ManufacturingCostSummary](../models/ManufacturingCostSummary.md) - Release opens cost collection and freezes the baseline.
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_RELEASABLE**: The order is not in `DRAFT`.
+- **BOM_NOT_RESOLVED**: No valid active BOM could be selected for the order scope.
+- **ROUTING_NOT_RESOLVED**: No valid active routing could be selected for the order scope.
+- **CROSS_COMPANY_MASTER_REFERENCE**: Selected BOM or routing belongs to another company.
+- **CROSS_SITE_MASTER_REFERENCE**: Selected BOM or routing belongs to another site than the production order, even if the company matches.
+- **PLANNED_MATERIAL_COST_UNAVAILABLE**: Inventory could not resolve planned component cost for release.
+
+## Test Cases
+
+- releases a draft order with valid BOM and routing snapshots
+- returns error when the order does not exist
+- returns error when the order is not in `DRAFT`
+- returns error when no active BOM can be resolved
+- returns error when no active routing can be resolved
+- returns error when BOM or routing belongs to another company
+- returns error when BOM or routing belongs to another site in the same company
+- returns error when inventory valuation for a required component is unavailable
+- creates work orders and a collecting cost summary at release