@tailor-platform/erp-kit 0.5.0 → 0.6.0

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

@@ -0,0 +1,54 @@
+# ReopenProductionOrder
+
+## Overview
+
+ReopenProductionOrder re-enables execution after a technically complete order needs more shop-floor work. It reverses the execution freeze and returns the linked cost summary to active collection.
+
+## Business Rules
+
+- Target order must exist and be in `TECHNICALLY_COMPLETE`.
+- A documented reopen reason is required.
+- Reopening is not allowed after the order has been administratively closed.
+- Reopening returns the linked manufacturing cost summary from either `PENDING_VARIANCE_REVIEW` or `VARIANCE_REVIEWED` back to `COLLECTING`.
+- A linked summary already in `SETTLED` is not reopenable through this workflow.
+- Once reopened, execution resumes under the existing released snapshots rather than creating a new release.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive reopen request] --> B{Order exists and is TECHNICALLY_COMPLETE?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_REOPENABLE]
+    B -->|Yes| D{Reopen reason provided?}
+    D -->|No| E[Return REOPEN_REASON_REQUIRED]
+    D -->|Yes| F[Resolve linked cost summary state]
+    F --> G{Summary pending review or variance reviewed?}
+    G -->|No| H[Return COST_SUMMARY_NOT_REOPENABLE]
+    G -->|Yes| I[Return cost summary to COLLECTING]
+    I --> J[Set order status to IN_PROGRESS]
+    J --> K[Return reopened order]
+```
+
+## External Dependencies
+
+- [ManufacturingCostSummary](../models/ManufacturingCostSummary.md) - Review state is reversed so additional execution can be costed.
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_REOPENABLE**: The order is not in `TECHNICALLY_COMPLETE`.
+- **REOPEN_REASON_REQUIRED**: No reopen reason was provided.
+- **COST_SUMMARY_NOT_REOPENABLE**: The linked cost summary is not in `PENDING_VARIANCE_REVIEW` or `VARIANCE_REVIEWED`.
+- **ORDER_ALREADY_CLOSED**: Administratively closed orders cannot be reopened through this workflow.
+
+## Test Cases
+
+- reopens a technically complete order for additional execution
+- returns error when the order does not exist
+- returns error when the order is not technically complete
+- returns error when no reopen reason is provided
+- reopens an order when the linked cost summary is `PENDING_VARIANCE_REVIEW`
+- reopens an order when the linked cost summary is `VARIANCE_REVIEWED`
+- returns error when the linked cost summary is already `SETTLED` or otherwise not reopenable
+- returns error when the order is already closed
+- returns the linked cost summary to collecting on reopen

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

@@ -0,0 +1,53 @@
+# ReportWorkOrderProgress
+
+## Overview
+
+ReportWorkOrderProgress records partial execution evidence such as completed quantity, scrap quantity, actual time, and exception notes. It also emits any required manufacturing scrap handoff when the report contains scrapped quantity.
+
+## Business Rules
+
+- Target work order must exist and be in `IN_PROGRESS`.
+- Reported completed quantity and scrap quantity must be zero or greater.
+- At least one of completed quantity, scrap quantity, or actual time must be positive.
+- Scrap reporting emits `ManufacturingScrapHandoff` exactly once per submitted scrap transaction.
+- Manufacturing-originated stock loss with a resolvable production or work-order reference must not bypass the manufacturing scrap handoff path.
+- Progress reporting updates parent production-order rollup.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive progress report] --> B{Work order exists and is IN_PROGRESS?}
+    B -->|No| C[Return WORK_ORDER_NOT_REPORTABLE]
+    B -->|Yes| D[Validate quantities and time]
+    D --> E{Positive scrap reported?}
+    E -->|Yes| F[Emit ManufacturingScrapHandoff]
+    E -->|No| G[Skip scrap handoff]
+    F --> H[Persist execution event]
+    G --> H
+    H --> I[Roll up parent order progress]
+    I --> J[Return updated work order]
+```
+
+## External Dependencies
+
+- [ProductionOrder](../models/ProductionOrder.md) - Progress rolls up into parent order execution state.
+
+## Error Scenarios
+
+- **WORK_ORDER_NOT_FOUND**: Target work order does not exist.
+- **WORK_ORDER_NOT_REPORTABLE**: Work order is not in `IN_PROGRESS`.
+- **INVALID_REPORTED_QUANTITY**: Reported completed or scrap quantity is negative.
+- **EMPTY_PROGRESS_TRANSACTION**: No positive quantity or time was reported.
+- **SCRAP_HANDOFF_REQUIRED**: Positive scrap was reported but required scrap-handoff data is incomplete.
+
+## Test Cases
+
+- records partial completed quantity and time on 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 completed or scrap quantity is negative
+- returns error when no positive quantity or time is provided
+- emits manufacturing scrap handoff when positive scrap is reported
+- returns error when positive scrap is reported without scrap handoff data
+- rolls up execution progress to the parent order

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

