@tailor-platform/erp-kit 0.5.1 → 0.6.0

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

@@ -0,0 +1,50 @@
+# ActivateBillOfMaterial
+
+## Overview
+
+ActivateBillOfMaterial validates a draft BOM version and makes it selectable for production-order release. Activation is where circular-reference checks, effectivity conflicts, and component readiness are enforced.
+
+## Business Rules
+
+- Target BOM must exist and be in `DRAFT`.
+- The BOM must contain at least one valid component line.
+- All referenced items must be active in the required scope.
+- Manufactured-child references must not create a direct or indirect circular structure.
+- Overlapping active effectivity windows for the same parent item and scope are rejected unless selection remains unambiguous.
+- Activation preserves any already released production-order snapshots from other versions.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive activate request] --> B{BOM exists and is DRAFT?}
+    B -->|No| C[Return BOM_NOT_ACTIVATABLE]
+    B -->|Yes| D[Validate component readiness]
+    D --> E[Check circular references]
+    E --> F[Check effectivity conflicts]
+    F --> G[Set status to ACTIVE]
+    G --> H[Return active BOM]
+```
+
+## External Dependencies
+
+- [detectBillOfMaterialCircularReference](../queries/DetectBillOfMaterialCircularReference.md) - Prevent cyclical manufactured-item structures.
+
+## Error Scenarios
+
+- **BOM_NOT_FOUND**: Target BOM does not exist.
+- **BOM_NOT_ACTIVATABLE**: The BOM is not in `DRAFT`.
+- **COMPONENT_LINE_REQUIRED**: The BOM has no component lines.
+- **COMPONENT_ITEM_INACTIVE**: A referenced component is inactive.
+- **CIRCULAR_BOM_REFERENCE**: A direct or indirect manufactured-item loop was detected.
+- **EFFECTIVITY_CONFLICT**: Activation would create conflicting active effectivity windows.
+
+## Test Cases
+
+- activates a valid draft BOM
+- returns error when the BOM does not exist
+- returns error when the BOM is not in `DRAFT`
+- returns error when the BOM has no component lines
+- returns error when a component item is inactive
+- returns error when a circular manufactured-item structure is detected
+- returns error when activation would create an effectivity conflict

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

@@ -0,0 +1,48 @@
+# ActivateRouting
+
+## Overview
+
+ActivateRouting validates a draft routing and makes it eligible for production-order release. Activation enforces operation completeness, sequence integrity, and active work-center readiness.
+
+## Business Rules
+
+- Target routing must exist and be in `DRAFT`.
+- The routing must contain at least one operation.
+- Operation sequence numbers must be unique and ordered.
+- Every referenced work center must be active and within the same company.
+- Activation preserves existing operation snapshots already frozen on released orders.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive activate request] --> B{Routing exists and is DRAFT?}
+    B -->|No| C[Return ROUTING_NOT_ACTIVATABLE]
+    B -->|Yes| D[Validate operations]
+    D --> E[Validate work-center readiness]
+    E --> F[Set status to ACTIVE]
+    F --> G[Return active routing]
+```
+
+## External Dependencies
+
+- [WorkCenter](../models/WorkCenter.md) - Referenced work centers must already be active.
+
+## Error Scenarios
+
+- **ROUTING_NOT_FOUND**: Target routing does not exist.
+- **ROUTING_NOT_ACTIVATABLE**: The routing is not in `DRAFT`.
+- **OPERATION_REQUIRED**: The routing has no operations.
+- **DUPLICATE_OPERATION_SEQUENCE**: Two operations use the same sequence number.
+- **WORK_CENTER_NOT_ACTIVE**: A referenced work center is inactive.
+- **CROSS_COMPANY_WORK_CENTER**: A work center belongs to a different company scope.
+
+## Test Cases
+
+- activates a valid draft routing
+- returns error when the routing does not exist
+- returns error when the routing is not in DRAFT
+- returns error when the routing has no operations
+- returns error when operation sequence numbers are duplicated
+- returns error when a referenced work center is inactive
+- returns error when a referenced work center is outside the routing company

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

