START WITH THE PRODUCT STEPS Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration. S19: Turn scattered software symptoms into a sanitized support case Starter kit Status: Proposed / not tested PURPOSE Repeated software issue or unresolved support exchange → structure already-observed behavior, known environment differences and safe reproduction steps → human-reviewed support-case draft with evidence inventory and unanswered questions. PREREQUISITES 1. Staff-supplied product/version, OS/browser version, timestamp/timezone, expected versus actual behavior, reproducibility frequency, last-known-good date, exact error text and sanitized screenshot IDs. Capture only a synthetic test record in a nonproduction setting when authorized; otherwise describe historical steps without reproducing them. Do not capture client names, desktop notifications, tokens or unrelated windows. 2. Synthetic files first. Real use requires firm-approved access, privacy, processing terms, retention controls, export coverage and a named reviewer. 3. Prepare any required original files or rendered evidence separately. This kit does not configure accounts, connectors or live actions. FILES AND FORMATS incidents.csv: incident_id, product, product_version, os_version, browser_version, observed_at, timezone, expected_behavior, actual_behavior, observed_steps, frequency, last_known_good, exact_error, screenshot_ids, source_ref evidence.csv: evidence_id, incident_id, evidence_type, sanitized_description, source_ref, privacy_review_status scope.txt: historical-only reproduction boundary and approved support recipient for later review Files without .example are blank input worksheets; CSV templates contain headers only. .example files contain invented records for the dry run. Text input .txt files contain blank labeled fields. Use the original base filename when supplying an example to the prompt, or explicitly map the example filename to that input. CSV files are UTF-8 with comma delimiters, quoted fields where needed, and CRLF row endings. Preserve identifiers as text when importing into Excel. Blank means missing or unresolved, never a zero or a pass. Multi-value fields use a pipe only where the fixture scope says so. SETUP AND DRY RUN 1. Copy this kit to an approved working folder. Keep examples separate from any real exports. Do not upload client, privileged, personal, credential or financial-account data to an unapproved service. 2. Read the .example text policy/scope files and all .example.csv inputs together. They define this fixture only. For a real pilot, fill the blank templates from approved exports without changing headers and obtain approved policy values. 3. Use native read-only exports, exact joins and arithmetic for deterministic checks. This kit includes no executable automation, OAuth setup, live-action instructions or importable Make blueprint. 4. Give only the approved prepared inputs to a firm-approved text assistant and use the recipe prompt below. Keep source IDs, source row numbers and unresolved evidence visible. 5. Compare the proposed result with expected-fixture-result.txt. Verify every listed issue and that the prompt invents no missing evidence. The expected file describes assertions, not a performed workflow run. 6. Have the named reviewer check source evidence and record remaining questions before any separately authorized action. RECIPE PROMPT Turn these sanitized incident notes into a support-case draft: environment, expected behavior, actual behavior, observed steps, frequency, first/last occurrence, source evidence and questions. Separate observations from hypotheses and do not fill missing details. Describe any requested reproduction using synthetic data only; do not execute it. Do not include credentials, client information, raw network logs or unrestricted screenshots. Do not contact support or change settings. INPUTS incidents.csv: incident_id, product, product_version, os_version, browser_version, observed_at, timezone, expected_behavior, actual_behavior, observed_steps, frequency, last_known_good, exact_error, screenshot_ids, source_ref evidence.csv: evidence_id, incident_id, evidence_type, sanitized_description, source_ref, privacy_review_status; scope.txt: historical-only reproduction boundary and approved support recipient for later review OUTPUT support-case.txt: product/environment, observed steps, expected and actual behavior, exact error, evidence references, contradictions and unanswered questions. No live reproduction, attachment review or vendor submission is implied. Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. REVIEW CHECKLIST [ ] Headers match the exact input schema and the export covers the stated scope [ ] Synthetic example files were used alone for the first dry run [ ] Every output finding retains its original source ID/row/page reference [ ] Missing keys, contradictions, unavailable originals and ambiguous dates remain unresolved [ ] Every expected fixture finding is present; no live action or unsupported result is claimed [ ] Responsible reviewer checks the original records before a real deployment RECIPE-SPECIFIC REVIEW Staff/IT verifies every fact and examines each attachment before deciding what can be shared with the verified vendor. Test two different products with similar names and a screenshot that contradicts the narrative. No automatic upload or external send. VALIDATION Exact CSV header order, field counts, serialized round-trip values and fixture semantics were checked during kit preparation. This does not test OCR, a vendor integration, a model response or end-to-end reliability. All data and identifiers are synthetic. Dates are fixed fixture dates, not current monitoring results.