@@ -0,0 +1,45 @@
+# RescheduleProductionOrder
+
+## Overview
+
+RescheduleProductionOrder changes the planned execution dates on a released order before execution starts. The command preserves the released snapshots and keeps the change auditable.
+
+## Business Rules
+
+- Target order must exist and be in `RELEASED`.
+- No work order may have started or received execution evidence.
+- Revised planned dates must be chronologically valid.
+- Rescheduling changes scheduling fields only; BOM, routing, and cost snapshots remain unchanged.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive reschedule request] --> B{Order exists and is RELEASED?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_RESCHEDULABLE]
+    B -->|Yes| D{Execution already started?}
+    D -->|Yes| E[Return EXECUTION_ALREADY_STARTED]
+    D -->|No| F[Validate revised dates]
+    F --> G[Persist scheduling update]
+    G --> H[Return rescheduled order]
+```
+
+## External Dependencies
+
+- None
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_RESCHEDULABLE**: The order is not in `RELEASED`.
+- **EXECUTION_ALREADY_STARTED**: Work-order execution has already begun.
+- **INVALID_DATE_RANGE**: Planned dates are missing or chronologically invalid.
+
+## Test Cases
+
+- reschedules a released order before execution starts
+- returns error when the order does not exist
+- returns error when the order is not in `RELEASED`
+- returns error when execution has already started
+- returns error when planned dates are invalid
+- preserves release snapshots after rescheduling

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

@@ -0,0 +1,44 @@
+# ResumeWorkOrder
+
+## Overview
+
+ResumeWorkOrder restarts a paused operation without losing the accumulated execution history recorded before the interruption.
+
+## Business Rules
+
+- Target work order must exist.
+- Work order must be in `PAUSED`.
+- Parent production order must still be execution-capable.
+- Resuming preserves previously reported quantity, scrap, and time.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive resume request] --> B{Work order exists?}
+    B -->|No| C[Return WORK_ORDER_NOT_FOUND]
+    B -->|Yes| D{Status is PAUSED?}
+    D -->|No| E[Return WORK_ORDER_NOT_RESUMABLE]
+    D -->|Yes| F{Parent order executable?}
+    F -->|No| G[Return PARENT_ORDER_NOT_EXECUTABLE]
+    F -->|Yes| H[Record resume event and set IN_PROGRESS]
+    H --> I[Return resumed work order]
+```
+
+## External Dependencies
+
+- [ProductionOrder](../models/ProductionOrder.md) - Parent production order must still allow execution.
+
+## Error Scenarios
+
+- **WORK_ORDER_NOT_FOUND**: Target work order does not exist.
+- **WORK_ORDER_NOT_RESUMABLE**: Work order is not in `PAUSED`.
+- **PARENT_ORDER_NOT_EXECUTABLE**: Parent production order does not allow execution.
+
+## Test Cases
+
+- resumes a paused work order
+- returns error when the work order does not exist
+- returns error when the work order is not paused
+- returns error when the parent production order no longer allows execution
+- preserves prior execution history after resume

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

