EV_PRODUCT_006 — Cross-order manufacturing cost comparison surface and costing-strategy scope

Deployment-specific product evidence for the cross-order manufacturing cost comparison surface. It establishes which quantity, cost, scrap, and status fields exist, which cross-order columns the pivoting table exposes, and how the module-level costing strategy bounds comparability. It does not establish a customer result, an executed comparison, or applicability to a specific vertical.

kind: evidence_catalog
schema_version: 1
evidence:
  - id: EV_PRODUCT_006
    type: internal_validation
    title: 'Cross-order manufacturing cost comparison surface and costing-strategy scope'
    source: >-
      MCP server d8189168 project_graph, flow_documents, and hook_graph responses
      captured during the create-proof authoring session on 2026-08-02, together
      with the structured authoring answers given in that session.
    publisher_or_owner: >-
      Naologic product repository via MCP server d8189168; authoring answers by
      Gabriel Paunescu
    published_at: null
    accessed_at: 2026-08-02
    supports:
      - >-
        manufacturing/order stores document-level orderedQuantity,
        quantityCompleted, plannedCost, totalCost, estimatedTotalCost,
        costOfScrap, overproductionQuantity, and itemId.
      - >-
        manufacturing/order.data.status has the values draft, open, in-progress,
        completed, and canceled, so completed historical runs can be isolated.
      - >-
        manufacturing/order classifies planned-versus-actual material usage per
        actual bill-of-material line through the Consumption Variance Type
        datatype, whose values are overused, underused, extra, matched, and
        unplanned.
      - >-
        The Manufacturing orders table with pivoting exposes order number, sales
        order, account, warehouse, item name, status, produced quantity, quantity
        remaining, overproduction, total quantity, packaged quantity, order date,
        scrap rate, cost per unit, total cost, planned cost, planned cost per
        unit, and raw material cost as columns of one cross-order view.
      - >-
        manufacturing/settings exposes one Manufacturing Costing Strategy
        datatype with six values: standard-cost-estimate,
        standard-cost-of-raw-materials,
        weighted-average-cost-of-raw-materials-by-warehouse,
        standard-cost-estimate-with-scrap,
        standard-cost-of-raw-materials-with-scrap, and
        weighted-average-cost-with-scrap. The setting is module-level, not per
        manufacturing order.
      - >-
        The manufacturing-order cost calculation resets every cost accumulator to
        zero and rebuilds from production reports, work orders, and time tickets
        on each run. Its stated rules are that the costing strategy from
        manufacturing settings controls the cost-per-unit formula and that a zero
        variant cost rejects the calculation.
      - >-
        The manufacturing-reports hook collection contains lead-time,
        manufacturing-order-status, production-scrap-and-yield, and
        work-center-utilization reports. No production-cost-by-run-quantity or
        batch-size comparison report was returned.
      - >-
        Searches for an inventory carrying-cost or economic-order-quantity
        implementation returned no matching hook. The nearest matches were a
        stock valuation report and a weighted-average item cost summary over
        existing stock, neither of which is an expected-stock value or a
        carrying-cost model.
    scope: 'Naologic manufacturing cost comparison and costing-strategy configuration'
    confidence: medium
    notes: >-
      Tools and queries: flow_documents list, search, datatypes, fields, and
      resolve_fields on manufacturing/order, manufacturing/settings, and
      manufacturing/productionReport; project_graph search and node on
      manufacturing/manufacturing.manufacturing-orders-table-with-pivoting;
      hook_graph search, hook, and collection on
      manufacturing-performance/compute-manufacturing-order-cost and
      manufacturing-reports. A search miss means unverified, not absent: the
      carrying-cost and batch-size misses establish that no implementation was
      found, not that none exists. No live customer data, database query, or
      deployment data was inspected. This record carries no vertical scope; it
      establishes product surfaces only.

Outstanding

1. The pivoting table's grouping was not executed. The column list was read from the project graph, not from a rendered, grouped comparison. Configuration and testing effort cannot be sized from this record.
2. No column was mapped to orderedQuantity. The verified columns include total quantity, produced quantity, and quantity. Grouping by ordered quantity must be confirmed against the manufacturing order itself.
3. This record carries no vertical scope. Any proof that cites it for directly applicable verticals must state that basis explicitly rather than inherit vertical breadth from product universality.