{
  "title": "Telecom reseller wholesale order records for AI",
  "source_page": "https://fiund.com/industries/telecom-reseller-wholesale-order-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A reseller acknowledgment is not an upstream carrier confirmation",
    "context": "Two invented orders share a plan name but have distinct parties and version references. No real customer, tariff, provisioning process or network information appears.",
    "records": [
      [
        "TW1",
        "Practice order O1",
        "Reseller acknowledges plan Cedar revision V1. Carrier confirmation explicitly names O1/V1 and service attribute A."
      ],
      [
        "TW2",
        "Practice order O2",
        "Reseller acknowledges Cedar V1; no matching carrier confirmation supplied."
      ],
      [
        "TW3",
        "Later offer revision",
        "Cedar V2 advertises attribute B. No O1 or O2 amendment, acceptance or upstream revision names V2."
      ]
    ],
    "question": "Which order has upstream confirmation, and can the later offer establish changed service attributes or confirmation for O2?",
    "answer": "TW1 supplies both reseller acknowledgment and carrier confirmation for O1/V1 with attribute A. TW2 supplies only the reseller's acknowledgment for O2. TW3 changes the available offer, not either named order, and does not establish carrier confirmation or attribute B for them. Preserve reporting party, order identity and offer version rather than treating a shared plan name as a shared fulfilled state.",
    "failureModes": [
      "Copying O1's carrier confirmation to O2 because their plan names match.",
      "Updating an existing order from a later promotional offer without an order amendment."
    ],
    "fields": [
      [
        "Order and party",
        "Identifies who reported each status."
      ],
      [
        "Offer revision versus order revision",
        "Separates catalog changes from accepted transaction terms."
      ],
      [
        "Upstream confirmation reference",
        "Preserves the specific carrier-to-order link."
      ]
    ],
    "holdout": "Add carrier confirmation for O2/V2 while the reseller order still says V1. Require a version conflict rather than a simple confirmed badge.",
    "boundary": "Use fabricated orders and labels. Exclude customer data, actual order numbers, private rates, carrier tariffs, provisioning details and network configurations."
  }
}