@@ -0,0 +1,52 @@
+# ReviewManufacturingCostSummary
+
+## Overview
+
+ReviewManufacturingCostSummary recalculates the final planned-versus-actual result for a technically complete order and freezes the variance classification through an explicit reviewer approval step.
+
+## Business Rules
+
+- Target cost summary must exist and be in `PENDING_VARIANCE_REVIEW`.
+- Parent production order must already be `TECHNICALLY_COMPLETE`.
+- Final variance must be recalculated against the frozen release baseline.
+- Review must preserve the named variance taxonomy: `MATERIAL_PRICE`, `MATERIAL_USAGE`, `LABOR_RATE`, `LABOR_EFFICIENCY`, `MACHINE_RATE`, `MACHINE_EFFICIENCY`, `SCRAP`, and `YIELD`.
+- Reviewer identity is required.
+- Approved review freezes the variance breakdown until the order is reopened.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive review request] --> B{Summary exists and is pending review?}
+    B -->|No| C[Return COST_SUMMARY_NOT_REVIEWABLE]
+    B -->|Yes| D[Recalculate final variances across the named taxonomy]
+    D --> E{All required categories supported?}
+    E -->|No| F[Return INCOMPLETE_VARIANCE_BREAKDOWN]
+    E -->|Yes| G{Reviewer provided?}
+    G -->|No| H[Return REVIEWER_REQUIRED]
+    G -->|Yes| I[Freeze variance lines and set VARIANCE_REVIEWED]
+    I --> J[Return reviewed summary]
+```
+
+## External Dependencies
+
+- [ProductionOrder](../models/ProductionOrder.md) - Parent order must already be technically complete before review.
+
+## Error Scenarios
+
+- **COST_SUMMARY_NOT_FOUND**: Target cost summary does not exist.
+- **COST_SUMMARY_NOT_REVIEWABLE**: Summary is not in `PENDING_VARIANCE_REVIEW`.
+- **PARENT_ORDER_NOT_TECHNICALLY_COMPLETE**: Parent production order is not ready for review.
+- **INCOMPLETE_VARIANCE_BREAKDOWN**: The review result cannot represent the full named variance taxonomy required by the feature.
+- **REVIEWER_REQUIRED**: Reviewer identity was not provided.
+- **VARIANCE_CALCULATION_FAILED**: Final variance could not be recalculated consistently.
+
+## Test Cases
+
+- reviews a pending cost summary and freezes the variance breakdown
+- returns error when the summary does not exist
+- returns error when the summary is not pending review
+- returns error when the parent order is not technically complete
+- returns error when the review result cannot represent all required variance types
+- returns error when reviewer identity is missing
+- keeps all required variance types distinct during review

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

@@ -0,0 +1,46 @@
+# StartWorkOrder
+
+## Overview
+
+StartWorkOrder begins execution on one released operation. It records the actual start signal and moves the work order into `IN_PROGRESS` so later reporting can accumulate quantities and time.
+
+## Business Rules
+
+- Target work order must exist.
+- Work order must be in `PENDING`.
+- Parent production order must be in an execution-capable state.
+- Required predecessor operations must already satisfy sequencing policy.
+- Starting the work order records the actual start timestamp.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive start request] --> B{Work order exists?}
+    B -->|No| C[Return WORK_ORDER_NOT_FOUND]
+    B -->|Yes| D{Status is PENDING?}
+    D -->|No| E[Return WORK_ORDER_NOT_STARTABLE]
+    D -->|Yes| F{Parent order and sequence ready?}
+    F -->|No| G[Return OPERATION_SEQUENCE_BLOCKED]
+    F -->|Yes| H[Record actual start and set IN_PROGRESS]
+    H --> I[Return started work order]
+```
+
+## External Dependencies
+
+- [ProductionOrder](../models/ProductionOrder.md) - Parent production order must still allow execution.
+
+## Error Scenarios
+
+- **WORK_ORDER_NOT_FOUND**: Target work order does not exist.
+- **WORK_ORDER_NOT_STARTABLE**: Work order is not in `PENDING`.
+- **PARENT_ORDER_NOT_EXECUTABLE**: Parent production order does not allow execution.
+- **OPERATION_SEQUENCE_BLOCKED**: Required predecessor work is not yet complete.
+
+## Test Cases
+
+- starts a pending work order
+- returns error when the work order does not exist
+- returns error when the work order is not pending
+- returns error when the parent production order is not executable
+- returns error when required predecessor work is incomplete

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

