@tailor-platform/erp-kit 0.5.1 → 0.6.0

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

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