EV_PRODUCT_001 — Global pricing configuration and apply path

Deployment-specific product evidence for the Backoffice Global Pricing workflow. It establishes an inspectable configuration-and-apply path, not a customer outcome or universal performance claim.

kind: evidence_catalog
schema_version: 1
evidence:
  - id: EV_PRODUCT_001
    type: internal_validation
    title: 'Global pricing configuration and apply path'
    source: >-
      MCP server d8189168 project_graph, flow_documents, and hook_graph
      responses captured during the Codex authoring task on 2026-08-01.
    publisher_or_owner: 'Naologic product repository via MCP server d8189168'
    published_at: null
    accessed_at: 2026-08-01
    supports:
      - >-
        The Backoffice Global Pricing table exposes Create global rule, Update,
        and a separate Apply row action.
      - >-
        The create and update forms expose Price Rule Name, Description, Global
        pricing strategy, Pricing strategy, Global price, and global pricing
        lines; their UI warning says creation does not apply the configuration.
      - >-
        The Global Pricing document allows weight-per-unit and unit-price
        strategies, draft and applied states, applied user and date metadata,
        and counts for items and variants applied to.
      - >-
        The Apply action triggers the synchronous price-list/apply-global-pricing
        hook, described as applying the global pricing list across all items
        referenced in the pricing list.
    scope: 'Naologic Global Pricing product workflow'
    confidence: medium
    notes: >-
      project_graph matches: price-lists/price-lists.global-pricing-table,
      create-global-pricing, update-global-pricing, and apply-global-pricing.
      flow_documents match: price-lists/globalPricing and
      PriceListsInterface.GlobalPricing. hook_graph match:
      price-list/apply-global-pricing. A hook_graph code-impact search for
      numberOfItemsAppliedTo, appliedDate, and appliedById returned no match, so
      the exact runtime writes to those fields remain unverified. MCP output does
      not establish a customer result, acceptance decision, or annual time saved.