@@ -0,0 +1,51 @@
+# TechnicallyCompleteProductionOrder
+
+## Overview
+
+TechnicallyCompleteProductionOrder freezes the production order after physical completion and moves the linked manufacturing cost summary into variance review. It marks the point where no more normal execution or rescheduling is expected.
+
+## Business Rules
+
+- Target order must exist and be in `COMPLETED`.
+- No additional execution, rescheduling, or material issue may still be expected.
+- Open execution exceptions must be resolved before technical completion.
+- Pending material issue requests or unresolved backflush issue intents must be cleared before technical completion.
+- Technical completion moves the linked manufacturing cost summary to `PENDING_VARIANCE_REVIEW`.
+- Further shop-floor reporting is blocked until a controlled reopen occurs.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive technical-complete request] --> B{Order exists and is COMPLETED?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_TECHNICALLY_COMPLETABLE]
+    B -->|Yes| D{Open execution exceptions remain?}
+    D -->|Yes| E[Return EXECUTION_EXCEPTION_REMAINS]
+    D -->|No| F{Pending material issue requests remain?}
+    F -->|Yes| G[Return PENDING_MATERIAL_ISSUE_REQUESTS]
+    F -->|No| H[Move cost summary to PENDING_VARIANCE_REVIEW]
+    H --> I[Set order status to TECHNICALLY_COMPLETE]
+    I --> J[Return technically complete order]
+```
+
+## External Dependencies
+
+- [ManufacturingCostSummary](../models/ManufacturingCostSummary.md) - Technical completion opens variance review on the linked summary.
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_TECHNICALLY_COMPLETABLE**: The order is not in `COMPLETED`.
+- **EXECUTION_EXCEPTION_REMAINS**: Unresolved execution exceptions still exist.
+- **PENDING_MATERIAL_ISSUE_REQUESTS**: Material issue requests or backflush intents are still unresolved for the order.
+- **COST_SUMMARY_NOT_READY**: The linked cost summary cannot move to review.
+
+## Test Cases
+
+- technically completes a completed order and opens variance review
+- returns error when the order does not exist
+- returns error when the order is not in `COMPLETED`
+- returns error when unresolved execution exceptions remain
+- returns error when pending material issue requests or unresolved backflush intents remain
+- returns error when the linked cost summary is not ready for review
+- blocks further shop-floor reporting after technical completion

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

@@ -0,0 +1,46 @@
+# UnreleaseProductionOrder
+
+## Overview
+
+UnreleaseProductionOrder returns a released order to `DRAFT` when execution has not meaningfully started. It removes the executable release artifacts so the planner can safely revise the order.
+
+## Business Rules
+
+- Target order must exist and be in `RELEASED`.
+- No work order may have started or received execution evidence.
+- No irreversible inventory handoff may exist for the order.
+- Unrelease removes or supersedes work orders, material requirements, and the unrevised release snapshot.
+- Orders with actual material or execution evidence must use controlled reopening instead of unrelease.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive unrelease request] --> B{Order exists and is RELEASED?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_UNRELEASABLE]
+    B -->|Yes| D{Any execution or inventory evidence?}
+    D -->|Yes| E[Return EXECUTION_ALREADY_STARTED]
+    D -->|No| F[Remove release artifacts]
+    F --> G[Set status to DRAFT]
+    G --> H[Return draft order]
+```
+
+## External Dependencies
+
+- [WorkOrder](../models/WorkOrder.md) - Unrelease is blocked once execution evidence exists on any child work order.
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_UNRELEASABLE**: The order is not in `RELEASED`.
+- **EXECUTION_ALREADY_STARTED**: A work order already has execution evidence.
+- **INVENTORY_HANDOFF_EXISTS**: Inventory-facing material or receipt evidence already exists.
+
+## Test Cases
+
+- unreleases a released order with no execution evidence
+- returns error when the order does not exist
+- returns error when the order is not in `RELEASED`
+- returns error when a work order has already started
+- returns error when inventory handoff evidence already exists
+- removes work orders and material requirements when unrelease succeeds

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

