You are a topic extraction system. Read the TEXT below and i...

Prompt

You are a topic extraction system. Read the TEXT below and identify the distinct topics it covers. Rules: - Extract 3–8 topics. Each topic is a concept, theme, or subject the text actually discusses — not every noun that appears. - Merge near-duplicates into a single topic (e.g. "pricing" and "cost" become one). - Rank topics from most to least central to the text. - Do NOT invent topics that aren't supported by the text. - Base topics only on the text provided; do not use outside knowledge. For each topic return: - label: 1–4 words, title case - relevance: a score from 0.0 to 1.0 for how central it is - evidence: a short quote (max 15 words) from the text supporting it Output ONLY valid JSON in this exact schema, nothing else: { "topics": [ { "label": "", "relevance": 0.0, "evidence": "" } ] } TEXT: """ Northwind Logistics spent most of last quarter untangling the fallout from its warehouse management upgrade. The new system was supposed to cut order processing time in half, but a misconfigured integration with the legacy inventory database meant that stock counts drifted out of sync within days of going live. Warehouse staff, many of whom had only received a single afternoon of training, began keeping their own spreadsheets as a workaround — which of course made the data problem worse. The financial impact was immediate. Expedited shipping to cover late orders added nearly €400,000 in unplanned costs, and two mid-sized retail clients quietly moved a portion of their volume to a competitor. Leadership had budgeted for a smooth cutover and hadn't set aside contingency funds, so the overrun landed awkwardly in the middle of an already tight fiscal year. What frustrated the operations team most was that the warning signs were there. A pilot run in the Rotterdam facility three months earlier had shown the same sync errors, but the report never made it past middle management. When the board finally reviewed the incident, the conversation kept circling back to how information moved — or failed to move — between the floor and the executive suite. Somewhat unexpectedly, the strongest recommendation to come out of the review had nothing to do with software: it was to rebuild the way frontline problems get escalated. """