EV_PRODUCT_005 — Manufacturing work-order reflow action, data model, and scheduling boundaries
Deployment-specific product evidence for the manufacturing work-order timeline and explicit active-schedule reflow path. It establishes inspectable product structure and scheduling behavior, not a live customer execution, buyer acceptance, runtime performance, or quantified outcome.
kind: evidence_catalog
schema_version: 1
evidence:
- id: EV_PRODUCT_005
type: internal_validation
title: 'Manufacturing work-order reflow action, data model, and scheduling boundaries'
source: >-
MCP server d8189168 project_graph, flow_documents, and hook_graph
responses captured during the Codex readiness review for P_00006,
S_00005, and PF_MULTI_003 on 2026-08-01.
publisher_or_owner: 'Naologic product repository via MCP server d8189168'
published_at: null
accessed_at: 2026-08-01
supports:
- >-
The Work Order Timeline exposes Work Order Number, Status, Work Center,
Start date, Details, Edit, and a separate Reflow Work Orders action.
Reflow Work Orders invokes manufacturing/manufacturing.reflow-work-orders,
which triggers manufacturing/recalculate-work-order-production-schedule.
- >-
Work orders store data.workOrderNumber, data.manufacturingOrderId,
data.workCenterId, data.plannedStartDate, data.plannedEndDate,
data.workOrderDependencyIds, and data.status. The parent and work-center
fields resolve respectively to manufacturing/order and
manufacturing/workCenter. Current dependency storage is the
workOrderDependencyIds array; workOrderDependencyId is deprecated.
- >-
Work-order statuses include draft, open, in-progress, completed,
scheduling, and maintenance. Open means no time has been logged;
in-progress means time has been logged. The reflow implementation locks
in-progress and maintenance work orders instead of treating them as
movable work.
- >-
Manufacturing orders store data.manufacturingOrderDate and
data.productionDueDate. The reflow implementation bases dependency-free
forward scheduling on data.manufacturingOrderDate, falling back to the
current date when that date is in the past. No data.requiredDate field
exists on manufacturing/workOrder.
- >-
The reflow hook builds dependencies from workOrderDependencyIds,
calculates a dependency-aware scheduling order, and forward-schedules
movable work into work-center time slots while accounting for occupied
capacity, working periods, holidays, and maintenance windows. Its
indexed implementation updates planned work-order start and end dates.
- >-
Work centers store data.availableTimeHoursPerDay,
data.outputLevels[].outputPerHour, data.outageStartDate,
data.outageEndDate, downtime reason, and status. Active centers can
receive work; downtime centers are temporarily unavailable.
- >-
Maintenance can be represented as a maintenance work order with planned
start and end dates. The maintenance-work-order creation hook rejects a
new maintenance window that overlaps existing work and asks the user to
move the conflicting work manually; creating an overlapping maintenance
block is therefore not a safe deterministic reflow-test setup step.
- >-
Direct work-order editing is a separate path: the Work Order Timeline
Edit action opens Update Work Order with Work Center, Start date, end
date, and Save fields or actions, and Save invokes
manufacturing/manufacturing.update-work-order-document. It is not the
explicit full-schedule reflow action.
- >-
The reflow implementation uses a confirmed hardcoded 24/7 default.
Tenant work-shift integration into that reflow calendar was not
established by the MCP review and must be separately verified before
relying on multi-shift or non-continuous-calendar behavior.
scope: >-
Naologic manufacturing work-order timeline, explicit active-schedule
reflow, related document fields, and scheduling implementation boundaries.
confidence: medium
notes: >-
MCP server d8189168 project_graph op=node targets included
LOGIC:manufacturing/manufacturing.work-order-timeline,
FLOW:manufacturing/manufacturing.reflow-work-orders,
PART:manufacturing/manufacturing.edit-work-order, and
FLOW:manufacturing/manufacturing.confirm-manufacturing-order. Matches
included the Reflow Work Orders runaction, the separate Edit modal and
update flow, and the confirmation flow.
flow_documents op=get, resolve_fields, field, datatypes, fields, search,
and relationships targeted manufacturing/workOrder, manufacturing/order,
manufacturing/workCenter, and manufacturing/workShift. Exact work-order
matches included data.workOrderNumber, data.manufacturingOrderId,
data.workCenterId, data.plannedStartDate, data.plannedEndDate,
data.workOrderDependencyIds, and data.status. data.requiredDate returned
an unknown-field miss; the parent manufacturing order resolved
data.productionDueDate, and the reflow code matched
data.manufacturingOrderDate. Work-center matches included available time,
output-per-hour, outage dates, downtime reasons, and status.
hook_graph op=hook targeted
manufacturing/recalculate-work-order-production-schedule and
manufacturing-ai/confirm-manufacturing-order-v4. Code-impact matches for
reflow included workOrderDependencyIds, lockedWorkOrders,
maintenanceWindows, manufacturingOrderDate, plannedStartDate,
plannedEndDate, and the hardcoded 24/7 scheduling default. The maintenance
overlap boundary was corroborated by
manufacturing-work-centers/create-maintenance-work-order-for-a-work-center.
No live execution, customer database, before-and-after schedule,
performance measurement, latency test, concurrent-user test, or buyer
result was inspected. The MCP results do not establish that every
representative reflow will change a date, that a buyer accepts the
result, or that tenant work-shift settings replace the reflow hook's 24/7
default.