@@ -0,0 +1,48 @@
+# UpdateBillOfMaterial
+
+## Overview
+
+UpdateBillOfMaterial revises mutable draft BOM content before activation. It supports changes to effectivity, default flags, `bomType`, and component lines while preserving released production-order snapshots.
+
+## Business Rules
+
+- Target BOM must exist.
+- Only `DRAFT` BOM versions are mutable through this command.
+- Updated component lines must still satisfy positive quantity and unit compatibility rules.
+- Inactive items cannot be introduced as new components.
+- Changing effectivity or default selection must not create an ambiguous active-selection plan once activated.
+- Updating a draft BOM must not alter any production-order snapshot already taken from another version.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive update request] --> B{BOM exists?}
+    B -->|No| C[Return BOM_NOT_FOUND]
+    B -->|Yes| D{Status is DRAFT?}
+    D -->|No| E[Return BOM_NOT_MUTABLE]
+    D -->|Yes| F[Validate revised fields and lines]
+    F --> G[Persist updated draft]
+    G --> H[Return updated BOM]
+```
+
+## External Dependencies
+
+- [Item](../../../item-management/docs/models/Item.md) - Any newly referenced component item must remain valid.
+
+## Error Scenarios
+
+- **BOM_NOT_FOUND**: Target BOM does not exist.
+- **BOM_NOT_MUTABLE**: The BOM is not in `DRAFT`.
+- **INVALID_COMPONENT_QUANTITY**: A revised component quantity is zero or negative.
+- **COMPONENT_ITEM_INACTIVE**: A new component references an inactive item.
+- **AMBIGUOUS_EFFECTIVITY_RULE**: Revised effectivity or default flags would create ambiguous selection behavior.
+
+## Test Cases
+
+- updates draft BOM metadata and component lines
+- returns error when the BOM does not exist
+- returns error when the BOM is not in `DRAFT`
+- returns error when a revised component quantity is invalid
+- returns error when a newly referenced component is inactive
+- returns error when effectivity changes would create ambiguous selection

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

@@ -0,0 +1,48 @@
+# UpdateProductionOrder
+
+## Overview
+
+UpdateProductionOrder revises mutable draft planning fields such as dates, quantity, and preferred BOM or routing before release freezes execution assumptions.
+
+## Business Rules
+
+- Target production order must exist.
+- Only `DRAFT` orders are mutable through this command.
+- Planned quantity must remain greater than zero.
+- Produced item, company, and site identity are immutable after creation.
+- Optional BOM or routing references must remain within the same company and site scope.
+- Updating a draft order does not create work orders or cost baselines.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive update request] --> B{Order exists?}
+    B -->|No| C[Return PRODUCTION_ORDER_NOT_FOUND]
+    B -->|Yes| D{Status is DRAFT?}
+    D -->|No| E[Return PRODUCTION_ORDER_NOT_MUTABLE]
+    D -->|Yes| F[Validate revised planning fields]
+    F --> G[Persist draft changes]
+    G --> H[Return updated order]
+```
+
+## External Dependencies
+
+- None
+
+## Error Scenarios
+
+- **PRODUCTION_ORDER_NOT_FOUND**: Target order does not exist.
+- **PRODUCTION_ORDER_NOT_MUTABLE**: The order is not in `DRAFT`.
+- **INVALID_PLANNED_QUANTITY**: Planned quantity is zero or negative.
+- **IMMUTABLE_SCOPE_FIELD**: The request attempts to change produced item or company or site identity.
+- **CROSS_SCOPE_MASTER_REFERENCE**: BOM or routing reference belongs to another company or site.
+
+## Test Cases
+
+- updates draft planning fields on a production order
+- returns error when the order does not exist
+- returns error when the order is not in `DRAFT`
+- returns error when planned quantity is not positive
+- returns error when immutable scope identity is changed
+- returns error when BOM or routing references are out of scope

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

