{
  "fixtureVersion": "2026-07-26.2",
  "synthetic": true,
  "license": "CC0-1.0",
  "inputs": {
    "marketing_launch_announcement": "Product: API Cost Dashboard\nAudience: engineering leaders evaluating infrastructure spend\nApproved facts:\n- Breaks API spend down by model and environment.\n- Supports CSV export.\n- Supports saved filters.\n- Launch date: July 30.\nProhibited claims: customer adoption, savings percentages, and performance improvements.\nRequired CTA: Open the dashboard.",
    "coding_scoped_bug_fix": "Repository: prompt-lab-date-fixture-v1\nAllowed files:\n- src/formatDate.js\n- tests/formatDate.test.js\n\nsrc/formatDate.js\n```js\nexport function formatDate(value) {\n  return new Date(value).toLocaleDateString('en-CA')\n}\n```\n\ntests/formatDate.test.js\n```js\nimport { strict as assert } from 'node:assert'\nimport { formatDate } from '../src/formatDate.js'\n\nprocess.env.TZ = 'America/Vancouver'\nassert.equal(formatDate('2026-07-30'), '2026-07-30')\n```\n\nVerification: npm test; npm run lint.",
    "coding_json_export": "Repository: prompt-lab-export-fixture-v1\nExisting contract: CSV export remains the default and keeps the filename report.csv.\nNew contract: add an explicit JSON option that exports only visible filtered rows; serialize dates as ISO 8601 strings.\nRelevant module:\n```js\nexport function exportReport(rows, format = 'csv') {\n  return downloadCsv(rows, 'report.csv')\n}\n```\nVerification: npm test; npm run lint; npm run build.",
    "extraction_invoice_json": "Required JSON keys, in this order:\n- invoice_number\n- invoice_date\n- currency\n- subtotal\n- tax\n- total\nDo not return any other key.\n\nNORTHSTAR OFFICE SUPPLY\nInvoice: NS-1042\nInvoice date: 2026-07-18\nCurrency: CAD\nSubtotal: 1250.00\nTax: 162.50\nTotal: 1412.50\nPayment terms: Net 30",
    "extraction_support_routing": "Return one JSON object with exactly these keys: label, evidence, confidence.\nAllowed labels: billing, bug, feature_request, account_access, unknown.\nAllowed confidence values: low, medium, high.\nThe evidence value must quote the ticket.\n\nTicket #014\nSubject: Cannot sign in after changing phones\nMessage: I replaced my phone yesterday and no longer have the authenticator app. The password reset works, but the verification code still goes to the old device. Please help me regain access.",
    "data_weekly_conversion": "week,sessions,conversions\n2026-06-29,1000,80\n2026-07-06,1200,84\n2026-07-13,900,81\n2026-07-20,1500,105",
    "data_anomaly_summary": "Minimum volume: 1,000 requests. Exclude rows below this threshold from anomaly findings.\n\nservice,region,day,request_count,p50_ms,p95_ms\napi,ca-central,2026-07-20,14000,82,210\napi,ca-central,2026-07-21,15000,85,460\napi,us-east,2026-07-21,18000,75,205\nworker,ca-central,2026-07-21,600,120,900\nworker,us-east,2026-07-21,4200,118,310",
    "research_provider_comparison": "[A: Data retention]\nProvider A retains API inputs and outputs for 30 days for abuse monitoring. Approved enterprise accounts can request zero retention.\n[A: Training use]\nAPI data is not used for model training by default.\n[A: Regional processing]\nRegional processing is available in the United States and European Union.\n[A: Enterprise controls]\nEnterprise administrators can set retention policy and audit-log access.\n\n[B: Data retention]\nProvider B retains API inputs and outputs for 7 days. Zero retention is unavailable for the standard plan.\n[B: Training use]\nAPI data is not used for training unless the customer opts in.\n[B: Regional processing]\nThe policy does not state where API processing occurs.\n[B: Enterprise controls]\nEnterprise accounts include audit logs; the policy does not describe administrator-set retention.",
    "research_evidence_table": "[Study A]\nPopulation: 95 professional developers.\nTask: implement a small HTTP service.\nComparison: coding assistant available versus unavailable.\nOutcome: median completion time.\nResult: the assistant group finished 18% faster.\nLimitation: one language and one bounded task.\n\n[Study B]\nPopulation: 42 computer-science students.\nTask: repair five seeded bugs.\nComparison: assistant available versus documentation only.\nOutcome: bugs repaired within 60 minutes.\nResult: 3.1 versus 2.8 bugs on average.\nLimitation: student sample and short time box.\n\n[Study C]\nPopulation: 310 pull requests from one company.\nTask: routine maintenance work.\nComparison: before versus after assistant rollout.\nOutcome: review-cycle duration.\nResult: no statistically clear change.\nLimitation: observational design and concurrent process changes.",
    "writing_executive_summary": "Incident: checkout availability degradation\nCustomer impact: 14% of checkout attempts failed in Canada.\nDuration: 47 minutes, from 14:08 to 14:55 UTC on July 22.\nConfirmed cause: a cache configuration deployed at 14:05 routed a subset of requests to stale inventory records.\nOpen question: the team has not confirmed why the pre-deploy canary missed the stale-record path.\nMitigation: configuration rolled back; stale records flushed; checkout error rate returned to baseline.\nNext decision: approve or reject a mandatory stale-record canary before the next cache configuration release.",
    "writing_localized_release_note": "## Saved billing filters\n\n`{{workspace_name}}` can now save billing filters in BenchLM Stats and reuse them in CSV exports.\n\nReview the filters at [Billing settings]({{billing_url}}).",
    "operations_meeting_actions": "Product launch meeting — July 24\n\nMaya will update the launch checklist by July 28.\nThe team agreed to test the CSV export on a large account, but no owner or date was assigned.\nOwen will ask legal to review the claims language. The notes do not set a due date.\nDecision: keep the dashboard launch on July 30."
  }
}