@@ -0,0 +1,49 @@
+# ActivateWorkCenter
+
+## Overview
+
+ActivateWorkCenter validates that a draft or inactive work center has the execution data required by planning and costing, then marks it available for routing and work-order use.
+
+## Business Rules
+
+- Target work center must exist.
+- Only `DRAFT` or `INACTIVE` work centers can be activated.
+- Required calendar or availability context must be present.
+- Capacity must be positive.
+- Any configured rates and overhead settings must be internally valid.
+- Activation makes the work center eligible for active routing operations.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive activate request] --> B{Work center exists?}
+    B -->|No| C[Return WORK_CENTER_NOT_FOUND]
+    B -->|Yes| D{Status activatable?}
+    D -->|No| E[Return WORK_CENTER_NOT_ACTIVATABLE]
+    D -->|Yes| F[Validate calendar, capacity, and rates]
+    F --> G[Set status to ACTIVE]
+    G --> H[Return active work center]
+```
+
+## External Dependencies
+
+- [Site](../../../organization/docs/models/Site.md) - Site-scoped activation requires a valid site context.
+
+## Error Scenarios
+
+- **WORK_CENTER_NOT_FOUND**: Target work center does not exist.
+- **WORK_CENTER_NOT_ACTIVATABLE**: The current status does not allow activation.
+- **MISSING_CALENDAR_CONTEXT**: Required calendar or availability data is missing.
+- **INVALID_CAPACITY**: Capacity is zero or negative.
+- **INVALID_RATE**: Labor or machine rate is negative.
+- **OVERHEAD_CURRENCY_REQUIRED**: Fixed-amount overhead requires a currency.
+
+## Test Cases
+
+- activates a valid draft work center
+- reactivates a valid inactive work center
+- returns error when the work center does not exist
+- returns error when the status does not allow activation
+- returns error when required calendar context is missing
+- returns error when capacity is not positive

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

@@ -0,0 +1,48 @@
+# CancelProductionOrder
+
+## Overview
+
+CancelProductionOrder abandons a draft or not-yet-started released order. It preserves audit history while blocking further execution updates and cascading cancellation to pending work orders.
+
+## Business Rules
+
+- Target order must exist.
+- Only `DRAFT` or `RELEASED` orders may be cancelled.
+- Released orders cannot be cancelled once meaningful execution or inventory evidence exists.
+- Cancelling a released order cascades cancellation to pending work orders.
+- Cancelled orders reject all further execution, completion, and closeout commands.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive cancel request] --> B{Order exists?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_FOUND]
+    B -->|Yes| D{Status cancellable?}
+    D -->|No| E[Return PRODUCTION_ORDER_NOT_CANCELLABLE]
+    D -->|Yes| F{Execution or inventory evidence exists?}
+    F -->|Yes| G[Return EXECUTION_ALREADY_STARTED]
+    F -->|No| H[Cancel order and pending work orders]
+    H --> I[Return cancelled order]
+```
+
+## External Dependencies
+
+- [WorkOrder](../models/WorkOrder.md) - Pending child work orders are cancelled with the parent order.
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_CANCELLABLE**: The current status does not allow cancellation.
+- **EXECUTION_ALREADY_STARTED**: Work-order execution evidence already exists.
+- **INVENTORY_HANDOFF_EXISTS**: Inventory issue or receipt evidence already exists.
+
+## Test Cases
+
+- cancels a draft production order
+- cancels a released order before execution starts
+- returns error when the order does not exist
+- returns error when the status does not allow cancellation
+- returns error when execution evidence already exists
+- returns error when inventory handoff evidence already exists
+- cascades cancellation to pending work orders

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

@@ -0,0 +1,46 @@
+# CloseProductionOrder
+
+## Overview
+
+CloseProductionOrder performs the final administrative close after technical completion and downstream cost settlement are done. The command is the last lifecycle step for the production order.
+
+## Business Rules
+
+- Target order must exist and be in `TECHNICALLY_COMPLETE`.
+- All open work orders and execution exceptions must already be resolved.
+- The linked manufacturing cost summary must be in `SETTLED`.
+- Closed orders reject further execution, reopen, or rescheduling commands.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive close request] --> B{Order exists and is TECHNICALLY_COMPLETE?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_CLOSABLE]
+    B -->|Yes| D{Open work or exceptions remain?}
+    D -->|Yes| E[Return OPEN_WORK_REMAINS]
+    D -->|No| F{Cost summary settled?}
+    F -->|No| G[Return COST_SUMMARY_NOT_SETTLED]
+    F -->|Yes| H[Set order status to CLOSED]
+    H --> I[Return closed order]
+```
+
+## External Dependencies
+
+- [ManufacturingCostSummary](../models/ManufacturingCostSummary.md) - Administrative close depends on settled variance review.
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_CLOSABLE**: The order is not in `TECHNICALLY_COMPLETE`.
+- **OPEN_WORK_REMAINS**: Open work orders or execution exceptions still exist.
+- **COST_SUMMARY_NOT_SETTLED**: The linked cost summary is not in `SETTLED`.
+
+## Test Cases
+
+- closes a technically complete order with a settled cost summary
+- returns error when the order does not exist
+- returns error when the order is not technically complete
+- returns error when open work or execution exceptions remain
+- returns error when the linked cost summary is not settled
+- blocks further execution commands after close

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

@@ -0,0 +1,48 @@
+# CompleteProductionOrder
+
+## Overview
+
+CompleteProductionOrder marks physical production complete once required work orders are finished and final receipt obligations are satisfied. The command freezes production execution while still allowing later technical completion and review.
+
+## Business Rules
+
+- Target order must exist and be in `IN_PROGRESS`.
+- All mandatory work orders must be completed.
+- Final output reporting must exist for the required good quantity.
+- Finished-goods or intermediate receipt handoff required by policy must already be submitted.
+- Completing the order blocks additional operational production work except through controlled reopen.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive complete request] --> B{Order exists and is IN_PROGRESS?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_COMPLETABLE]
+    B -->|Yes| D{All required work orders complete?}
+    D -->|No| E[Return OPEN_WORK_ORDER_REMAINS]
+    D -->|Yes| F{Final reporting and receipt handoff complete?}
+    F -->|No| G[Return FINAL_RECEIPT_REQUIRED]
+    F -->|Yes| H[Set status to COMPLETED]
+    H --> I[Return completed order]
+```
+
+## External Dependencies
+
+- [WorkOrder](../models/WorkOrder.md) - Completion requires the operation-level plan to be done.
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_COMPLETABLE**: The order is not in `IN_PROGRESS`.
+- **OPEN_WORK_ORDER_REMAINS**: One or more required work orders are still open.
+- **FINAL_OUTPUT_REQUIRED**: Final output reporting is incomplete.
+- **FINAL_RECEIPT_REQUIRED**: Required receipt handoff evidence is missing.
+
+## Test Cases
+
+- completes an in-progress order after all required work orders finish
+- returns error when the order does not exist
+- returns error when the order is not in `IN_PROGRESS`
+- returns error when required work orders remain open
+- returns error when final output reporting is incomplete
+- returns error when required receipt handoff evidence is missing

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