@@ -0,0 +1,52 @@
+# UpdateRouting
+
+## Overview
+
+UpdateRouting revises mutable draft routing content before activation. It supports operation resequencing, instruction changes, and work-center reassignment while preserving snapshots already frozen on released production orders.
+
+## Business Rules
+
+- Target routing must exist.
+- Only `DRAFT` routings are mutable through this command.
+- Revised operation sequence numbers must remain unique.
+- Revised standard times must be zero or greater.
+- Every referenced work center must exist in the same company scope.
+- Updating a routing never mutates operation snapshots already copied onto released work orders.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive update request] --> B{Routing exists?}
+    B -->|No| C[Return ROUTING_NOT_FOUND]
+    B -->|Yes| D{Status is DRAFT?}
+    D -->|No| E[Return ROUTING_NOT_MUTABLE]
+    D -->|Yes| F[Validate revised operations]
+    F --> G[Persist draft changes]
+    G --> H[Return updated routing]
+```
+
+## External Dependencies
+
+- [Item](../../../item-management/docs/models/Item.md) - The routing remains scoped to one manufactured parent item.
+- [WorkCenter](../models/WorkCenter.md) - Revised operations must continue to reference valid work centers.
+
+## Error Scenarios
+
+- **ROUTING_NOT_FOUND**: Target routing does not exist.
+- **ROUTING_NOT_MUTABLE**: The routing is not in `DRAFT`.
+- **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
+
+- updates draft routing operations
+- returns error when the routing does not exist
+- returns error when the routing is not in DRAFT
+- returns error when revised sequence numbers conflict
+- returns error when a revised standard time is negative
+- returns error when a referenced work center does not exist
+- returns error when a referenced work center is outside the routing company
+- preserves released routing snapshots after update

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

@@ -0,0 +1,48 @@
+# UpdateWorkCenter
+
+## Overview
+
+UpdateWorkCenter revises mutable work-center master data such as capacity, calendar, rate assumptions, and overhead policy. The command keeps existing production-order cost snapshots immutable even when active master data changes.
+
+## Business Rules
+
+- Target work center must exist.
+- Draft and active work centers may be updated.
+- Scope identity and unique code remain immutable after creation.
+- Capacity must remain positive.
+- Labor and machine rates must be zero or greater.
+- Fixed-amount overhead requires a currency.
+- Updates do not retroactively change released production-order baselines.
+
+## Process Flow
+
+```mermaid
+flowchart TD
+    A[Receive update request] --> B{Work center exists?}
+    B -->|No| C[Return WORK_CENTER_NOT_FOUND]
+    B -->|Yes| D[Validate mutable fields]
+    D --> E[Persist work center changes]
+    E --> F[Return updated work center]
+```
+
+## External Dependencies
+
+- None
+
+## Error Scenarios
+
+- **WORK_CENTER_NOT_FOUND**: Target work center does not exist.
+- **IMMUTABLE_SCOPE_FIELD**: The request attempts to change immutable scope or code fields.
+- **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
+
+- updates an active work center without changing scope identity
+- returns error when the work center does not exist
+- returns error when immutable scope fields are changed
+- returns error when capacity is not positive
+- returns error when a rate is negative
+- preserves released cost baselines after update