S_00007 — Targeted schedule edits with explicit reflow

This solution addresses P_00008; the problem owns the forward reference in its ordered solutionsIds array.

kind: solution_catalog
schema_version: 1
solutions:
  - id: S_00007
    proofIds: []
    priority: 45
    name: 'Targeted schedule edits with explicit reflow'
    status: approved
    mechanism: >-
      Represent the production schedule as work orders with recorded work
      centers and planned start and end dates on a timeline. Let staff revise an
      individual work order through an Edit and Save path that recalculates the
      work order and pushes overlapping work forward, while reserving
      recalculation of the full active schedule for a separate explicit reflow
      action. An ordinary targeted edit therefore does not automatically invoke
      the distinct full-schedule reflow hook.
    capabilities:
      - name: 'Review work orders on a production-schedule timeline'
        classification: native
        conditions:
          - 'Work orders, work centers, planned dates, and statuses must be recorded and current.'
          - 'The timeline reflects the records returned by its configured searches and filters.'
        evidence_ids: []
      - name: "Edit a work order's assigned work center and planned dates"
        classification: native
        conditions:
          - 'The work order and its related manufacturing records must resolve.'
          - 'The save path executes synchronously; response time under representative load has not been verified.'
        evidence_ids: []
      - name: 'Check schedule overlaps and push conflicting work forward during an edit'
        classification: native
        conditions:
          - 'The affected work orders must contain usable planned dates and work-center assignments.'
          - 'The synchronous workload can grow with the number of overlapping work orders.'
          - 'Concurrent-edit and locking behavior has not been verified.'
        evidence_ids: []
      - name: 'Recalculate the active schedule through an explicit reflow action'
        classification: native
        conditions:
          - 'Work-center capacity, calendars, dependencies, blocked periods, and active-work status must be maintained.'
          - 'The reflow hook executes synchronously and may update multiple work orders.'
          - "Runtime at the customer's schedule size and concurrent-user load must be tested before recommendation."
        evidence_ids: []
    expected_outcome_hypotheses:
      - >-
        Staff can revise a representative individual work order without
        automatically invoking the separate full-active-schedule reflow hook.
      - >-
        Overlapping scheduled work can be moved forward through the targeted
        update path rather than requiring manual correction of every affected
        record.
      - >-
        The application can maintain acceptable interactive response times
        during representative schedule-entry volume and concurrency.
    limitations:
      - >-
        MCP establishes the execution paths but provides no latency,
        throughput, database-locking, or concurrent-user measurements. It does
        not establish that the reported stall is solved.
      - >-
        The targeted update hook is synchronous, recalculates derived work-order
        data, and can cascade through overlapping work orders. A targeted edit
        is therefore not necessarily a bounded or lightweight operation.
      - >-
        The full-schedule reflow hook is also synchronous and reads and updates
        active schedule records. The interface may wait while it runs.
      - >-
        The incumbent application's failure mode has not been diagnosed, so
        this mechanism must not be presented as correcting a known database,
        network, code, or vendor defect.
      - >-
        Schedule behavior depends on current work-center, date, dependency,
        calendar, and status data.
    prohibited_claims:
      - 'That schedule entry cannot stall in this implementation.'
      - 'That targeted work-order updates always complete within a particular response time.'
      - 'That schedule edits are constant-time or cannot cascade through other work orders.'
      - 'That the synchronous reflow action remains interactive at any schedule size.'
      - 'That the incumbent database, network, application code, or vendor causes the reported stall.'
      - 'That schedule data is lost or corrupted.'
      - 'Any quantified productivity, downtime, throughput, or performance improvement.'